COMP 2147 System Analysis Design and Testing

Your company has been awarded the contract to create a “Clinical Management System” software using Object Oriented /Unified Process methodology for the ABC family medicine and walk in clinic. Some members of your team interviewed the client; the clinic manager, to collect requirements about the proposed system and took the following interview notes The doctor should be able to do the following three tasks either by generating a print out from the system (and hand it to the patient) or send directly to the external party electronically (if the third party offers an electronic interface).

a. Prescriptions (print out given to the patient or sent to the pharmacy electronically)

b. Lab Requisitions (print out given to the patient or sent to the Laboratory electronically: and receiving the test results back electronically as well).

 

c. Specialist Referrals (print out given to the patient or sent to Specialists doctors’ offices electronically: and receiving the specialists notes/letters back electronically as well)

Project Deliverables

1. Create a system service request for creating a Clinical Management System for ABC clinic as requested by its Manager John Doe (use template from chapter 3-slide 8)

2. Develop a professional scale project charter (1-2 pages) as stipulated by PMBOK®. Please research find some suitable template for project charter.

3. Develop a Feasibility Analysis document (4-5 page long) to justify the project from financial, organizational, and technical view point (use various templates from chapter 4).

4. Perform textual analysis of the business processes of ABC clinic as described above in this document in order to identify the candidate actors and use cases and create a use case diagram (first cut).

5. Pick any TEN (10) use cases from your project and create Written Use Cases at the Kite Level (bird-eye view, use the template in chapter7 of the text book (fig 7-32, 7-34 on page 226/228).

6. Create Three (3) Activity Diagrams for any three business processes belonging to your project, use the template in chapter7 of the text book (fig 7-37, 7-38, and 7-39 on page 233/234).

7. Modify the first cut use case diagram created in the above step based on the additional details derived from the written use cases activity diagrams and create a refined and detailed use case diagram by incorporating <>, <>, and <> relationships.

8. Create a context level data flow diagram (DFD) to capture the scope of your project, use the example in chapter7 of the text book (fig 7-4 on page 187) 

9. Decompose the context level data flow diagram to create the Level-0 DFD (text book names it as Level-0 but the Visual Paradigm tutorials name it as Level-1).

10.Create a decision table to capture the process logic for your system (use the reduced version on page 204, fig 7-19). The table should contain at least 2 conditions and 4 courses of action.

11.Pick any one Business Process and create a BPMN diagram.

12.Create a conceptual Data Model (ER) model (incorporate entity generalization hierarchies, if any, and business rules for overlap and disjoint)

13.Create an ER Model for fully normalized relations (Logical Data Model), use example 9-16 on page 331.

14.Create a class diagram that would display class names, attributes, associations and relationships (generalization, composition, and aggregation)

15.Create wireframes for at least Five (5) important forms (and/or reports) for your project, use example in fig 10-3A (power point for Chapter 10 slide no 11)

16.Create a Dialogue diagram for any one actor/scenario, use example (Power Point chapter 11 slide no 49)

17.Create a testing strategy for your system which should include the test types and testing process you would specify [One page document] (use information provided in chapter 13, page 457-464)