PMU E-Alumnus
Final Project Report
MISY 4341 Object Oriented Analysis and Design
Section 201
Zainab A. AlDawood
200800915
Instructor: Dr. Samer Al-Imamy
Summer 2012
1
Table of Content
Excusive Summery…………………………………………………………. 3
Section One
1.0 Project Management…………………………...….………..…………...4
Section Two
2.0 System Analysis
2.1 Use Case Diagram………….…………………………………...5
2.2 Use Cases…………………...…………………………………..6
2.3 Domain Model…….…………………………………………..10
Section Three
3.0 System Design
3.1 Class Diagram…………..………………………………….....11
3.2 Interaction Diagram……...…………………………………...12
Section Four
4.0 Prototypes…...…………..…………………………………………...17
References.................................................................................................19
2
Executive Summary
From the first step of establishing Prince Mohammed bin Fahad University, the sense of
development and modern technology achievement is taking its place within its strategy. So, the
need of tracking this big achievement and monitoring the performance of its students is
becoming more important since the technological, social and cultural changes took their place
in the kingdom. Therefore, in order for PMU to check the consequences and the results of
educational strategy it follows, an alumnus system should be established to keep updating the
band between PMU faculties and the graduates as well, so both sides see the impacts and being
updated with whatever changes and demands of the current economical and industrial
environments. However, this analysis and design of PMU e- alumnus system discovers the
need of this implementation as well as the requirements and the diagrams that facilitate the way
to get this in reality.
The system will require the Administration office to register all MIS graduated
students in the Alumni System. Then, the Alumni students will have their own accounts in the
system that they can access through login ID and password. Faculty of MIS, as well as MIS
Alumni students, will have the same advantage of having the account. Through that account,
Alumni and faculty can receive e-mails about the up-coming events and activities in the
University. In addition, students, through the system, can submit requests to any faculty
regarding assessment or recommendation letter.
The system will be analyzed from different perspectives; from the business point of
view and a systematic point of view using the system analysis, design analysis, and
programming. First, there will analysis of system, which includes the main use cases, use case
diagram, and domain model, some prototypes of the system. Second, there will be design of the
system, which include class diagram, interaction diagram or either a sequences diagrams for the
main events and use cases within the system.
3
Section One
1.0 Project Management
4
Section Two
2.0 System Analysis
2.1 Use Case Diagram
5
2.2 Use Case
Use case: 1
Use case name & priority: Create accounts, essential.
Short description: The administrators create user account in Alumni system.
List of actors: administrator.
Use case pre-condition: admin must get all graduate students information from
registration departments.
Use case main flow:
1. Student completes his/her major credit hours, and is graduated.
2. Administration create a new account in the Alumni system
3. Administration enters the graduated student information such as name,
ID, etc
4. Administration save the information
5. System immediately will assign the ID as a username and will offer a
random temporary password
6. Student will receive the login information from administration via e-mail
including the features of the Alumni System.
7. Graduated student is a member in the Alumni system
8. Steps 1-7 are repeated for every graduated student.
Use case exceptional flow:
1a. Error creating new profile:
1. Administrator exits the page and opens it again.
2. Administrator refreshes the page.
6a. Student didn’t receive Email:
1. Student sends Email to the system to request account verification.
Use case post-condition:
1. All user must have unique username and password
2. Users are able to view their account.
Comments:
No comments.
6
Use case: 2
Use case name & priority: Manage events, essential.
Short description: The administrators manage events in Alumni system, by edit
event information or create new events.
List of actors: Administrator.
Use case pre-condition: Admin must be login to the system.
Use case main flow:
1. Administrator select events page (Link), to add new events
information.
2. System displays all events information that are saved in the database
and a new events button, create event.
3. Administrator chose to create new or edit existing events.
4. Administrator select to create new events by press create event
button.
5. System will display events form fields to be filled.
6. Administrator fill field (title, date, time, location … etc) and press
save button.
7. System save the new events to database
8. Administrator select to edit events information by press edit button.
9. System display events field to updated, (title, date, time, location ...etc)
10. Administrator update data and select save button
11. System saves the new events to database and display completed
process message.
12. System sends the new event to the users account.
Use case exceptional flow:
6a. Administrator not able to save information:
1. The Administrator exits or refreshes the page without save
Use case post-condition:
1. New events are created and send to the users account.
2. Users are able to view new events.
Comments:
No comments.
7
Use case: 3
Use case name & priority: Login, essential.
Short description: The Alumni system user needs to access into the system by insert
his/her own username and password.
List of actors: Administrator, students, Instructors.
Use case pre-condition: The user must be saved in to the system database which
means he is already exists in the system and have username and password.
Use case main flow:
1. Student checks PMU email and open administrator’s message.
2. Student takes user name and password to log in to Alumni System.
3. Student opens PMU website and go to Alumni home page.
4. Alumni home page will show log in information at the upper right corner.
5. Student types user name and password and press sign in to enter the
profile.
6. System checks the validation of the information entered by the student.
7. System approves information and opens student’s profile.
8. System will show a welcome message to the student for the first log in.
9. Student checks email and events that have been sent by administrator,
and edit profile, change the password and setting, etc.
10. Steps will be repeated to all students who will join the system in the
future.
Use case exceptional flow:
5a. Users enter a wrong username and password:
1.users re-enter password and username.
6a. System fails to check the validation and show error message:
1. The user exits the page without login.
2. The user login after a short period of time.
Use case post-condition:
1. Users are logged in the system.
2.The system opened the user’s account home page.
Comments:
No comments.
8
Use case: 4
Use case name & priority: get events, essential.
Short description: When the instructor and students select to view if there are any
events in Alumni system.
List of actors: Instructors, students.
Use case pre-condition: The user must be login to his account using his own
username and password.
Use case main flow:
1. Instructor/student log in to their Alumni account.
2. System displays account home page that include the events messages
3. Instructor/student press the events email.
4. System displays the event message with information.
5. Instructor/student view the event information.
Use case exceptional flow:
4a. System fail to display new emails:
1. Instructor/student exits the account and re-log in.
Use case post-condition:
1.instructor/student viewed the events.
Comments:
No comments.
9
2.3 Domain Model
10
Section Three
3.0 System Design
3.1 Class Diagram
11
3.2 Interaction Diagrams
Contract CO 1:
Operation: Create Account.
Cross-reference: create account use case.
Precondition: admin must get all graduate students information from registration departments.
Post condition:

Account form for was filled and sent to the controller.

Student/instructor account was created.

Student/instructor account was added to the users’ accounts database.
Figure 3.1 create account sequence diagram.
12
Contract CO 2:
Operation: manage Event (type; date; time)
Cross References: manage event use case.
Precondition: Admin must be login to the system.
Post-condition:

An event was created.

Attributes of event were initialized

Events are stored in event collection.
Figure 3.2 manage event sequence diagram.
13
Contract CO 3:
Operation: login.
Cross References: login use case.
Preconditions: The user must be saved in to the system database which means he is already exists in
the system and have username and password.
Post-condition:

Username and password checked by the system

If username and password matched, it’s accepted; else, username and password are rejected.

Accepted username and password are eligible by the system
Figure 3.3 login sequence diagram
14
Contract CO 4:
Operation: get event
Cross-reference: get event use case.
Precondition: The user must be login to his account using his own username and password.
Post condition:

Event information was retrieved from event collection.

Event feedback was sent to users.
Figure 3.4 get event sequence diagram.
15
Section Four
4.0 Prototypes
16
17
18
References
Larman, C. (n.d.). Use Cases. In applying UML and patterns (Third ed., pp. (61100)).Prentic Hall PTR.
Larman, C. (n.d.). domain model . In Applying UML and patterns (Third ed., pp.
(131-180)). Prentice Hall PTR.
Larman, C. (n,d,). UML interaction Diagram. . In applying UML and patterns (Third
ed., pp. (221-247)).Prentic Hall PTR.
Larman, C. (n,d,).UML Class Diagram. In applying UML and patterns (Third ed., pp.
(249-270)).Prentic Hall PTR.
Larman, C. (n,d,).GRASP: designing objects with responsibilities. In applying UML
and patterns (Third ed., pp. (271-319)).Prentic Hall PTR.
Larman, C. (n,d,).GRASP: objects design examples with GRASP. In applying UML
and patterns (Third ed., pp. (321-362)).Prentic Hall PTR.
All diagrams were drown using www.creately.com
Project management was designed in www.smartsheet.com
19