Software Engineering - Fitness First Online Management System - Case Study Example

Table of Contents Table of Contents 1 Vision 3 1.0 Introduction 3 2.1 Positioning 4 2.2 Product Position Statement 6 3. Stakeholder Description 8 3.1 Stakeholder Summary 8 3.2 User Environment 9 4. Product Overview 10 4.1 Needs and Features 10 5. Other Product Requirements 11 Project plan 13 1.Introduction 13 2.Project Organization 14 3.Project Practices and Measurements, 15 4.Deployment 18 5.Lesson Learned 18 Work Item list 18 Glossary 22 References 26 List of Tables Problem Statement...........................................................................................................................5 Product Position Statement..............................................................................................................6 Stakeholder summary.......................................................................................................................8 Needs and features.........................................................................................................................10 Other Product Requirements..........................................................................................................11 Project milestones and objectives .................................................................................................16 Work items list.............................................................................................................................16 List of figures User Environment …………………………………….……………………………………………………………………………………………9 Abstract To enable many people be able to train on their physical fitness, dancing skills and swimming Fitness first team wants to develop an online management system. The new system will incorporate the old functions only that the services will be online, where members can book any session and purchase the desired program at anyplace anytime. Having been sponsored by the Fitness First Centre the development team was able to design a document for the new system with the following artifacts: The vision which detailed the current problem and the proposed solutions in addition to analyzing the stakeholders and the product features. The plan of the project which identifies the high-level of the project and the milestone for tasks. The list of all scheduled tasks that have to be done on time referred to as Work Items List. This document sets a stage for subsequent reports on the project. Fitness first online management system Vision 1.0 Introduction Physical fitness, dancing and swimming are aspects in every person’s life that require support and guidance to perfect and achieve the goals, it is worthy pointing out that fitness first team acknowledges that everybody is different and has different objectives and goals in the dynamic life. Sometimes to achieve those goals and objectives need assistance and support from a second party, this has been the trend with those seeking to be physically fit, trained dancer or swimmer. Currently fitness first centre uses decentralized management system with each department having records of the trainee. There is a tedious process of the management searching for records of the particular trainee to update them and ensure that the changes reflect to all other departments. In most cases trainers have fixed schedules which normally force the trainee to drop out of the program, uncertainties when they occur for instance on the trainee part the trainer may not be informed within time and if that is done. Rescheduling training session is also another problem with the current training centre. Therefore the manual system has resulted into difficulties in the updating trainee records, generating progress report, due dates of the training program and rescheduling of the training program. To address this problem a centralized system for fitness first with a web interface which manages all the departments within the centre is required. 2.1 Positioning The problems and the solutions for the current system are tabulated below Table 2.1 problem statement (Vision 2010) The problem of With the current system, each department of the fitness centre have installed their copy of the same software. This is not only cost consuming to the management but also time wasting for clients who need to come to the centre to book training session, inquiries or any updates on the training program. affects The fitness centre spent $ 700 to buy the management software and over $ 2500 for maintaining every year. The trainees have to come to the centre to be served. The impact of which is The maintenance cost is too high given that every department does its maintenance separately. Time wastage for both staff and trainees in booking scheduling of the training session plus other services. A successful solution will be The best solution will be an online management system which will centralize the activities of the fitness centre, where all the trainee records will be stored at a central location where each department can easily access. This has the following benefits: Cost-effective: centralization of data hence only one system to maintain. Time saving: trainees can select and buy training program online and schedule their training program. Fast update: updates from one department are reflected to all other departments automatically. Reduce the number of workers: because customers can buy their training product online, a single staff can handle all the booking process. Easy record search: the system will provide an easy way of searching for records by entering unique number, like trainee id number. Easy back-up: the system will enable the fitness first centre to have a quick back-up process because of data centralization; a single staff can backup information for the whole company. User friendly system: unlike the current system the new system will be more user friendly with the use of graphical interface that is not only attractive but easy to learn and use. 2.2 Product Position Statement The position of the product in the market place is illustrated below in the table. It looks at the competitive advantage over other physical fitness centre. Table 2.2 product position statement (vision 2010) For The target customers is individuals who want to be physically fit and sports clubs Who The fitness centre needs to buy it because it saves time for both staff and trainees and it saves money. The fitness first online management system Is a fitness management system. That provides Cost-effective: one system for all departments of the fitness first centre Save time: everyone can access the system online anywhere and anytime. Trainees can book training programs online. Fast update: when one department updates the items in the system the changes are immediately seen by others. Staff reduction: a task that was performed by many people like booking can be done online by the trainees themselves. Easier backup- given that data is centralized only one database is backed up. Easy search: given that all the departments will be connected, searching a file will be much easier. User friendly system: users will have a web interface that is graphically designed which makes exciting and easy to learn. Unlike Other fitness automated system. Such as Our product Provides management functionalities such managing the tasks and also scheduling training sessions for the clients. Provide automation and different categories of training groups (clubs) The system will be hosted hence online services to anyone in anytime at anywhere. 3. Stakeholder Description 3.1 Stakeholder Summary A stakeholder is anybody who will be directly or indirectly be affected by the system. The stakeholders involved in this project are listed below. The background, interest and influence the success of the project are also tabulated. Table 3.1 stakeholder summary (vision 2010) Name Description Responsibilities Fitness first The customer who requires to develop the system and also sponsor of the project This is the customer and the sponsor of the system. Therefore, they have a great influence on the project since they will be monitoring the system progress. Mohamed Abdu Is a hardworking and creative team member with good experience in software and database development He has a high influence on the project because he will help to create database, create user interface and reports. Muteb Ali Is a hardworking and creative team member with good experience in software and database development He has a high influence on the project because he will help to create database, add/update items, and generate reports. Dorcas Khan Is a hardworking and creative, team member with good experience in software and database development and web designer. She is a team member. she has a high influence on the project because he will help to create database, create user interfaces and create orders and receipts. 3.2 User Environment Figure 3.2 working process at the fitness centre Currently, there are five staffs at the help desk centre that assist in the registration of new clients to the fitness program and scheduling of the training programs. When the new system comes into play they will be reduced to two staffs because there are still customers who will come to register at the centre even if they can do it online. The above figures (fig 3.2) depict the process of purchasing a training program online which takes about 5 minutes. These include the validation of the customer’s credit card details, availability of the program and validation of the user information. There are no queues when registering because customers can do it online anywhere. The current system is running on Windows XP operating system higher versions such as Windows 7 are recommended because of their powerful functionality and features. The new system will work well with the existing environment and use the already installed printers, scanners and the software application package Microsoft Office. 4. Product Overview 4.1 Needs and Features The needs from the fitness first training centre and the features of the products are tabulated below: Table 1.4 Needs and features (vision 2010). Need Priority Features Planned Release Mange staff member’s accounts 1 Account Management 05/11/2011 Manage member’s accounts 1 Account Management 05/11/2011 Search for item 2 Basic search; advanced search Basic search: 10/11/2011 Advanced search :15/11/2011 Add new items to fitness first database 3 Add new item 17/11/2011 Update item’s information 4 Update item 2/12/2011 Make a membership registration 2 Register member 8/12/2011 General daily, monthly, annually reports; receipts 5 General reports 15/12/2011 Note: priority level from 1-5, 1 is the most import item while 5 is the least import item. 5. Other Product Requirements Table 5.1 other product requirements (vision 2010) Requirements Priority planned release Windows 7/vista, (Windows 7 our recommendation), Browser Firefox 3.5 +, Google chrome , RAM 1 GB + Microsoft SQL Server 2008 1 N/A Encryption of the passwords before adding to database 1 10/11/2011 Response time must be less than 5 sec 2 N/A Installation document 4 03/01/2012 User guide 4 O3/01/2012 Note: priority level from 1-5, 1 is the most import item while 5 is the least import item. Fitness First Online Management system Project plan 1. Introduction This section provides the deification of the project, which includes the goals and objectives of the project. Moreover, the plan will act as an agreement between the project sponsor, project manager, project team and other personnel associated with or affected by the system. Project can be defined as a set of activities that are to be undertaken to achieve specific goals and objectives the tasks are carried out under a given time frame and within a defined budget. Therefore to work on a project it needs a well defined plan because the environment keeps on changing and without a plan the project can fail. The project plan defines the following: Project organization. Project practices and measurements. Project Milestones and objectives. Deployment. Lessons learned 2. Project Organization This project is divided into several content areas with each area headed by a member who is answerable to the project leader. He/she is tasked with making sure that bugs and enhancement requests are managed and give a weekly report of the progress. The following are content areas: Task management: the team members will be allocated a task, each member will have his/her task with a timeline, weekly reports are required every Friday when the team meet to discuss on the progress. Teamwork is encouraged where any difficulty experienced a member is shared out and handled as a team. Database management: database design will be teamwork where members will discuss on the structure of the database. Then members will manage the database individually where each will have different tasks such as updating or adding sample data or deleting data etc in the specific tables. Interface design: Mohamed Abdu will be in control of the web site interface design because he has vest experience in this field. HTML/CSS pages will be developed then submitted to the team members on the basis of their role in the development process. Search for items (basic and advanced search): Muteb Ali will take over this task of search function, users of the system can search items using; trainee id, club category, training program (physical fitness, swimming or dancing). Program purchase management and receipts: Mohamed Abdu will be in charge of the member registration, buying of the training program and producing of the receipts. The functionality of this module will resemble the shopping cart. Add/Update items: Dorcas Khan Generate reports: Shakal Patel Alpha test: each member is tasked to test their tasks while developing. The parts are then integrated and tested by all members. Beta test: the system will be installed to the fitness first centre offices and tested by the entire staff in 3 weeks. 3. Project Practices and Measurements, To address the fact that we are doing content development rather than coding, OpenUp practices will be adapted by the team. The key artifacts include: project plan, and risk word document and Work item list excel file(project plan 2010). Two primary measurements using a point system are used for tracking the project progress. It is estimated that 1 point represents 2h of work (Project Plan, 2010): Project backlog: The project backlog shows progress relative to overall work to be done within the project. Iteration backlog: The iteration backlog shows progress relative to work intended for the current iteration. 1. Project Milestone and Objectives The table below shows the high-level objectivities, tasks and estimated time for each task. Table 4.1 project milestones and objectives Phase Iteration Primary objectives(risk and use case scenarios) Schedule start or milestone Target velocity Inception I1 Project acceptance Vision Statement Project Plan Work Items List Risk analysis 25 days Elaboration I2 Requirements analysis: Use case model (overview diagram; use case relationships; description of default and alternative flows for each use case; non-functional requirements for use cases, if relevant). Non-functional, use case independent requirements. Rich picture diagram including comments. Architecture for the project. Design interface. 25 days Construction I3 Home page. Add new account. Login. Basic Search Have 30% of content ready to review 13 Construction I4 Advanced search Add/Update items. Register members Have 60% of content ready to review 5 Transition I6 Finalize content. Installation Guide User guide. 2 4. Deployment N/A 5. Lesson Learned There was a good teamwork among the team members, however time for members to gather and discuss was limited. Proper time estimate for the project overly and for each task should be done by the project managers. Work Item list Fitness First Online Management System Table 1 work item list (Work item list 2010) Name or key words of description Priority  Size estimate (points) State Reference material Target iteration Assigned to (name) Hours worked Estimate of hours remaining Produce draft vision 1 2 Done < Copy of work_items_list_tpl.xls > 1 Mohamed 17 0 Produce draft glossary 1 2 Done < Copy of work_items_list_tpl.xls > 1 Muteb 17 0 Produce draft project plan 1 2 Done < Copy of work_items_list_tpl.xls > 1 Khan 17 0 Produce draft risks 1 2 Done < Copy of work_items_list_tpl.xls > 1 Mohamed 17 0 Produce draft work item list 1 2 Done < Copy of work_items_list_tpl.xls > 1 Mohamed 17 0 Finalise the vision 1 2 Done 2 Khan 17 0 Finalise glossary 1 2 Done 2 Khan 17 0 Finalize the project plan 1 2 Done 2 Muteb 17 0 Finalise risks 1 2 Done 2 Muteb 17 0 Finalise the Work Item list 1 3 Done 3 Khan 17 0 Produce the item list 1 3 New 3 Khan 0 36 Produce draft Supporting requirements 1 4 New 2 Mohamed 0 37 Produce draft Actor, Use cases and Use case model 1 2 New 2 Mohamed 0 34 Produce draft Test cases 1 3 New 2 Khan 0 32 Produce draft Architecture 1 3 New 1 Khan 0 32 Produce draft Design 1 4 New 1 Muteb 0 32 Produce draft Architectural proof of concept 1 3 new 1 Muteb 0 32 Produce draft Iteration plan 1 3 New 1 Khan 0 31 Finalise Status assessment 1 3 New 12 Mohamed 0 31 Finalise Supporting requirements 1 4 New 2 Khan 0 35 Finalise Actor, Use cases and Use case model 1 3 New 2 Khan 0 234 Finalise Test cases 1 4 New 2 Muteb 0 24 Finalise Architecture 1 3 New 3 Muteb 0 36 Finalise design 1 5 New 3 Khan 0 16 Finalise architectural proof of concept 1 10 New 3 Khan 0 35 Finalise iteration plan 1 2 New 2 Mohamed 0 34 Database design 2 2 New 2 Mohamed 0 35 User interface 3 10 New 1 Khan 0 36 Search interface 3 2 New 1 Khan 0 35 Search interface 3 2 New 1 Muteb 0 25 Return interface 3 2 New 1 Muteb 0 23 Add/Update items 3 2 New 1 Khan 0 38 Daily Status Report 4 3 New 1 Muteb 0 39 Monthly status report 5 4 New 1 Mohamed 0 36 Alpha Test 6 14 New 3 0 135 Beta Test 6 14 New 3 0 136 Work Items List Table 1 – work items list (Work Items List, 2011). Table 1 provides a list of all scheduled works need to be done in the project as well as in the future. Table includes: Name, Priority, Size estimate, State, Target iteration, Assigned To, Effort Estimate left, Hours worked and reference material. • Priority: order of which tasks should be done first. • Size estimate: an estimate of the time (number are in days) needed to finish the task. • State: current status of the tasks. • Assigned To: members will be in charge of the task. • Effort Estimate left: the estimate of left hours to finish the task. • Hours worked: hours were spent to do the task. Glossary (Schwalbe, 2007) Benefits Statements of advantageous project outcomes, such as increased revenues, reduced costs, performance and efficiency improvements. Note that benefits should be quantified where possible so that they are tangible and provide a basis for measurement. Note that less precise benefits may be intangible, or even indeterminable. Budget A budget sets out your plans in cost terms, for either a Project (Project Budget) or a Stage (Stage Budget), in order to gain authorization for the expenditure and to provide a basis for financial control for that work. Trainees/ Customers The person or group that is the direct beneficiary of a project or service is the trainee / Customer. These are the people for whom the project is being undertaken (indirect beneficiaries are stakeholders Data All recorded information, regardless of form or characteristic. Database An organised body of related information. Also see electronic database and index or the Library's Databases. Limitations Boundaries and restrictions. Milestone A key event during the life of a project, usually completing project deliverables or other noteworthy achievement. Not Applicable ("N/A") A contract term used to indicate that a standard clause or phrase does not apply. Objectives Predetermined results toward which effort is directed. Project A project is any endeavour undertaken to develop a product, produce a result, or provide a service. Project Plan The Project Plan is the document that identifies how the project is to be established, managed and executed. Requirements Requirements are descriptions of how a product or service should act, appear, or perform. Requirements generally refer to the features and functions of the deliverables you are building on your project. Requirements are considered to be a part of project scope. High-level scope is defined in your project definition (charter). The requirements form the detailed scope. After your requirements are approved, they can be changed through the scope change management process. Sponsor The person who has authority over the project, provides funding, approves scope changes, provides high-level direction and champions the project within an organisation. Stakeholder A stakeholder is anyone, internal or external to an organisation that has an interest in a project or will be affected by its deliverables. Start Date The start date is the date on which an activity is started. Testing That element of inspection that determines the properties or elements, including functional operation of supplies or their components, by the application of established scientific principles and procedures. Use Case The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would during their day-to-day activities. References Fitness first (2011), retrieved from, http://www.fitnessfirst.com.au/ Project Plan. (2010). Retrieved from http://epf.eclipse.org/wikis/openup/practice.mgmt.release_ planning.base/guidances/templates/project_plan_1534BA2B.html Risk List. (2010). Retrieved from http://epf.eclipse.org/wikis/openup/core.mgmt.common.extend_supp/guidances/templates/risk_list_33A6AE1E.html Schwalbe, K. (2007). Information Technology Project Management (5th ed.). Australia: Cengage Learning. Vision. (2010). Retrieved from http://epf.eclipse.org/wikis/openup/core.tech.common.extend_supp/guidances/templates/vision_E93BBDB6.html Work Items List. (2010). Retrieved from ttp://epf.eclipse.org/wikis/openup/core.mgmt.common. extend_supp/guidances/templates/work_items_list_B30CEE46.html Read More