Scribd
Upload
144 views1 page

Non-Functional Requirements For The HCS

The document outlines 10 non-functional requirements for a health care system, including requirements for patient identification using personal health numbers, login IDs and passwords for users, administrative rights to modify the database, a 1 second maximum response time, supporting over 1000 users simultaneously, a user-friendly interface, data backup capabilities, error checking abilities, and 24/7 availability.

Uploaded by

Murad Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
144 views1 page

Non-Functional Requirements For The HCS

The document outlines 10 non-functional requirements for a health care system, including requirements for patient identification using personal health numbers, login IDs and passwords for users, administrative rights to modify the database, a 1 second maximum response time, supporting over 1000 users simultaneously, a user-friendly interface, data backup capabilities, error checking abilities, and 24/7 availability.

Uploaded by

Murad Ali
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

Non-Functional Requirements for Health Care System

i)

Patient Identification

ii)

Login ID

iii)

Modification

iv)

Administrators Rights

v)

Response time

vi)

Capacity

The system requires the patient to identify their-self using personal


health number.
The User who uses the system shall have a Login ID and Password
Any modification for the Database shall be done only by the
administrator in the ward.
Administrator shall be able to view and modify all information in
Health Care System.
The system shall give responses in one second after checking the
patients information.
The System must support more than 1000 people at a time.

vii) User Interface

The user interface shall be friendly.

viii) Back up

The system shall provide the capability to back-up the data.

ix)

Error Checker

x)

Availability

The system shall have the ability to check and correct the error.
The system shall be available 24/7.

You might also like