Reference no: EM132383047
ITSU2010 Technical Documentation of Software Engineers Assignment - Victorian Institute of Technology, Australia
Case Study - "Course Registration Process of Eastern State University (ESU)"
Background - The process of assigning professors to courses and the registration of students is a frustrating and time-consuming experience.
After the professors of ESU have decided which courses they are going to teach for the semester, the Registrar's office enters the information into the computer system. A batch report is printed for the professors indicating which courses they will teach. A course catalog is printed and distributed to the students.
The students currently fill out (mulitpart, multicolor) registration forms that indicate their choice in courses, and return the completed forms to the Registrar's office. The typical student load is four courses. The staff of the Registrar's office then enters the students' forms into the mainframe computer system. Once the students' curriculum for the semester has been entered, a batch job is run overnight to assign students to courses. Most of the time the students get their first choice; however, in those cases where there is a conflict, the Registrar's office talks with each student to get additional choices.
Once all the students have been successfully assigned to courses, a hard copy of the students' schedule is sent to the students for their verification. Most student registrations are processed within a week, but some exceptional cases take up to two weeks to solve.
Once the initial registration period is completed, professors receive a student roster for each course they are scheduled to teach.
Problem Statement -
- At the beginning of each semester, students may request a course catalog containing a list of course offerings for the semester.
- Information about each course, such as professor, department, and prerequisites will be included to help students make informed decisions.
- The new system will allow students to select four course offerings for the coming semester.
- In addition, each student will indicate two alternative choices in case a course offering becomes filled or canceled.
- No course offering will have more than ten students or fewer than three students.
- A course offering with fewer than three students will be canceled.
- Once the registration process is completed for a student, the registration system sends information to the billing system so the student can be billed for the semester.
- Professors must be able to access the online system to indicate which courses they will be teaching, and to see which students signed up for their course offerings.
- For each semester, there is a period that students can change their schedule. Students must be able to access the system during this time to add or drop courses.
Tasks -
1. Write the actors and their role in the case study?
2. Identify and write seven use cases in the case study?
3. Pick two use cases from the list of use cases which you have identified.
4. Identify the preconditions for the selected use cases.
5. Write main flow for each use case.
6. Write sub flows for each use case.
7. Sketch the use case diagram based on your analysis of the system.
8. Draw the use case diagram using StarUML software.
9. Write the Software Requirement Specification document (in the given format).
10. Write Use case specification for each use cases.
After Class Reading - Chapter 3 and 4 - recommended book 01 (Jim Arlow and Ila Neustadt, 2005, UML 2 and the Unified Process: Practical Object-Oriented Analysis and Design).