1. PMU E-Alumnus Project Final Presentation
MISY 4341 Object Oriented Analysis And Design
Section 201
Zainab A. AlDawood
Instructor: Dr. Samer Al-Imamy
Summer 2012

2. My Outline
Excusive Summery Section One 1.0 Project Management Section Two 2.0 System Analysis 2.1 Use Case Diagram 2.2 Use Cases 2.3 Domain Model Section Three 3.0 System Design 3.1 Class Diagram 3.2 Interaction Diagram Section Four 4.0 Prototypes References

3. PMU E-Alumnus 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 s 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 include 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.

4. 1.0 Project Management

5. 2.0 System Analysis 2.1Context Diagram

6. 2.2Use Cases Description
Use case: 1 Use case name & priority: Send events, essential. Short description: The administrators send all events to the user account in Alumni system. List of actors: administrator. Use case pre-condition: admin must create events. Use case main flow: The Administrator must be login to the system The Administrator creates new events The Administrator must select to submit events The system shall be send the events to all user account in the system Use case exceptional flow: The Administrator exits the page without submit The users don’t receive the events. Use case post-condition: All users must receive events note in their accounts. User select events page. Comments: No comments.

7. 2.2Use cases Description Con.
Use case: 2 Use case name & priority: Create accounts, essential. Short description: The administrators select to 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: The Administrator must be login to the system The Administrator must select user account page The system shall be connected to system data base The Administrator shall be fill all fields information The system shall be able to save user record in to system database Use case exceptional flow: The Administrator exits the page without save The system not connected to database The Administrator leave some field empty Use case post-condition: All user must have unique username and password User select events page Comments: No comments.

8. Use cases Description Con.
Use case: 3 Use case name & priority: Manage request, essential. Short description: The administrators select to manage user request in Alumni system and send feedback to them. List of actors: administrator. Use case pre-condition: admin must login into the system. Use case main flow: The Administrator must be login to the system and select request page. The system shall be able to display all user requests. The system shall be connected to system data base The Administrator shall be able to check request information. The system shall be able to save admin feedback record in to system database Use case exceptional flow: The Administrator exits the page without check request. The system not connected to database Use case post-condition: The user must received feedback Comments: No comments.

9. 2.3Domain Model

10. 3.0 System Design 3.1Class Diagram

11. 3.2 Interaction Diagrams + Contracts
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.

12. Following, CO 1-SequenceDiagram

13. CO 2 Description
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.

14. Following, CO 2 Sequence Diagram

15. CO 3- Description
Contract CO 3: 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.

16. Following, CO 3- Sequence Diagram

17. Prototypes of the system Prototype 1

18. Prototype 2

19. Prototype 3

20. Prototype 4

21. Prototype 5

22. Thank you 
Welcome to any Suggestion toward improving my system analysis and design !!?