1 / 22

Team Members

Team Members. Rachid Alaoui Medarhri (Senior Student). Tarek Bougroug (Senior Student). Supervised By : Dr. Driss Kettani. Context Presentation & Objectives. One of the Software Engineering II requirements. To inform the audience about a new and an important topic in the S.E scope.

jlandwehr
Download Presentation

Team Members

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team Members • Rachid Alaoui Medarhri (Senior Student). • Tarek Bougroug (Senior Student). Supervised By : Dr. Driss Kettani

  2. Context Presentation & Objectives • One of the Software Engineering II requirements. • To inform the audience about a new and an important topic in the S.E scope. • To enhance our communication’s skills.

  3. Outline • Introduction. • UML foundation. • UML Diagrams & Notation. • UML Case Study. • Conclusion.

  4. Introduction ???????? • What is UML for?

  5. UML Foundation Good Question • Why UML was needed?

  6. UML Diagrams & Notation • Use Case Diagram. • Class Diagram. • Interaction Diagram ( Sequence & Collaboration). • Activity Diagram. • State Chart Diagram. • Deployment Diagram. • Object Diagram.

  7. Use Case Diagram • It is a diagram that specifies the actors of the system with all the use cases and of course the relations. • We construct it once we have all the requirements specification.

  8. Class Diagram • It Models class structure and contents using design elements such as classes, packages and objects. • It also displays relationships such as containment, inheritance, associations and others. • It is divided into two parts * Business concept model. * Business type model.

  9. Interaction Diagram ( Sequence & Collaboration) • It is made to model the behavioral aspect of the system. • It illustrates the events of the actor on the use cases. • It requires a detail Use case What is a detail use case?

  10. Detail Use case • Actor • Use case Name • Use case Description • Basic flow • Alternative flow

  11. Interaction Diagram ( Sequence & Collaboration) • The sequence diagram. Displays the time sequence of the objects participating in the interaction. This consists of the vertical dimension (time) and horizontal dimension (different objects). • The collaboration diagram. Displays an interaction organized around the objects and their links to one another. Numbers are used to show the sequence of messages

  12. UML Case Study. • Please Refer to the paper of the problem domain.

  13. The use case diagram

  14. Business Concept Model (class diagram)

  15. Business Type Model (class diagram)

  16. The Detail Use Case • Actor: Buyer. • Use Case: Search home. • Case description: This use case allows the Buyer to search for a home using specific search key depending on how he wants to narrow his\her search. • This use case start when a Buyer arrives to an internet terminal (A PC connected to internet) and join the company website to search for a home.

  17. The Detail Use Case • Basic flow: • The Buyer types the http address on a browser. • The Buyer enters the login name and the password in the access form. • The system verifies both the login name and the password of the Buyer. • The Buyer specifies the search. • The system verifies the search. • The system gives the result of the search.

  18. The Detail Use Case • Alternative flow: • Incorrect login name or password, if in the basic flow (2) the Buyer enters a wrong login name or password. An error message is displayed to the user (Buyer), and he\she is given the chance to reenter a new login name and password. • Incorrect entry for the search, if in the basic flow (4) the Buyer enters a non existing type of a search depending on how he\she narrows his\her search. An error message is displayed to the user (Buyer), and he\she is given the chance to make a new search.

  19. The Sequence Diagram

  20. The Collaboration Diagram

  21. Conclusion • UML is new and important. • The rest of UML diagrams. • Special thanx to Dr. Kettani and the audiance.

More Related