Professional Documents
Culture Documents
• Admin
• Owner
• Customer
• User
• Academic advisor
• Teacher
• Students
Help understand the functions of the system. Help understand the performance of the system.
Such as (log in -Search an item ) such as (security , validation ,flexibility and
maintainability )
Explain the characteristics that a system is Explain the way in which the product should work (how it
expected to have. should behave).
Identify what the system must or must not do. Identify how the system should do it.
Will allow the system to perform, even if the non- The system will not work with non-functional requirements
functional requirements are not met. alone.
Ensures the system will meet user requirements. Ensures the product meets user expectations.
Usually defined by the user. Usually defined by software engineers, developers,
software architects or other technical experts.
For example : The user SHALL be able to log in For example : The system MUST respond to log in requests
through a web interface within 1 second
Problem statement 1: university enrolment
The educational structure of the university consists of divisions. Divisions contain
several departments. While a single division administers each degree, the degree may
include courses from other divisions.
In fact, the university prides itself on the freedom of choice given to students in
selecting courses towards their degrees.
The flexibility of this course selection process puts strains on the university.
pre-enrolment activities
• The pre-enrolment activities must include mail-outs of last semester’s
examination grades to students, together with any enrolment instructions.
Validation :
Discuses this scenario, extract the users role and justify the function and non-
functional requirements.
Problem statement: Solution
User Roles:
System Functions:
Functional requirements :
* Pre-Enrollment Activities:
* Enrollment Processing:
Non-Functional requirements :
* Validation:
* Generate notifications for students about any issues in their submitted program
(e.g., missing prerequisites, timetable clashes).
* Technical Considerations:
* User Interface: Easy to use for students and staff with different levels of access.
* Integration: Consider future integration with other systems (e.g., financial systems).