Reference no: EM132675370
Introductory System Analysis and Design Assignment
Learning Outcome 1: Apply appropriate problem solving processes based on logical and critical thinking and systems modelling to produce the system's scope, analyse system requirements and design potential information system solutions.
Learning Outcome 2: Prepare a business case for a proposed business problem solution and produce a suitable system specification report.
Case Study
Background
Keith Cruz is a martial arts master who manages an academy that offers training in martial arts and self defence. It currently offers a small range of classes that include Karate, Jiu Jitsu, Judo and self-defence. He plans to increase the range of classes offered in the near future.
Keith needs to keep track of which aspects of the academy generate enough revenue to support it. As many clients participate in more than one of the academy's classes, and pay through various arrangements, it takes a lot of paper work to assign revenues and costs to the different type of classes. Everything is done manually at the moment. The manual assignment of the revenue and costs of running the classes has not been entirely successful which makes it difficult for Keith to keep track.
Keith approached one his clients, Rick Parson (an IT consultant) to analyse and design an appropriate business information system for the academy.
Information gathered from several interviews with Keith
Rick participated in several interview sessions with Keith about the academy's operations. The information elicited is as follows:
Keith specifies which classes will be offered. For example, the group classes currently include Karate, Jiu Jitsu, Judo and Self Defence. Keith schedules the class sessions and hires qualified and experienced instructors for each type class. He keeps details of instructors (name, address and contact numbers) in a file. The instructors submit monthly invoices to the academy for the class sessions that the instructors conduct for the month so they can get paid.
The academy currently has 4 rooms in its premises for the classes. Sessions usually run for 60 minutes and are usually scheduled between 5 to 9pm. At this point in time, each class is usually scheduled to run every day during the week (except weekends). A class session schedule is produced at the beginning of every month.
If clients wish to attend any class they are expected to join the academy. Information about the client is recorded (client's name, address, email, contact number, and date joined). The client must supply the name and contact number of a person in case of any emergency.
Clients can enroll for as many classes. Clients need to register for the sessions they wish to attend for a class. If a client does not register but attends a session, the client is allowed to join the session if it is not full.
Keith needs to be notified when a session is full so another session can be added if needed. A message will be sent in advance to clients registered for a session if there are any changes to the sessions e.g. change to either the time or instructor for the session.
The academy offers different options for payment from clients. Clients can pay for a session every time they attend the session. The rate for a class vary depending on the type of class.
Clients will get a reduced rate if they register for a string of 12 sessions. They can also pay a fixed fee for a class and attend any number of its sessions for 6 months. Both of these options are only applicable to certain classes. Keith would like the system to inform a client who has taken up one of these options when the client attends their last session. If clients do not take either of these 2 options for a class, they are expected to make a payment for every class session they attend. If a client cancels a registration, the client is removed from the registration list for the session. If a client does cancel a registration and does not attend the session, the client is charge a non-attendance fee.
Client attendance is recorded when they attend a class session. The payments by clients who opt to pay for a session every time they attend are recorded. Payments for a string of 12 sessions or for unlimited sessions for 6 months are made when clients enroll for a class.
Keith and his administrative staff will be the users of the system. The administrative staff members will be responsible for any functions not handled by Keith.
Output Reports
The following reports are required:
1. A report that shows (for a specified time period) each type of class, the clients enrolled, and the payment option chosen by each client.
2. A report that shows (for a specified time period), the total number of attendances, the total amount of payments received from the clients who attended, and the total amount paid to the instructors for each type of class.
3. A report that lists the clients who attended a particular class session. The report should also list the clients who registered but did not attend the session. Besides listing information about the clients, the report should also list the payment option chosen by each client who attended the session. The name of the instructor should also be included in the report.
4. A report that shows (for a specified time period) for each instructor, the class and total number of class sessions taught by the instructor, and the total amount paid to the instructor for the class.
Each report should have control breaks where applicable and the data should be sorted.
Assignment Requirements
Unfortunately, Rick had to take on another job and has asked you, as a trainee analyst in his company, to finish the job.
By analysing the information gathered from the interviews prepare a Functional Requirements Report. The guide for the report is detailed below.
1. Needs and/or Problem description, and proposed solution (system capabilities) of new system.
2. A Context Data Flow Diagram to illustrate the scope and boundary of the new system. Provide a description of the data flows in the Context DFD. A mark will not be given for a data flow if a description is not provided.
3. Description of functionality of the new system. You must provide the major (must have) use cases and their descriptions for the new system based on the requirements identified in the case study.
• Provide a use-case glossary that shows the name of each use case, a brief description of the use case and the actor(s) for the use case. Look at the assignment example (in the assignment folder on BB) for an example of a brief description of a use case.
• You must number your use cases in the glossary. Marks will be deducted if they are not numbered.
• The use cases should be presented in a "logical" sequence.
4. Description of the data requirements for the new system. You must provide:
a. An ER Diagram
b. The name, description and an example of the data stored in each of the attributes for each entity of interest to the system and relationship (where applicable). You can make some reasonable assumptions when describing the attributes. You must indicate which attribute is the identifier for each entity.
5. Design input screen(s) for 6 use cases from your use case glossary that is used to record/update data.
a. Indicate clearly which use case the input screen(s) is for. Provide the use case number, name and brief description (from the use case glossary).
b. For fields on the screen that are not display only fields, indicate which data entry control is used for the input field. Also specify its associated attributes (from the ERD). Look at the assignment example (in the assignment folder on BB) for an example
c. List the flow of activities i.e. the key steps followed for the dialog with a written description of what the user and system do at each step (see example on BB).
Important: You must design your own screens. You will be reported for academic misconduct if you copy screens from another source. Indicate which tool you used to design your screen e.g. MSWord drawing tool.
6. Design the 4 output reports specified in this assignment. Each report should have control breaks where applicable and the data should be sorted.
a. For fields on the report specify its associated attributes (from the ERD). If the report displays derived data e.g. totals, explain how the value was derived.
Important: You must design your own reports. You will be reported for academic misconduct if you copy output reports/screens from another source. Indicate which tool you used to design your report e.g. MSWord drawing tool.
Appendix
7. Marking scheme (signed by group members).
Attachment:- Introductory System Analysis and Design.rar