Requirement Engineering The following paragraphs that you are going to read it will explain you clearly what the systems “Online Enrolment System” will do, the services that users of different roles will able to use and the constraints on its operation. Users Requirement 1. Students that will be able to use the Online Enrolment System will provide them Username and Password. 2. Students will be able to use the system on a specific day that will be announcement from the University. 3. Student that will sign in correct, the system will be providing some important information for the student. The courses that are available for the upcoming semester with instructors that will teach the course, dates of the courses, the program outline. 4. Students will select up to 5-6 courses max. 5. After student has select the course, he/she will need to send their selection. System Requirement 1.1 The administrator of the System will be the only one that will have access to create the profile (username, password) that the system will ask from the users. 1.2 The username will be the Registration number of the students and the password will be decided from administrator according the name of the student and the registration number. For Example, Username: F20132539 Password: MC201339 2.1 On a specific day the University will be announcement to the students the system will be open from 9:00-13:00 and 4:00-17:00 3.1 if the username and the password are correct the system in 2-3 seconds must redirect the users into a new webpage that students will able to see some of the important information about the next semester. For example, courses that are able to enrolment, instructor, dates/time. 3.2 The other important function that system must provide is the program outline and more specific about the courses that they have done or no. For example, courses that students have done in the previous semester shouldn’t be visible or students cannot select it. 3.3 Courses that need prerequisite need to be visible but must not be able to select from students that they didn’t done the prerequisite. 3.4 Form of prerequisites will be providing in the website in order to download it if the need to enrolment courses that needs a prerequisite. 4.1 Students will have to tick the box next to the course that would like to enrolment. 4.2 The courses that students are able select them are the ones that don’t need any prerequisites. The ones that need prerequisite will not be acceptable to select them. 4.3 If a student wants to enrolment a course that needs prerequisite as we refer above he/she will need to download the form fill it up and sent to chairperson of the current department in order to get approve. 4.3 However the students will need to keep doing the process of selecting courses that are available until they have an answer back. 5.1 When the students have select the courses, at the bottom of the page they will provide them a submit button to send the selections. 5.2 The submit button will be functional (send the selections to the university) when the first course has been selected. Functional and Non-Functional Requirements FUNCTIONAL REQUIREMENTS DESCRIPTION Process-oriented • The system should allow students to view course schedule while registering for classes. • Students are notified about any changes may occur in the schedule of courses. • The system provides the user accurate acknowledgement of passed and future courses needed to complete their requirement. • The system will provide a report that clearly shows what courses the student has completed and what courses they still need to take • They system should sent a final schedule emailed to students when registration is over • They system should log our users who are inactive for more than 10 minutes Information-oriented • Students that does not meet the prerequisites for a course, they cannot enroll to it. • Administrator should provide to students username and password NON - FUNCTIONAL REQUIRMENTS DESCRIPTION Operational • The system can run on handheld devices. • The system should be able to work on any Web browser. • The system should provide three type of users. Administrators, Staff, and students. • If a user lose his account, an email should be sent to the relevant email for password recovery within 10 minutes. Performance • The system should be available for use 24 hours per day, 365 days per year. • They system should be able to handle at least 300 users at the same time. Security • The system includes all available safeguards from malicious software. • Only platform managers can see personnel records of staff. • Only platform managers can add/remove a record of staff. • The system must effectively recover from a crash within ten minutes. Effective recovery means that the data is still in a consistent state when the system returns.