1. ASK PMU! MISY 4341- Object-Oriented Analysis and Design
Instructor: Dr. Sameer Al-Imamy
Sec: 201
Group members:
Asma Ragheb  
Mona Al-Umairi
Spring 2012

2. Executive summary
PMU is a very advanced university and continues to strive to obtain the highest technology. Therefore “ASK PMU!” is a survey system that will enhance the studying experience at PMU and support students, faculty and staff research projects. “ASK PMU!” is a survey system that allows all kinds of PMU users to create and send surveys directly to there chosen PMU Responders . Also obtain specific analysis for there surveys effortlessly. And in order to keep the system updated and user friendly feedback from PMU users will be of very high priority and used in modifying and updating the system according to the users needs.

3. Project Management

4. Project Management

5. Use case Diagram (Context Diagram)

6. Use Cases Use Case Number: 2.
Use Case Name & Priority: Create Survey, essential.
Use Case Short Description: User is able to create survey through select questions type and add the questions of the survey, and create the survey successfully.
List of Actors: PMU user.
Use Case Precondition: User must login to ASK PMU system.
Use Case Main Flow:
User selects question type, and enters the question.
System checks if all requirements filled out and add the questions and create the survey successfully.
Use Case Exceptional Flow: PMU User didn’t select the question type or enter the question
A.2. System checks if the question type selected and the question is entered.
A.3. Systems asks the user to select the question type or write the question.
A.4. Go back to basic flow 2.
Use Case Post Conditions: User creates survey successfully

7. Use Cases Use Case Exceptional Flow: System didn’t receive response
Use Case Number: 1.
Use Case Name & Priority: Analysis, essential.
Use Case Short Description: User is able to get the final result of the survey, and the system analysis the result successfully.
List of Actors: the use case is extend for the response to survey use case which its actor is PMU responders.
Use Case Precondition: Receive responded survey.
Use Case Main Flow:
System receives the responded surveys and analyzing the results.
System checks if the results are correct and the system analysis the survey results successfully.
Use Case Exceptional Flow: System didn’t receive response
A.1. System checks if there is any response to the survey.
A.2. Systems alerts the user that there is no response received.
A.3. Use case ends.
Use Case Post Conditions: Analyzing the survey results successfully.

8. Use Cases Analysis Use Case Basic Flow:
System gets the responded surveys.
System collects the number of responded surveys received.
System use statistical methods to analysis the answered for each question in the survey.
System done from analyzing the survey results.
System checks if the results are correct.
System analysis the survey results successfully.

9. Use Cases Use Case Number: 6.
Use Case Name & Priority: Login, essential.
Use Case Short Description: User is able to enter username/password combination and login to the system successfully.
List of Actors: PMU user and Validation system .
Use Case Precondition: User must exist in the database.
Use Case Main Flow:
User enters a combination of username and password.
System validates the combination and login the user successfully.
Use Case Exceptional Flow: User record does not exist in the database
A.2. System validation finds that the user record does not exist in the database.
A.3. Systems alerts the user that their record does not exist.
A.4. Use case ends.
Use Case Post Conditions: User can log in Successfully.

10. Domain Model

11. Class Diagram

12. Contracts Contract CO1: makeSurvey Operation: Create Survey( )
Cross references: Use case: Create Survey
Preconditions: none
Post-conditions:
A Survey instance was created (instance creation).
Survey was associated with the controller (association formed).
Attributes of Survey were initialized.

13. Interaction Diagram

14. Contracts Contract CO2: enterQuestion Operation: enterQuestion(type)
Cross references: Use case: Create Survey
Preconditions: There is underway survey
Post-conditions:
A SurveyQuestion instance Q was created (instance creation).
Q was associated with the current Survey (association formed).
Q.type became Type (attribute modification).
The current Survey was associated with the SurveyRepository( associated formed); ( to add it to the database of surveyCollection).

15. Interaction Diagram

16. Contracts Contract CO3: fillupSurvey Operation: fillupSurvey(surveyID)
Cross references: Use Cases: Response to Survey
Preconditions: There is an underway survey
Post-conditions:
A surveyresponse instance R was created(instance creation)
R was associated with the current survey(association formed)
R was associated with surveycollection based on

17. Interaction Diagram

18. Contracts Contract CO4: getanalysis Operation: getanalysis(surveyID)
Cross references: Use Cases: Analysis
Preconditions: there is an underway survey and surveyresponses received
Post-conditions:
surveyresponsis retrieved and sent to Analysis
Analysis is retrieved and used to generate a report

19. Interaction Diagram

20. Interaction Diagram

21. Prototype

22. Thank You…