Report: System Analysis and Design for SG Medical System

This report provides a comprehensive analysis and design of a new software system for the Sydney Group (SG) Medical System. It begins with an introduction outlining the need for system upgrades and the benefits of implementing new IT resources. The report details the data structure types required for managing doctor and patient information, including attributes like DoctorID, Specialty, PatientID, and PatientName. It then presents data modeling and an entity-relationship diagram using standard notations to illustrate the relationships between different entities within the SG Medical System. A project schedule is discussed, proposing a four-month timeline for development and testing, with detailed phases for conceptualization, front-end and back-end implementation, redesign, and testing. The report justifies the selection of the SCRUM methodology, emphasizing its suitability for the project's requirements. Detailed activities at each phase of the chosen methodology are described, along with techniques, models, and tools, such as PERT charts and Gantt charts, to support project development. The report concludes with recommendations for continued software development, emphasizing the need for an agile and user-friendly interface and a detailed data migration plan and process.

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

1SYSTEM ANALYSIS AND DESIGN
Table of Contents
Introduction................................................................................................................................2
Data structure types................................................................................................................2
Selection of data modeling, method, explaining, and drawing the entities relationship at SG
using standard notations.........................................................................................................3
Discussion on the project schedule........................................................................................4
Reasons for the reasonable project schedule..........................................................................5
Selection of suitable system development methodology with justification...........................6
Detailed activities at each phase of the selected methodology for project development.......6
Techniques, models and tools to support the project development activities........................8
Recommendation........................................................................................................................9
Conclusion..................................................................................................................................9
Reference..................................................................................................................................11

2SYSTEM ANALYSIS AND DESIGN
Introduction
Implementing a software system in any organization is the way to update the existing
system. Upgrading a traditional way of system demands the replacement of outdated ideas.
This calls for utilizing IT resources, which are appropriate for the implementation. It is to be
kept in mind that the system upgrading to the latest technology is built on the hope for the
betterment of the efficiencies. This is only done to increase the level of the services provided
to the clients (Abrahamsson et al. 2017). The following report would include the detailed idea
of introducing new software for handling the medical system in the organization called
Sydney Group or SG Medical System. The new system would have the provision for
assigning a patient to the relevant doctor on duty including other organizational strategies
regarding assigning patients. The system would also hold the details about a patient and the
treatment records. With the help of the iTech center, the organization plans to develop the
software using the functionalities of Object Oriented Programs, which would further include
all the records of the hospital staff in attending to specific patients. A schedule for
development of the entire software is to be made providing specific period for development
of the software along with the testing period.
Data structure types
The new software implementation in the system management for the Sydney Group
Medical System requires holding the attributes of the registered doctors employed in the
organization. This would have the attributes DoctorID and Specialty. The doctors admit the
patients to the hospital and these patients would have the attributes of PatientID and
PatientName. Assignment of a patient to the required doctors is dependent on the doctors.
The software would have the provision of making a patient history and treatment details
available to all the staff of the hospital and should be accessible from any computer in the

3SYSTEM ANALYSIS AND DESIGN
organization (Chess et al. 2016). In addition, this software would provide the patients in
booking appointments online both from the hospital website and from mobile application.
Therefore, considering these requirements, it could be said that the appropriate data
structure that could be used in developing the management software would be the basic
record data structure. It has the ability to implement a collection of fields with varied data
types taken in specific sequence (Bittencourt, Verter and Yalovsky 2018). A record database
implemented in Object Oriented Programming provides the procedure to hold numerous
records, having the ability to be viewed through the computer analog of a mathematical tuple.
Selection of data modeling, method, explaining, and drawing the entities
relationship at SG using standard notations
Data Modeling: The data modeling, method used and the systems of the SG medical
system being involved in the software according to the requirements of the software is
represented in the Data Modeling chart as described below:
Fig: Data Modeling for SG Medical Systems

4SYSTEM ANALYSIS AND DESIGN
Entity Relationship Model of SG Medical System: The relationship between the
different entities of the SG medical system being involved in the software according to the
requirements of the software using standard notations is represented in an Entity Relationship
diagram as below:
Fig: Entity Relationship Diagram
Discussion on the project schedule
Scheduling is the process by which a project is handled according to the development
procedure. A software development project cannot be handled properly if scheduling fails to
fall on order. A scheduling plan defines the exact deliverables of a project according to the
given time including the milestones that has to be delivered in the project timelines.
Scheduling delivers the guidance and pathway for a project to progress (Hossain et al. 2016).
It is necessary that the system management include a proper scheduling program according to

5SYSTEM ANALYSIS AND DESIGN
the requirements of the software development for the SG Medical System. The proposed
planning of schedule helps to monitor the problems due to which a project does not meet the
time proposed. The scheduling do not represent an actual project but is an estimation of how
a task is to be completed, at what time period and what resources should be used for the
completion of the tasks.
Reasons for the reasonable project schedule
The software development of the hospital management system of SG Medical System
has a proposed schedule of four months for the entire project. This would include three
months for the development of the software and coding while one month for the testing of the
software (Venugopal, Mathai and Abraham 2015). As the requirements of the project are
concerned, it is essential that the rigorous testing of the software be done to avoid any data
redundancies in the generation of patient bills (Turk, France and Rumpe 2014). According to
the requirements, the appointed doctors would admit the patients to the hospital. There is no
bound on the number of patients admitted by a doctor. Therefore, chances are there that data
duplicity may appear (Ying and Lei 2014). Testing for one month would rectify any mistakes
that have been there in the coding and development of the software. The Project Schedule
would include the following:
 Conceptual phase: 15 days
 Front End Design phase (Level 1–Level 3 Prototyping): 15 days
 Front End Implementation phase: one month
 Back End Implementation phase: one month
 Redesign phase: Redesign & Reengineering: 15 days
 Testing phase: One Month

6SYSTEM ANALYSIS AND DESIGN
Selection of suitable system development methodology with justification
It is required that before continuing with development methodology, project
requirements are checked thoroughly with the clinical context and the environment of the
Medical System, the primary and secondary user ends and the mapping of stakeholders. It is
possible only then to acquire a feasible user interface and system development (Thüm et al.
2014). The open source software that is being developed in this context is suggested
according to many literatures as per researches. This allows any user to contribute to the
software even without being in the same location. Hospital admissions may occur out of
medical emergencies even out of the hospital. Participation in the admission process can
happen at any time from any place irrespective of presence in the hospital. The more compact
the systems get with time; it would implement standard development technologies as
appropriate.
If the methodology is deviated, it may be possible that time constrains or team
shortage may occur as a result. However, by using the SCRUM methodology, the doctor’s
end could be developed (StClair et al. 2015). Since, the project requirements state that it
should be the decision of a doctor about how many patients to be admitted and it would
depend on them if they would attend to any patient appointed to them.
Detailed activities at each phase of the selected methodology for project
development
The software development process would depend on the selected methodology and
this would include the steps that will be discussed further in details. The project manager and
developer would implement the SCRUM methodology at first to decide the features to be
incorporated in the software. Since the Sydney Group assigns the project, therefore, it is
assumed that the project ownership would belong to the organization (Alexandros et al.

7SYSTEM ANALYSIS AND DESIGN
2017). Any alterations to the requirements depend upon the organization. However, the
stakeholders of the organization mostly belong to the medical background people. It can be
assumed that their IT skills are not polished enough to understand technical complexities, and
hence, the project head and the executive need to work as a team (Sanchez-Gordon, Sánchez-
Gordón and Luján-Mora 2016). The project development would require seamless
communication between these people.
Along with the process development, the advancement of the project should be
documented to have a documented description about the flowcharts and the project
advancement (Jan et al. 2016). The remaining system was utilized to generate the system
requirements. The developer and the tester utilized their own sense of the general
requirements of the software to bridge the gap of the lack in details.
The shortcomings in the existing system were solved by the prototype testing and
formulated the requirements. The data entity relationship of the database was provided in
Comma Separated Values or CSV with three databases (Naz et al. 2016). These are the
database of the existing system, the database of the new system and the database containing
dynamic data for testing.
The data migration details are described as below:
Before Start of
Parallel Run
During
Parallel
Run
Before the
cutover
Cutover After the
Cutover
Existing System
Database
Current Database Update Freeze data Migrate
Dynamic data
Discard
data
New System
Database (Test)
Sample data:
Static to Dynamic
Update Discard
data
Discard data Discard
data

8SYSTEM ANALYSIS AND DESIGN
New System
Database
(Production)
Static data:
Current dynamic
data
No Update Freeze
Data
Static data:
Current
Dynamic Data
Update
data
Table: Data Migration Technique
Techniques, models and tools to support the project development activities
It is essential to check the project development activities to see if the project plans are
being effectively executed according to the project schedule (Verner et al. 2014). The project
needs to be monitored for further checking of the probability of risks and measures taken to
tackle them in the process. These monitoring processes include the Program Evaluation
Review Technique or PERT for controlling the tasks necessary for the project and the Gantt
chart for reviewing the project timeline (Lesser and Ban 2016). Defining and controlling of
the task is done by PERT charts. PERT needs to implement the following steps to maintain
the project development activities:
 Identification of the specific requirement activities and milestones achieved
 Determination of the sequence of the activities required
 Construction of the network diagram that would implement the data modeling
plans
 Estimation of the time required for completing each activity, including the
optimistic time, the most-likely time and the pessimistic time
 Determination of the critical path with earliest start time, earliest finish time,
latest start time and latest finish time
The Gantt chart implementation would help in determining the time taken to complete
the task of developing the software for the Sydney Group hospital management (Keyes
2016). The implementation could be done in the following way:

9SYSTEM ANALYSIS AND DESIGN
 All the activities of the plan would be listed
 The timeline would include the days and weeks required for the allotted tasks
 The tasks would be plotted on to a graph
 Activities would be scheduled accordingly to gain a work development graph
Recommendation
According to the findings, it is recommended that the software development program
for Sydney Group Medical Centre should be continued for total implementation. The
techniques applied to carry on with the project planning and implementation of the software
program. The program might face challenges, as the users of the interface in the end would be
of medical background. This recommends that the developers make the software as agile and
flexible as possible. The feasibility of using it effortlessly would generate positive feedback
from the users, therefore it is recommended that the developers create the software making it
as less complex as possible.
Conclusion
Therefore, it can be concluded from the report as discussed, that the Sydney Group
Medical System should implement the new software to ease the admission of patients in the
hospital. The software would enable the easy admissions of patients from the appointed
doctor’s end. The software would provide the doctor to admit a patient on his or her own will,
even assigning a patient to a doctor. Right from the admission process, the management
software is capable of delivering flexibility, as the admission process is not confined only to a
static entry from a device. The software is to be made available from all the connecting
devices dynamically. However, it can be possible, that since the users are from medical
background, the software could be difficult to use for them since they are not used to IT

10SYSTEM ANALYSIS AND DESIGN
complications. Therefore, if the developers make the software easy to use it would be
accessible to the users as well. The software would also comprise of the billing systems based
on the information of the treatment of each patient including their patient ID and the
appointed doctor. The system would transfer to the administrator through the hospital
reception employees.

11SYSTEM ANALYSIS AND DESIGN
Reference
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Alexandros, N.K., Sakas, D.P., Vlachos, D.S. and Dimitrios, N.K., 2017. Comparing Scrum
and XP Agile Methodologies Using Dynamic Simulation Modeling. In Strategic Innovative
Marketing (pp. 391-397). Springer, Cham.
Bittencourt, O., Verter, V. and Yalovsky, M., 2018. Hospital capacity management based on
the queueing theory. International Journal of Productivity and Performance Management,
(just-accepted), pp.00-00.
Chess, B., Do, A., Fay, S. and Thornton, R., Hewlett-Packard Enterprise Development LP,
2016. Apparatus and method for developing secure software. U.S. Patent 9,400,889.
Hossain, M.S., Halim, M.A., Rahman, M.M. and Alam, K., 2016. A Method to Specify
Requirements for A Hospital Management Software. The Indonesian Management &
Accounting Research (IMAR), 5(1), pp.79-90.
Jan, S.R., Shah, S.T.U., Johar, Z.U., Shah, Y. and Khan, F., 2016. An Innovative Approach to
Investigate Various Software Testing Techniques and Strategies. International Journal of
Scientific Research in Science, Engineering and Technology (IJSRSET), Print ISSN, pp.2395-
1990.
Keyes, J., 2016. Social software engineering: development and collaboration with social
networking. Auerbach Publications.
Lesser, E. and Ban, L., 2016. How leading companies practice software development and
delivery to achieve a competitive edge. Strategy & Leadership, 44(1), pp.41-47.