Question

In: Computer Science

Task # 3:          Identify Functional and Non-Functional Requirements for the given system description: The proposed...

Task # 3:          Identify Functional and Non-Functional Requirements for the given system description:

The proposed software product is the Hospital Patient Info Management System (HPIMS). The system will be used to get the information from the patients and then storing that data for future usage. The current system in use is a paper-based system. It is too slow and cannot provide updated lists of patients within a reasonable timeframe. The intentions of the system are to reduce over-time pay and increase the number of patients that can be treated accurately.

General Description:

Product Perspective

This Hospital Patient Info Management System is a self-contained system that manages activities
of the hospital as Patient Info. Various stakeholders are involved in the hospital patient info
system.

Product Functions

The system functions can be described as follows:

 Registration: When a patient is admitted, the front-desk staff checks to see if the patient
is already registered with the hospital. If he is, his/her Personal Health Number (PHN) is
entered into the computer. Otherwise, a new Personal Health Number is given to this
patient. The patient’s information such as date of birth, address and telephone number is
also entered into computer system.

 Patient check out: If a patient checks out, the administrative staff shall delete his PHN
from the system and the just evacuated bed is included in available-beds list.

 Report Generation: The system generates reports on the following information: List of
detailed information regarding the patient who had admitted in the hospital

User Characteristics:

The system will be used in the hospital. The administrators, front-desk staff will be the main
users. Given the condition that not all the users are computer-literate. Some users may have to be
trained on using the system. The system is also designed to be user-friendly. It uses a Graphical
User Interface (GUI).

 Front-desk staff: They all have general reception and secretarial duties. Every staff has
some basic computer training. They are responsible for patient’s check-in or notification
of appropriate people.

 Administrators: They all have post-secondary education relating to general business
administration practices. Every administrator has basic computer training. They are
responsible for all of the scheduling and updating day/night employee shifts.

General Constraints

 The system must be delivered by January 1st 2011.

 The existing Telecommunication infrastructure is based on IEEE100802.3 standards and
the system must conform to this standard using category 5 cables for networking

 The system must be user-friendly

Assumptions and Dependencies.

 It is assumed that one hundred IBM compatible computers will be available before the

system is installed and tested.

 It is assumed that the Hospital will have enough trained staff to take care of the system

Solutions

Expert Solution

Functional Requirements

Registration

When a patient is admitted, the front-desk staff checks to see if the patient
is already registered with the hospital. If he is, his/her Personal Health Number (PHN) is
entered into the computer. Otherwise, a new Personal Health Number is given to this
patient. The patient’s information such as date of birth, address and telephone number is
also entered into computer system
SRS001 Add patients
The HPIMS shall allow front-desk staff to add new patients to the system.
SRS002 Assign ID
The HPIMS shall allow front-desk staff to give each patient a ID and add it to the patient’s record. This ID shall be used by the patient throughout his/her stay in hospital.

Check Out

If a patient checks out, the administrative staff shall delete his PHN
from the system and the just evacuated bed is included in available-beds list.
SRS003 Delete Patient ID
The administrative staff in the ward shall be allowed to delete the ID of the patient from the system when the patient checks out.
SRS004 Add to beds-available list
The administrative staff in the ward shall be allowed to put the beds just evacuated in beds-available list.

Report Generation

The system generates reports on the following information: List of
detailed information regarding the patient who had admitted in the hospital
SRS005 Patient information
The HPIMS shall generate reports on patients about the following information: patient’s PHN, patient’s name, ward name, bed number and the doctor’s name which was assigned.
SRS006 Bed Aavailability
The HPIMS shall generate reports on bed availability about the following information: ward name, bed number, occupied/unoccupied.

Database

User Characteristics: The system will be used in the hospital. The administrators, front-desk staff will be the main
users. Given the condition that not all the users are computer-literate. Some users may have to be
trained on using the system. The system is also designed to be user-friendly. It uses a Graphical
User Interface (GUI)

SRS007 Patient Mandatory Information
Each patient shall have the following mandatory information: first name, last name, phone number, personal health number, address, postal code, city, country, patient identification number.
SRS008 Update Patient Information
The HPIMS shall allow the user to update any of the patient’s information as described in SRS007.

Non-Functional Requirements

Security

SRS009 Patient Identification
The system requires the patient to identify himself /herself using PHN
SRS010 Logon ID
Any user who uses the system shall have a Logon ID and Password.
SRS011 Modification
Any modification (insert, delete, update) for the Database shall be synchronized and done only by the administrator in the ward.
SRS012 Front Desk staff Rights
Front Desk staff shall be able to view all information in HPIMS, add new patients to HPIMS but shall not be able to modify any information in it.

They all have general reception and secretarial duties. Every staff has
some basic computer training. They are responsible for patient’s check-in or notification
of appropriate people
SRS013 Administrators' Rights
Administrators shall be able to view and modify all information in HPIMS.

They all have post-secondary education relating to general business
administration practices. Every administrator has basic computer training. They are
responsible for all of the scheduling and updating day/night employee shifts.

General Constraints

Performance Requirements

The existing Telecommunication infrastructure is based on IEEE100802.3 standards and
the system must conform to this standard using category 5 cables for networking

SRS014 Response Time
The system shall give responses in 1 second after checking the patient’s information.
SRS015 Capacity
The System must support 1000 people at a time.
SRS016 User-interface
The user-interface using GUI screen shall respond within 5 seconds.The system must be user-friendly Assumptions and Dependencies

SRS017 Conformity
The systems must conform to the Microsoft Accessibility guidelines

Maintainability

SRS018 Back Up
The system shall provide the capability to back-up the Data
SRS019 Errors
The system shall keep a log of all the errors.

Reliability
It is assumed that the Hospital will have enough trained staff to take care of the system
SRS020 Availability
The system shall be available all the time. It is assumed that one hundred IBM compatible computers will be available before the system is installed and tested. The system must be delivered by January 1st 2011


Related Solutions

1. Identify and briefly describe the functional and non-functional requirements for the proposed system
1. Identify and briefly describe the functional and non-functional requirements for the proposed system
I need al functional and non functional requirements and design constraints for this system: Payroll Management...
I need al functional and non functional requirements and design constraints for this system: Payroll Management System As the head of Information Technology at Mena, Inc., you are tasked with building a new payroll management system to replace the existing system which is hopelessly out of date. Mena needs a new system to allow employees to record timecard information electronically and automatically generate paychecks based on the number of hours worked and total amount of sales (for commissioned employees). The...
Q:Make a requirements document highlighting all functional and non-functional requirements as per the case above. Your...
Q:Make a requirements document highlighting all functional and non-functional requirements as per the case above. Your requirements must be validated for conciseness, completeness, non-ambiguity, verifiability, feasibility, and traceability: Register for the system by providing their name, Student ID and email address and a password Log in to the system by entering their Student ID and password Search for textbooks (by title or ISBN number or author) and scroll through the results of their search. The results of their search should...
Write down a list of functional and non-functional requirements for the following scenario that proposes to...
Write down a list of functional and non-functional requirements for the following scenario that proposes to develop a share management software. You are allowed to make any valid assumptions. A share management company wants to design software that can provide the latest information and investment strategies for their clients who are private investors and portfolio managers. The proposed software should present a holistic solution for clients to efficiently monitor their performance, dividends and successfully manage their portfolio. It should allow...
Please identify each property/requirement as a functional or non-functional. For every non-functional property/requirement, please add a...
Please identify each property/requirement as a functional or non-functional. For every non-functional property/requirement, please add a remark to explain why. Ticket Booking System Property/Requirement F: Functional NF: Non-functional 1 The system must perform the backup on a daily basis and weekly basis. 2 The users must be allowed to pick a web browser of their choice. 3 Users can call to book tickets. 4 The system must complete the request for booking a ticket in less than 5 seconds. 5...
Functional requirements for Product rating based on sentiment analysis and non functional requirments? This project aims...
Functional requirements for Product rating based on sentiment analysis and non functional requirments? This project aims to develop a sentiment analysis system for product rating. It is an e-commerce web application. The main goal of this sentiment analysis system is to understand the hidden sentiments of customers in feedback and comments and analyze their product rating patterns. When registered customers (they can create account by themselves and then modify their account) use this application to view products, product features, and...
Discuss different ways to identify functional requirements in a Functional Needs Assessment Process. Which is the...
Discuss different ways to identify functional requirements in a Functional Needs Assessment Process. Which is the most compelling, and why?
Discuss different ways to identify functional requirements in a Functional Needs Assessment Process according to your...
Discuss different ways to identify functional requirements in a Functional Needs Assessment Process according to your text. Which are particularly compelling to you, why? How do you think you could secure buy-in and participation in this process since it must take place before vendor demonstrations and site visits, with subject matter experts?
For a Desktop Browser create system requirements that consist of Functional, Data, and Performance requirements written...
For a Desktop Browser create system requirements that consist of Functional, Data, and Performance requirements written in Natural Language. Categorize the requirements into subsections according to functional areas, e.g., configuration, reliability, security, etc. Each Top-Level Requirement in Natural Language must be contained in a separate paragraph. The text of each requirement must be preceded by a unique identifier, to facilitate traceability. The identifier must have the following format: DWB-XXXX-REQ-#### Requirements text…………. The XXXX part is a requirement-type identifier and has...
Briefly explain what is meant by “non-functional requirements” and why they are documented separately from the...
Briefly explain what is meant by “non-functional requirements” and why they are documented separately from the functional requirements.
ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT