Think about the system that handles student admissions at your university. The primary function of the system should be to track a student from the request for information through the admission process until the student is either admitted or rejected for attendance at the school. Write the use case report that can describe an "admit student" use case.
• Create the use case diagram for the one use case. Pretend that students of alumni are handled differently from other students. Also, a generic update student information use case is available for your system to use.
• Choose one use case diagram and create a sequence diagram. Pretend that a temporary student object is used by the system to hold information about people before they send in an admission form. After the form is sent in, these people are considered students.
• Create a class diagram for the student admission system. An admissions form includes the contents of the form, SAT information, and references. Additional information is captured about students of alumni, such as their parents' graduation year(s), contact information, and college major(s).
• Create a behavioral state machine diagram to depict a person as he or she moves through the admissions process.