ChemExec System Analysis and Design
VerifiedAdded on 2023/01/20
|9
|1153
|93
AI Summary
This report discusses the system analysis and design of the ChemExec system, which aims to computerize the ordering, delivery, and billing processes of health care facilities. It covers the business problem, purpose statement, benefits, system capabilities, requirements, and design of the system.
Contribute Materials
Your contribution can guide someone’s learning journey. Share your
documents today.
BIT230 System Analysis and
Design
April 19
2019
Student ID:
Student Name:
Assessment 1 –
Semester 1
Design
April 19
2019
Student ID:
Student Name:
Assessment 1 –
Semester 1
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Report
Contents
Report..........................................................................................................................................................2
System Scope..............................................................................................................................................3
Business Problem....................................................................................................................................3
Purpose Statement...................................................................................................................................3
Benefits...................................................................................................................................................3
System Capabilities.................................................................................................................................3
Exclusion.................................................................................................................................................3
System’s FURPS+ Requirements................................................................................................................4
Functional Requirements.........................................................................................................................4
Usability Requirements...........................................................................................................................5
Reliability Requirements.........................................................................................................................5
Performance Requirements......................................................................................................................5
Supportability Requirements...................................................................................................................5
Design Requirements...............................................................................................................................6
Non Functional Requirements: Event Table................................................................................................6
Use Case Diagram.......................................................................................................................................8
References...................................................................................................................................................9
Contents
Report..........................................................................................................................................................2
System Scope..............................................................................................................................................3
Business Problem....................................................................................................................................3
Purpose Statement...................................................................................................................................3
Benefits...................................................................................................................................................3
System Capabilities.................................................................................................................................3
Exclusion.................................................................................................................................................3
System’s FURPS+ Requirements................................................................................................................4
Functional Requirements.........................................................................................................................4
Usability Requirements...........................................................................................................................5
Reliability Requirements.........................................................................................................................5
Performance Requirements......................................................................................................................5
Supportability Requirements...................................................................................................................5
Design Requirements...............................................................................................................................6
Non Functional Requirements: Event Table................................................................................................6
Use Case Diagram.......................................................................................................................................8
References...................................................................................................................................................9
System Scope
Business Problem
Currently the patient orders of health care facilities are being taken over phone and most of other
work is also being done manually and billing is being done by third party which is not working
according to the requirements. The business of ChemExec is being increased day by day and it is
not easy to manage complete functionality and inventory management manually.
Purpose Statement
The main objective of the ChecmExec system is to maintain the all records from taking orders to
delivery and billing should be computerize. The complete ChecmExec system should be
computerized.
Benefits
There are lots of benefits of the computerized ChecmExec system as shown below-
- The important data will be managed easily.
- The billing is very critical and it will be accurate.
- The records will be saved for future use also.
System Capabilities
The system will be capable of doing all the tasks required in ChemExec like below-
- The system will be capable of taking patient orders from Health Care Facilities.
- The system will be capable to deliver all orders to Health Care Facilities on time by doing
all internal tasks like making manifests, assembling all components of orders etc.
- The system will be capable of doing billing.
- The system will be capable of managing inventory.
Exclusion
Business Problem
Currently the patient orders of health care facilities are being taken over phone and most of other
work is also being done manually and billing is being done by third party which is not working
according to the requirements. The business of ChemExec is being increased day by day and it is
not easy to manage complete functionality and inventory management manually.
Purpose Statement
The main objective of the ChecmExec system is to maintain the all records from taking orders to
delivery and billing should be computerize. The complete ChecmExec system should be
computerized.
Benefits
There are lots of benefits of the computerized ChecmExec system as shown below-
- The important data will be managed easily.
- The billing is very critical and it will be accurate.
- The records will be saved for future use also.
System Capabilities
The system will be capable of doing all the tasks required in ChemExec like below-
- The system will be capable of taking patient orders from Health Care Facilities.
- The system will be capable to deliver all orders to Health Care Facilities on time by doing
all internal tasks like making manifests, assembling all components of orders etc.
- The system will be capable of doing billing.
- The system will be capable of managing inventory.
Exclusion
Remove the separate working of all different branches of ChemExec. Make a single system that
will work for all branches.
System’s FURPS+ Requirements
The requirement is a capability or condition which is necessarily obeyed by the system. There
are different types of requirement e.g. Functional, Non-Functional etc.
FURPS+ categorize the requirements like below-
F- Functional Requirements
U- Usability Requirements
R- Reliability Requirements
P- Performance Requirements
S- Supportability Requirements
+ indicates that there are some other requirements also likebelow-
- Design Requirements
- Physical Requirements
- Interface Requirements etc.
Functional Requirements
There are different functional requirements in ChemExec system as shown below-
Number Requirement
1 Health Care Facilities will order the cases.
2 The ChemExec system will accepts pharmacy orders for patients from Health
Care Facilities.
3 Health Care Facilities submit Patient’s prescription.
4 System will generate case manifests for each floor or wing of each client.
5 Assign case manifests to pharmacists.
6 PA collects all drugs of a patient in plastic drawer.
7 PA assembles all components of order.
8 Pharmacist makes the final check before order.
9 System will store manifest into computer.
10 Process billing online.
11 PA assembles all cases.
will work for all branches.
System’s FURPS+ Requirements
The requirement is a capability or condition which is necessarily obeyed by the system. There
are different types of requirement e.g. Functional, Non-Functional etc.
FURPS+ categorize the requirements like below-
F- Functional Requirements
U- Usability Requirements
R- Reliability Requirements
P- Performance Requirements
S- Supportability Requirements
+ indicates that there are some other requirements also likebelow-
- Design Requirements
- Physical Requirements
- Interface Requirements etc.
Functional Requirements
There are different functional requirements in ChemExec system as shown below-
Number Requirement
1 Health Care Facilities will order the cases.
2 The ChemExec system will accepts pharmacy orders for patients from Health
Care Facilities.
3 Health Care Facilities submit Patient’s prescription.
4 System will generate case manifests for each floor or wing of each client.
5 Assign case manifests to pharmacists.
6 PA collects all drugs of a patient in plastic drawer.
7 PA assembles all components of order.
8 Pharmacist makes the final check before order.
9 System will store manifest into computer.
10 Process billing online.
11 PA assembles all cases.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser
12 Delivery Persons delivers the orders to the health Care Facilities.
Usability Requirements
There are different non functional usability requirements in ChemExec system as shown below-
Number Requirements
1 The ChemExec system should guide users to work on the system.
2 The ChemExec system should be easy to understand.
3 The ChemExec system should not obstruct the users.
4 The ChemExec system must be easy to correct mistakes.
Reliability Requirements
There are different non functional reliability requirements in ChemExec system as shown below-
Number Requirements
1 The ChemExec system should be designed as a robust and lenient to operator
errors.
2 The ChemExec system should recover from power cuts etc.
3 The ChemExec system should be reliable with less number of interruptions.
4 The ChemExec system must give stable results.
Performance Requirements
There are different non functional performance requirements in ChemExec system as shown
below-
Number Requirements
1 There should not be any restriction of time or place on the usage of system.
2 The ChemExec system should response quickly.
3 The ChemExec system should be able to dialog with users all the time.
Supportability Requirements
There are different non functional supportability requirements in ChemExec system as shown
below-
Number Requirements
Usability Requirements
There are different non functional usability requirements in ChemExec system as shown below-
Number Requirements
1 The ChemExec system should guide users to work on the system.
2 The ChemExec system should be easy to understand.
3 The ChemExec system should not obstruct the users.
4 The ChemExec system must be easy to correct mistakes.
Reliability Requirements
There are different non functional reliability requirements in ChemExec system as shown below-
Number Requirements
1 The ChemExec system should be designed as a robust and lenient to operator
errors.
2 The ChemExec system should recover from power cuts etc.
3 The ChemExec system should be reliable with less number of interruptions.
4 The ChemExec system must give stable results.
Performance Requirements
There are different non functional performance requirements in ChemExec system as shown
below-
Number Requirements
1 There should not be any restriction of time or place on the usage of system.
2 The ChemExec system should response quickly.
3 The ChemExec system should be able to dialog with users all the time.
Supportability Requirements
There are different non functional supportability requirements in ChemExec system as shown
below-
Number Requirements
1 The ChemExec system should support different languages.
2 The ChemExec system should be maintainable.
3 The ChemExec system should be able to migrate to upgraded hardwares or
softwares..
4 The ChemExec system should be able to migrate to different networks.
Design Requirements
There are different non functional design requirements in ChemExec system as shown below-
Number Requirements
1 The ChemExec system should be designed in the way that it will work many
years.
2 There should be good interface to interact with the users.
Non Functional Requirements: Event Table
Event Trigger Source Use Case Response Destination
Send Orders Patient
Orders will
reached at
System
Online
Health Care
Facilities
Send Orders Received
Patient Order
ChemExec
System
Accept
Orders
Orders
Accepted or
Rejected
Clerical Staff Accept
Orders
Accept and
Confirm or
Reject Patient
Orders
Health Care
Facilities
Submit
Patient’s
Prescriptions
Patient’s
Prescriptions
Health Care
Facilities
Submit
Patient’s
Prescriptions
Received
Patient’s
Prescriptions
ChemExec
System
Generate
Case
Manifests
Case
Manifests
Generated
ChemExec
System
Generate
Case
Manifests
Case
Manifests
Generated
ChemExec
System
Assign Case
Manifests
Case
Manifests
Assigned
Shift
Supervisor
Assign Case
Manifests
Case
Manifests
Assigned
Pharmacist
Collect All
Drugs
All Drugs
Collected
PA Collect All
Drugs
All Drugs
Collected
PA
Assemble all
Components
All
Components
Assembled
PA Assemble all
Components
of Order
All
Components
Assembled
PA
2 The ChemExec system should be maintainable.
3 The ChemExec system should be able to migrate to upgraded hardwares or
softwares..
4 The ChemExec system should be able to migrate to different networks.
Design Requirements
There are different non functional design requirements in ChemExec system as shown below-
Number Requirements
1 The ChemExec system should be designed in the way that it will work many
years.
2 There should be good interface to interact with the users.
Non Functional Requirements: Event Table
Event Trigger Source Use Case Response Destination
Send Orders Patient
Orders will
reached at
System
Online
Health Care
Facilities
Send Orders Received
Patient Order
ChemExec
System
Accept
Orders
Orders
Accepted or
Rejected
Clerical Staff Accept
Orders
Accept and
Confirm or
Reject Patient
Orders
Health Care
Facilities
Submit
Patient’s
Prescriptions
Patient’s
Prescriptions
Health Care
Facilities
Submit
Patient’s
Prescriptions
Received
Patient’s
Prescriptions
ChemExec
System
Generate
Case
Manifests
Case
Manifests
Generated
ChemExec
System
Generate
Case
Manifests
Case
Manifests
Generated
ChemExec
System
Assign Case
Manifests
Case
Manifests
Assigned
Shift
Supervisor
Assign Case
Manifests
Case
Manifests
Assigned
Pharmacist
Collect All
Drugs
All Drugs
Collected
PA Collect All
Drugs
All Drugs
Collected
PA
Assemble all
Components
All
Components
Assembled
PA Assemble all
Components
of Order
All
Components
Assembled
PA
Final Check Check Orders Pharmacist Final Check
of Orders
Check Orders Pharmacist
Store
Manifest
Store
Manifest
Clerical Staff Store
Manifest into
Computer
Store
Manifest
ChemExec
System
Process
Billing
Process
Billing
ChemExec
System
Process
Billing
Process
Billing
Health Care
Facilities
Assemble all
Cases
All Cases
Assembled
PA Assemble all
Cases
All Cases
Assembled
Delivery
Persons
Deliver all
Cases
All Cases
Delivered
Delivery
Persons
Deliver all
Cases
All Cases
Delivered
Health Care
Facilities
of Orders
Check Orders Pharmacist
Store
Manifest
Store
Manifest
Clerical Staff Store
Manifest into
Computer
Store
Manifest
ChemExec
System
Process
Billing
Process
Billing
ChemExec
System
Process
Billing
Process
Billing
Health Care
Facilities
Assemble all
Cases
All Cases
Assembled
PA Assemble all
Cases
All Cases
Assembled
Delivery
Persons
Deliver all
Cases
All Cases
Delivered
Delivery
Persons
Deliver all
Cases
All Cases
Delivered
Health Care
Facilities
Secure Best Marks with AI Grader
Need help grading? Try our AI Grader for instant feedback on your assignments.
Use Case Diagram
References
uml-diagrams.org (2014). UML Use Case Diagrams. [online]. Available from: http://www.uml-
diagrams.org/use-case-diagrams.html. [Accessed: 19 April 2019]
TechTarget (2015). Use Case Diagram. [online]. Available from:
http://whatis.techtarget.com/definition/use-case-diagram. [Accessed: 19 April 2019]
Altexsoft.com (2018). Functional and Nonfunctional Requirements: Specifications and Types.
[online]. Available from: https://www.altexsoft.com/blog/business/functional-and-non-
functional-requirements-specification-and-types/. [Accessed: 19 April 2019]
revolvy.com (2019). FURPS. [online]. Available from: https://www.revolvy.com/page/FURPS.
[Accessed: 19 April 2019]
uml-diagrams.org (2014). UML Use Case Diagrams. [online]. Available from: http://www.uml-
diagrams.org/use-case-diagrams.html. [Accessed: 19 April 2019]
TechTarget (2015). Use Case Diagram. [online]. Available from:
http://whatis.techtarget.com/definition/use-case-diagram. [Accessed: 19 April 2019]
Altexsoft.com (2018). Functional and Nonfunctional Requirements: Specifications and Types.
[online]. Available from: https://www.altexsoft.com/blog/business/functional-and-non-
functional-requirements-specification-and-types/. [Accessed: 19 April 2019]
revolvy.com (2019). FURPS. [online]. Available from: https://www.revolvy.com/page/FURPS.
[Accessed: 19 April 2019]
1 out of 9
Related Documents
Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
© 2024 | Zucol Services PVT LTD | All rights reserved.