University of South Australia 

School of ITMS 

INFS 1021: Systems Analysis (SA) A3 Assignment – 

Group Length: 2000 words,  Weighting: 25%,  Due Date: 11 pm Sunday 31st May

INSTRUCTIONS TO STUDENTS
This task is to be done in groups which must have been approved by your tutor. Assignments will be returned to you within two to three weeks of submission. Feedback on this assignment will be provided via a rubric which will be available on the course website. Please read the assessment summary and assessment details sections of your course outline booklet carefully for further information relating to assessment in this course.
SPECIFICATIONS 
This assignment will enable you to improve your skills as a systems analyst and carry out various activities in the systems analysis phase of the systems development life cycle. It requires you to investigate and document system requirements, identify and document use cases, carry out domain modelling and use case modelling.
The assignment should be created using the template provided on the course website.
Each group member is also required to fill out the “Declaration of Contribution” form which is available in the assignment template document. As stated in the form, if any contribution does not meet the assessment requirements, the course coordinator may adjust individual marks up or down, depending on the level of contribution made.
Marking Criteria 
The rubric that will be used when assessing your work will be available on the course website. The word limit will not be checked for this assessment. This task will assess completeness of the objectives listed below.
• Completeness, suitability and thoroughness of responses to the questions
• Technical correctness of the various models created;
• Adequate presentation and format;
• Use of the template provided;
• Correct spelling and grammar;
• Clarity of expression;
• Clearly labelled questions and answers;
2 Submission Instructions 
The assignment MUST be submitted via Learnonline through the course website or via MyUniSA. Please submit ONLY ONE assignment per group – nominate someone to submit the assignment on the group’s behalf. Include as part of your submission ONE .pdf document containing the responses to the questions relating to the given scenario. Individual submissions will NOT be considered or marked. Refer to your course outline for further information regarding extensions. Late submissions will not be accepted for this course unless an extension has been approved by the course coordinator (see section on extensions in your course outline for further details). Late submissions that have not been approved will receive a mark of zero.
***IMPORTANT INFORMATION***
It is up to each group to make sure that the submitted work does not contain any parts copied from another group in this or any previous year, from this or any similar course; or from a common source such as a textbook or website. The assignment must be your own collective work, and not contracted to a substitute person. If we are suspicious, we reserve the right to call you in and to test your understanding of what you have submitted in an oral examination. If plagiarism is detected it will be investigated and appropriate consequences will follow.
SCENARIO
A Medical Practice has tasked your team to develop the requirements for their medical practice management system. The system is to allow the practice to record patient appointments and allow doctors to capture the medical history of their patients. A patient’s primary doctor can access the details of their patients at any time. However if a patient temporarily sees a different doctor, that doctor can only access the patient’s medical records during the consultation. The system must record the times when doctors are available during business hours from Monday to Friday, 8 am to 9 pm, and Saturday and Sunday from 9 am to 4 pm. The system must be available with 98% certainty during these business hours. Response times for accessing a patient’s record, which can be a maximum of 100 megabytes, must not exceed 7 seconds. At times doctors will also be able to be rostered as a locum service in shifts from 6am to 2pm, 2 pm to 10pm or 10pm to 6am. A doctor may not be rostered on for more than 40 hours per week and if rostered as a locum shift may not take another shift without a 14 hour break. The medical practice has ten doctors. Only one doctor will be rostered on a locum shift at a time. During business hours two nurses must also be rostered on and again may not work more than 40 hours per week. A doctor consults with patients in their office and must be able to access the system from their office. The history of all updates is logged and the system is backed up daily. The system logs a person out after ten minutes without use. Doctors on the locum roster are to be provided with a tablet device with mobile phone and global positioning system connections. The application on the device is to contain an emergency call button that contacts police in the event of an emergency and transmits the address that the doctor is consulting at. The tablet device application is to be able to connect with the patient records stored at the main medical practice but only show the record of the patient that the doctor is consulting with at that time. Doctors consult with patients in either fifteen minute or 30 minute blocks. In addition to a patient’s medical history, a patient’s record must include their name, address, date of birth, emergency contacts, any current medications, a photograph of their face and key details such as hair colour, eye colour, height, weight and gender. Associated with a patient but stored separately is their financial records – bills incurred, outstanding and medical insurance details. The reception staff must be able to manage appointments in person or on the phone for new and existing patients. After an appointment, the reception staff must be able to call up the billing information for a patient based on what services a doctor has provided, accept cash or electronic payment and print out invoices for the patient or their parent, guardian or carer. Note that a patient without private medical insurance receives a Medicare rebate on their services and a patient with private medical insurance receives an additional rebate but there typically is some gap fee that remains to be paid. The business manager for the Practice must also be able to access the system for basic accounting activities, transferring the data into a standard accounting package for analysis. The business manager must be able to identify the total Medicare rebate as well as the Private Insurance company rebates and invoice accordingly. The business manager must also be able to identify the costs of the business associated with the time sheets that doctors complete each week. Doctors enter their time sheets via their office computer. Finally doctors must be able to access the Internet from their terminals and as well use the specialist Pharmacy application provided by AAA Pharmacy Pty Ltd. Each doctor must be able to print scripts for patients from their office or the surgery, the receptionists print invoices for patients and the business manager prints report information. It is imperative that patient privacy is strictly respected so there must be suitable security measures in place to ensure this. The Practice has one IT administrator that can perform general IT duties for the terminals and servers but must not be able to access patient records without an additional password entered by the most senior doctor of the practice. The system is expected to handle approximately 300 patients.
QUESTIONS 1. 
SYSTEM REQUIREMENTS
 a. Who are the stakeholders for the system? Provide your response using the grid format and/or template given in the previous assignment. For each stakeholder identified, list what aspects of the system are of particular interest to them. Express stakeholders’ interests using the following template: “As a , I want to so that .” 
b. To collect information on the functional requirements for the system, what are some techniques that might be used? Identify what information would need to be obtained through interviews. Who would you interview? Include ten sample interview questions you would ask to obtain the required information. Ensure you obtain sufficient information to define use cases and create models. c. What are the primary functional requirements for the system? Provide your response using the format specified in lectures and tutorials. d. Identify and describe non-functional requirements for the system. Provide your response using the format specified in lectures and tutorials.

2. USE CASES 
a. Identify all the actors who will be using the system. 
b. Prepare a table containing all use cases and a brief use case description (1-2 sentences) for each use case. 
c. Draw a use case diagram for the system representing the actors and use cases identified. 

3. DOMAIN MODELLING 
a. List the domain classes for the system and their attributes. 
b. Based on the domain classes identified, develop a domain model class diagram showing domain classes with attributes, primary keys, relationships, and multiplicity constraints. 
c. Associations are the naturally occurring relationships between classes. They apply in two directions and can be read separately each way. For example two classes called Customer and Order could have the following associations: 
• A Customer can place zero or more Orders. 
• An Order must be placed by exactly one Customer. List all of the associations (in both directions) between the classes for the domain model in part b using the format specified above. 
4. USE CASE MODELLING 
a. Write a fully developed use case description for the use case Book Appointment. Assume the patient is new and making the appointment in person at the Practice. 
b. Develop an activity diagram for the use case in part a. 
c. Prepare a system sequence diagram for the use case in part a. 
d. Based on the domain model and the list of use cases developed, do a CRUD analysis for each of the identified classes. Provide your response in the CRUD table format given in Figure 5-13 of the textbook, pg 147, which shows use cases down the left and domain classes across the top of the table. 
5 Important Notes: 
• Justify and document any decisions and assumptions made. 
• You must use the templates/layouts provided in the course notes and/or textbook for any answers, tables, models, diagrams or use case descriptions created. Diagrams must conform to the UML notation used in this course. 
• Diagrams may be produced using a UML case tool or hand-drawn provided that they are legible and well laid out. It is the group’s responsibility to ensure these are appropriately presented and incorporated into the document template. 
• DO NOT include the scenario or question text in the document template. Use the template document as is. Do not modify any headings and include your responses in the area indicated. 
• Post any questions in relation to the scenario or assignment on the SA A3 Assignment – Group Q&A Forum on the course website.