Software Metrics and Requirements Specifications
Software Metrics
Process Metrics
Quality-Related Metrics: Focus on the quality of work products and deliverables. To improve service quality, stakeholder needs and expectations should be monitored and measured. Shortfalls should be identified and addressed.
Productivity-Related Metrics: Production of work products related to effort expended. Examples include user satisfaction, average calls per hour, staff effectiveness, fine collection rate, and turnover.
- Statistical SQA data: Error categorization and analysis (e.g., number of errors reported)
- Defect removal efficiency: Propagation of errors from one process activity to another
- Reuse data: The number of components produced and their degree of reusability
Project Metrics
Every project should measure:
- Inputs: Measures of the resources (e.g., people, tools) required to do the work.
- Outputs: Measures of the deliverables or work products created during the software engineering process.
- Results: Measures that indicate the effectiveness of the deliverables.
Examples: Person-months, cost, lines of code, difficulty level, total absentees per month, revenue per employee.
Library Management System SRS
1. Scope
Update the library system to enable users to:
- View details of available books
- Borrow books up to a maximum limit
- Pay fines after the due date
The system will also provide functionalities for:
- Inserting book details
- Deleting books
- Issuing books
- Calculating fines
- Receiving user feedback
2. Functional Requirements
2.1 Registration
Users will register to the LMS by providing details such as name, address, phone number, and email address.
2.2 Sign Up
After successful registration, users will receive a unique membership ID and password to sign up to the system.
2.3 Search Book
After entering a book name keyword, a list of related books will be displayed.
2.4 Issue Book
The searched book will be issued, and a confirmation message will be given if the book is available.
3. Non-Functional Requirements
3.1 Usability
Users should be able to access the system using a phone.
3.2 Availability
The system shall be operational 24 hours a day, 7 days a week.
Hospital Patient Info Management System (HPIMS) SRS
1. Scope
The proposed software product, HPIMS, will replace the current paper-based system. It will collect and store patient information for future use, aiming to reduce overtime pay and increase the number of patients treated accurately.
2. Functional Requirements
2.1 Registration
- SRS001 Add Patients: The HPIMS shall allow front-desk staff to add new patients.
- SRS002 Assign ID: The HPIMS shall assign a unique ID to each patient, used throughout their stay.
2.2 Check Out
- SRS003 Delete Patient ID: Administrative staff can delete the patient’s ID upon checkout.
- SRS004 Add to Beds-Available List: Staff can update bed availability upon patient checkout.
2.3 Report Generation
- SRS005 Patient Information: Generate reports including PHN, name, ward, bed number, and doctor.
- SRS006 Bed Availability: Generate reports on bed availability by ward and bed number.
2.4 Database
- SRS007 Patient Mandatory Information: Store mandatory patient information (name, contact details, PHN, address, patient ID).
- SRS008 Update Patient Information: Allow users to update patient information.
3. Non-Functional Requirements
3.1 Security
- SRS012 Patient Identification: Patients identify themselves using their PHN.
- SRS013 Logon ID: All users require a Logon ID and password.
- SRS014 Modification: Only ward administrators can modify the database.
- SRS015 Front Desk Staff Rights: Front desk staff can view and add patients but not modify information.
- SRS016 Administrators’ Rights: Administrators can view and modify all information.