Professional Documents
Culture Documents
* EXECUTIVE SUMMARY:
The purpose of this document is to define requirements of the Student Mark analysis captured in the use cases of the use case model. The Supplementary Specifications and the use-case model together captures a complete set of requirements on the system.This students mark list analysis is very much useful in illustrating the entire students details.
*SCHEDULE MANAGEMENT:
*Functionality:
Faculty can enter mark only for the registered students.
*Usability:
The desktop user-interface shall be Windows 95/98/2000/xp compliant.
* Reliability:
The System should function properly for allotted time slot and produces report with no more than 10% down time.
*Performance:
The System must be able to complete 80% of all transactions within 2 minutes.
*Supportability:
None.
*RISK MANAGEMENT:
*Security:
1.The System should secure so that only faculty can enter marks and obtain reports. 2. Marks should be modifies only by the faculty.
*Design Constraints:
The system shall provide a window-based desktop interface. Student marks analyzing system has to be developed for analyzing obtained by the students who scored in Semester Examination The System should provide following functionalities 1. The System obtains following informations from the faculty generates report Roll No, Name, Department, Semester, Marks obtained in each subject. 2. The total for each student should be calculated and ranked based on total and pass in all the subject appeared. 3. The Final report should display rank, percentage, Class, Pass/Fail Status for each student. 4. The report should also contain information about no of students passed, failed, list of students who got more than 60% in each subject, overall list of students who got >=60%
This use case starts when the Faculty wishes to Login to the Student Marks Analyzing System. 1. The System requests that the Faculty enter his/her name and password. 2. The Faculty enters his/her name and password. 3. The System validates the entered name and password and logs the Faculty into the System.
Alternative Flows:
If, in the Basic flow, the Faculty enters an invalid name and/or password, the system displays an error message. The Faculty chooses to either return to the beginning of the Basic flow or cancel the login, at which point the use case ends.
*Special Requirements:
none
*Pre-Conditions:
none
*Post-Conditions:
If the use case was successful, the Faculty is now logged into the system. If not, the system State is unchanged.
*Extension Points:
Enter Marks for each Student.
*Brief Description:
The Faculty uses this usecase to enter marks for each student.