Optimizing Student Registration System Requirements
Ensuring the efficiency, reliability, correctness, integrity, and usability of a student registration system by analyzing the current requirements and incorporating McCall software quality factors effectively to improve system performance. The document highlights the importance of speed, GPA calculation accuracy, quick bug resolution, system failure prevention, secure access to final marks, and user-friendly design for students.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
The following are requirements of student's registration system. What is wrong with these requirements? What quality factor is missing? Rewrite the requirement document to reflect how McCall software quality factors are used:
1- The system speed should not be slow. And students should be able to register their courses as fast as they can. (efficiency) The registration system should respond time should be less than .055 seconds, and the students should be able to register their courses in 10 minutes.
2- The application should be able to calculate students GPA correctly. (Reliability) The probability for a non-accurate GPA, containing one or more mistakes, will not exceed 1%.
3-Any changes to the system or bugs correction should not take a long time (Correctness) Any changes or bug correction should not take more than 30 minutes, while in registration period it should not take more than 10 minutes.
4- The system should not be in failure mode the shortest possible time. (Reliability) One of the requirements of the Registration system is that it should not fail during registration period, the recovery time should not exceed than 20 minutes in case of failure.
5- Students should be able to access their final marks. (Integrity) Students should be allowed to view their final marks. They should not be able to make any changes
6- System should be easy to be understood by students. (Usability) Training of new students will take no more than two days, this should enable the student to submit the application in 20 minutes.
