Experience systems analysis and design by working on a
project with real-world application. You will have an opportunity to apply the knowledge you gain from
the textbook and the lectures and to demonstrate your ability to not only understand the material, but
to think critically about the material and the way it is applied.
Instructions:
All 3 assignments will be based on the same business problem. You will be asked to analyze the business
problem, investigate the system requirements, and create the necessary models for your internal
stakeholders.
The Business Problem (Same as Assignment 1):
Overview:
You have been asked to develop software for a pharmaceutical retail service named Pharm@Home.
Pharm@Home aims to allow customers in the Toronto area to order drugs and basic medical supplies
online (eg. bandages), and then have it delivered straight to their homes. The Pharm@Home system
must be able to handle customer registration, ordering, billing, and delivery. It must also handle internal
business processes such as inventory/stock levels, physical order fulfillment, employee information and
status, and managerial reports.
Details:
Pharm@Home aims to stock both non-prescription medication (eg. Tylenol) as well as medication that
does require a prescription (eg. Antibiotics). Any customers who order prescription medication must
have a valid prescription from a physician, and the order will be fulfilled by a licensed pharmacist
employed by Pharm@Home. The Pharmacist will also provide instructions for correct usage of the
prescription drug (eg. “Take 2 daily”) to the customer.
Customers will be required to make an account with Pharm@Home to be able to order. On registration,
customers will be required to provide their personal information, billing information, and delivery
information.
Pharm@Home will outsource all their deliveries to an external courier service called TPS (Toronto Postal
Service). The Pharm@Home system should automatically interact with the TPS system and create a
courier request for every order (assume TPS provides an API to their system). Pharm@Home will stock
their inventory at a single warehouse and all physical order fulfillment will occur there. You can assume
for simplicity’s sake that as long as the TPS system receives the necessary order information, then they
will handle package pick-up and delivery.
Customers should be able to interface with Pharm@Home via a mobile app. Employees will interface
with the same app but have their own accounts with necessary privileges and features.
Besides the ability to order drugs and supplies, customers should also be able to access their own order
and billing history, update their personal info, etc… Managerial staff should be able to see general
summary reports of sales and inventory. Pharmacists and other staff should be able to see any
information that is relevant to their job (ie. only pharmacists need to see a customer’s prescription).
This is not a complete description of the targeted system. It is your job as a systems’ analyst to search
for more information, understand the business problem, and canvas any needed requirements in depth.
This could include but is not limited to: health-insurance/OHIP/UHIP related processes, inventory reordering from suppliers, or social-media presence. You are required to show that you have done diligent
research into the business problem by eliciting some further requirements in addition to all of the
requirements stated above. Assuming you have already done this in Assignment 1, you can use the
same elicited requirements in Assignments 2 and 3.
Assignment Tasks:
1) Create a full set of Use Case Diagrams for the Pharm@Home system. (30 marks)
a. Be aware of appropriate usage of <> and <>.
b. One single comprehensive UCD is also acceptable.
2) Create a CRUD table showing use cases and corresponding domain classes. (10 marks)
3) Write a fully developed use case description for 1 major use case. (ie: vital to the business
function) (10 marks)
4) Create an activity diagram to show the flow of activities for the Customer creates an Order use
case. (15 marks)
a. Hint: there will be at least 1 branch in the diagram.
5) Create a UI storyboard for the Pharmacist actor for the use case: Pharmacist fulfills prescription
order. (15 marks)
a. Reminder: Employees of Pharm@Home interface with the system via mobile app (see
business problem description). Think about what the Pharmacist Employee would need
to see and do to complete their job and realize this use case.
6) Create a system sequence diagram to accompany your UI storyboard from #5 for the Pharmacist
fulfills prescription order use case. (20 marks)
a. Note: Although the UI storyboard is for the Pharmacist actor, the Pharmacist is not the
only external actor involved in this use case. Think about what data must be passed
between external actors and the system and do not forget to include them on your SSD.
Submission:
- You are required to submit a SINGLE .PDF or .DOC(x) file containing all of your answers and
models. Mark deductions may be given for not adhering to these instructions.
Grading:
You will be marked on comprehensiveness, readability, accuracy, and design quality. All models used
in systems analysis have a purpose. That is, they have a specific goal or message that is to be conveyed
to the reader via the model, it is important that your model clearly conveys this.
• Comprehensiveness: Does the model or set of models fully encompass the business problem?
Are all relevant aspects of the business problem conveyed in the model(s)?
• Readability: Is it clear to the reader what the model represents? Can all parts of the model be
easily deciphered? Is there redundancy in the model?
• Accuracy: Are aspects of the model such as relationships, multiplicity, cardinality, etc… correct?
Is the notation used correct? Are there modelling concepts being used incorrectly or are certain
modelling concepts lacking when necessary? Is there consistency between models (eg. design
sequence diagrams and design class diagrams)?
• Design quality: (Applies primarily to class diagrams, ERDs, etc…) Does the system design make
sense? Are there many foreseeable problems with the system design?
Depending on the model, these grading criteria may be weighted differently. (ie. Readability may
have a lower weight than the other criteria.)
Sample Solution
