System Analysis and Design

This document provides an overview of system analysis and design, including work breakdown structure, entities in hospital management system, use case and actors, testing methodologies, and more. It is relevant to the SBM4201 course at your university.

0SYSTEM ANALYSIS AND DESIGN
Unit Code and Title: SBM4201 System Analysis and Design
Name of Student-
Name of University-
Author’s Note-

1SYSTEM ANALYSIS AND DESIGN
Portfolio 1: Individual assignment
Question 1:
Task 1: Work Breakdown Structure
0
Baseball
1
System Design
1.1
Gathering
Requirements
1.2
Analyzing
Requirements
1.3
Designing Software
1.4
Dividing the
sub-systems
2
Design Phase
2.1
Subsystem A Designing
2.2
Subsystem B Designing
2.3
Subsystem C Designing
3
Programming Phase
3.1
Subsystem A
Programming
3.2
Subsystem B
Programming
3.3
Subsystem C
Programming
4
Testing Phase
4.1
Subsystem A Testing
4.2
Subsystem B Testing
4.3
Subsystem C Testing
0
1
2345
6
789
10
111213
14
151617
19.5 days 0%
4/03/19 29/03/19
5 days 0%
4/03/19 8/03/19
1 day 0%
4/03/19 4/03/19
2 days 0%
5/03/19 6/03/19
1 day 0%
7/03/19 7/03/19
1 day 0%
8/03/19 8/03/19
10 days 0%
4/03/19 15/03/19
5 days 0%
4/03/19 8/03/19
4 days 0%
11/03/19 14/03/19
5 days 0%
11/03/19 15/03/19
18 days 0%
4/03/19 27/03/19
9 days 0%
4/03/19 14/03/19
6 days 0%
15/03/19 22/03/19
8 days 0%
18/03/19 27/03/19
19.5 days 0%
4/03/19 29/03/19
1.5 days 0%
4/03/19 5/03/19
1 day 0%
25/03/19 25/03/19
1.5 days 0%
28/03/19 29/03/19
Figure 1: WBS for the Baseball Project
(Source: Created by Author)

2SYSTEM ANALYSIS AND DESIGN
Task 2: Start Finish Date and Critical path
Figure 2: Critical Path
(Source: Created by Author)

3SYSTEM ANALYSIS AND DESIGN
Question 2:
Task 1: Entities in Hospital Management System
The entities that are related with the Hospital Management systems are shown in the table
below:
Entity Attributes
Booking bookingID, name, bookingDate
Customer customerName, customerID, customerPhone
Bed bedID, bookingDate
Receptionist recepID, recepName, recepPhone
Task 2: Use Case and Actors
Entities Attributes
Receptionist Name
Address
Email
Working Hours
Phone number
Receptionist ID
Nurses Name
Phone Number
Nurse ID
Patient Attended

4SYSTEM ANALYSIS AND DESIGN
Working Hours
Doctors DName
Patient_ID
DPhone_number
Visiting_time
Task 3: Use Case Diagram
Figure 1: Use case Diagram of Hospital Management System
(Source: Created by author)

5SYSTEM ANALYSIS AND DESIGN
Portfolio 2:
Figure 2: Class Diagram
(Source: Created by author)

6SYSTEM ANALYSIS AND DESIGN
Portfolio 3:
Entity Relationship Diagram
Figure 1: Entity Relationship Diagram
(Source: Created by Author)

7SYSTEM ANALYSIS AND DESIGN
Class Diagram
Figure 2: Class Diagram
(Source: Created by Author)

8SYSTEM ANALYSIS AND DESIGN
State Machine Diagram
Figure 3: State Machine Diagram
(Source: Created by author)

9SYSTEM ANALYSIS AND DESIGN
Sequence Diagram
Figure 4: Sequence Diagram
(Source: Created by Author)

10SYSTEM ANALYSIS AND DESIGN
Portfolio 4:
Activity Diagram
Figure 1: Activity Diagram
(Source: Created by Author)

11SYSTEM ANALYSIS AND DESIGN
System Architecture Diagram
Figure 2: System Architecture Diagram
(Source: Created by Author)

12SYSTEM ANALYSIS AND DESIGN
User Interface
Page 1
Figure 3: Page 1 User Interface
(Source: Created by author)

13SYSTEM ANALYSIS AND DESIGN
Figure 4: Page 2 User Interface
(Source: Created by author)

14SYSTEM ANALYSIS AND DESIGN
Figure 5: Page 3 User Interface
(Source: Created by author)

15SYSTEM ANALYSIS AND DESIGN
Portfolio 5:Deployment and Testing Methodologies
Testing is an essential part for developing a software or an application. With the help of
system deployment and testing method, a robust as well as stable application can be built up. It is
considered as the most important part of developing a software (Samokhvalov, Probst, and Rehm
2018). With including large number of platforms as well as devices, the testing methodologies
can be used. These methodologies helps to included more specified requirements in the
application.
The methodologies are considered as set of testing process that helps to develop a SDLC
including from Unit Testing to the entire system testing (Karamcheti, Mann and Rosenberg
2018). By selecting a proper testing methodology, is very much important for developing a
software. Basically there are three different testing categories that are available; grey box testing,
another is black box testing, and white box testing. All these three types of testing are briefly
described in the section below:
a) White Box Testing: This is considered as a particular technique which is used in
examining all the program structure as well as business logic that are included in developing the
software. The white box testing helps to validate the program or validate a code for a particular
application. The white box testing sometimes is also referred as clear box testing as well as Glass
Box testing (Mustaqbal, Firdaus and Rahmadi 2016). The techniques that are included in this
type of testing actually are statement coverage, sometimes branch coverage is also used, and also
path coverage is used is used sometimes. The statement coverage includes examining all
programming statements. The branch coverage includes series of all the running tests for

16SYSTEM ANALYSIS AND DESIGN
ensuring that all the branches included in the application are tested. The path coverage technique
helps to test all the paths that are possible for covering the branch or the statement.
b) Black Box Testing: This particular type of testing is particularly a type of method that
is used for testing the functionalities of a particular application which are based on some specific
requirement of the application (Henard et al. 2016). The Black Box testing does not focus on
some internal code or the structure of the application. The techniques that are included in this
type testing testing are: analysis of Boundary Value, analyzing the equivalence Partitioning,
making some particular decision tables, state models, domain testing, as well as exploratory
testing.
c) Grey Box Testing: This particular method of testing is basically performed with less
number of information related to the internal structure for the application (Beckmann et al.
2015). Generally, the testing that is carried out in this testing is similar to black box testing but
some critical areas are omitted out from the while box testing.
Selection of testing Methodology: The methodology that is used for developing the
information system for Training Inc. are white box testing as well as black box testing. The white
box testing is used for examining entire structure of program as well as carry out the business
logic. The white box testing is used for developing Training Inc. information system for testing
the functionality about how the application will be tested.

17SYSTEM ANALYSIS AND DESIGN
Bibliography
Beckmann, M., Michalke, V.N., Schlutter, A. and Vogelsang, A., 2017, September. Removal of
redundant elements within UML activity diagrams. In 2017 ACM/IEEE 20th International
Conference on Model Driven Engineering Languages and Systems (MODELS) (pp. 334-343).
IEEE.
Cerqueira, T.G., Ramalho, F. and Marinho, L.B., 2016. A Content-Based Approach for
Recommending UML Sequence Diagrams. In SEKE (pp. 644-649).
Nagar, D. and Kumar, J., 2018. State Oriented Software System Testing for Object Oriented
Applications using UML Diagrams. Journal of Advanced Research in Cloud Computing,
Virtualization and Web Applications, 1(2), pp.19-22.
Torchiano, M., Scanniello, G., Ricca, F., Reggio, G. and Leotta, M., 2017. Do UML object
diagrams affect design comprehensibility? Results from a family of four controlled
experiments. Journal of Visual Languages & Computing, 41, pp.10-21.
Beckmann, M., Michalke, V.N., Schlutter, A. and Vogelsang, A., 2017, September. Removal of
redundant elements within UML activity diagrams. In 2017 ACM/IEEE 20th International
Conference on Model Driven Engineering Languages and Systems (MODELS) (pp. 334-343).
IEEE.
Henard, C., Papadakis, M., Harman, M., Jia, Y. and Le Traon, Y., 2016, May. Comparing white-
box and black-box test prioritization. In 2016 IEEE/ACM 38th International Conference on
Software Engineering (ICSE) (pp. 523-534). IEEE.

18SYSTEM ANALYSIS AND DESIGN
Karamcheti, S., Mann, G. and Rosenberg, D., 2018, October. Adaptive Grey-Box Fuzz-Testing
with Thompson Sampling. In Proceedings of the 11th ACM Workshop on Artificial Intelligence
and Security (pp. 37-47). ACM.
Mustaqbal, M.S., Firdaus, R.F. and Rahmadi, H., 2016. Pengujian Aplikasi Menggunakan Black
Box Testing Boundary Value Analysis (Studi Kasus: Aplikasi Prediksi Kelulusan
SMNPTN). Jurnal Ilmiah Teknologi Informasi Terapan, 1(3).
Samokhvalov, A.V., Probst, C. and Rehm, J., 2018. Glass-Box Testing the Centre for Addiction
and Mental Health Integrated Care Pathway for Major Depressive and Alcohol Use Disorders: Is
It More Than a Sum of Its Components?. Canadian Journal of Addiction, 9(1), pp.7-17.