Reference no: EM132222529

1. Task Description

1.1 Overview

You are required to read the provided Case Study document and complete each of the activities and questions in the weeks advised.

The answers to all activities and questions are to be collected in one "Systems Requirements Report" with a title page, page numbers, table of contents, headings and all other report formatting.

The purpose of the fullSystem Requirements Reportis to guide and enable your fictional client to make a rational selection from options for a proposed computer application.

The Initial Investigation part of this report has been completed in Part A of this assignment.

Part B includes other seand models to complete the full Systems Requirements Report. For example, you will need to complete, and add to Part A, the following:
• Fact Finding Documents
• Use Cases
• ERD and Domain Model Class Diagrams
• System Sequence Diagrams
• Project Management Charts with progress against tasks
• Conclusions and Recommendations.

Note: you are encouraged to use feedback from Part A to improve your report before submission of the full System Requirements Report. Please indicate changes made in response to feedback using highlighted text and/or commenting.

1.6 Software
You are required to use appropriate computer software packages to produce output for many of the above techniques. This approach should assist you with the inevitable changes that you (or another analyst, in a real life system) will need to make, and also gives a better quality and hence more readable result.Hand-drawn diagrams are not suitable for this project.

Case Study - You Can Fit In

ACTIVITY 1

1. Use the background information to create a short summary (one short paragraph) about the "You Can Fit In" business.
2. Create an organisation chart for the You Can Fit In business.
3. Use the information above to describe the area of the organisation under study (i.e. the business functions that will be handled by the new information system).
4. Add the background information, organisation chart, and business functions to your Report document in Part A: Initial Investigation.

ACTIVITY 2
1. Either by yourself or with another class member, brainstorm all the functions that the You Can Fit In system might fulfil. Keep it at a very high level.
2. Prepare a draft System Vision Document for the new You Can Fit In system. This System Vision Document will be revised when you find out more about the requirements for the system. An example System Vision Document can be seen in Figure 1.8 of your textbook (Figure 1.5 in the 6thed).
3. Add your System Vision Document to your Report document in Part A: Initial Investigation.

ACTIVITY 3
1. Create a table, listing all tasks separately, with their duration;
2. Identify all dependencies, and indicate what predecessor tasks are required;
3. Construct a Gantt chart in Microsoft Project or other project management software;
4. Identify the PERT/CPM chart in the software, and identify the critical path;
5. Determine the overall duration of the project;
6. Take clear screenshots of the Gantt chart and PERT/CPM chart and paste into your Report document in Part A: Initial Investigation under Project Management.
7. Include the overall duration and critical path in your report.

ACTIVITY 4
1. What are the risks associated with this project? Create a list of up to 10 risks and their likelihood of happening (see Study Guide topic 4, activity 4.6 for an example of how this should be set out).
2. Define the anticipated benefits of the new system. This should include both tangible and intangible benefits. Wherever possible, translate the intangible benefits into anticipated tangible benefits.
3. Define the expected costs of the new system. Look at the examples given in workshop activities for some examples of expense categories. It is OK to give estimates at this point. For our purposes the process is more important than the raw base costings that you identify for equipment and human resources.
4. Use two or more cost-benefit analysis techniques to decide whether to proceed with the project.
5. Identify any assumptions and interpretations that you are making with respect to the information that you have been given, that you are estimating, and that you are projecting (into the future).
6. Create a new section in Part A of your report: Risk and Cost Benefit Analysis. Insert your work from above, and give a clear indication as to whether it is feasible to continue with the project.
7. Does the proposed system present a strong business case? Why or why not? Include a recommendation as to whether the system should proceed, as the final part of your preliminary report. The Preliminary Investigation part of your Report can now be submitted.

ACTIVITY 5
1. What fact-finding techniques, apart from interviews, do you recommend to find out the requirements for the new system? Provide some examples of the information that you have determined through this process (Remember, this is a role play...while you will need to create your findings [make it up]... both your fact finding activities, and the "facts" that you determine, need to be plausible and sensible).
2. Identify at least two staff members with different primary job roles of interest to this project.
3. Develop a list of questions for an interview with each staff member. Identify the time anticipated for the interview. Review your topic on creating interview questions, and make sure you include suitable question types.
4. Include the interview plans in the Appendices for your Report.
5. Include the recommendations for other fact-finding techniques, in your Report.

ACTIVITY 6
1. Write down a list of the main functions needed to be handled by the new system.
2. What are the roles that will be interacting with the system?
3. Using all the information that you know about the You Can Fit In business so far, create a use-case diagram for the new system.
4. Select four use-cases and write a brief use-case description for them.
5. Pick one of these use-cases and write a full use-case description for it. Use an activity diagram in the full description.
6. Include the following in your report:
• the use-case diagram;
• the brief use-case descriptions;
• the full use-case description, including your activity diagram.

ACTIVITY 7
1. Review the You Can Fit In fact-finding summary and all other information you have about the required system. Be willing to critically analyse this for duplications and inconsistencies.
2. Draw an ERD with crows-foot cardinality notation. Assume that system entities include members, classes, merchandise, and fitness instructors (at minimum).
3. Design tables - making sure each table only refers to one "thing". As you create the database design, identify primary and foreign keys by underlining primary keys, and making foreign keys italic.
4. If you add primary keys which use codes - for example a code for the instructorID, then identify the format of these codes.
5. Create suitable sample data to populate the fields for at least three records in each table.
6. Include the following in your report:
• The ERD you have completed;
• The database design (schemas);
• Formats of codes used;
• Sample data for each table.

ACTIVITY 8
1. Create a system sequence diagram for one of the use cases identified in Activity 6.
2. Add this system sequence diagram to your report in the appropriate area.
3. Search online for potential commercial software packages for You Can Fit In. Identify two packages, and compare their features, and their suitability to be used as the new system.
4. Present at least three options for the new system in your report. One of these must be in-house development, and two of the others may be the commercial packages in (3) above.
5. Review your feasibility analysis for the new system. Taking all options into consideration, make a recommendation for the new system, in your "Conclusion and Recommendations" section.

ACTIVITY 9
Ensure your report is professionally presented. This means your report should include:
• a title page, with the name of the Report, and the analyst's name (your name);
• an executive summary;
• a table of contents, with page numbers;
• page numbers on all pages except the title page;
• Headings, sub-headings, dot-points and numbering where necessary. Headings should be numbered or the structure should otherwise be easily identified;
• Appendices where necessary;
• Formatting and whitespace (space where there is no text or pictures) used appropriately - be willing to start each new section on a new page;
• Page orientation used appropriately. For example, if you have an ERD that will show better in landscape orientation than portrait orientation , set a Section break (Page Layout > Breaks) before this page, set the page to landscape and then set another Section break to start the new page in portrait again.

Attachment:- Case Study.rar