Information Systems Analysis and Design

This report investigates and documents the system requirements for designing and developing a hospital information system (HIS). It discusses the different approaches to systems development, the functional and non-functional requirements of the system, and the cost benefit analysis. The report also includes the project schedule and techniques for system information requirement investigation.

COIT 20248: Information Systems Analysis and Design
Term 1, 2019
Assessment 1 - Systems Development
Lecturer: Lecturer Name
Tutor: Tutor Name
Prepared by:
Student Name
Student Number

Table of Contents
2. Approach to Systems Development..................................................................................................2
3. Systems Requirements......................................................................................................................2
4. Project Cost Benefit Analysis.............................................................................................................4
5. Project Schedule................................................................................................................................6
6. System Information Requirement Investigation Techniques...........................................................11
7. Reflections and Conclusions............................................................................................................12
8. References.......................................................................................................................................13

1. Introduction
The report aims in investigating and documenting the system requirements related to designing and
developing a hospital information system (HIS). The HIS is to be developed in order to improve the
efficiency of information storage and information management. The implementation of a hospital
information system is capable of improving the overall efficiency of providing medical help.
The following section of the report will discuss the different aspects of hospital management system
and the approaches to develop a HIS. The report further gives an overview of the functional and the
non-functional requirements of the system. The HIS to be developed is expected to provide business
benefit to the organization and therefore, the cost benefit of the system is analysed in the report.
The objective of the proposed project is to build a system that will be value for money and will work
in a long term basis. The system should be capable of dispatching e-prescription for the outpatients.
The project aims in providing training related to the operation of the proposed system so that the
users do not face any difficulty in operating the system. The report further gives an overview of the
project schedule and the techniques for system information requirement investigation.
Page 1

2. Approach to Systems Development
A number of software development methodologies are there to choose from, in
implementation of the proposed hospital information system. This section of the report will
discuss the methodology chosen in development of the hospital information system. The
proposed systems development methodologies include waterfall, agile, RAD and JAD.
The waterfall model of systems development is a sequential model that divides the entire
project into a number of smaller phases. Each of those project phases id designed to
perform certain specific activities (Turk, France and Rumpe 2014). However, start of each
phase depends on the end of each phase. One major disadvantage of making use of this
particular systems development methodology is that, the testing phase is mainly executed
after completion of all major phases (Törngren et al., 2014). Any issues if identified in the
testing phase will result in modifying the entire system.
The agile software development methodology on the other hand is mainly based on
iterative development approach (Hassan, Qamar and Idris 2015). In this system
development approach, the requirements and the solution of a system mainly evolves
through collaboration of self-organizing and cross functional teams (Popli and Chauhan
2014). The agile software development methodology has a benefit over waterfall model as
the agile model provides opportunities to incorporate changes in a project.
RAD or rapid application development is a part of agile system development method and it
mainly focuses on development of a working software by considering the users feedback
(Vijayasarathy and Butler 2016). The strict planning and requirements ordering is generally
absent in this system development method.
JAD or joint application development method is generally used for designing a computer
based system and is mainly associated with the development of a software through
continuous interaction with the user (Abrahamsson et al. 2017). Similar to agile and RAD,
this system development method considers users’ feedback as first priority (Despa 2014).
Therefore, JAD system development method is proposed as it brings users and developers
together while developing a particular system. JAD method of systems development proves
to be a cost effective approach as well.
3. Systems Requirements
This section of the report will identify the major functional and the non-functional
requirements of the proposed system.
The system that is proposed involves development of a hospital management system that
will enable better management of the patients’ data.
The primary functional requirements of the proposed system are as follows-
 The system should be incorporated with a unique patient identifier
 The feature of quick registration should be incorporated into the system
 Strong access control is to be incorporated into the system in order to ensure tight
security
Page 2

 The system should be capable of generating e prescription
 The system should provide its user a secure remote access to view the information
related to their health
 The system should be capable of generating automatic reports that will help the
stakeholders to track the patients’ information, services, material and medication.
The non-functional requirements of the proposed hospital management system are as
follows-
Security: Ensuring appropriate security is considered to be a major non-functional
requirement of a system (Eckhardt, Vogelsang and Fernández 2016). This is particularly
because the system that is proposed is a hospital information system and the system should
ensure confidentiality in storage and access of the patients’ data. Furthermore, it is being
proposed that the system will be able to provide secure remote access to the notes and
information as a primary functional requirement.
Usability: usability is another significant non-functional requirement of the system. Since
the hospital management system will be used and managed by patients of all age group, it is
quite essential to develop a system that will be easy to use and understand.
Less Response Time: The proposed application will be handling emergency cases and
situations as well and therefore, development of an application with less response time is
needed to be considered. Less Response Time is one significant non-functional requirement
that the system should consider using.
The above two paragraphs give an idea of the functional and non-functional requirement of
the proposed system. The software development process should consider all the proposed
functional and non-functional requirement to deliver a high quality hospital information
system.
Page 3

4. Project Cost Benefit Analysis
This section of the report will discuss the financial feasibility of the proposed project. The
cost benefit analysis process can be described as a systematic approach of defining the
feasibility of a particular project (Newcomer, Hatry and Wholey 2015).
The proposed hospital information system project is a critical project and therefore
calculating the ROI and NPV of the proposed project becomes a necessity.
RMO Cost/Benefit Analysis for
HIS
Year of
Project
year 0 year1 year 2 year 3 year 4 year 5 TOTALS
Net economic benefit $0.00 $3,18,000.00 $3,18,000.0
0
$3,18,000.0
0
$3,18,000.00 $3,18,000.00
Discount Rate 8% 1 0.9259 0.8573 0.7938 0.7350 0.6806
PV Of Benefits $0.00 $2,94,444.44 $2,72,633.7
4
$2,52,438.6
5
$2,33,739.49 $2,16,425.46
NPV of all BENEFITS $0.00 $2,94,444.44 $5,67,078.1
9
$8,19,516.8
4
$10,53,256.34 $12,69,681.79 $46,46,23
4.68
One Time Costs $7,50,000.00
Recurring Costs $0.00 $90,000.00 $90,000.00 $90,000.00 $90,000.00 $90,000.00
Discount Rate 8% 1.0000 0.9259 0.9259 0.9259 0.9259 0.9259
PV Of Recurring Costs $0.00 $83,333.33 $83,333.33 $83,333.33 $83,333.33 $83,333.33
NPV Of All Costs $3,18,000.00 $4,01,333.33 $4,84,666.6
7
$5,68,000.0
0
$6,51,333.33 $7,34,666.67 $29,33,16
8.78
Overall NPV $17,13,06
5.90
Overall ROI = (Overall NPV / NPV Of All Costs 0.58
Break-Even Analysis
Yearly NPV Cash Flow $0.00 $2,11,111.11 $1,89,300.4
1
$1,69,105.3
2
$1,50,406.16 $1,33,092.12
Overall NPV Cash Flow $15,81,000.00 ($1,06,888.8
9)
$82,411.52 $2,51,516.8
4
$4,01,923.00 $5,35,015.13
Project break-even occurs between years 1 and
2
Page 4

Use 1st year of positive cash flow to calculate break-even
fraction
106889/
(106889+104222)=0.506
0.5063
1 years +185days (0.506*365)
OR
1.506 years
Table 1: Table indicating the Cost Benefit Analysis of the proposed HIS Project
The project budget is $ 750000, and the discount rate is 8 percent. The system will help in reducing
the overall cost by $26,500 per month while that of the estimated maintenance cost is $7500 per
month.
The cost benefit analysis of the proposed project indicates a positive net present value (NPV) and a
positive ROI (Return of Investment) (ohansson and Kriström 2018). Therefore the project is
feasible (Hansson, Helton and Feiler 2018). The tangible benefit of the project is its positive ROI
(break even occurs in 1.5 years) while that of the intangible benefits of the project is increase in
efficiency of the hospital management process.
Page 5

5. Project Schedule
Project scheduling is an important aspect of project management. The system to be
developed is quite critical and therefore, appropriate project scheduling was necessary
(Kerzner and Kerzner 2017). Since it is software development project, all the related tasks
associated with the development of a software is considered. The project scheduling is done
considering the fact that JAD system development method is considered for development of
the system (Luna et al. 2014). The resources for the project has been allocated on a fixed
price basis. The scheduling is done by keeping into consideration the budget allocated for
the project. If the project follows this planned approach, it is possible to implement the
hospital information system proposed within the specific budget of $750,000.00.
The activities involved and the duration of each activity in development and implementation
of the proposed Hospital information is indicated in the figure below-
Page 6

The completion of each activity indicated in the figure above is necessary for successful
implementation of the project.
Page 7

The figure below indicates the Gantt chart generated as per the scheduling activities in the
project.
Page 8

Page 9

FIGURE 1: Representing the Gantt Chart of the HIS project
The Gantt chart in the figure above indicates the sequential activities that are involved in
development and implementation of the proposed hospital information system. The work
break down structure of HIS project is indicated in the figure below-
Hospital Information
System
Project starts Requrement Analysis
Understanding the project
requirements
Identifying the features to
be incorporated in the
System
feasibility study
Documentation
Milestone 1: Completion
of Requirement Analysis
Planning
Designing the system
structure
Allocating a project team
identifying the project
resources
Developing a project
schedule
Development of Project
Plan
Milestone 2: Approval of
Project Plan
Implementation
Framework
designing System
framework
Coding the system
Database
designing the database
coding the database
linking the applictaion with
the database
Milestone 3: Completion
of System Development
Testing
Unit testing
Alpha Testing
System testing
Beta testing
Usability testing
User acceptance testing
Debugging(if required)
Milestone 4: Completion
of Project Testing Phase
Deployment and
Training
Demonstrating the
application
Training the users
debugging(if required)
Milestone 5: Completion
of 1st Users Training
Project
Handover/Maintainance
Documents handover
Payment completion
Resource release
Client feedback and
maintainance
Arranging Second Training
Session
Projetc ends
Figure 2: Representing the WBS of HIS project
Each activities in the project has been allocated a significant and realistic time for successful project
implementation. The scope of the project involves delivery of a fully functional hospital management
system. The scheduling details indicate that it will take at least a year to complete the entire project.
Since a considerable amount of time is being allocated for the project, the project schedule is found
to be realistic. Following this approach of project implementation, it can be expected that the
project team will be able to deliver a fully functional hospital information system.
Page 10

6. System Information Requirement Investigation Techniques
The proposed project of designing a hospital information system is a critical project and
therefore, choice of an accurate system information requirement investigation technique
becomes essential. Prior to that, it is necessary to identify the stakeholders associated with
the project. The major stakeholders in the project and their interest is indicated in the table
below-
Stakeholders Interest Impact
Hospital Committee High Medium
Project Owner High High
Project Manager High Low
Software Development Team Medium Medium
Patients Medium High
Training Team Medium Low
The table above identifies the stakeholders associated with the project and their description
of interest in the project. The table identifies the main stakeholders of the project. In order
to keep the identified stakeholders engaged with the project, a communication plan can be
developed detailing the communication need, purpose and communication vehicle.
The proposed project is quite critical and therefore, identification of proper system
investigation requirement technique becomes essential (Morrison-Saunders et al. 2015).
Investigation of requirement generally follows a planned procedure of gathering
information, defining the requirements of the system, prioritizing the system requirements
and reviewing the recommendations (Conforto et al. 2014). There are a number of
requirement investigation techniques, such as reviewing the existing project reports,
conducting interviews, building prototypes, observing and documenting a business process,
conducting joint application design sessions and others. Out of these requirement
investigation techniques, the three most useful techniques include reviewing and analysis of
existing documents, observing the business process and conducting interviews and surveys.
Review of Existing Documents: This technique is useful as it provides an idea of the
mistakes that should not be repeated during system implementation.
Observing Business Process: The choice of this information gathering technique is justified
as well particularly because it helps in identifying the functionality of the system.
Conducting Interviews and Surveys: This method of information gathering is effective as it
helps in collection of information from sources having firsthand knowledge about similar
projects.
Page 11

7. Reflections and Conclusions
The project has helped me in developing a knowledge related to various system
development methods. While choosing a correct system development methodology for the
proposed project, I have researched about the different systems development process.
While working in this project, I have understood the importance of project scheduling and
financial analysis of the project prior to project start. The financial analysis of the proposed
project indicates that the project is feasible and should be implemented. However, one of
the main constraint that can affect the project is the time allocated for implementation of
the system. This is particularly because the JAD method involves users’ feedback in change
implementation.
The report gives an idea of the functional as well as the non-functional requirement of the
proposed system. The systems requirements and the cost benefit analysis of the project
indicates that the project is feasible and should be executed in a planned manner. It is
recommended that users’ feedback is to be taken during the implementation of the system
to improve its usability. The JAD system development method that is chosen is likely to
ensure that all the users’ requirements are met during the implementation of the proposed
hospital information system project.
Page 12

8. References
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Conforto, E.C., Salum, F., Amaral, D.C., Da Silva, S.L. and De Almeida, L.F.M., (2014). Can agile project
management be adopted by industries other than software development?. Project Management
Journal, 45(3), pp.21-34.
Despa, M.L., (2014). Comparative study on software development methodologies. Database Systems
Journal, 5(3), pp.37-56.
Eckhardt, J., Vogelsang, A. and Fernández, D.M., (2016), May. Are" non-functional" requirements
really non-functional? an investigation of non-functional requirements in practice. In 2016 IEEE/ACM
38th International Conference on Software Engineering (ICSE) (pp. 832-842). IEEE.
Hansson, J., Helton, S. and Feiler, P., (2018). ROI analysis of the system architecture virtual
integration initiative (No. CMU/SEI-2018-TR-002). Carnegie-Mellon Univerity Software Engineering
Institute Pittsburgh United States.
Hassan, S., Qamar, U. and Idris, M.A., (2015), September. Purification of requirement engineering
model for rapid application development. In 2015 6th IEEE International Conference on Software
Engineering and Service Science (ICSESS) (pp. 357-362). IEEE.
Johansson, P.O. and Kriström, B., (2018). Cost-benefit analysis. Cambridge University Press.
Kerzner, H. and Kerzner, H.R., (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Laplante, P.A., (2017). Requirements engineering for software and systems. Auerbach Publications.
Luna, F., González-Álvarez, D.L., Chicano, F. and Vega-Rodríguez, M.A., (2014). The software project
scheduling problem: A scalability analysis of multi-objective metaheuristics. Applied Soft
Computing, 15, pp.136-148.
Morrison-Saunders, A., Bond, A., Pope, J. and Retief, F., (2015). Demonstrating the benefits of impact
assessment for proponents. Impact Assessment and Project Appraisal, 33(2), pp.108-115.
Newcomer, K.E., Hatry, H.P. and Wholey, J.S., (2015). Cost-effectiveness and cost-benefit
analysis. Handbook of practical program evaluation, p.636.
Popli, R. and Chauhan, N., (2014), February. Cost and effort estimation in agile software
development. In 2014 international conference on reliability optimization and information
technology (ICROIT) (pp. 57-61). IEEE.
Törngren, M., Qamar, A., Biehl, M., Loiret, F. and El-Khoury, J., (2014). Integrating viewpoints in the
development of mechatronic products. Mechatronics, 24(7), pp.745-762.
Turk, D., France, R. and Rumpe, B., (2014). Limitations of agile software processes. arXiv preprint
arXiv:1409.6600.
Vijayasarathy, L.R. and Butler, C.W., (2016). Choice of software development methodologies: Do
organizational, project, and team characteristics matter?. IEEE software, 33(5), pp.86-94.
Page 13