System Analysis and Design

This document provides information about system analysis and design, including work breakdown structure, critical path, hospital management system, class diagram, ER diagram, and more.

Running head: SYSTEM ANALYSIS AND DESIGN
System Analysis and Design
Name of the Student
Name of the University
Author’s note:

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Portfolio 1:.................................................................................................................................2
Question 1: Work Breakdown Structure and Critical Path....................................................2
1.1 Work Breakdown Structure..........................................................................................2
1.2 Critical Path..................................................................................................................3
Question 2: Hospital Management System............................................................................3
2.1 Entities and Attributes:.................................................................................................3
2.2 Use Case and Actors Identification:.............................................................................5
2.3 Use case diagram:........................................................................................................7
Portfolio 2...................................................................................................................................8
Question 1:.............................................................................................................................8
2.1 Class diagram...............................................................................................................8
Portfolio 3:.................................................................................................................................9
3.1 ER Diagram:.....................................................................................................................9
3.2 Class Diagram:...............................................................................................................10
3.3 State Machine Diagram:.................................................................................................10
3.4 Sequence Diagram:........................................................................................................11
Portfolio 4:...............................................................................................................................12
4.1 Activity Diagram:...........................................................................................................12
4.2 System Architecture Diagram:.......................................................................................12
4.3 User Interface:................................................................................................................13
Portfolio 5:...............................................................................................................................13
5.1 Testing and Deployment Activities:...............................................................................13
5.1.1 Testing:....................................................................................................................13
5.1.2 Deployment:............................................................................................................14
Bibliography:............................................................................................................................15

2SYSTEM ANALYSIS AND DESIGN
Portfolio 1:
Question 1: Work Breakdown Structure and Critical Path
1.1 Work Breakdown Structure
Task Name Duration Start Finish Predecessors
Portfolio1Ganttchart 45 days Tue 30-04-19 Mon 01-07-19
1.0 System Design 5 days Tue 30-04-19 Mon 06-05-19
2.0 Design Phase 14 days Tue 07-05-19 Fri 24-05-19
2.1 Subsystem A 5 days Tue 07-05-19 Mon 13-05-19
2.2 Subsystem B 4 days Tue 14-05-19 Fri 17-05-19 3
2.3 Subsystem C 5 days Mon 20-05-
19 Fri 24-05-19 4
3.0 Programming 22 days Mon 27-05-
19 Tue 25-06-19
3.1 Program A 9 days Mon 27-05-
19 Thu 06-06-19 5
3.2 Program B 5 days Fri 07-06-19 Thu 13-06-19 7
3.3 Program C 8 days Fri 14-06-19 Tue 25-06-19 8
4.0 Testing 4 days Wed 26-06-
19 Mon 01-07-19 9
Figure 1: Work Breakdown Structure
(Source: Created by Author)

3SYSTEM ANALYSIS AND DESIGN
1.2 Critical Path
ID Task
Mode
Task Name Duration Start Finish
0 Portfolio1Ganttchart45 days Tue
30-04-19
Mon
01-07-19
1 1.0 System Design 5 days Tue 30-04-19 Mon 06-05-19
2 2.0 Design Phase 14 days Tue 07-05-19 Fri 24-05-19
3 2.1 Subsystem A5 days Tue 07-05-19 Mon 13-05-19
4 2.2 Subsystem B4 days Tue 14-05-19 Fri 17-05-19
5 2.3 Subsystem C5 days Mon 20-05-19 Fri 24-05-19
6 3.0 Programming 22 days Mon 27-05-19Tue 25-06-19
7 3.1 Program A 9 days Mon 27-05-19 Thu 06-06-19
8 3.2 Program B 5 days Fri 07-06-19 Thu 13-06-19
9 3.3 Program C 8 days Fri 14-06-19 Tue 25-06-19
10 4.0 Testing 4 days Wed 26-06-19Mon 01-07-19
S T M F T S W S T M F T S W S T M F
22 Apr '19 06 May '19 20 May '19 03 Jun '19 17 Jun '19 01 Jul '19
Figure 2: Critical Path
(Source: Created by Author)
Question 2: Hospital Management System
2.1 Entities and Attributes:
Entities Actors
Receptionist Receptionist_id
Name
Address
Email_addess
Contact
Salary
Join_date
Patient Patient_id
Name
Address

4SYSTEM ANALYSIS AND DESIGN
Email_addess
Contact
Contact_Person
Contact_Person_Phone_Number
Doctor Doctor_id
Name
Address
Email_addess
Contact
Type
Appointment Appointment_id
Appointment_date
Appointment_time
Doctor_id
Patient_id
Illness_overview
Admission Admission_id
Admission_date
Bed_number
Patient_id
Illness
Expected_Release_Date
Service_Details
Bed Bed_number
Ward

5SYSTEM ANALYSIS AND DESIGN
Charge
Status
Payment Payment_id
Patient_id
Payment_amount
tax
discount
Total_payment
Payment_method
2.2 Use Case and Actors Identification:
The list of use case are as following.
i. Schedule Admissions
ii. Patient registration
iii. Schedule Appointments
iv. Admit Patients
v. Collect Patient Data
vi. Allot Bed
vii. Receive Payments
viii. Keep Records
ix. Distribute Reports
x. Provide Receipts
xi. Insurance Claims
The list of the actors are as following.

6SYSTEM ANALYSIS AND DESIGN
i. Receptionist
ii. Patient
iii. Doctors

7SYSTEM ANALYSIS AND DESIGN
2.3 Use case diagram:
Figure 3: Use Case Diagram of Hospital Management System
(Source: Created by Author)

8SYSTEM ANALYSIS AND DESIGN
Portfolio 2
Question 1:
2.1 Class diagram
Figure 4: Class Diagram of Software Protection and Licensing
(Source: Created by Author)

9SYSTEM ANALYSIS AND DESIGN
Portfolio 3:
3.1 ER Diagram:
Figure 5: Entity Relationship Diagram of Training Inc.
(Source: Created by Author)

10SYSTEM ANALYSIS AND DESIGN
3.2 Class Diagram:
Figure 6: Class Diagram of Training Inc.
(Source: Created by Author)
3.3 State Machine Diagram:
Figure 7: State Machine Diagram of Training Inc.
(Source: Created by Author)

11SYSTEM ANALYSIS AND DESIGN
3.4 Sequence Diagram:
Figure 8: Sequence Diagram of Training Inc.
(Source: Created by Author)

12SYSTEM ANALYSIS AND DESIGN
Portfolio 4:
4.1 Activity Diagram:
Figure 9: Activity Diagram of Training Inc.
(Source: Created by Author)
4.2 System Architecture Diagram:

13SYSTEM ANALYSIS AND DESIGN
Figure 10: System Architecture Diagram of Training Inc. System
(Source: Created by Author)
4.3 User Interface:
Figure 11: User Interface Diagram of Training Inc. System
(Source: Created by Author)
Portfolio 5:
5.1 Testing and Deployment Activities:
5.1.1 Testing:
To test the system, the black box testing will be used. The first step is creating the
system test plan. The system test plan will be created by the testing team and reviewed by the
system engineer. The next phase is system test cases. The testing team along with the

14SYSTEM ANALYSIS AND DESIGN
assistance of system engineer will create a set of system test cases. The final stage is testing
the application based on the proposed system test cases.
5.1.2 Deployment:
The system will be used by various users who will operate from different
geographical location. The cloud deployment is the best solution for Training Inc. based on
the system requirement and business complexity. In order to deploy the system into the cloud,
the organization can consider PaaS or platform as a service as the best option. The
organization will contract a team of developers who will develop the system and deploy it
into the cloud. The organization will sign a contract or SLA with the service provider to agree
upon the service each of them will provide.

15SYSTEM ANALYSIS AND DESIGN
Bibliography:
Afanasyev, A.N., Voit, N.N., Voevodin, E.Y. and Gainullin, R.F., 2015, October. Control of
UML diagrams in designing automated systems software. In 2015 9th International
Conference on Application of Information and Communication Technologies (AICT) (pp.
285-288). IEEE.
Sarmiento-Carnevali, M.L., Harrison, T.J., Dutta, S., Bemment, S.D., Ward, C.P. and Dixon,
R., 2017. Design, construction, deployment and testing of a full-scale Repoint Light track
switch (I).
Storrle, H., 2016, September. Diagram Size vs. Layout Flaws: Understanding Quality Factors
of UML Diagrams. In Proceedings of the 10th ACM/IEEE International Symposium on
Empirical Software Engineering and Measurement (p. 31). ACM.