22 Jan IT 304 Module Three Activity Guidelines and Rubric
In this module, you learned that users of a new system and system analysts work together to develop and model the requirements of a system. You also learned that use case diagrams support the visualization of both requirements and design of a software system. Use case diagrams are considered to be high level to help stakeholders and users understand the system. Meanwhile, use case specifications are low level, and are intended to be used by the developers coding the program. For this activity, you will create use case diagrams and their use case specifications.
Prompt
Imagine you are an employee of a consulting firm. The consulting firm was hired to design a new system that will better automate how a patient checks into a patient care facility for medical services. Part of the consulting services that you will provide include developing use case diagrams and their use case specifications that demonstrate how the various actors will use the IT system. UML should be used to illustrate how the software solution should facilitate certain check-in/check-out services for a patient.
For this week’s activity, you will create:
Use Case Diagrams: The four use case diagrams must illustrate the check-in/check-out process of the patient at the clinic. They must include an identification of:
Actors
Relationships between the actors
System boundaries
Use Case Specifications: The four use case specifications must apply the features, functionality, and operations in the software solution mentioned in the business case.
All required use case diagrams and their use case specifications must be complete, without any missing components, as you will be graded on completion.
The four key services that you will create use case diagrams and use case specifications for are:
Capture patient information/reason for visit
Verify patient insurance
Capture patient copay
Schedule next appointment
You can use a tool of your choice to help you create the use case diagrams, but we recommend using Lucidchart, draw.io, or MS Visio. The following resources can help you complete your use case diagrams:
Lucidchart UML Activity Diagram Tutorial
Visio 2016 Tutorial
Microsoft Azure Dev Tools for Teaching link to access Visio
Draw.io Quick Start Tutorial video
Draw.io Diagram Software
UML Use Case Diagram Tutorial
All You Need to Know about Use Case Modeling
The following resources can help you with your use case specifications:
How to Write Detailed Use Case Descriptions
Use Case Description
Use Case Specification Template
What to Submit
Upload and submit a file that contains your four use case diagrams and your four use case specifications.
Module Three Activity Rubric
Criteria Proficient (100%) Needs Improvement (85%) Not Evident (0%) Value
Use Case Diagrams Identifies the actors, relationships between the actors, and system boundaries Shows progress toward proficiency, but with errors or omissions; areas for improvement may include clarifying or correcting relationships between actors Does not attempt criterion 40
Use Case Specifications Applies the features, functionality, and operations in the software solution mentioned in the business case Shows progress toward proficiency, but with errors or omissions; areas for improvement may include identifying the features of the system solution Does not attempt criterion 40
Completion Creates all required use case diagrams and their use case specifications without any missing components Shows progress toward proficiency, but with errors or omissions; areas for improvement may include submitting any missing components of the use case diagrams and their use case specifications Does not attempt criterion 20
Total: 100%
