Object oriented design
Download
1 / 19

Week 11 - PowerPoint PPT Presentation


  • 104 Views
  • Uploaded on

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

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Week 11' - isha


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Object oriented design

Object Oriented Design

Week 11

SYST39409- Object Oriented Methodologies


Agenda
Agenda

  • ICE-08 Take up

  • Schedule

  • Today

    • Sequence Diagrams - Part I

      • Interface & Business Logic

    • Capstone Discussion (last hour)

SYST39409- Object Oriented Methodologies


Design models with their respective input models
Design Models with Their Respective Input Models



Ice 08 review
ICE-08 Review

SYST39409- Object Oriented Methodologies





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





User interface for the Place Order use case.

SYST39409- Object Oriented Methodologies


Use Case Realization

SYST39409- Object Oriented Methodologies



Interface Layer

Business Logic Layer

SYST39409- Object Oriented Methodologies


Ice 09
ICE-09

SYST39409- Object Oriented Methodologies


Next week
Next Week

  • Sequence Diagrams continued…

SYST39409- Object Oriented Methodologies


ad