This is for Software Design Architecture.

Task 6: Types of Requirements As a result of digging into some more details of the university teaching support system in the course of further elicitation and documentation activities, an initial set of requirements has been specified in natural language. Unfortunately, these requirements are not yet organized according to their type (i.e., functional requirements, quality requirements, or constraints). Below you will find an excerpt from the requirements specification, including twelve specific requirements. Requirements for the University Teaching Support System Req-l: The system shall comply with the privacy policies of the university. Req-2: Every time a student accesses a certain course material, the respective download statistic shall be incremented by one. Req-3: The students' examination results shall be protected against any unauthorized access. Req-4: Due to special security policies regarding the access to exam results, examination officers are required to change their password at least once every three months. Req-5: The system shall be available between 5 am and 3 am of the following day on weekdays, and from 6 am until 11 pm during the weekend. Req-6: Once a lecturer has entered the exam grades, the system shall generate an examination certificate automatically. Req-7: Students shall be able to perform the exam registration process in less than 5 minutes. Req-8: The system shall be delivered and ready for operation at the beginning of the next winter term. Req-9: The grade point average shall be round up to the fifth decimal place. Req-10: The format for storing examination results shall be compatible to the one employed in TeachSupport 2". Req-11: If a lecturer uploads new course material, an automatic notification shall be sent to the students participating in the corresponding course. Req-12: The system shall allow students to submit anonymous evaluation forms for lectures and course material