Reference no: EM131291573

Assignment 2

2. Develop use cases

By using user use goal technique

user	User goal and resulting use case
Potential patient	• Create account • Schedule appointment • View medication prescription • View directions for taking medication • View lab reports • Send a message
doctors	• Make appointment schedule • Make lab reports staff
staff	• Register current users

2.1 Using the Community Patient Portal System Part 1 and Community Patient Portal System Part 2 case study , create a list of all actors. Create a definition for each actor. Use the format "A (n) actorName is a ...." and then complete the sentence. For example, "A Student is a Person who is enrolled in a University." Place your actors and definitions in a table with 2 columns, one for Actor and the other for the definition.

An actor is an UML name for end users or also can be define as something that interacts with the system. The list of actors from the case study include

i. Patients
ii. Doctors
iii. Staffs
iv. HIPPA electronic health record system

A patient is a person who is seeking attendance in hospital
A doctor is a person attending to patients
A staff is an employee who assist on various operations
HIPPA is a system that keeps health records

actors	definition
Patient	Person seeking hospital attendance
doctors	Person, employee attending to patients
staff	Employee assisting on various operations
HIPPA	Integrated system that keeps health record's

2.2 Use the user goal technique and/or the event decomposition technique to create a list of use cases for each actor identified above. A use case can be used by more than one actor. Define/describe each use case. Place the use cases and descriptions in a table with 2 columns, one for the Use Case name and the other for the Description/Definition.

user	User goal and resulting use case
patient	• Create account • Schedule appointment • View medication prescription • View directions for taking medication • View lab reports • Send a message • Refill prescription
doctors	• Make appointment schedule • Make lab reports
staff	• Register current users
HIPPA(system)	• Recording system

2.3 Using the CASE tool, draw a UML use case diagram following the notation conventions in your textbook and CASE tool.

A use case diagram is a UML diagram used to graphically show use cases and their relationship to actors

2.4 Use the event decomposition technique and create a list of use cases for each event. Name the event, state the type of event, and name and define the resulting use case.

An event is something that occurs that occurs at a specific time and place can be described and should be remembered by the system
Event decomposition is a type of use case technique that is more comprehensive

Events	Type of event	Use case
Patients creates account	external	Create an account
Patient setups two step verification	external
Patients logins into system	external	Account verified
Patients makes appointment	external	Process appointment creation
Display currently scheduled appointment	temporal	Process appointment creation
Patients schedule appointment	external
Patients select view medication	external	Process prescription refill
List medication	temporal
Patient refill prescription	external
Patient select view lab results	external	Generate lab report
Display lab report results
Patient select date displayed
Display results
Patient views lab results
Patient prints lab results

 

 

3. Develop a class diagram

3.1Using the two discussions for the CPPS case study and the noun analysis technique, identify potential classes from your noun analysis.

3.2 Create a table of the classes with the class name in one column and the definition in the other. For the definition, use the format "A (n) className is a ...." and then complete the sentence.

Class name	definition
patient	A patient is a person who creates account in the cpps system
account	An account is a registration created by patient
appointment	An appointment is a schedule created by patient
medication	A medication is a prescription by the doctor
labResult	A labResult is a report from a test
test	A test is a labResult that is detailed
report	A report is a test that is generates results
message	A message is a text that has recipient

3.3 Identify the relationships among the classes.

There is binary relationship or association between the classes where the multiplicity varies between different associations among the classes
Unary relationship is between labResult and test

3.4 Create a UML class diagram using the classes you have identified and add names to the associations and multiplicity constraints.

Class diagram is a UML diagram that shows classes with attributes and associations
Associations is a natural occurring relationship between classes
Multiplicity is term for the number of associations between classes: 1 to 1 or 1 to many

3.5 What are your impressions of the noun technique?

• It quickly help identify classes
• Ends up with a list of many nouns that cannot even be stored on the system
• It's a good start point for beginners when there is nobody to help in brainstorming
• It's a popular and much simpler technique

3.6 How can you use the CRUD technique to verify and validate your use cases?

CRUD stands for create, read/report, update and delete. You can use this technique to validate your use cases by following the following steps

• You must identify all the entities and domain classes involved in the new system
• You must verify that a use case has been identified that creates new instance, updates existing instance, reads or reports values of instances
• When a needed use case has been overlooked add a new use case and then identify the stakeholders
• Make sure it's clear which application is responsible for adding and maintain the data

Discussion Points

Post your one of your models from your Assignment 2 document in the Peer Review Forum with a brief discussion of its contents and any features you like or issues you encountered. Your initial post (250-300 words).

Attachment:- Assignment.rar