Systems Analysis and Design Report: SG Medical Center Software Project

This report details the development of a new software application for the Sydney Group (SG) medical center. The project aims to improve the efficiency of organizational work procedures by creating a system to track patient history and schedule appointments. The report covers various aspects of the project, including data structure types (primitive and non-primitive), the selection and explanation of the Entity Relationship (ER) diagram for data modeling, a discussion on the project schedule, and the justification for choosing the Waterfall model as the system development methodology. The report outlines the detailed activities within the Waterfall model, project management tools like PERT and Gantt charts, and concludes with recommendations for flexible project durations and improved testing phases. The system will enable doctors, nurses, receptionists, and management staff to access patient information and facilitate online appointment booking and bill payments via a mobile application. The ER diagram includes entities for Doctors, Patient_Treatment, and Patient, defining their attributes and relationships. The project schedule spans four months, with three months dedicated to development and one month for testing. The report emphasizes the importance of clear requirements, a clear solution, and minimal customer feedback during development, which aligns well with the Waterfall model's structured phases. The report highlights the challenges of adhering to the project schedule and the need for flexibility to accommodate potential errors and bugs.

Running head: SYSTEMS ANALYSIS AND DESIGN
SYSTEMS ANALYSIS AND DESIGN
Name of the student:
Name of the university:
Author note:

1
SYSTEMS ANALYSIS AND DESIGN
1.Introduction:
The aim of the project is to develop a new software application for the Sydney Group
(SG) medical centre in order to bring improvement and efficiency in the organizational work
procedure. The medical center has a number of registered doctors. The doctors are attributed
with doctor ID and the domain of their specialty. The doctors are assigned with the duty of
admitting patient to the center. The patients are identified with Patient ID and Patient name. The
patients who are admitted to the center will be assigned on one doctor per one patient basis.
However, if opted, one doctor can admit any number of patients and that is optional. Once a
patient is admitted, the patient must be assigned with at least one doctor.
It is the choice of the doctor that how many patient they want to treat. For the purpose of
documentation, the SG center wants to develop a system so that the details of the patients can be
recorded. The details will include date, time, and results of the treatment that needs to be
recorded.
The program for the project will be developed using object oriented programming (OOP).the
project will consider the following specifications:
 With the help of the program the doctor, nurse, receptionist and management staff at the
SG will be able to keep track of patient history and they will be able to schedule
appointments from anywhere. They can do the same from any computer inside or outside
the centre.

2
SYSTEMS ANALYSIS AND DESIGN
 Upgrade to the centre webpage can be done with the program to facilitate the patients to
book any doctor. The process can be completed online from anywhere as per the
convenient of the patient.
 Mobile application using android studio need to be developed that will allow patients to
pay bills and book online.
The report will contain data modeling method and the explanation on the selection of the data
modeling method, ER diagram based on the entities required for the database design.
Additionally a discussion will be carried out on the project scheduling and the system
development methodology along with the justification for the choice of the selection. The project
will highlight the development methodology in details with the required activities at each phase
of the design methodology required for the project development.
2.Data structure types:
2.1 Primitive Data Structures
Primitive Data Structures can be defined as the basic data structures that are able to
operate directly once the machine instructions are initiated. Based on different computers it has
different representations style (Berztiss , 2014).
Integers, Floating point numbers, Character constants, String constants and Pointers are
included in this category.
2.2 Non-primitive Data Structures
The nature of the Non-primitive data structures is different from the primitive data
structure in terms of complexity and derived from primitive data structures (Lafore, 2017).

3
SYSTEMS ANALYSIS AND DESIGN
The emphasize is given on the grouping of same or different data sets and there is close
relationship between each data item that are grouped. Arrays, Lists and Files are included under
this category (Joyce & Weems, 2016).
3. Selection of data modeling method and explanation and drawing of the entities:
3.1. Drawing of the entities:
The entity relationship diagram (ER ) has been used to draw the entities
3.2Explanation of the entities:
The ER diagram has three entities: Doctors, Patient_Treatment, Patient.
The attributes of the Doctors are: Doctor Id, Speciality
The attributes of the Patient_Treatment are: Patient, Doctor, Date, Time result
The attributes of the Patient are: Patient Id, Doctor_Reference, Patient_Name.
Following are relation between the entities:

4
SYSTEMS ANALYSIS AND DESIGN
A doctor may treat one patient or does not treat at all. However , once a patient has been
admitted , the patient has to be assigned with a doctor or many doctor can be assigned for a
particular patient. . A patient can only be admitted by a doctor reference. The doctor assigned
for a patient has to be taken from the table Doctors. However , all the Doctor Id in the table may
not be mapped against the attribute Doctor in the table Patient_Treatment. Here , the attribute
Doctor serves as foreign key in the table.

5
SYSTEMS ANALYSIS AND DESIGN
4.Discussion on Project schedule:
Week Activities Duration excluding holiday
(Sunday will be marked as
holiday)
1-3
Planning and Requirement
Analysis for the project
18 days
4-5 Requirement documentation 12 days
6-12 Design and implementation 42 days
13-16 Testing of the system 24 days
The project is scheduled to be completed within four month. Three month is assigned for
the development process and one month is assigned for the testing purpose as per the
requirements of the SG medical center.
The project schedule is discussed in details in the following section :

6
SYSTEMS ANALYSIS AND DESIGN
4.1. Development of the system:
Week 1-3:
Planning and Requirement Analysis
For week one to three, the development team will review the requirements and various
tools that will be necessary for the development.
Week 4-5:
Requirement documentation:
After doing the requirement analysis, the product requirements will be documented to
present it to the client to get the approval to start working on the proposed plan.
Week 6-12:
Design and implementation:
Once the planning, analyzing and documentation of the requirements is done, the actual
design and development will take place.
4.2Testing of the system
Week 13-16:
The system will be tested in the proposed period to ensure that the system is running
smooth without issues and it is meeting the requirements as per the client demands.
Justification of the proposed project duration:
Considering the nature of the project and the given time constrain, the project schedule is
tough to meet.. Sometimes, code might have errors, which will delay the project. The time frame

7
SYSTEMS ANALYSIS AND DESIGN
needs to be flexible if required. The project may also have issues during the testing phase. For
the testing purpose only one month is assigned. However, if the program has bugs and errors, the
code have to be modified yet again which will require much more time.
5.Choice and justification of the development methodology:
Although several development methodologies can be used for software development, it requires
proper analysis of certain requirements that needs to consider before choosing a development
methodologies. The requirements are as follows:
Clear requirements:
The requirements that the project must consider is clear before the development takes place.
Clear solution:
The solution or what the end product is makes no confusion and the developers has a
clear view of what needs to be done
Feedback on the work:
Minimal or no feedback is required from the customers until the project is completed and
ready to be used
Enhancement to the work:
The work does not require frequent enhancement during the development phase, as the
requirements are clear and well defined

8
SYSTEMS ANALYSIS AND DESIGN
Cost Of delay:
The cost of delay is not a major concern for the project and if required will not affect the
development.
The project that iTech needs to develop for the Sydney Group Medical Systems exactly
meet these requirements already discussed. For this kind of projects, Waterfall model is the ideal
development methodology to choose .with the model it is easy to visualize such projects as the
model has very clear phase of requirement analysis, design, development, implementation,
testing and deployment.
6.Detailed activities of waterfall model
The waterfall model is discussed bellow in details:
Analysis of requirement:
The requirements for the project are gathered and documented in this phase
Design of the System:
A study is conducted in this phase to analyze the documented requirements to prepare the
system design
Implementation:
With the help of the system inputs the developments takes place in small units the integration is
done in the next phase.

9
SYSTEMS ANALYSIS AND DESIGN
Integration and testing:
The integration of the units developed in the previous phase is done in this
phase. Each unit is tested after the development to ensure the functionality of the units
developed.
Deployment of the system:
Once the development and testing is done the system is deployed in the consumer
environment
Maintenance:
After the deployment of the project, the client environment may come up with issues .in order to
fix those issues, security patches and updates are released for product enhancement. Maintenance
is aimed at providing necessary improvements for the system in the client environment.
7. Tools of project management:
The execution of project management is a challenging task with lot of complexities and any
single tool is not sufficient for the purpose to handle all the requirements (Schwalbe, 2015).
Following are the two standard project management tools commonly used:
 Program Evaluation Review Technique (PERT)
 Gantt Charts
8. Conclusion and recommendation:
The report concludes that software that needs to be designed for the SG medical center is
quite approachable in terms design and complexity. Software design projects are subject to error
as the code designed for the program may not always work as expected .