The Logiman Ren Use Case.

Brief Description This use case describes how a user logs into the Course Registration System (CRS). Flow of Events Basic Flow (Main Flow of Events) This use case starts when the actor wishes to log into the CRS. The CRS requests that the actor enters his/her name and password. The actor enters his/her name and password. The system validates the entered name and password and logs actor into the system. Alternative Flow (Exception Flow of Events) If in the Basic flow, the actor enters an invalid name or password, the system displays an error massage. If the error of entering password is less than 3 times, the Actor can return to enter the password again. Otherwise, the use cases ends. Special Requirements None Pre-Conditions None Post-Conditions //System States If the use case was successful, actors can entered into the system. Extension Points None The ViewReportCard Use Case Brief Description This use case allows a Student to view report card in order to know his/her own grade for the courses he/she chooses in the semester. Flow of events Basic Flow (Main Flow of Events) This use case starts when a Student wishes to view the report card. The system will show the report card to the Student. Special Requirements None. Pre-Conditions The Student must be logged into the system before this use case begins. Post-Conditions //System States If the use case is successful, the system will show the report card to the Student. The report card can only be read, but can not be changed.

Extension Points None The RegisterForCourse Use Case Brief Description This use case allows a Student to select which course offering from the NewCourseDatalogue he/she wants to learn in the semester. Flow of Events Basic Flow (Main Flow of Events) This use case starts when a Student wants to register for the courses he/she wants to learn. The system requests the Student to choose to add courses or drop courses. In add courses: The system shows the list of course that the Student can choose. The Student adds the course he/she wishes to learn to the list. And each student has 3 lists to fill. In drop courses: The system shows the list of courses the Student has previously selected. The Student drops the course he/she doesn’t wish to learn from the list. Alternative Flow (Exception Flow of Events) If the system finds that the course the Student wants to add to the list has added before, the system will display an error message indicating that this course has been in his/her list. If the list is full when the Student still wants to add courses, the system will display an error message indicating that the list of which courses he/she wants to learn is full. If the system finds a schedule conflict when trying to establish the course list the Student choose to take, the system will display an error message indicating that a schedule conflict occurs. If there’s no professor teaches the course that the Student chooses, the system will display an error message indicating that this course is unable to choose. Special Requirements None. Pre-Conditions The Student must be logged into the system before this use case begins. Post-Conditions //System States If the use case is successful, the course list of which courses he/she wants to learn will be updated. Otherwise, the system state will not be changed. Extension Points

None. The SummitGrades Use Case Brief Description This use case allows a Professor to summit the grades of students for the courses that he/she taught in the semester. Flow of Events Basic Flow (Main Flow of Events) This use case starts when a Professor wants to summit grades for the course he/she taught. The system requests the Professor to choose a course that he/she wants to summit grades. The system will show all students who take this course in the semester. Then the Professor can summit grade one by one to each student. Alternative Flow (Exception Flow of Events) If the Professor chooses the course he/she doesn’t teach in this semester, the system will display an error message and the Professor can go back to choose another course again. Special Requirements None Pre-Conditions The Professor must be logged into the system before this use case begins. Post-Conditions //System States If the use case is successful, the report card will be updated. Otherwise, the system state will not be changed. Extension Points None. The SelectCoursestoTeach Use Case Brief Description This use case allows a Professor to select the course offering from the course catalogue for the courses that he/she wishes to teach in the upcoming semester. Flow of Events Basic Flow (Main Flow of Events) This use case starts when a Professor wishes to sign up to teach some course offering for the upcoming semester. The system shows the list of course offerings that the professor is eligible to teach. The system also shows the list of courses the professor has previously selected to teach. The Professor selects or de-selects the course offerings that he/she wishes to teach.

Alternative Flow (Exception Flow of Events) Schedule Conflict - If the system finds a schedule conflict when trying to establish the course offerings the Professor should take, the system will display an error message indicating that a schedule conflict occurs. Course Conflict – If the system finds the course that a Professor wants to teach has already chosen by another one, the system will display an error message indicating that a course conflict occurs. Special Requirements None. Pre-Conditions The Professor must be logged into the system before this use case begins. Post-Conditions //System States If the use case is successful, the course offerings (that a Professor schedules to teach) will be updated. Otherwise, the system state will not be changed. Extension Points None. The CloseRegistration Use Case Brief Description This use case allows the Registrar to deal with the problem of student’s course distributing. After the course distributing is over, the Registrar will send a message to the billing system in order to ask students for billing the classes. Flow of Events Basic Flow (Main Flow of Events) This use case starts after students’ course registration is over, and the Registrar need to close the whole registration. The system will take the course registration into 3 parts. If there is less than 3 students choose one course, that course will not be opened in the semester. And the system will notify the students who choose this class and the professor who select this course to teach. If there are more than 10 students choose one course, the system will random pick only 10 students to enter this class. After, the system will write the information of the students that be chosen into CourseStudent and notify the students who aren’t be chosen from the random picking process. If the numbers of students that choose one course are between 3 and 10, the system will write the information of the students into CourseStudent. The Registrar then sends messages of the result of the course registration to the Billing System to ask students to pay the bill.

Special Requirements None. Pre-Conditions The Registrar must be logged into the system before this use case begins. Post-Conditions //System States If the use case is successful, the course registration will be end and the Billing System will send a message to Students in order for money. Extension Points None.

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer for students: Only $4.99/month.

Master Your Semester with a Special Offer from Scribd & The New York Times

Cancel anytime.