SBM4201 System Analysis and Design

This document provides an overview of the SBM4201 System Analysis and Design course. It includes a breakdown of work structure, possible entities in a hospital management system, use cases and actors, class diagram, ERD, state machine diagram, sequence diagram, activity diagram, system architecture diagram, user interface design, and planning for testing and deployment activities.

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

1
SBM4201 SYSTEM ANALYSIS AND DESIGN
Question 1:
Work breakdown Structure
0
Development of customer
database for the Max
league baseball team
1
System Design
2
Design Phase
2.1
Subsystem A Design
2.2
Subsystem B Design
2.3
Subsystem C Design
3
Programming
3.1
Program A
3.2
Program B
3.3
Program C
4
Testing
0
1
2
345
6
789
10
45 days 0%
06-05-19 05-07-19
5 days 0%
06-05-19 10-05-19
14 days 0%
13-05-19 30-05-19
5 days 0%
13-05-19 17-05-19
4 days 0%
20-05-19 23-05-19
5 days 0%
24-05-19 30-05-19
22 days 0%
31-05-19 01-07-19
9 days 0%
31-05-19 12-06-19
5 days 0%
13-06-19 19-06-19
8 days 0%
20-06-19 01-07-19
4 days 0%
02-07-19 05-07-19
Start And finish date of each task and its critical path

2
SBM4201 SYSTEM ANALYSIS AND DESIGN
Question 2:
Possible entities in Hospital Management System
Hospital (Hospital_ID, Hospital_Name, Bed_available, Rooms_available)
Insurance_Policy (Policy_ID, Poicy_name, Amount)
Patient (P_ID, P_Name, Age, Sex, Address, DoB, MoB, Policy_ID)
Room (Room_ID, Room_No, Room_Type, Room_Cost)
Admission (Admission_ID, P_ID, Hospital_ID, Room_ID, Reception_ID, Date,
Time)
Bill (Bill_ID, Policy_ID, Bill_purpose, Bill_total)
Accountant (Account_ID, Account_name, Age, Address, MOB, Working_Time,
Account_salary)
Payment (Pay_ID, Bill_ID, P_ID, Account_ID, Pay_Type, Pay_Date)
Repection (Recption_ID, reception_name, Age, Address, MOB, Shifting)
Doctor (D_ID, Hospital_ID, D_Name, Age, Address, Salary, MOB, Designation,
Passed_From)
Appointment (Appointment_ID, P_ID, D_ID, Reception_ID, Appointment_Date,
Appointment_time)
Prescription (Pres_ID, D_ID, Med_ID, P_ID, Date, fee)
Medicine (Med_ID, Med_Name, company, M_Date, E_date, Price)
Blood (Blood_ID, Blood_Group, Availability)
Possible Use cases and actors

3
SBM4201 SYSTEM ANALYSIS AND DESIGN
Actors: Receptionist, Admin and Doctor
Use Cases: Billing System, Hospitalization, Patent Registration, Consult Doctor,
Consultation Billing, File insurance Claim, File medical Record, Add Doctor, Update Doctor,
Delete Doctor, Add Staff, Modify Staff, Delete Staff, Prescribe Test, Modify test, Delete
Test.
Use Case Diagram explaining Hospital Management System Process
Software Protection and Licensing
Class Diagram

4
SBM4201 SYSTEM ANALYSIS AND DESIGN
Class Diagram

5
SBM4201 SYSTEM ANALYSIS AND DESIGN
ERD
State machine Diagram

6
SBM4201 SYSTEM ANALYSIS AND DESIGN
Sequence Diagram

7
SBM4201 SYSTEM ANALYSIS AND DESIGN
Activity diagram
System Architecture Diagram

8
SBM4201 SYSTEM ANALYSIS AND DESIGN
User Interface Design

9
SBM4201 SYSTEM ANALYSIS AND DESIGN
Planning suitable testing and deployment activities
The following stages are needed to be included for testing the deployment of the application
such as:
 Functional Testing – How the application works?
 Compatibility Testing – Is the app consistent for every one and under different
platform?
 Performance Testing – Does the application have effect on the performance and
respond quickly?
 Security Testing – What is the security of the app against different types of network
attacks?
 Usability testing – Is the app easy to use and provides the expected result?

10
SBM4201 SYSTEM ANALYSIS AND DESIGN
Bibliography
Dakic, D., Stefanovic, D., Lolic, T., Sladojevic, S., & Anderla, A. (2018, March). Production
planning business process modelling using UML class diagram. In 2018 17th
International Symposium INFOTEH-JAHORINA (INFOTEH) (pp. 1-6). IEEE.
Haoues, M., Sellami, A., & Ben-Abdallah, H. (2016, November). Predicting the functional
change status in UML activity diagram from the use case diagram. In 2016 IEEE/ACS
13th International Conference of Computer Systems and Applications (AICCSA) (pp.
1-8). IEEE.