UML Diagrams for AIK9 Limited Clinic System: A Case Study

This assignment provides a comprehensive analysis of the AIK9 Limited clinic system using UML diagrams. It identifies key stakeholders such as dog owners, vets, and senior vets, and elicits their requirements for the system. The assignment includes a use case diagram illustrating interactions between users and the system, along with detailed use case specifications for creating a new support case. The analysis covers actors, goals, triggers, preconditions, main success flow, alternate flows, and post-conditions, offering a thorough understanding of the system's functionality and design. The document is available on Desklib, where students can find a wealth of study resources, including solved assignments and past papers.

Running head: UML DIAGRAMS
UML Diagrams: AIK9 Limited Clinic System
Name of the Student:
Name of the University:
Author Note

1
UML DIAGRAMS
Question 1 Identify Stakeholders & Elicit Requirements
a) The main stakeholders associated with the system are:
Dog Owner, The vet and Senior Vet
b) The set of requirement to be fulfilled for each of the actor of the system are:
Dog Owner
 The owner should be able to enter their problems into the system.
 The owner should be able to register a case with the Dog Id.
The vet
 The vet should be able to view the list of case and provide solution to the problems
registered by the owners.
Senior Vet
 The Senior Vet should be able to manage the cases on their merits.
Question 2 Identify Interactions between Users and the Clinic System
a) The Use case diagram of the AIK9 Limited Clinic System:

2
UML DIAGRAMS
Figure 1: Use Case Diagram of the AIK9 Limited Clinic System
Source: (created by Author)
The main actors associated with the system are Dog Owner, The vet and Senior Vet.
Use Case Actors Description
Registration Dog Owner The owner can register in the system
Enter a new Case Dog Owner The owner is able to enter a new case into the
system
Enter Description Dog Owner The owner should be able to enter the description
of the system
Supporting Case Dog Owner The user should be able to enter a supporting case
to the existing case.
View Case The Vet The vet would be allowed to view the list of cases.
Take on a Case The Vet The vet would be allowed to take on a case.
Case Status The Vet The vet would be able to view the status of the

3
UML DIAGRAMS
case.
Comments/Notes The Vet The vet would be able to provide useful comments
to the existing case and notes if required.
Unassigned Case The Vet The vet would be able to un-assign a case if
required.
Change Case
Status
The Vet The vet would be able to change the status of the
case when a new vet takes up the case
Owner
Notification
Senior Vet, Dog
Owner
The Senior vet would set up a notification in the
system so that the owner of the case is notified if a
solution to their problem is obtained.
Close Case Senior Vet The Senior vet would be close any irrelevant case
in the system
Case
Management
Senior Vet The senior vet would be able to manage the case
such as closing and deleting case.
Delete Case Senior Vet The Senior vet would be delete any irrelevant case
in the system

4
UML DIAGRAMS
b)
The situation provided for the question: “an owner shall be able to create a new support
case”.
The description for the given use case is provided below:
Use Case Specification Template
Use Case Identification and History
Use Case ID & Name: UC4: Supporting Case Version:
Objective: Allows the dog to add support to an existing case
Created by: <Author name> Date:
Actors & Goals: Support the existing problem
Stakeholders Dog Owner
Trigger: The Case is triggered by the Dog Owner
Preconditions
The preconditions are that the case has to be registered in the system and the Dog Owner is also
registered in the system
Main Success Flow
The case will be successfully completed if the owner can successfully enter the case in the system.
This flow shows that no case was registered into the system previously.
User Actions System Actions
Looking for same type of problem faced by the
user which exists in the system.
The system would provide a list of cases for the
user to select from.
Providing the system with a short description The system provides the users with the dialog
box where the full description is to be
provided.
Provide a detailed description to the case The system stores the case.
Alternate Flow
This flow show the process if the case is already registered into the system.
User Actions System Actions
The user looks for the case in the system The system would provide a list of cases for
the user to select from.
The user doesn’t find any case that matches his
criteria
The system asks the user to enter a new case
The users enters a new case The system directs the user to the process of
filling out a new case
Post conditions
After the process the veterinary would be able to view the newly updated case

5
UML DIAGRAMS
Other Notes (Assumptions, Issues,)
No Assumptions or Issues

6
UML DIAGRAMS
Bibliography
Shah, S.A.A., Shahzad, R.K., Bukhari, S.S.A. and Humayun, M., 2016. Automated Test Case
Generation Using UML Class & Sequence Diagram. British Journal of Applied Science &
Technology, 15(3).
Terekhov, A., Bryksin, T. and Litvinov, Y., 2017. How to make visual modeling more attractive
to software developers. In Present and Ulterior Software Engineering (pp. 139-152). Springer,
Cham.
Wautelet, Y. and Poelmans, S., 2017, February. Aligning the elements of the RUP/UML
business use-case model and the BPMN business process diagram. In International Working
Conference on Requirements Engineering: Foundation for Software Quality (pp. 22-30).
Springer, Cham.
Wautelet, Y. and Poelmans, S., 2017, November. An Integrated Enterprise Modeling Framework
Using the RUP/UML Business Use-Case Model and BPMN. In IFIP Working Conference on
The Practice of Enterprise Modeling (pp. 299-315). Springer, Cham.