CS230

Requirements Engineering

2022 Feasibility Report

Record Management
System
Central Hospital

Prepared For: Prepared By:

GROUP 3

Central Hospital Suva ID Name

S11194519 Aditi Sodagar
[62 Ratu Sukuna Road, Suva, Fiji]
S11198967 Karan Parmar
[+679 – 2867675] S11199815 Savindya M. Fernando
S11187832 Repeka Tawale
Table of Contents

List of Figures ....................................................................................................................................... 3

List of Tables ......................................................................................................................................... 3
1. Scope & Viability........................................................................................................................... 4
2. Executive Summary ..................................................................................................................... 5
3. Background Information .............................................................................................................. 6
4. Elicitation Techniques Applied ................................................................................................... 7
5. Proposed System ......................................................................................................................... 9
5.1 Description of the System ........................................................................................................ 9
5.2 Advantages and Disadvantages of the Proposed System ................................................ 11
5.3 Staffing ...................................................................................................................................... 12
5.3.1 Skill matrix ......................................................................................................................... 12
5.3.2 Activity matrix .................................................................................................................... 13
5.4 Space Requirements............................................................................................................... 14
5.5. Basic Layout (Architecture) ................................................................................................... 15
5.6 Cost benefit Analysis............................................................................................................... 19
5.6.1 Software Development Cost ........................................................................................... 19
5.6.2 Annual cost after Installation .......................................................................................... 20
5.6.3 Benefits .............................................................................................................................. 21
5.6.4 Cost Benefit ....................................................................................................................... 22
5.7. Computer Software Requirements ...................................................................................... 23
5.8. Site Possibilities .................................................................................................................. 25
6. Feasibility Study ............................................................................................................................. 26
Technical Feasibility....................................................................................................................... 26
Economic Feasibility ...................................................................................................................... 28
Risk Feasibility ................................................................................................................................ 30
Resource and Time Feasibility ..................................................................................................... 33
Social/Legal Feasibility .................................................................................................................. 34
7. Project Schedule ............................................................................................................................ 36
8. Final Recommendation ................................................................................................................. 38
9. References...................................................................................................................................... 39
10. Mark Allocation Sheet ................................................................................................................. 40
List of Figures

Figure 1: Skill Matrix ................................................................................................. 12

Figure 2: Basic layout ............................................................................................... 15
Figure 3: A Web Page .............................................................................................. 16
Figure 4: Receptionist Portal .................................................................................... 16
Figure 5: Doctor Portal ............................................................................................. 17
Figure 6: Patient Portal............................................................................................. 17
Figure 7: Secretary Portal ........................................................................................ 18
Figure 8 : Project Schedule ...................................................................................... 36
Figure 9 : Gantt Chart............................................................................................... 37

List of Tables

Table 1: Activity Matrix ............................................................................................. 13

Table 2 : Cost Estimation Table ............................................................................... 19
Table 3: After Installation Costing Table................................................................... 20
Table 4: Benefits ...................................................................................................... 21
Table 5: Cost Benefit Analysis Table........................................................................ 22
Table 6: Feasibility Study Table ............................................................................... 35
 1. Scope & Viability

Manual system leads to bulky paperwork and long delays in attending to patients.
The objective of this project is to reduce the paperwork by providing portals to the
staff, so that the staff can assist the patients well. With the new developed system,
the receptionist can record all patient’s information and medical details into the
system and send them to their respective doctors. Doctors will be able to access
that information when log into the portal. Doctors will also be able to update their
patient’s medical details via the portal. Patient’s medical records will be private and
securely stored in AWS cloud data center. Only relevant users can access the
patient’s records.

The limitation of the system includes internet accessibility and system breakdown.
All relevant users need to have 24/7 internet accessibility in order to access the
records stored in AWS cloud. System breakdown may occur due to simultaneous
access from the users or a possibility of a power cut.

The advantages of the new system (Portal) that it can be easily accessed and used
by the patients and the hospital staff, it improves the hospital management, patients
won’t have to wait in long queues to book appointments and they also don’t have to
visit the hospital to collect the lab results which can be easily viewed in the patient
portal. They can also sync their medical records to various connected health devices
allowing them to discuss their health betterment.

The new developed system will be manageable and viable. It would be worth
implementing as it will reduces long waiting hours for patient to get looked at by the
doctor. Medical stuff faces a lot issues when addressing to the needs of patients or
stakeholders manually. There is a dire need of such system to cater for all sorts of
information. The system will make patients wait lesser and get treated fast and
effectively. Since their details will be readily available in the system. Doctors or
receptionist would not have to be running around looking for the patient’s previous
medical report but access that information via mobile phones or tablets.

CS230 Page 3
 2. Executive Summary

A hospital is responsible in providing the most effective possible way to get their
patients attended quickly. With over hundreds of sick and injured patients coming to
the hospital in a day to get treated, there is a need to have a system to serve the
patients and doctors for managing their records and help them to coordinate
effectively. Looking for their medical report in a bunch of filling cabinet or even
making a new file for a new patient can be time consuming and very tiring. This
system can be a major booster and very effective, the patients can see the
information in matter of seconds and it can be passed them to their respective
doctors. Doctors can access patient information from their personal mobile phone or
laptops via the doctor portal. Thus, the system will also provide portability and
accessibility. The hospital can take advantage of the automated services provided by
the system to manage the records of all the departments and provide a health living
to the patients.

CS230 Page 4
 3. Background Information

The main purpose of a hospital is to provide the best complete health care for all
patients. Over the years, hospitals in Fiji lack computerized health information
systems that added to the woes of the already overloaded staff in the hospitals.
Manual practices of filling patients record have been causing unnecessary delays for
both patients and health workers.

The new system would be able to solve problems occurring at the hospital. The six
departments will be able to use and interact with the new system easily and
effectively.

CS230 Page 5
 4. Elicitation Techniques Applied

Requirement elicitation is discovering requirements while working with the customers

from the application domain. The systems analyst of them team gathers
requirements about the services that the system should provide and the operational
constraints of the system to meets the needs of the customers. A wish list is
gathered for each stakeholder before starting the elicitation process.

There are several approaches of gathering requirements, for this application domain
it would be suitable to use interviews, questionnaries and documentation for
collecting the requirements for the application domain. For the system analyst used
the following elicitation throughout the development of a new system in the hospital:

Interviews

Interviews include the application domain expert and the system analyst working
together to collect information about the system. Organization reports, annual reports
and long-range planning goals of the hospital were reviewed before initiating the
interview. The system analyst conducted a structured interview with the domain
expert to gather consistent and unambiguous requirements. Interview assisted in
building a strong business relationship between the domain and system analyst.
Interview also assisted in verifying facts, clarifying ambiguity, identifying end-users
and requirements, opinions and ideas. Few local civilians were briefly interviewed to
determine their experience and the services provided by the hospital.

Questionaries

A questionnaire is one of the most essential elicitation strategies since it allows

collection of data. It can quickly gather facts, suggestions and behaviors from the
targeted audience. A valid sample size was determined for distributing the
questionnaires. Survey monkey was used to prepare a wide range of questions and
questionnaire was distributed among the stakeholders of the system. Most of the
questions were multiple choice and scale rating to understand the working of the
current system.

CS230 Page 6
 Documentation

Documentation is a technique where existing documents are analyzed and evaluate for
possible requirements. The analyst from the team gathered information about the
organization goals, the people, the workflow and many more using some documents of the
hospital like the manuals, job descriptions and reports. It helped in clarifying the
requirements by differentiating between what is current and what is not, thereby giving a
foundation for future analysis. It supported useful material that are already in place and
available to use. (Canvass, 2021)

CS230 Page 7
 5. Proposed System

5.1 Description of the System

A central hospital, located in Suva Fiji, intends to own an online platform which will
allow hospital staffs to manage patient records, appointments and finance. This
system will also provide a portal to patients to check their records, e-prescription and
book appointments. The system will majorly use by 6 departments, namely the
Outpatient department (OPD), Inpatient Service (IP), Operation Theatre Complex,
Pharmacy Department, Radiology Department (X-ray) and Medical Record
Department (MRD). Each of these department consist of 5 doctors (including a head
of department). Other staffs using this system are Head Doctor of the hospital, 5
receptionists, 5 secretaries, 50 nurses and 10 lab technicians.

As per the requirement, the system will be a portal web application which will be
accessible in both, smartphones and personal computers. This web application will
consist of four main portals and one home page. These include;

• Home Page

This page will contain an introduction about the hospital. It will also contain the list of
departments and its details upon clicking on it. Furthermore, the home page will
provide option to login as per the user using the system. These options will be;
Patient, Doctor, Receptionist and Secretary. The user will be required to login into
the desired portal and will be greeted with a personalized interface (portal).

• Patient’s Portal

This portal will allow patients to interact with the hospital via the online platform. The
patient will be required to login into the portal to access the facilities. If the patient is
new, he/she will be required to sign-up. The patient portal will have a personalized
interface which will mainly allow users to book appointment in the given
departments. Additional functionalities will include; allowing them to view their
medical details, facilitating for online payments, receiving e-prescriptions and
allowing printing and download in PDF format, and permitting patients to connect
and sync their data from health devices into the medical records in the system.

CS230 Page 8
 • Doctor’s Portal

This portal will facilitate doctors with personalized interaction with the hospital via the
online platform. The doctor will be required to login into the portal which will
authenticate the doctor (this will be verified by the system). Once login is authorized,
the doctor will be greeted with a personal interface which will allow doctors to check
any scheduled appointment (Automated appointments) with any patient. Doctors can
confirm, cancel and reschedule appointments via the same portal. Furthermore, the
doctors will be able to update patient’s record and information once seeing them.
Doctors will also be able to send e-prescriptions to patients if needed to.

• Receptionist’s Portal

This portal will mainly allow receptionists to record patient’s details into the system
and allude them to a particular doctor. The receptionists will have details of every
doctor in each department which will allow the receptionist to refer to patients to an
appropriate doctor. The portal will provide facilities to capture thorough details about
the patients such as the patient’s medical conditions, allergies, medications,
surgeries, vaccinations, hospitalizations, family history, social history, and
contraindications. The receptionist will be able to view regular patients visiting
different departments.

• Secretary’s Portal

This portal will allow the secretary to keep details of financial records, and generate
relevant financial monthly, quarterly and yearly. Furthermore, the secretary will have
detailed records of doctors, nurses, practitioners and other staff, and also be able to
generate periodical reports. The secretary will also be able to send newsletter to
subscribe users which may include, patients, doctors, and other eligible users.

CS230 Page 9
 5.2 Advantages and Disadvantages of the Proposed System

Advantages of the system:

• The web application contains all the key components of a hospital such as
tracking the patient’s medical history and scheduling appointments.
• The web application also provides newsletters to users and doctors. This will
help the hospital to engage with the users in a personalized way by sending
relevant material and promotions to their inboxes.
• The application is user friendly allowing easy use to the target audience that is
patients, doctors, finance department and secretaries.
• The application is extremely secured as all the data including the patient
portal details is stored in the AWS cloud data center.

Disadvantages of the system

• Since it is a web application it would not work with internet, so there is a need
for high internet speed connectivity.
• The system will not include auto updates. Hence, if a new staff has been
appointed, the system developer needs to be called in order to make a new
portal for that staff.

CS230 Page 10
 5.3 Staffing
5.3.1 Skill matrix

Figure 1: Skill Matrix

CS230 Page 11
 5.3.2 Activity matrix

Responsible Accountable Consulted Informed

Project Aditi Karan Repeka Savindya
Planning
Information Savindya & Karan Karan Aditi
design & Repeka
analysis
Graphic Aditi Repeka Savindya Karan
Design
Content Karan Savindya Aditi Repeka
Development
Testing Karan Savindya Repeka Aditi
Publishing Savindya Aditi Repeka Karan
Maintenance Repeka Karan Aditi Savindya

Table 1: Activity Matrix

CS230 Page 12
 5.4 Space Requirements

The space requirements would be elaborated more in the feasibility report. The
space requirements for the system are listed as follows:

• A small room to place the servers for the system.

• Computers for Receptionists, Doctors, Finance department, Secretaries and
other departments to use the web application online.
The space requirements add cost to the development of the system which is
included in the cost benefit Analysis.

CS230 Page 13
 5.5. Basic Layout (Architecture)

AWS Cloud
Data Center
Hosted by
Hostinger

Patient Portal Web Application

• Book Appointment (Home Page)
• View medical results
• Pay medical bills • Login into Secretary Portal
online respective
• Receive e- portals • Send newsletters
prescription • View financial
reports
• Sync data from
health devices • View staff details

Receptionist Portal
Doctor Portal
• Add patient
• Schedule
information
appointments
• Refer patient to
• Update patient’s
respective doctor
records
• Review regular
• Receive appointment
patients visiting each
reminders.
department

Figure 2: Basic layout

CS230 Page 14
 Wireframes

Figure 3: A Web Page

Figure 4: Receptionist Portal

CS230 Page 15
 Figure 5: Doctor Portal

Figure 6: Patient Portal

CS230 Page 16
 Figure 7: Secretary Portal

CS230 Page 17
 5.6 Cost benefit Analysis
5.6.1 Software Development Cost

Cost Elements Details Cost per Unit Totals

Hardware The hardware required for $8242 $8242
the system that is
computers for staff to use
the system.
Web hosting The web service provider, $4.99USD/month $120 yearly ($60
Hostinger provides three USD/year)
plans for hosting a website.
The most suitable plan for
this system would be the
business plan.
AWS Cloud AWS cloud data center to $200 $200
store the data securely

Software Cost required to develop to $40,000 $40,000

Development whole system

User-training Cost involved in training the $1000 $1000

user to use the newly built
system.
Total $49,562

Table 2 : Cost Estimation Table

CS230 Page 18
 5.6.2 Annual cost after Installation

Cost Elements Details Cost per Unit Totals

Internet and Estimated electricity $0.34 $5242
electricity bill for a year
Maintenance System needs $1000 $1000
maintenance every
year and if
necessary, updating
or adding features
for example adding
a new department
detail.
Web hosting The web service $4.99USD/month $120 yearly ($60
provider, Hostinger USD/year)
provides three plans
for hosting a
website. The most
suitable plan for this
system would be the
business plan.
Routers, servers $3000 $3000
and power backups
Total $9362

Table 3: After Installation Costing Table

CS230 Page 19
 5.6.3 Benefits
Category Details Totals
Finance Financial transactions and $50000
reports can be generated via
the system so there will be
no need for extra hands.

Promotion Newsletter are sent to $30000

subscribed patients to which
creates reputation of the
hospital among people
Total $80000

Table 4: Benefits

CS230 Page 20
 5.6.4 Cost Benefit

Cost/Benefit
Year 0 Year 1 Year 2 Year 3 Year 4 Year 5 Total
Analysis

Benefit $80000 $80000 $80000 $80000 $80000

Value
Discount 0.9 0.8 0.7 0.6 0.5
Present $73,394.50 $69266.68 $67284.10 $67263.17 $69149.68 $346,358.13
Value
Benefit
Initial Cost $49562 $49562
of Project

Ongoing $9362 $9362 $9362 $9362 $9362

cost
Discount 0.9 0.8 0.7 0.6 0.5
Present $8588.99 $8,026.41 $7,642.18 $7,415.58 $7,335.37 $39008.53
Value Cost

Table 5: Cost Benefit Analysis Table

CS230 Page 21
 5.7. Computer Software Requirements
Functional Requirements:

1. The system shall allow the doctors to view the services, timings and non-
working days on their calendar.
2. The system shall allow the Doctors to view appointments to confirm,
reschedule, and cancel patient appointment bookings.
3. The system should also send a reminder to the doctors regarding their
upcoming appointments.
4. The system shall allow the doctors to update the patient’s record and
information after seeing them.
5. The system should allow the relevant Doctors to view the patient details
including health conditions, allergies, medications, vaccinations, surgeries,
hospitalizations, social history, family history, contraindications.
6. The system shall allow the relevant users to view the daily patients visiting the
hospital for each department.
7. The system shall provide options for email/SMS/push notifications to patients
and providers.
8. The system shall allow the patients to view the e-prescriptions with printing
and PDF downloads via the patient portal.
9. The system should allow the users to view the recorded results.
10. The system should record the hospital finances and generate relevant
financial reports monthly, quarterly, and annually.
11. The system should record all details of hospital staffs and generate relevant
reports from them.
12. The system shall allow the secretaries to send newsletters to patients and
doctors.
13. The system shall record finances and generate relevant financial reports
monthly, quarterly, and annually.
14. The system shall record the details of hospital staff and allow the head of the
hospital and the secretary to view the generated relevant reports.
15. The system shall allow the secretary to send newsletter to the patients and
the doctors.

CS230 Page 22
 16. The system shall allow the patients to sync their data from various connected
health devices into their patient health records.
17. The system shall allow the receptionists to record the patient’s details and
refer them to respective doctor/specialist.

Non-functional

1. The system should be accessible via smartphones and desktop PCs.

2. Since it is a system made for a hospital, the system should be available 24/7.
3. The system shall have zero downtime deployment.
4. The data in the system shall be securely stored in AWD cloud platform.
5. All the user’s history should be confidential unless required by a doctor.
6. Any user who wishes to use the system should login using a valid username
and password.
7. The system shall offer data backup.
8. The system should support 500 users at a time.

CS230 Page 23
 5.8. Site Possibilities

The site will be preferably located in the staff’s computers of Suva Central Hospital.
The web application will be accessed via any web browser, either on a personal
computer (PC) or a smartphone, by doctors, secretaries, receptionists, and patients.
The main reason for the location of the site is that it will serve as a medium to
manage records of the hospital. The location will also be best suited for the doctors
to coordinate with the receptionist about the patients for setting up appointments and
refer them to respective specialists.

CS230 Page 24
 6. Feasibility Study

A feasibility analysis or feasibility study assesses the feasibility of a project idea from
different perspectives. The goal is to allow top managers to narrow down their
choices and make informed pass or fail decisions.
The five key areas that need to be covered in the overall feasibility study are:

a Technical Feasibility

Inspects whether software can be built with all tools and experts available.

1 hardware and software components

Hardware needs

Hardware is required to create the web application for the hospital record
management. Therefore, the hardware components used during the web application
development are few mid-spec personal computers. All of this will be available to the
project team in the assigned workspace. The use of servers, routers, and other
devices, is to install at least a model of the hardware system to get the fastest possible
response. Management relies heavily on lower network delays in addition to a stable
internet connection. Therefore, the host server should be located as close to the end
user as possible. If the first traffic path fails, the second traffic path takes over
immediately.

CS230 Page 25
 Software needs

The management of Suva Central Hospital is considering the dissemination of the

technology and believes that a newly developed system is what they need.
Hospital wants to develop a system consisting of an excellent hospital record
management that can collect and record patient data, health status, vaccinations,
allergies, and email / SMS / push notifications and appointment reminders. With the
help of this software, doctors can view appointments and also if desired, review,
reschedule or cancel appointments. It should also be included to provide detailed
financial and personnel reports.
The team has chosen to use Visual Studio as a platform and build the web
application by using HTML and CSS followed by JavaScript.

2 Capabilities of the engineering team

Capabilities of each team member is essential as the team should have enough
skills and resources to develop the app with a given technology background and
considers not only the current state of the chosen technology but also the
maintainability and future scalability of the product.

CS230 Page 26
 b Economic Feasibility

Economic valuation is an important part of investment, dealing with factors that can be
financially quantified, measured and compared (Chen, 1996).
The most influential factors which determine the final cost to build the hospital
management app are:

1 Development cost and essential services

Description Amount
Monitors and PCs $ 1000.00
Routers, servers and power backups $ 3000.00
Internet Charges $ 242.00
Electricity $ 5000.00
Total $ 8242.00

2 Mobile platforms and devices supported

Description Amount
PC (macOS and Windows) $ 3169.00
Smart phones (iOS and Android) $ 2429.00
Total $ 5498.00

3 Ongoing maintenance Cost

Description Amount
Future maintenance $ 1000.00
Tax $ 1000.00
Total $ 2000.00

CS230 Page 27
 Complexity and number of app features based on size and level of development
4
team.

A feature is a particular action or undertaking that works with the software and gives the
desired outcomes. This can be more mind boggling, for example, logging in or signing
up to the patient entryway, or synchronizing patient information from different associated
clinical gadgets. The quantity of elements and the intricacy of their execution are
straightforwardly connected with the expense of building your application.
Clients are charged for web application development services in light of the accompany.
Fixed charge
An installment which suggests the expense charged for a particular timetable. This might
function admirably for the hospital record management project, particularly the
necessities are clear and obvious extent of work.
Time Material
A pricing structure that is ascertain by the time and resources required for a project and
along these lines is ordinarily determined in view of an hourly rate. This approach gives
adaptability during the application development process and fits more mind boggling and
continuous tasks.
The formula used to compute web application development cost is as per the following:

Total Hourly
Development × = Cost
Rate
Time

Total Development Time 4 months

Hourly Rate $ 11.50
Working Hours 8 hours
11. 50 * 8 *120 days * 4
Total Cost for the development Team
= $ 44,160.00

CS230 Page 28
 The advantage of economic feasibility is that the app development cost is affirmed
with the client before development starts.
Total Budget
Complexity and number of app features $ 44160.00
App development cost $ 8236.00
Mobile platforms and devices supported $ 5498.00
Ongoing Maintenance Cost $ 2000.00
Total Budget $ 60,000.00

c Risk Feasibility

Risk area Risks Action to reduce risks Risk Owner Risk

Level
Software Bugs and Software development Software
Broken Code and software testing developers, High
was inextricably linked Quality
to ensure a successful Assurance
release. The team Engineer,
Technology looked for small steps or Software
milestones and kept on Architect
validating at each phase
of the record
management system.

The time required for the • Each task was

software to be created given a time frame
was inaccurate. for completion.
• Developers have
been assigned an
Project
Time Estimation allocation time to High
Manager
investigate
particularly complex
or unknown parts of
the project and
avoid risks.

CS230 Page 29
 Uncertainly about the • Conducted User
product user actually testing and surveys.
adopts the new software. • Organized Focus
Quality
End-user groups for the
Assurance High
Management users.
Engineer
• Planned Frequent
releases and Beta
testing.

Team members are a • Reward and

crucial factor when it recognize team
comes to a development members
team. Loss of one • Offer flexible time
member will create allocation
additional costs for the • Have at least two
Project
Employee turnover business related to hiring additional team High
Manager
and training new members as backup
employees. members where
they can collaborate
and share
knowledge with the
key members

Unclear requirements • Additional questions

often lead to unwanted were asked about
glitches and accidents. In user needs and
Software addition, requirements to
Data analyst High
Requirements misunderstandings of understand the
needs can lead to huge requirements more.
waste of time and
money.

CS230 Page 30
 Developers tend • When deciding
to speed up the on group
design process as individuals the
design is the most project manager
important part of picked out
software individuals with
development. This superior
is a waste of knowledge on
programming user designing
time. and software
structure Process. User Interface
Compromising on • Placed software Designer,
developers and High
designs Software
user interface
Architect
designers or
system architects
in separate team
roles in the
development and
design process,
reducing the time
spent on
additional
responsibilities.

CS230 Page 31
 d Resource and Time Feasibility

Resource
This aspect looks at the resources needed to complete the project and whether the
number of resources available is sufficient to complete the project efficiently.
All the resources have been identified in order to produce a device compatible, user
friendly and easy to use health management app. The main resource of the development
process is the project management team. A team of four project members was selected to
develop the project with the team’s name “Digitally Dyslexic”. Furthermore, Software
component used was Visual Studio, where languages such as HTML, CSS and Java-
Script were used.
Furthermore, Hardware components such as Computers and laptops, routers and servers
were used.

Time
Time reflects the planning, timing, and start and end of projects related to other projects
and activities in the organization. As with any resource, time is limited and should be
managed carefully. Time feasibility study concentrates on considering the time expected
to finish the project. This is a proportion of the project rationality and subsequently decides
if cutoff times are alluring or compulsory. Setting cutoff times and determined items that
should be completed, keeps the task on track and centered.
Given our technical expertise the deadline for the project is mandatory. The large project
will divide into smaller phases and would give each stage a mini-deadline so that
employees will feel less overwhelmed and be able to focus on more manageable goals.
After a critical assessment and project analysis, estimated time is allocated for building
and developing the hospital record management system will take about 4 months
considering interference with normal business operations and dependencies. Team will
have more time to notice any mistakes and fixed them before the project is completed. It
is much easier to fix a problem in the beginning of a project than to go back and fix every
step of the project from the initial phase onward.

CS230 Page 32
 e Social/Legal Feasibility

Social

Social feasibility is one of the feasibility studies that considers people's acceptance of
the system to be launched. Before implementing any changes, some suggestions
were made to ensure user collaboration. The team describes
the impact of introducing the new system on users, considering whether labor-force
retraining is necessary.

Legal

Legal feasibility is a measure of how well a system can be implemented within an

existing legal and Organization’s Policy. The analyst considered the below facts about
the above feasibility study:

Description Solution
1. Will the system be approved by its The project is given approval from the
corresponding higher authorities? Government and the Ministry of
Health.
2. Will the system violate any legal The system will not violate any legal
issue in Fiji? aspect including copy right issues.
3. Are there any Political The system will not have any political
Repercussions in using the impacts on patients, nurses,
system? receptionists, secretaries, doctors and
lab technicians who will be using the
system.

CS230 Page 33
 4. Are there any conflicts between • There will be no conflict between
the proposed system and the legal the proposed system and the legal
requirement? contract as it will contribute
towards the development of the
medical sector in Fiji and the
Fijians with adequate care and
treatment by the proposed system.
• The Information Privacy act will be
taken into consideration by the
team while the system is being
developed.

Table 6: Feasibility Study Table

CS230 Page 34
 7. Project Schedule

Figure 8 : Project Schedule

CS230 Page 35
 Figure 9 : Gantt Chart

CS230 Page 36
 8. Final Recommendation

To conclude, the central hospital needs a system to manage the hospital records
and help the hospital staff serve patients effectively and efficiently. The proposed
system will serve the requirements of the hospital and automate all the work that is
currently done manually like booking appointments, adding patient records, sharing
e-prescriptions, generating hospital financial reports and many more. This system
will also help the hospital to get in touch with more people via newsletters. Living in
this digitizing world, hospitals do need an automated record management system to
facilitate patients with adequate care and treatment. Therefore, the system analyst of
the team suggests to build on this web application and start with requirements
elicitation and analysis process.

CS230 Page 37
 9. References

Altexsoft. (2022, january 06). Technical Feasibility in Software Engineering: Things

to Consider Before Development Starts. Retrieved from
https://www.altexsoft.com/blog/technical-feasibility/
Bidgoli, N. N. (2014, july 9). CHAPTER 10. BUILDING SUCCESSFUL
INFORMATION SYSTEMS. Retrieved from
https://www.slideserve.com/noam/building-successful-information-systems
Chen, M. (1996). Simplified project economic evaluation. Retrieved from
https://www.umsl.edu/~sauterv/analysis/F08papers/Katimuneetorn_Feasibility
_Study.html#
Lastovetska, A. (2022, March 7). App Development Cost: Understand Your Budget
To Build Powerful Apps. Retrieved from https://mlsdev.com/blog/app-
development-cost
Nantucket Nectars, H. B. (2014, july 4). CHAPTER 10. BUILDING SUCCESSFUL
INFORMATION SYSTEMS. Retrieved from
https://www.slideserve.com/noam/building-successful-information-systems
Roszczyk, W. (2022, march 12). Top 10 software development risks. Retrieved from
https://www.itproportal.com/features/top-10-software-development-risks/
Sveta Cherednichenko. (2022, February 22). How to Conduct the Technical
Feasibility Analysis in Software Development. Retrieved from
https://mobindustry.net/blog/how-to-conduct-the-technical-feasibility-analysis-
in-software-development/
T, C. (2021, september 9). Business Analysis. Retrieved from
https://businessanalyst.techcanvass.com/top-elicitation-techniques-for-
business-analysis/

CS230 Page 37
10. Mark Allocation Sheet

Group number ___3___ Project manager __Aditi Sodagar___________

Member Percentage Responsibilities

Student ID Contribution

S11194519 25% Proposed System, Final Recommendation

S11198967 25% Proposed System, Project Schedule

S11199815 25% Feasibility Study, Project Schedule

Scope and Viability, Executive summary, Elicitation

S11187832 25%
Technique applied, and Background Information

Signed

Member Name ID Signature

Aditi Sodagar S11194519 A

Karan Parmar S11198967 K

Savindya M Fernando S11199815 S

Repeka Tawale S11187832 R