1 / 19

Week 11

Object Oriented Design. Week 11. Agenda. ICE-08 Take up Schedule Today Sequence Diagrams - Part I Interface & Business Logic Capstone Discussion (last hour). Design Models with Their Respective Input Models. ICE-08 Review. Use-Case Controller is responsible for coordinating and

isha
Download Presentation

Week 11

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. Object Oriented Design Week 11 SYST39409- Object Oriented Methodologies

  2. Agenda • ICE-08 Take up • Schedule • Today • Sequence Diagrams - Part I • Interface & Business Logic • Capstone Discussion (last hour) SYST39409- Object Oriented Methodologies

  3. Design Models with Their Respective Input Models

  4. SYST39409- Object Oriented Methodologies

  5. ICE-08 Review SYST39409- Object Oriented Methodologies

  6. SYST39409- Object Oriented Methodologies

  7. SYST39409- Object Oriented Methodologies

  8. SYST39409- Object Oriented Methodologies

  9. Use-Case Controller is responsible for coordinating and sequencing the interactions between the system and its actors, while preserving the integrity of the data and the flow defined in the use case specification. Three different types of objects usually participate in a use-case realization, each one encapsulating a different kind of behaviour. Widely known and adopted by UML as the stereotypes <<boundary>>, <<entity>> and <<control>>: • boundary or interface objects are generally used to translate actor's actions to the system into events in the system, and vice-versa; • entity objects are used to handle information that outlives use cases and often persistent; • control objects are used to encapsulate behaviour related to a specific use case that isn't naturally placed in any of the previous two types of objects, such as coordination, sequencing, transaction, and control of other objects. Control objects usually last only during the execution of one use case. SYST39409- Object Oriented Methodologies

  10. SYST39409- Object Oriented Methodologies

  11. SYST39409- Object Oriented Methodologies

  12. SYST39409- Object Oriented Methodologies

  13. User interface for the Place Order use case. SYST39409- Object Oriented Methodologies

  14. Use Case Realization SYST39409- Object Oriented Methodologies

  15. Standard Stereotypes Found in Design Models

  16. Interface Layer Business Logic Layer SYST39409- Object Oriented Methodologies

  17. ICE-09 SYST39409- Object Oriented Methodologies

  18. Next Week • Sequence Diagrams continued… SYST39409- Object Oriented Methodologies

More Related