COIT 20248: Information Systems Analysis and Design.

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
1. Introduction.......................................................................................................................................1
2. Approach to Systems Development..................................................................................................2
3. Systems Requirements......................................................................................................................3
4. Project Cost Benefit Analysis.............................................................................................................4
5. Project Schedule................................................................................................................................6
6. System Information Requirement Investigation Techniques.............................................................9
7. Reflections and Conclusions............................................................................................................10
References...........................................................................................................................................11

1. Introduction
Presence of an information (IT) system in a hospital is essential to manage the data that is generated
round the clock for 365 days in a year. This report aims to understand the designing needs of a
hospital management system (HIS). This report will analyse the needs and the requirement
specification of the system to be deployed. For developing a HIS, at first, the requirement gathering
phase is to be executed well. The report aims to identify the system requirements of the chosen
project, requirement approaches to system development along with the financial viability of the
project. The following section of this report will further identify the functional and non-functional
requirement of the software system to be developed. The report further specifies the scheduling
needs of the information system to be built. Requirements gathering is a vital aspect of system
development, and therefore the report will be identifying the information requirement investigation
technique that will be followed in designing the proposed HIS. The report concludes with a
summary of the findings of the report.
Page 1

2. Approach to Systems Development
The success of a software development project largely depends on the approach chosen for
designing the software. It becomes integral for the project team to choose an approach
that will help in the delivery of the software on scheduled time (Kerzner and Kerzner 2017).
There are several approaches to software development such as Waterfall SDLC, Agile, RAD,
JAD and others. A specific approach of system development will be chosen based on the
needs and the requirement of the project to be delivered.
The waterfall method of system development can be described as a sequential model that
divides the entire project into several individual phases for easier management. In this
system development approach, the phases are completed sequentially. One of the most
significant advantages of this approach is that this particular approach of system
development involves detailed documentation (Schwalbe 2015). However, the major
disadvantage is that the testing phase comes quite late in the development process.
Waterfall model can be effectively implemented in software development when the
requirements are clear.
The agile method of software development is a widely used method as well. It is an
approach of software development that mainly evolves through a collaborative effort put by
cross-functional teams. One of the most specific advantages of the agile approach is that
this method of software development promotes continuous iteration throughout the
software development life cycle (Milosevic and Martinelli 2016). However, one of the most
significant disadvantages of this approach is that it is quite critical to access the actual effort
needed at the initiation of the software development. Furthermore, the documentation
process is not quite prevalent in agile.
RAD and JAD are part of an agile development framework. Rapid Application development
is an iterative process of designing software. It involves developing prototypes for
evaluation until the objectives of the software to be developed are met (Kerzner 2017).
Similarly, JAD is a process that makes use of users’ feedback in the development of the
software. The advantage of JAD and RAD is that the software is developed with a correct
specification. However, the disadvantage is that both RAD and JAD involves a lengthy
procedure of software development.
Therefore, an agile process is chosen as it will ensure effective system development by
dividing the project into several manageable units called sprints.
The choice of agile method is justified for this project as one of the major advantages of this
method is customer satisfaction. The agile software development methodology offers rapid
and continuous delivery of useful software. In this software development methodology, the
customers, testers and developers interact continuously for delivery of working software.
The only disadvantage of this method is that it lacks documentation. Since the requirements
of the chosen project are clear, the use of the agile method is justified for this project.
Page 2

3. Systems Requirements
The viability of a proposed system largely depends on the approach of systems development
(Heagney 2016). This section of the report will identify the primary functional and non-
functional requirements of the proposed system.
The functional requirements of the system proposed are as follows-
1. The use of this system is subjected to registration and login with a unique health identifier
as a part of added security.
2. The system will ensure access control. Access to the system will be controlled by making
use of passwords and biometrics.
3. The system will involve the generation of e-prescription that will increase the operational
efficiency of the system.
4. To ensure data access during emergencies, the system will involve the facility of remote
data access to its authorised users (Laplante 2017).
5. Automatic report generation of the health data and medical background of the patients is
another functional requirement of the system.
Along with the functional requirements, it becomes critical to identify the non-functional
requirements of the proposed system as well. The following paragraphs identify and justify
the need for major non-functional requirements of the system.
1. Security: Designing a secure system is one of the most significant non-functional
requirement of a system (Harrison and Lock 2017). The proposed HIS will be storing the
sensitive health details of the clients, and therefore it is quite essential to ensure maximum
security in the system (Eckhardt, Vogelsang and Fernández 2016). Therefore, security is one
of the most significant non-functional requirement of this proposed system
2. Performance: The proposed system should be able to deliver an improved performance
The system is to be designed in such a manner that along with management of the data, the
system can ensure effective information flow and improved performance (Adams 2015).
3. User-friendly Interface: The proposed system will mainly be accessed by the staffs and
the patients, and therefore, presence of an easy and user-friendly interface is one of the
basic non-functional requirement of the proposed system (Dabbagh and Lee 2014).
The above-discussed points give an idea of the significant non-functional requirement of HIS
that is proposed to be implemented.
Page 3

4. Project Cost Benefit Analysis
This section of the report will analyse the financial viability of the hospital information
system. A cost-benefit analysis has been performed on the assigned budget of the project
(Mir and Pinnington 2014). For developing a hospital information system, a budget of
$750,000 has been allocated. The discount rate considered for this project is 8%, and the
maintenance cost is estimated to be $7500 per month.
The financial analysis gives an idea of the Net Present Value (NPV) and the Return of
Investment (ROI) of the proposed project.
RMO Cost/Benefit Analysis of the
Proposed Hospital Information
System
Year of
Project
year 0 year1 year 2 year 3 year 4 year 5 TOTALS
Net economic
benefit
$0.00 $3,18,00
0.00
$3,18,00
0.00
$3,18,00
0.00
$3,18,0
00.00
$3,18,0
00.00
Discount Rate
8%
1 0.9259 0.8573 0.7938 0.7350 0.6806
PV Of Benefits $0.00 $2,94,44
4.44
$2,72,63
3.74
$2,52,43
8.65
$2,33,7
39.49
$2,16,4
25.46
NPV of all
BENEFITS
$0.00 $2,94,44
4.44
$5,67,07
8.19
$8,19,51
6.84
$10,53,
256.34
$12,69,
681.79
$46,46,
234.68
One Time
Costs
$7,50,0
00.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,0
00.00
$4,01,33
3.33
$4,84,66
6.67
$5,68,00
0.00
$6,51,3
33.33
$7,34,6
66.67
$29,33,
168.78
Overall NPV $17,13,
Page 4

065.90
Overall ROI = (Overall
NPV / NPV Of All Costs
0.58
Break-Even
Analysis
Yearly NPV
Cash Flow
$0.00 $2,11,11
1.11
$1,89,30
0.41
$1,69,10
5.32
$1,50,4
06.16
$1,33,0
92.12
Overall NPV
Cash Flow
$15,81,
000.00
($1,06,8
88.89)
$82,411.
52
$2,51,51
6.84
$4,01,9
23.00
$5,35,0
15.13
Project break-even
occurs between years 1
and 2
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: RMO Cost/Benefit Analysis of the Proposed Hospital Information System
The data from the above table indicates that the HIS project has a positive ROI and NPV. The break-
even analysis indicates that the proposed project will be able to gain profits within 1.5 years of its
implementation. Therefore, the project is said to have positive economic feasibility.
The tangible benefit can be measured in monetary terms. The tangible benefit of this project is that
the project will be able to gain profit within
Years. The HIS to be implemented with an increase the efficiency of delivering medical services,
which is the intangible benefit of the proposed project.
Page 5

5. Project Schedule
The work breakdown structure of the project is indicated in the figure below-
HIS
Project Starts Planning Phase
Meeting With Clients
Specification identification
Requirements Gathering
Sharing the Documents
with Clients for Approval
Development of a Project
Plan
Milestone 1: Approval of
Project Plan
Inititaion Phase
Development of the Project
Schedule as per plan
Development of Project
Budget
Approval of Schedule and
Budget of the Project
Development of Project
Charter
Milestone 2: Approval of
Project Charter
Execution Phase
Design Phase
Designing the Interface of
the Software
Finalization of the
graphical designs
Coding
Coding the Software
Database Coding
Linking the software with
the Database
Milestone 3: Completion of
Project Coding and Linking
with Database
Testing Phase
System Testing of the
Software
Beta Testing
User Acceptance Testing
Identification of Bugs in
the System
Fixing the Bugs
Milestone 4: Completion of
Software Testing
Training Phase
Identification of the
Training Participants
Identification of the
Training Needs
users' Training
Collection of Feedback
Setting up date for next
Training
Milestone 5: Completion of
Training
Evaluation Phase
Validation of the Software
Developed
Checking if the Project is
able to meet the
requirements specified
Verification of the
specification
Milestone 6: Detailed
Project Documentation
Closure Phase
Payment Completion
Client Sign Off
Resource Release
Documentation
Milestone 7: Project
Completion
The schedule Gantt chart of the project is indicated in the following figure-
Page 6

Page 7

FIGURE 1: Figure Representing the Gantt chart
The project schedule that is developed is quite realistic because an entire hospital information
system is to be developed. From the Gantt chart above, it can be observed that the information
system to be developed will take almost one year for completion (Marchewka 2014). The schedule
developed is realistic, which can help in achieving the project scope. The scope of the project is to
develop a system that can help in easier management of the patients’ data. The structure of the
hospital information system that is proposed can significantly help in developing the system.
The WBS prepared for the project matches with the schedule developed. The Gantt chart in the
figure above clearly indicates the major milestone of the project and the phases that are required to
be followed to ensure successful project completion (Too and Weaver 2014). The scope, goals and
requirements of the project are aligned with the schedule prepared for the project.
Page 8

6. System Information Requirement Investigation Techniques
In order to ensure the successful implementation of a project, it is quite vital to ensure
effective stakeholders’ engagement. The stakeholders associated with this project are as
follows-
1. Management of Hospital
2. Staffs and Employees
3. Project Sponsors
4. Patients
5. Trainers
6. Project manager
7. Software Development Team
Requirement identification is a critical step in the management and implementation of the
software. The three useful information requirement investigation techniques are as follows
–
1. Brainstorming: It is an effective process of requirement. Project reports of similar projects
can be evaluated to gather requirements of the current project (Abrahamsson et al. 2017).
2. Prototyping: This is another effective method of information gathering. Prototyping can
help in identifying the issues associated with the proposed system and can help in solving
them as well.
3. Interview: Interview is another effective process of requirements is gathering. The
process involves the collection of information from a specific group of individuals who might
know the subject (Plataniotis et al., 2015).
The above discussed three requirements gathering techniques are quite useful in the
implementation of this HIS. All three methods can help in gathering the required
information about the project.
Prototyping is considered to be one of the most effective techniques used in software
development as it helps in unveiling the errors in the system design approach. The other
two methods are equally effective in the collection of the requirements associated with the
implementation of the project (Kerzner 2019). This particular project must involve the use of
all these investigation techniques for the collection of appropriate information.
Page 9

7. Reflections and Conclusions
The report gives an idea of the requirement specification of a proposed project. Requirement
identification is mainly carried out at the initiation phase of the project, and it gives an idea of the
major operational needs of the project. While working on this assignment, I have understood the
importance of various requirements gathering tools and techniques. I have understood the
importance of calculating the cost feasibility and have understood the need for effective scheduling.
The report identifies the functional and non-functional requirement of the proposed IT project. It
provides a brief analysis of the cost consideration and the schedule consideration of the proposed
project. The report analyses the system goals, requirements and the scope of the project. The
proposed schedule is quite reasonable, and therefore it is expected that the project will be a
success.
Page 10

References
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., (2017). Agile software development
methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Adams, K.M., (2015). Nonfunctional requirements in systems analysis and design (Vol. 28).
Cham, Switzerland: Springer.
Dabbagh, M. and Lee, S.P., (2014). An approach for integrating the prioritization of
functional and nonfunctional requirements. The Scientific World Journal, 2014.
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.
Harrison, F. and Lock, D., (2017). Advanced project management: a structured approach.
Routledge.
Heagney, J., (2016). Fundamentals of project management. Amacom.
Kerzner, H. and Kerzner, H.R., (2017). Project management: a systems approach to planning,
scheduling, and controlling. John Wiley & Sons.
Kerzner, H., (2017). Project management metrics, KPIs, and dashboards: a guide to
measuring and monitoring project performance. John Wiley & Sons.
Kerzner, H., (2019). Using the project management maturity model: strategic planning for
project management. Wiley.
Laplante, P.A., (2017). Requirements engineering for software and systems. Auerbach
Publications.
Marchewka, J.T., (2014). Information technology project management. John Wiley & Sons.
Milosevic, D.Z. and Martinelli, R.J., (2016). Project management toolbox: tools and
techniques for the practicing project manager. John Wiley & Sons.
Mir, F.A. and Pinnington, A.H., (2014). Exploring the value of project management: linking
project management performance and project success. International journal of project
management, 32(2), pp.202-217.
Page 11

Plataniotis, G., Ma, Q., Proper, E. and de Kinderen, S., (2015), May. Traceability and
modeling of requirements in enterprise architecture from a design rationale perspective.
In 2015 IEEE 9th International Conference on Research Challenges in Information Science
(RCIS) (pp. 518-519). IEEE.
Schwalbe, K., (2015). Information technology project management. Cengage Learning.
Too, E.G. and Weaver, P., (2014). The management of project management: A conceptual
framework for project governance. International Journal of Project Management, 32(8),
pp.1382-1394.
Page 12