+ All Categories

Week 11

Date post: 22-Feb-2016
Category:
Upload: isha
View: 43 times
Download: 0 times
Share this document with a friend
Description:
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 - PowerPoint PPT Presentation
Popular Tags:
19
Week 11 Object Oriented Design Jerry Kotuba SYST39409- Object Oriented Methodologies 1
Transcript
Page 1: Week 11

SYST39409- Object Oriented Methodologies 1

Week 11Object Oriented Design

Jerry Kotuba

Page 2: 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)

Jerry Kotuba

Page 3: Week 11

Design Models with Their Respective Input Models

3

Page 4: Week 11

SYST39409- Object Oriented Methodologies 4Jerry Kotuba

Page 5: Week 11

SYST39409- Object Oriented Methodologies 5

ICE-08 Review

Jerry Kotuba

Page 6: Week 11
Page 7: Week 11

SYST39409- Object Oriented Methodologies 7Jerry Kotuba

Page 8: Week 11

SYST39409- Object Oriented Methodologies 8Jerry Kotuba

Page 9: Week 11

SYST39409- Object Oriented Methodologies 9Jerry Kotuba

Page 10: Week 11

SYST39409- Object Oriented Methodologies 10Jerry Kotuba

Use-Case Controller is responsible for coordinating andsequencing the interactions between the system and its actors, whilepreserving the integrity of the data and the flow defined in the usecase specification.

Three different types of objects usually participatein a use-case realization, each one encapsulating a different kind ofbehaviour.

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 tothe system into events in the system, and vice-versa;

• entity objects are used to handle information that outlives usecases and often persistent;

• control objects are used to encapsulate behaviour related to aspecific use case that isn't naturally placed in any of theprevious two types of objects, such as coordination, sequencing,transaction, and control of other objects. Control objects usuallylast only during the execution of one use case.

Page 11: Week 11

SYST39409- Object Oriented Methodologies 11Jerry Kotuba

Page 12: Week 11

SYST39409- Object Oriented Methodologies 12Jerry Kotuba

Page 13: Week 11

SYST39409- Object Oriented Methodologies 13Jerry Kotuba

Page 14: Week 11

SYST39409- Object Oriented Methodologies 14Jerry Kotuba

User interface for the Place Order use case.

Page 15: Week 11

SYST39409- Object Oriented Methodologies 15Jerry Kotuba

Use Case Realization

Page 16: Week 11

Standard Stereotypes Found in Design Models

16

Page 17: Week 11

SYST39409- Object Oriented Methodologies 17Jerry Kotuba

Business Logic LayerInterface Layer

Page 18: Week 11

SYST39409- Object Oriented Methodologies 18

ICE-09

Jerry Kotuba

Page 19: Week 11

SYST39409- Object Oriented Methodologies 19

Next Week

Sequence Diagrams continued…

Jerry Kotuba


Recommended