COIT 20248: Information Systems Analysis

and Design
Assessment 1

Contents
1. Introduction............................................................................................................................1
1.1 Aim:......................................................................................................................................1
1.2 Objective:.............................................................................................................................1
2. Approach to Systems Development.......................................................................................1
2.1 Developing Information System for Australian Institute of Technology............................1
2.2 Justification for Selected System development Approach...................................................2
3. Systems Requirements :.........................................................................................................2
3.1 FUNCTIONAL REQUIREMNTS:......................................................................................2
3.2 NON-FUNCTIONAL REQUIREMENTS..........................................................................3
4. Project Cost Benefit Analysis................................................................................................3
4.1 Explanation of Project cost benefit analysis........................................................................3
4.2 Excel sheet of cost benefit analysis......................................................................................4
5. Project Schedule.....................................................................................................................5
5.1 Work Breakdown Structure..................................................................................................5
5.2 Gantt chart providing Project Duration................................................................................6
6. System Information Requirement Investigation Techniques.................................................7
6.1 STAKEHOLDERS:.............................................................................................................7
6.2 THREE USEFUL INVESTIGATION TECHNIQUES:......................................................7
7. Reflections and Conclusions:.................................................................................................8
References..................................................................................................................................9
1. Introduction
Aims of the report:
The aim of the report is to develop and frame a Medical Center Management System based
on the needs of the given case study NMC. Hospital management program is designed to
meet the special needs of small and large hospitals worldwide. All the modules and features
required are specifically designed to meet your needs. Customers in India and overseas have
approved this kit. They are not only pleased and appreciative, they are extremely satisfied.
The entire application is cloud based and designed with the latest technology on 3-tier
architecture.
The application's sound database makes it easier to use and extend. The kit can be highly
personalized and tailored to our customers ' preferences and desires. Long analysis of the
functionality and basic specifications of the hospital has given it a great technical and usage-
oriented form. This includes all appropriate modules including registration of patients,
medications, doctor, wards, admin, storage, patient appointments, bill payment, record
changes, discharge information etc.

Project objectives
• Identify system requirements for System Management System
• Maintain the database
• Provide effective ways to keep track of deadline details
• Increase performance, usability of system

2. Approach to Systems Development

2.1 Developing Information System for NMC

Manual record keeping takes time and is particularly vulnerable to mistake. The purpose of
this project is to automate or render online the daily operations, such as room tasks, the
admission of new patients, patient discharge, doctor's appointments and finally measure the
bill and so on. I have tried my best by using organized & streamlined technique & menu-
oriented interface to make the complicated Hospital Management System as simple as
possible. Hospital is an important part of our life, supplying patients with different illnesses,
which could be triggered by change in the environment, heightened workload and mental
distress tension, etc, with the finest care services. The hospitals need to keep track of

Page 1
everyday events and accounts of their patients, physicians, health care professionals,
volunteers and other personnel that keeps the hospital functioning smoothly and efficiently.
But it is incredibly tedious and error prone to keep track of all the events and their reports on
paper. The measurement of constant population and number of patients attending a hospital is
often very inaccurate and time-consuming. It is inherently untrustworthy, inefficient and
error-prone to archive and preserve these papers. Also, keeping these notes on paper isn't
commercially and technologically viable. This keeps the manual method running as the base
of our project. An automated version of the manual system called "Health Institutions
Administration Support System" has been developed.
The key goal of this initiative is to have up to 90 percent with a paperless hospital. It also
attempts to provide the current networks with reliable, low-cost automation. The device
delivers excellent data protection on all user experience levels and provides recovery and
replication features that are comprehensive and efficient.

2.2 Justification for Selected System Development Approach

In our product growth phase, we employed the Iterative and Incremental Progress Model
(IID). This approach to construction is also called Iterative Waterfall Growth. Iterative and
Gradual development, designed to follow the more conventional waterfall paradigm, is a
software development technique. This model has been planned to accommodate such a large
undertaking. In specific, the broad and complex project calls for increased production and
research. The type of waterfall is renowned for its continuous cycle of checking. Therefore, I
prefer to build my program with the waterfall pattern.
The waterfall model has other advantages:
o Versatile and user-friendly.
o The rigidity of the model makes it easier to handle.
o Processes one at a time shall be assessed and completed
o Fits best with smaller projects with very well-understood criteria.

Page 2
 Fig 1. Waterfall Model

3. Systems Requirements :
Any framework of information needs is important to build. These are classified into two
groups of operational specifications, concentrating on what system needs to do and non-
functional requirements based on how the system should operate. (Eriksson 2012)
Specifically:

3.1 FUNCTIONAL REQUIREMNTS:

Functional requirements are as follows:
 Registration
Users must register to use the system
 Authentication
Employee, Doctors, Owners and customers must be given valid username and
password to access the system
 Authorization Level
Different users are given different accessibility depending upon there authorization
level.
 Payment
Payment record must be controlled by the system
 Audit Tracking
It will keep track of activities that affect the system

3.2 NON-FUNCTIONAL REQUIREMENTS

Non-Functional requirements for the system are as follows:
 Performance
Tells what response time of system is when the system is used by multiple users
 Capacity
Tells how much data can system store
 Maintainability
How well system is maintained whenever there is change done in the system
Page 3
 Security
Tells how safe the system is
 Usability
Tells about the user interface and how easily user can use the system

4. Project Cost Benefit Analysis

4.1 Explanation of Project cost benefit analysis

The most critical factor of implementing a program is cost-benefit analysis. We evaluate the
decisions through this method. It outlines both the project risks and benefits. The costs
accrued must be transparent, indirect, measurable, incentive and risk costs. Direct and
indirect income and intangible gains shall be the assets involved. On the basis of the project
cost benefit analysis, the practicable study is performed. Such three main criteria test whether
or not the proposal is feasible:
• Net Present Value (NPV)
• Return On Investment(ROI)
• Break Even Analysis(BEA)
Cost-benefit analysis is a straightforward method to calculate the value of a project against
the cost of its output. In the implementation process of the project, project administrators use
cost-benefit analyses to explain the importance of a project. The contractor and project
manager ought to explain the project at the start of the project to gain permission from the
organisation. The cost-benefit analysis measures the cost of the project to its market interest.
Few businesses tend to carry out projects that cost more than the amount they generate. This
means that project managers assess the cost-benefit by generating data about the gain interest
and the project expense.

All project-related calculations are provided in Excel Sheet. The project originally spent
$150,000 and was cut by 5%. The estimate is completed and the results show ROI is 28% and
the split only happens after 2 years and 95 days, which means that after 2.26 years we get a
return. This means that the Hospital life system's electronic initiative is feasible.

4.2 Excel sheet of cost benefit analysis

Page 4
 Figure 1: Cost benefit Analysis

5. Project Schedule
5.1 Work Breakdown Structure
The structure of work breakdown is essential to the life-cycle and scheduling of the project.
This explains the hierarchy of tasks and stages that illustrate the project process. The tasks are
specified and then divided into sub-tasks which indicates the number of levels of general
project knowledge. (Devi & Reddy 2012) This figure shows the breakdown of the project
work structure. The project has five activities such as the requirements research, device
research, coding & checking. As seen in Figure, these tasks are split further into subtasks.
These tasks indicate that they are intertwined and dependent on each other and influence the
length of the program.

Page 5
Work Breakdown Structure

1 Task Name Duration Start Finish

2 Planning 31 days 12/01/21 12/02/21

3 Design 28 days 13/02/21 13/03/21

4 Coding 29 days 14/03/21 12/04/21

5 Delivery 8 days 13/04/21 20/04/21

Page 6
5.2 Gantt chart providing Project Duration
The project schedule is the duration of the whole project's task. Activities depending on
which project costs are measured are described on these assignments. We can test the
feasibility of a project by using the project plan. (The 2010 Longer). The Gantt diagram
suggests the scope of the assignments. It indicates that all tasks can be done over a certain
timeframe, some of which are different. The entire project is finished within 260 days, which
demonstrates how practical this project is. This shows that we can defer and complete our
project by 105 days. The tasks are interrelated by a supervisor who says these have to be done
before new tasks start otherwise the duration of the project may increase. The allocation of
resources is also possible because of the project. There is a crucial way that says that these
tasks cannot be delayed because the project may be delayed.

Gantt chart

Page 7
6. System Information Requirement Investigation Techniques
6.1 STAKEHOLDERS:
Stakeholders are a group of individuals who are interested in project creation. (Jacksons &
Satzinger 2015 in Brussels). Two categories of stakeholders interested in this initiative are:

INTERNAL STAKEHOLDERS:
 EMPLOYEES
 DOCTORS
 OWNERS
 MANAGER

EXTERNAL STAKEHOLDERS
 GOVERNMENT
 CREDITOR
 SUPPLIER
 CUSTOMERS

6.2 THREE USEFUL INVESTIGATION TECHNIQUES:

Investigation methods are very effective in the design of applications because they tend to
satisfy various kinds of system construction criteria. They also state the participation of
multiple stakeholders. Many testing strategies such as interview, researcher, test, etc. are
available. We have taken the prototyping from this device production based on which the
most popular methods of study are listed below:

Interview & Question:

In this method, the participants in the previous framework are interviewed and information
based on the interview obtained. The interview will contain questions that are open-ended
and close-ended. This will allow us to see what are the weaknesses in the former program and
what the customers want from the current system.

Page 8
Usability:
This methodology can be conveniently used in this program implementation as the previous
system is paper based and asking customers can provide an understanding of whether a new
system is required.

Business Documents Analysis:

This approach analyzes the issue of the present structure, corporate principles and the
likelihood of meeting future specifications.

Usability:
This method is useful here, as it takes less time and the concerns relevant to the previous
system can be conveniently illustrated.

Prototyping:
Where fewer participants are involved and system development is difficult, prototyping
inquiry approach is used.

Usability:
That is a helpful strategy as the author can quickly adjust this according to request if the user
makes any changes to the program.

7. Reflections and Conclusions:

A small health facility, Number-One Medical Center (NMC) Inc. The organization presently
consists of eight wage-earning doctors, 12 nurses, 4 service personnel, and 3 employees.
Clerical staff conduct duties such as collection, email, cash refunds, payroll and arranging of
meetings. On the day of their appointment, most patients pay for treatment in cash or check.
But the doctor to provide the respective services often accepts loans on the basis of an
interview. The doctor file a report with one of the workers to establish a receipt for the data
created by the doctor when the payment is accepted. The constraints in this project include
teaching the user how to use the new program, internet access to the device, login
authentication, system repair and routine maintenance. The successes are that we introduced
the new program effectively over a given period of time and we benefit after three years.
After functional and not functional specifications have been defined, the Hospital
Management System concept was introduced using the Waterfall and Prototyping
methodology. We calculate the cost of the project and we analyze the preparation of the
project. This program is easy to understand and user friendly and holds all the details that
Page 9
avoid replication. In addition, all prior device issues are eliminated and implemented in
compliance with the user specifications and the budget given.

References

Arthur M. Langer, 2010, Analysis and Design of Information Systems,3 rdedition,
Springer-Verlag, London.

 Devi, T.R & Reddy,V.S,2012,’Work Breakdown Structure of the Project’, Journal of

Engineering Research and Application,vol.2,no.2,pp.683-686.Available from:
https://pdfs.semanticscholar.org/3233/5561af964619bba1bebad2bac5a155b58c52.pdf

 Eriksson, U,2012,’Functional vs Non Functional Requirements’. Available from:

http://reqtest.com/requirements-blog/functional-vs-non-functional-requirements/

 Investopedia, Cost Benefit Analysis. Available from:

https://www.investopedia.com/terms/c/cost-benefitanalysis.asp

 Satzinger J, Jackson, R & Burd, S 2010, System Analysis and Design in a changing
world, 5th edition. Cengage Learning, Boston.

 Valacich, J, George, J & Hoffer, J 2015, Essentials of systems analysis and design, 3rd
edition. Pearson Prentice Hall, Upper Saddle River, N.J.

Page 10