This assignment contains the explanations of a use case diagram that is used to represent a regular modeling for the graduation petition process used by Marymount University. The diagram itself resides on the next page. In order to obtain a better understanding of the petitioning process, it is first necessary to explain both the preconditions and possible scenarios that can occur within the overall process. Because almost the entire process is performed in online environment, there are several exceptions, which require increased attention. The Use Case diagram represents the main events performed from two views: students and Register Office.
A student is authentication to the system based on his credentials, namely username, password and student ID. If these are accepted, then he can choose the “Graduation Plans” section. There he can either review a previously saved plan or edit it. If he chooses to edit the plan, then he must choose Major, Minor and Session date (FA, SP or SU). After completing these details, the student can select to Submit the form.
From Register office view, the things are seen differently with respect to the petitioning process. For instance, a register must first enter student’s ID in order to review the already completed Graduation Plan or to edit them as per system requirements. The regular options for an Register are: Create, Edit and View. If he creates or edits the Graduation Plan filled-in by the student, then he can change any of the options (Major, Minor and Session Date). The Register can then Save, Edit or submit the chosen plan on behalf of the student.
The present diagram can still be refined in order to cover the situations from practice that weren’t included by its
2. Use Case Diagram for petition Graduation Program
Use Case Narrative
Author: XYZ Date: xx-xx-xxxx
Use-Case Name: graduation petition process.
User-Case ID: TMA-IT210
Use-case Type: Graduation Program
Source: Requirement- to allow the user to confirm when they will graduate from a list of semesters in the next year (FA, SP, SU).
Primary actor: Undergraduate/Graduate Marymount student.
Secondary Actors: Register
Description: use case describes the event of a student who applies for Graduate Petition Process. He needs to know when he can graduate according the established graduation plans – from a list of semesters in the next year (e.g. Fall, Spring or Summer).
Objective/Goal: The necessary to confirm applying for Graduation.
1-To be currently undergraduate or graduate student.
2-To have active online account in the Students Management System.
3)-To be eligible for GPA in the next semesters (FA, SP, SU).
4. Trigger: An undergraduate or a graduate student decides to find out when he can graduate in the next year.
Typical course of Events
15) The Register can then: Save, Edit or submit the form.
6. Exceptions/Alternate Flows:
7. Conclusion: this Use Case concludes when the student can graduate from the list of semesters from the next year (FA, SP, SU).
1) If the student can’t access the GPA online application, he must contact Registrar/IT Department.
2) Receive ticket with details to attend the Graduation.
On the remaining number of available places for Graduation program once the registration period progresses).
8. Implementation Constraints and Specifications: GUI must be included in the application for checking the available GPA options.
Assumptions: the Graduation options are already available for the next year (in the application) when the student wants to check them.
It is assumed the presented Use Case is not used for the 1st time (the student could have already tried to submit application for one of the available semesters in the past)
Assignment Writing Help
Engineering Assignment Services
Do My Assignment Help
Write My Essay Services