Systems Analysis and Design Report: Data Structures and Systems

This report provides a comprehensive analysis of systems analysis and design, focusing on the development of software for Sydney Group Medical (SG Medical). The report begins with an introduction to data structure types, differentiating between primitive and non-primitive structures. It then outlines a proposed project schedule, assessing its feasibility and highlighting potential challenges. The core of the report delves into the development process, detailing weekly activities from initial requirements gathering to software testing and deployment. The discussion includes development methodologies, emphasizing the importance of a proper interface, coding language, and clear requirements documentation. The waterfall model is proposed as a suitable methodology, with a breakdown of its stages. The report also identifies project management tools, such as PERT and Gantt charts, and concludes with recommendations for improving project scheduling and management, including the need for a flexible schedule and experienced project managers. The overall aim of the software design is to increase efficiency in the medical process and data management.

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
Table of Contents
Introduction:....................................................................................................................................2
Data structure types:........................................................................................................................3
Primitive Data Structures.............................................................................................................3
Non-primitive Data Structures.....................................................................................................3
Entities relationship Diagram :........................................................................................................4
Project schedule:..............................................................................................................................4
Development of the system:............................................................................................................5
Week 1-3:.....................................................................................................................................5
Week 4-5:.....................................................................................................................................5
Documentation:........................................................................................................................5
Week 6-12:...................................................................................................................................5
Designing of the software:.......................................................................................................5
Testing of the system:......................................................................................................................6
Week 13-16:.................................................................................................................................6
Is the Project Schedule reasonable:.................................................................................................6
Development Methodology:............................................................................................................6
Requirement of proper interface:.................................................................................................6
Requirement of proper coding language:....................................................................................7
Proper Description of Requirements:..........................................................................................7

2
SYSTEMS ANALYSIS AND DESIGN
Proper Description of Outcome:..................................................................................................7
Availability of Resources:...........................................................................................................7
Detailed activities of waterfall model..............................................................................................7
Analysis of requirement:..............................................................................................................7
Design of the System:..................................................................................................................7
Implementation:...........................................................................................................................8
Integration and testing:................................................................................................................8
Deployment of the system:..........................................................................................................8
Maintenance:................................................................................................................................8
Tools of project management:.........................................................................................................8
Conclusion and recommendation:...................................................................................................8
References:....................................................................................................................................10

3
SYSTEMS ANALYSIS AND DESIGN
Introduction:
The report discusses the various data structure types, which are primitive and the non-
primitive data structure types. The report also discusses the project schedule an it is stated if the
project schedule is justifies or not. Project presented discusses the case of development of a new
software. The software is to be designed for the Sydney Group Medical. The motive of the
software design is the increase of efficiency in the medical process thus causing a lesser number
of death cases. The doctors would be holding an unique doctor ID while the patients would also
be having a unique patient ID. While assigning a doctor to the patient a particular doctor ID
would be assigned against the particular patient ID. More than one doctor may attend a particular
patient. It should be made sure that after the admission of the patient the patient at least one
doctor should be assigned.
For the storage of the data as to how many patients the doctor is handling the SG Medical
wants to design this software. This will help in the efficient management of the data and would
also present the other details such as the date, time and the result of the report.
The concept of object oriented programming(OOP) can be used in order to do the
programming of the project (Smith 2015). The program will be written for the satisfaction of few
of the requirements. The first requirement involves that the software should be able to track the
record of the patient from any place. The system should not only track the record of the patient
but should also be able to arrange appointment for the patient. The software should be platform
independent that is should run on any operating system. The program should be developed
enough to allow the patient to pick any doctor the patient wants to visit.

4
SYSTEMS ANALYSIS AND DESIGN
Data structure types:
Primitive Data Structures
Primitive data structures are the basic type of data structure. As the machine level
instructions are initiated these type of data structures are capable of operating directly (Lafore
2017). Few type of primitive data structure involve integers, floating point numbers, character
constants, string constants and pointers.
Non-primitive Data Structures
The Non- primitive data structure is not as same as the primitive data structure on the
basis of complexity. The Non- primitive data structure is derived from the primitive form of data
structure.
The idea is to group all type of data sets, same or different and there is close relationship
present among the data items that are grouped. The Arrays, Lists and the Files all are grouped
under this category (Joyce and Weems 2016).

5
SYSTEMS ANALYSIS AND DESIGN
Entities relationship Diagram :
Project schedule:
The project schedule is so designed such that the project is completed within four
months. The coding, development and designing process may involve about three hours while
the testing process would be requiring one hour (Kerzner and Kerzner 2017). The schedule has
been set as per the requirement of the Medical hospital.
Below a week wise break up has been provided for the three month designing section of
the software. The various tasks around the week will range from the development of the project
to the testing an deployment of the software :

6
SYSTEMS ANALYSIS AND DESIGN
Development of the system:
Week 1-3:
How to proceed:
In this time span of three weeks the team will discuss on how to proceed with the
software design. For the answer the requirement of the project has to be known properly. The
tools that are required are also identified. This is the most important part as this part will help the
team identify its goal.
Week 4-5:
Documentation:
After the identification of the requirements, those are put in the documented format and
presented to the client. If the client approves the plan then the team can proceed with the project.
Week 6-12:
Designing of the software:
After the approval of the client the designing part of the software starts. The team needs
to get hold of all the tools that are required during the completion of the project. In this duration
the code is written and executed and after the completion of the execution it is deployed in a
dummy environment in order to check if the program is carrying out the required tasks. The
program would be done with the concept of object oriented programming and a long duration is
allotted for the designing purpose as this is the most difficult and complex part.

7
SYSTEMS ANALYSIS AND DESIGN
Testing of the system:
Week 13-16:
The system is tested in this week span and if any error occurs then it is rectified in the
code. If the system runs and executes in a proper manner then the software can be handed over to
the client.
Is the Project Schedule reasonable:
The project schedule is tough to satisfy and achieve with respect to the fact that the task
is complex in nature. At the starting of the project the schedule may seem achievable. However,
in reality the satisfaction of the schedule is not possible as there may be unexpected errors that
may pop in the middle of the project. The project schedule does not look reasonable as errors
may even take place at the time of the testing process and all this would again require the
checking of the design and would again effect the project schedule and gradually would not meet
the overall schedule.
Development Methodology:
The development methodology would involve the processes that may be involved or required for
the proper development of the software. Few of them are:
Requirement of proper interface:
The proper interface should be provided so that the best quality software can be developed.

8
SYSTEMS ANALYSIS AND DESIGN
Requirement of proper coding language:
The design of an efficient software requires the use of the best form of coding platform sitable
for the task.
Proper Description of Requirements:
The requirements as to what tools should be used should be mentioned clearly in the
requirements.
Proper Description of Outcome:
The outcome of the development of the software should be clear.
Availability of Resources:
The resources should be available in abundance such that there may be sudden
requirements of various tools while the project is ongoing.
The best way such that the iTech may achieve all the above said criteria in the process of
design of the developments of the Sydney Group Medical System software the use of Waterfall
model should be made (Rouse 2016). The model can very easily analyze the requirement of the
project and the tools that are necessary for the completion of the project.
Detailed activities of waterfall model
Analysis of requirement:
The requirement of the project is analyzed in this part of the analysis.
Design of the System:
A rough design of the system is made in order to get the idea how to proceed with the project.

9
SYSTEMS ANALYSIS AND DESIGN
Implementation:
The implementation of the design is made in this step of waterfall model.
Integration and testing:
All the units of the previous stage are united together and after the development of the
units each of the units are tested.
Deployment of the system:
After completion of all the processes and testing the software is finally deployed.
Maintenance:
The maintenance of the software is also an equally important part as the issues may continue to
arise and it is responsibility of the team to handle these issues as well.
Tools of project management:
Project Management being a complex and lengthy process is not an easy task to be achieved
and use of any one specific tool is not sufficient for this purpose (Martinelli and Milosevic
2016). The two most generally used project management tools are:
 Program Evaluation Review Technique (PERT)
 Gantt Charts
Conclusion and recommendation:
From the report it can be concluded that the software that has to be designed for the SG
Medical has to be very structured and efficient as that is responsible for the storage of large
number of data. The proper implementation of such type of big and major projects involve the

10
SYSTEMS ANALYSIS AND DESIGN
proper planning and setting up the requirements. For this the report puts forward the idea of
project scheduling. The report also discusses if the project schedule is reasonable or not as this
may arouse future problems for the organization undertaking the project and the organization
that is getting the project done. The Water fall model has also been discussed, which is another
trusted method for the designing, implementation and the deployment purpose of any project.
Other than these the organization should also follow the ethics code of conduct during the
implementation of the project.
The recommendation is to improve the project schedule and design a project schedule
that is flexible and can be adjusted if any issue arises mid way of the project. A well trained,
experienced manager is also necessary for proper management of the work and the proper
management of the people.

11
SYSTEMS ANALYSIS AND DESIGN
References:
Joyce, D.T. and Weems, C., 2016. Object-oriented data structures using Java. Jones & Bartlett
Publishers.
Smith, B., 2015. Object-oriented programming. In Advanced ActionScript 3 (pp. 1-23). Apress,
Berkeley, CA.
Rouse, M., 2016. Waterfall model. Essential guide: CIO guide to project management basics
DevOps and Agile, pp.1-50.
Martinelli, R.J. and Milosevic, D.Z., 2016. Project management toolbox: tools and techniques
for the practicing project manager. John Wiley & Sons.
Kerzner, H. and Kerzner, H.R., 2017. Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Lafore, R., 2017. Data structures and algorithms in Java. Sams Publishing.