The tasks You are assumed to be one of the software consultants appointed to shoulder the system analysis responsibilities in, the project outlined in, the case study. You will plan and manage the project as well as investigate and document its system requirements. You will produce a report that discusses this project based on your understanding of it and the related investigation results through the tasks below. Task 1: Approaches to Systems Development • How would you go about developing Hospital Information System? Compare different Software Development approaches to consider the best suited for developing HIS. • Justify the choice of your selected approach to systems development. Task 2: Systems Requirements • What are the primary functional requirements for the system in the case study? List and discuss Length: 2000 words these requirements. • What are the non-functional requirements for the system in the case study? List and discuss these non-functional requirements. Justify the choice of your non-functional requirements Task 3: Project Cost Benefit Analysis • Discuss your project Cost Benefit Analysis (CBA). CBA should focus the following two main points: a. To determine if an investment (or decision) is sound, ascertaining if – and by how much – its benefits outweigh its costs; and b. To provide a basis for comparing investments (or decisions), comparing the total expected cost of each option with its total expected benefits. • Provide an excel spread sheet with details in a Project Cost Benefit Analysis. Task 4:) Project Schedule • Show a work breakdown structure and a project schedule as a Gantt Chart. Explain both of them and discuss how they relate to each other. • Given the system goals, requirements, and scope as they are currently understood, is the project schedule reasonable? Why or why not? Task 5: System Information Requirement Investigation Techniques • Who are the stakeholders involved? • Explain your choice of the 3 most useful investigation techniques. • Justify the usefulness of these 3 investigation techniques. Information Systems Analysis and Design Assessment - Systems Development Lecturer: Lecturer Name Tutor: Tutor Name Prepared by: Student Name Student Number Table of Contents (TOC) Insert a word generated table of contents here How to create a table of contents in Microsoft Word 1. Apply the built-in Heading styles to the headings in your text. 2. In Word 2007 and Word 2010: References > Table of Contents > choose an option from the menu. 1. Introduction Add your contents here. Note: In this section, you provide a clear definition of the aims of this report. You also identify the project objectives. Explain all findings in the reporting document. 2. Approach to Systems Development Please add your contents here. There are many approaches to Systems development such as Water fall SDLC, Agile, RAD JAD. etc. You need to clearly explain which .

1. The tasks
You are assumed to be one of the software consultants
appointed to shoulder the system analysis responsibilities in,
the project outlined in, the case study. You will plan and
manage the project as well as investigate and document its
system requirements. You will produce a report that discusses
this project based on your understanding of it and the related
investigation results through the tasks below.
Task 1:
Approaches to Systems Development • How would you go
about developing Hospital Information System? Compare
different Software Development approaches to consider the best
suited for developing HIS. • Justify the choice of your selected
approach to systems development.
Task 2: Systems Requirements • What are the primary
functional requirements for the system in the case study? List
and discuss
Length: 2000 words
these requirements. • What are the non-functional requirements
for the system in the case study? List and discuss these non-
functional requirements. Justify the choice of your non-
functional requirements
Task 3: Project Cost Benefit Analysis • Discuss your project
Cost Benefit Analysis (CBA). CBA should focus the following
two main points: a. To determine if an investment (or decision)
is sound, ascertaining if – and by how much – its benefits
outweigh its costs; and b. To provide a basis for comparing
investments (or decisions), comparing the total expected cost of
each option with its total expected benefits.
• Provide an excel spread sheet with details in a Project Cost
Benefit Analysis.
Task 4:) Project Schedule • Show a work breakdown structure
and a project schedule as a Gantt Chart. Explain both of them

2. and discuss how they relate to each other.
• Given the system goals, requirements, and scope as they are
currently understood, is the project schedule reasonable? Why
or why not?
Task 5: System Information Requirement Investigation
Techniques • Who are the stakeholders involved? • Explain your
choice of the 3 most useful investigation techniques. • Justify
the usefulness of these 3 investigation techniques.
Information Systems Analysis and Design
Assessment - Systems Development
Lecturer: Lecturer Name
Tutor: Tutor Name
Prepared by:
Student Name
Student Number
Table of Contents (TOC)
Insert a word generated table of contents here
How to create a table of contents in Microsoft Word
1. Apply the built-in Heading styles to the headings in your
text.
2. In Word 2007 and Word 2010: References > Table of
Contents > choose an option from the menu.
1. Introduction
Add your contents here.
Note: In this section, you provide a clear definition of the aims
of this report. You also identify the project objectives. Explain

3. all findings in the reporting document.
2. Approach to Systems Development
Please add your contents here. There are many approaches to
Systems development such as Water fall SDLC, Agile, RAD
JAD. etc. You need to clearly explain which approach is
suitable for your project and why. Give justifications of
choosing your approach. Justfications can be provided by
discussing the advantages and disadvantages of approaches.
3. Systems Requirements
Add your contents here. You need to clearly address and explain
all Functional and non-functional requirements. Why you would
like to have your stated non-functional requirements. Simply
putting non-functional requirements in a dotted form is not an
explanation.
4. Project Cost Benefit Analysis
Add your contents here – Briefly explain what this section is all
about.
Discuss ROI, NPV and tangible and intangible benefits of this
project. Relate it to the table and the calculations you would do.
Table 1: Table Caption
Add your Project Cost Benefit Analysis table here.
5. Project Schedule
Add your contents here. Project Schedule should be drawn using
Gantt chart. Pay attention on pre and post tasks you have
identified. It must match with the approach you have chosen.
Add your Gantt Chart here.
FIGURE 1: Figure Caption
6. System Information Requirement Investigation Techniques

4. Add your contents here. Explain the useful techniques used to
investigate the new automated information system, and why
they are chosen. Give description and usefulness of each
identified techniques.
7. Reflections and Conclusions
Add your reflections about this project (e.g. achievement and
constraints), as a paragraph here.
Add your work of conclusions with a summary of your findings,
as a different paragraph here. Recommend whether or not the
project should continue/ how to continue.
8. References
Use Harvard Style referencing such as:
Satzinger, J., Jackson, R., and Burd, S. ( 2015). Systems
analysis and design in a changing world. Cengage Learning,
Boston, MA, USA.
Information Systems Analysis & Design
Case Study for Assignment
Designing Hospital Information Systems A Hospital Information
System (HIS) basically is a synonym for information
management system at use in hospitals. Hospitals generate a
wealth of data round the clock, 365 days a year, all of which
needs to be well managed to ensure efficient functioning.
Patients visit such as establishments for outpatient care in an
emergency, or get admitted for either a short stay (a few hours)
or long in duration (that may sometimes be indefinite). The
recent trend sees a growing emphasis on improving overall
efficiency and clinical management.
Important HIS Aspects to Consider Requirements Management
In the requirements gathering phase, one should undertake an
as-is study exercise to perform a comprehensive impact analysis
of all business processes in order to identify the ones that will

5. be affected by having the new system in place and the way this
will occur. The various business processes that exist, the
stakeholders involved and the systems / applications currently
being used within the establishment that would be affected,
albeit to varying degrees. Once this has been finalised and
agreed upon, a requirements analysis followed by
documentation needs to be prepared. Once finalised, the
software requirement specification and functional design
documents should be prepared with proper functional
architecture in place. These should be signed-off by the
competent authorities on both the customer and the vendor
sides. The documents should then be turned over to the system
design team for further action to ensure that the required system
is delivered as per the specifications.
General Requirements– An Overview Generally, the system
should be safe and secure from a data management point-of-
view. Highly sensitive data is handled by such systems and
hence the comfort-level related to privacy and safety issues
need to be addressed aggressively. The system should ensure
efficient flow of information that provides interdepartmental
support to the establishment, functional and process integration,
be adaptable and flexible from a user perspective, and last, but
not the least, be standards-based to ensure interoperability in
terms of syntactic, semantic and process. The following points
are that need to be given serious attention in order to build and
implement a viable solution that will be able to deliver true
value-for-money on a long-term basis: I. Use of a unique patient
identifier like UHID (unique health identifier); II. Quick
registration in times of emergency – use of “break-the-glass
feature”, with due record of who did what, when and why (the
reason for this action); III. Data security, patient confidentiality
and privacy; IV. User-based-role-based access control with a
sound and practical process using password/biometrics; V.
Eligibility check of all insurance and ability to accept an
upfront deposit to cover the estimated cost of care; VI. E-
prescription for outpatients, Computerized Physician Order

6. Entry (CPOE) for others; VII. For investigations, the consultant
needs to know the total costs and the individual investigation
charges. This would allow them to prioritise the ones that the
patients must get done right away irrespective of the costs while
leaving the rest later when they can afford them; VIII. The
Electronic Medical Record (EMR) needs to be integrated with
Laboratory Information System (LIS), Radiology Information
System (RIS) and Picture Archiving and
Communication System (PACS) to allow all images to be
viewed and compared with any archived images; IX. Secured
remote access to view information and add notes; X. Checking
for Economic Order Quantity (EOQ) and re-order levels and
automated listing of near-expiry items at least 90 days prior to
expiry; XI. Slow moving materials in the medical stores should
be tracked and appropriate alerts should ensure that all
stakeholders are aware of the situation; XII. Bar coding for
tracking patients, services, material and medication; and XIII.
Management Information System (MIS) reports that serve as de
facto registers will need to be maintained as per prevailing
rules, regulations and legal requirements.
A budget of $750,000.00 has been granted to develop the new
HIS. This total budget includes development cost, and any
other cost you can think of this project will incur. Estimated
discount rate of 8% is provided. It is estimated that the new HIS
system will help in reducing cost by $26,500 per month.
Maintenance cost could be estimated at around $7500.00 per
month.
Additional Observations
A fact that is frequently overlooked, mostly unappreciated and
grossly underestimated is that it is the end-user of any IT
system that makes or breaks it. It is vital to take them into

7. confidence and actively engage them right at the planning phase
itself and continued through each and every stage of the
software development life cycle. Otherwise one is, more often
than not, left to sincerely rue the decision. The importance of
training and retraining of all users can neither be over-stated
nor overemphasised and should not be just one-off.
Furthermore, the training needs to be periodic. Oneoff intense
training followed by periodic re-training is vital. Every major
upgrade or functionality change that would impact the business
process should be considered equivalent to a new
implementation. In all such instances, an appropriate training
schedule needs to be prepared and rigorously followed to ensure
the project’s success.