1. UML Needed for Requirements Spec Pepper

2. Need UML for Requirements Use Case Activity Diagram Tool: StarUML

3. Use cases  Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself.  A set of use cases should describe all possible interactions with the system.  High-level graphical model supplemented by more detailed tabular description  Sequence diagrams may be used to add detail to use-cases by showing the sequence of event processing in the system. 3Chapter 4 Requirements engineering

4. Use cases for the MHC-PMS 4Chapter 4 Requirements engineering

5. Use case modeling - Interaction Originally developed for requirements phase – Shows system boundary – Shows interactions with the outside world Model discrete task - Set of scenarios with one goal Actors (roles) may be people or other systems. Diagram or Text – Start with the main success case – Write the other scenarios into the case as extensions – Can include other already defined use cases – Pre-condition / Guarantee at end / Trigger to start event – Keep steps simple and show who is involved in each step 5Chapter 5 System modeling

6. Tabular description of the ‘Transfer data’ use-case MHC-PMS: Transfer data ActorsMedical receptionist, patient records system (PRS) DescriptionA receptionist may transfer data from the MHC-PMS to a general patient record database that is maintained by a health authority. The information transferred may either be updated personal information (address, phone number, etc.) or a summary of the patient’s diagnosis and treatment. DataPatient’s personal information, treatment summary StimulusUser command issued by medical receptionist ResponseConfirmation that PRS has been updated CommentsThe receptionist must have appropriate security permissions to access the patient information and the PRS. 6Chapter 5 System modeling

7. Transfer-data use case  A use case in the MHC-PMS 7Chapter 5 System modeling

8. Use cases in the MHC-PMS involving the role ‘Medical Receptionist’ 8Chapter 5 System modeling

9. Star UML Use Case Details: http://staruml.sourceforge.net/docs/user- guide(en)/ch05_1.html http://staruml.sourceforge.net/docs/user- guide(en)/ch05_1.html Use case pepper page: http://home.adelphi.edu/~pe16132/csc480/li nk/umlPage.htm http://home.adelphi.edu/~pe16132/csc480/li nk/umlPage.htm

10. UML Activity Diagrams - behavior Can be used to define high level business process or workflows – Shows how the system will be used at a high level – Order of activity made of many actions – Different from flowcharts - Support parallel behavior – Shows essential sequencing Components – Actions box - (can be a basis for another activity diagram) – Process line Fork line - one in and several out - multiple actions can start Join line - close parallel actions - every action done by this line – Condition diamonds - decisions Branch diamond - start conditional Merge diamond - join back to the flow – Partition lines Illustrate which system does what 10Chapter 5 System modeling

11. Process model of involuntary detention 11Chapter 5 System modeling

12. Summary Use Case – Action in circle – Actor figures – Actors can show inheritance – Can accompany with a normal use case doc – Line drawn around system responsibilities Activity Diagram – Actions in circles and related systems in boxes – Sequential flow – Clearly identify parallel processes