Act6_SYI

profilehybridtek
Mo5.docx

Project One System Requirements Specification (SRS) Template

Complete this template by replacing the bracketed text with the relevant information in each section. If there are sections that you believe, do not need to be considered in this SRS (based on the scenario provided), type in "Does not apply." Then provide a 1- to 3-sentence rationale for why that section does not apply to this system.

The content in this file is an annotated outline specifying high-level system requirements, adapted from the ISO/IEC/IEEE 29148 International Standard (2011), page 44.

References

ISO/IEC/IEEE. (2011). International standard: Systems and software engineering—life cycle processes—requirements engineering 29148. Switzerland. Retrieved from https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6146379

System Requirements Specification

Millennia HealthCenter

Name:

Date:

Table of Contents 1. Introduction 3 1.1 System purpose 3 1.2 System scope 3 1.3 System overview 3 1.3.1 System context 3 1.3.2 System functions 3 1.3.3 User characteristics 3 1.4 Definitions 3 2. References 3 3. System requirements 3 3.1 Functional requirements 3 3.2 Usability requirements 3 3.3 Performance requirements 4 3.4 System interface 4 3.5 System operations 4 3.6 System modes and states 4 3.7 Physical characteristics 4 3.8 Environmental conditions 4 3.9 System security 4 3.10 Information management 4 3.11 Policies and regulations 4 3.12 System life cycle sustainment 4 3.13 Packaging, handling, shipping, and transportation 4 4. Verification 5 5. Appendices 5 5.1 Assumptions and dependencies 5 5.2 Acronyms and abbreviations 5

3. System requirements

The system requirements present a very diversified approach on what the new system being implemented will entail, mainly the functional requirements and non-functional requirements that meet the interest of consumers and the dedicated effort for use and implement ability in respect to system inputs and management capabilities.

3.1 Functional requirements

The functional requirements work best at making the doctors and system users able to implement their transactions will ease and make the flow of work sustainable. One of the main inputs in functional requirement is transaction handling from when the patient checks in at the receptionist; only the system input will be used without having o deal with any paperwork needed to record the patient's data. Transaction handling means the ability for all stakeholders to fully rely on the system requirements without any risk of patient data confidentiality and integrity when completing tasks related to operations and patient booking.

The system will offer sustainable input for administrative requirements, mainly handling patient data and finding patient records through system use. The new system will be using patients' identification numbers issued by the system, which captures user data, and anytime the patient's data is fed in the system, it becomes easy to identify the data based on all the other elements rather than relying on insurance or jobs. The system functional requirement will remove any errors and delays in implementable system actions that make workflow effective.

The other functional requirement will be on system communication, which means the user in each department can upload information in the system. It is working in real-time, which offers conveniency in information sharing. Dedication, confidentiality, and information sharing are mainly controlled by the level of clearance used by the user within each department. Specific use of data is included in the development of strategic use implement ability.

The unified system will be managing and controlling all the operations in the organization, which makes it easy to conduct audits in the operations both for the level of work done by each employee of the organization and income generated through the development of sustainable measures for the dependency of data and systematic development of inputs and realistic.

The last functional requirement will be on speed of system management. The time required to serve each patient will have to get low as the system's patient holding capacity, processing power is high, creating efficiency, and not an employee will work in fa of choosing the wrong patient. Patient records will always come with user identification images on the profile, which the user or the patient can confirm and have clearance certification between the primary information that needs to be shared. Indeed, the system will present the real definition of convenience and ease of use to increase productivity.

3.2 Usability requirements

The users in the organization are the various stakeholders in the system, starting from the receptionists, system administrators, nurses, doctors, and pharmacists in the organization. All the stakeholders need a system that is unified in all departments and serves users' interests with a lot of ease. In that instance, the system will offer the greatest ease of use. Each user will have a login interface with a specified job role that comes with the level of clearance required to access patient data easily. All the information will be happening in real-time, meaning no time wasted in getting the other department's information or checking patients on progress.

The useability requirements will also come with ease of use, mainly in patient's data through service requirement that patients currently cleared in one department are forwarded in the next department in more like a queue meaning the other party already knows what to do even the patient arrives. For instance, if the patient has an appointment with a doctor, the patient's clearance with the receptionist will immediately reflect on the doctor's pending appointments. After clearance by doctor and needs some medicine, the patient will be reflecting on pharmacy as pending to get medication. Once cleared, the system will show which department needs to go next, creating convenience in usability.

3.3 Performance requirements

The performance requirements revolve around three main attributes: patient data privacy, system unity in all departments, and accuracy in access and error elimination. The system will stipulate patients' information into sections needed for people with each need in data privacy. For example, nurses, doctors, and pharmacists will not need to worry about patients' information falling into the wrong hands or being exposed. The system will be working as a unified system with only one that serves all departments' interests and presents information in the most natural form. The last performance input will include accuracy by error elimination and presentation of data from booking to system management inputs. The outcome of the entire management procedures will make workflow efficient and performance in terms of time spent recording patient data so fast, leaving a great room to serve more patients.

3.4 System interface

The system interface will differ depending on the input in place and the person with the role being implemented. The system interface will be the most interesting to use, which makes users feel engaged and offers confidentiality and access to information with ease. It means, based on the work done by the nurse or patients, key input methods will be visible, with bright background and information development options following orderly in tabular forms that are easy to interpret. The admins are the ones who will have higher access to patient records but will not be able to change the data. That is not their responsibility. In a real sense, the system will help easy work for each person in terms of job role and job description.

3.5 System operations

The system will operate ideally based on user specifications based on user interface and performance. As patients come in through the system, most of the patients will book online and have everything set meaning upon reaching the receptionist. It is just confirmation and directs the patient in the right direction. Thus, as each stakeholder in the system will have inputs in their user interface, the resulting outcome will reflect on performance, mainly the quality of services, accuracy, and unit time required to serve each patient with the right flow of information input done in real-time. All the issues that will impact or even slow the system's operations will handle by the user support under the technical team in the IT department.

3.6 System modes and states

The system can be controlled in its control unit to have the operational mode and maintenance mode, making it possible to offer actions on the system for proper utilization of services. In most cases, the maintenance mode will make the system inaccessible. However, in case of any emergency, a user can send a signal through the system emergency alert, and the right input can be offered to the system input actions. The main aim of the system mode is to ensure information is not tempered with and during maintenance and operations mode.

3.7 Physical characteristics

The system will be operated under the corporate website, accessible through user login credentials. The users can log in to the system website and accessing patient data in real-time. Using the website is normally easy as each patient can easily sign into the system, make bookings, conduct the conductor, and even have a provision for video conferencing with the doctors and nurses when making inquiries and even booking appointments and patients' follow-ups after discharge. The data will be backed up every day and connected to cloud services for security and storage systems.

3.8 Environmental conditions

Does not apply.

The system will run independently on the organization's requirements, which will not be part of any environmental conditions. The system will be purely neutral to any political and environmental factors that can impact the organization.

3.9 System security

System security will have the greatest input for the organization. The only way to access the information is by offering login credentials, even for patients who create their user profiles. At the same time, the patients will not understand important history recorded unless with the help of doctors or people with proper clearance. The main information will be on booking appointments, the number of appointments, and the normal personal data such as user identification information.

Data protection will be greatly significant through encryption, mainly for data backups in the cloud services and data stored in the organization. The passwords, mainly for the employees, will be unique for each member and will not require auto- remember meaning it will need to be keyed in. In case of more than three wrong attempts, the user will be put on hold, and an alert will be sent to system support. Data security is the greatest priority in the system.

3.10 Information management

System information management will be managed through the user interface to know the right user and the amount of information the user has access to and maintain patient's privacy at the greatest level of certainty and control input. As the system will be working as a unit, communication between the departments will be made easy. The different system databases will be linked to give the best flow of work and information. Information will be controlled at the operational, management, and strategic levels to ensure the free flow of information and even relaying feedback.

3.11 Policies and regulations

The system will abide by all policies and regulations set mainly when handling patient's data in terms of cyber security threats and set standards, confidentiality, and flow of information in the most realistic format of compliance, mainly to HPIAA training for ensuring safety and fraud prevention.

3.12 System life cycle sustainment

The system life cycle sustainment will be done through a website; system analytics will serve important roles in making all the outcomes get reviews mainly for performance, speed, maintenance, data collection, and workflow analysis. User feedback on the challenges made will be evaluated when making quarterly returns analysis.

3.13 Packaging, handling, shipping, and transportation

Does not apply.

The system will operate in a healthcare system will not need any shipping or packaging.

References

High-quality health systems in the Sustainable Development Goals era: time for a revolution. 

https://www.thelancet.com/commissions/quality-health-systems

Health care information systems: a practical approach for health care management.

https://www.wiley.com/en-us/Health+Care+Information+Systems

5

Project One

System Requirements Specification (SRS)

Template

Complete this template by replacing the bracketed text with the relevant information in each

section. If there are sections that you believe

,

do not need to be considered in this SRS (based

on the scenario provided), type in

"

Does not apply.

"

Then provide a

1

-

to 3

-

sentence rationale

for

why that section does not apply

to

this system.

The content in this file is an annotated outline specifyin

g high

-

level system requirements,

adapted from the ISO/IEC/IEEE 29148 International Standard

(2011)

, page 44.

References

ISO/IEC/IEEE. (2011).

International

s

tandard: Systems and software engineering

l

ife cycle

processes

r

equirements

engineering

29148

. Switzerland. Retrieved from

https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6146379

Project One

System Requirements Specification (SRS) Template

Complete this template by replacing the bracketed text with the relevant information in each

section. If there are sections that you believe, do not need to be considered in this SRS (based

on the scenario provided), type in "Does not apply." Then provide a 1- to 3-sentence rationale

for why that section does not apply to this system.

The content in this file is an annotated outline specifying high-level system requirements,

adapted from the ISO/IEC/IEEE 29148 International Standard (2011), page 44.

References

ISO/IEC/IEEE. (2011). International standard: Systems and software engineering—life cycle

processes—requirements engineering 29148. Switzerland. Retrieved from

https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6146379