20.UseCaseAnalysis

20.UseCaseAnalysis - Use Case Analysis continued Control...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright 1998-1999 Rational Software, all rights reserved 1/18 Use Case Analysis – continued Control Classes Building Analysis Classes (Modified considerably by your Instructor)
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright 1998-1999 Rational Software, all rights reserved 2/18 Control Classes A class used to model control behavior specific to one or more use cases . Encapsulate use-case-specific behavior. Behavior of a control object is closely related to the realization of a specific use case . Might ‘say’ control objects " run " the use-case realizations. Some control objects can participate in more than one use-case realization if the use-case tasks are strongly related. Similarly, some use cases may require more than one control class; but in general, there is a one-to-one correspondence – as a heuristic.
Background image of page 2
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright 1998-1999 Rational Software, all rights reserved 3/18 Use Case Use-case dependent , Environment independent <<control>> Analysis class stereotype What is a Control Class? Is a Use-case behavior coordinator; sequences; controls; orchestrates use-case. One control class per use case (generally)
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright 1998-1999 Rational Software, all rights reserved 4/18 Control Classes – not always needed Provides coordinating behavior in the system. The system sometimes can perform some use cases without control classes (just using entity and boundary classes) – particularly use case only involves simple manipulation of stored information. Complex use cases generally require one or more control classes to coordinate the behavior of other objects in the system. Examples of control classes include Transaction managers, Tesource coordinators and Error handlers. Think about these activities!!
Background image of page 4
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright 1998-1999 Rational Software, all rights reserved 5/18 Control Classes decouple : Decouple boundary objects from one another, making the system more tolerant of changes in the system boundary. Also decouple use-case specific behavior from the entity objects , making them (the entity objects) more reusable across use cases and systems. Note: we are in the initial stages of ‘design’ Decoupling may positively affect some of the non- functional requirements (that are addressed in design in considerable detail), such as maintainability, performance, reusability .
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
OOAD Using the UML - Use-Case Analysis, v 4.2 Copyright 1998-1999 Rational Software, all rights reserved 6/18 Control Class provided behavior : Surroundings-independent (does not change when the surroundings / environment change) Define control logic Order/Direct sequence of activities to realize the use- case. (Consider registering for courses….
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 07/26/2011 for the course CEN 6016 taught by Professor Sanchez,a during the Spring '08 term at UNF.

Page1 / 18

20.UseCaseAnalysis - Use Case Analysis continued Control...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online