Sad Use Case
Starting point: the overall HE-Business Process Diagram
[pic]
Overview of Use Cases within the various Business Processes.
BP: Enrolment (ENR) • ENR1: Enroll in the university • ENR2: Enroll in a study year • ENR3: Enroll in (individual) courses
BP: Course Development (CD) • CD1: Register a study • CD2: Add courses to a study year • CD3: Register a course
BP: Facilitating Activities (FA) • FA1: Register organizational unit • FA2: Register staff member
BP: Education Process • EP1: Register test results Use Case ENR1: enroll in the university (belongs to BP: Enrolment)
[pic]
Goal: to register a new student at the university
Primary actor: applicant (to become a student)
Stakeholders and their interests: - Student: wants to start university studies, and therefore wants to be registered properly for a given study. - University: wants to have students registered in a uniform, structured way. - Registrar: wants a smooth and efficient administration (registration) process, with minimal efforts and disturbances.
Pre-conditions: - Basic data on studies already registered in the system, since a student always registers for a (at least one) study.
Post-condition: student properly registered for a study.
Happy Path (main scenario) 1. Applicant present him/herself at the registrar administration desk. 2. Registrar controls whether the applicant is eligible for application [BRENR1.1] 3. Registrar hands over an application form to the applicant [Alt course A] [Alt course B]. 4. Applicant fills in the application form 5. Registrar controls the application form (all required items filled in, in the correct way, according to BR’s) [Alt course C] [Alt course D]. 6. Registrar registers the form data in the system (“fees paid” not checked) [Alt course E] [Alt course F] 7. System generates student ID 8. System executes “enrollment in
[pic]
Overview of Use Cases within the various Business Processes.
BP: Enrolment (ENR) • ENR1: Enroll in the university • ENR2: Enroll in a study year • ENR3: Enroll in (individual) courses
BP: Course Development (CD) • CD1: Register a study • CD2: Add courses to a study year • CD3: Register a course
BP: Facilitating Activities (FA) • FA1: Register organizational unit • FA2: Register staff member
BP: Education Process • EP1: Register test results Use Case ENR1: enroll in the university (belongs to BP: Enrolment)
[pic]
Goal: to register a new student at the university
Primary actor: applicant (to become a student)
Stakeholders and their interests: - Student: wants to start university studies, and therefore wants to be registered properly for a given study. - University: wants to have students registered in a uniform, structured way. - Registrar: wants a smooth and efficient administration (registration) process, with minimal efforts and disturbances.
Pre-conditions: - Basic data on studies already registered in the system, since a student always registers for a (at least one) study.
Post-condition: student properly registered for a study.
Happy Path (main scenario) 1. Applicant present him/herself at the registrar administration desk. 2. Registrar controls whether the applicant is eligible for application [BRENR1.1] 3. Registrar hands over an application form to the applicant [Alt course A] [Alt course B]. 4. Applicant fills in the application form 5. Registrar controls the application form (all required items filled in, in the correct way, according to BR’s) [Alt course C] [Alt course D]. 6. Registrar registers the form data in the system (“fees paid” not checked) [Alt course E] [Alt course F] 7. System generates student ID 8. System executes “enrollment in