1 / 12

Use Case Controller

Use Case Controller. System sequence diagram (SSD) shows input messages from external actors within use case Only indicates that messages go to system Use case controller classes are designed as collection point for incoming messages Artifact – class invented to handle needed system function

ovidio
Download Presentation

Use Case Controller

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. Use Case Controller • System sequence diagram (SSD) shows input messages from external actors within use case • Only indicates that messages go to system • Use case controller classes are designed as collection point for incoming messages • Artifact – class invented to handle needed system function • Use case controller acts as intermediary between outside world and internal system

  2. Designing with Sequence Diagrams • Sequence diagrams used to explain object interactions and document design decisions • Documents inputs to and outputs from system for single use case or scenario • Captures interactions between system and external world as represented by actors • Inputs are messages from actor to system • Outputs are return messages showing data

  3. SSD for the Look Up Item AvailabilityUse Case

  4. First-Cut Sequence Diagram • Start with elements from SSD • Replace :System object with use case controller • Add other objects to be included in use case • Select input message from the use case • Add all objects that must collaborate • Determine other messages to be sent • Which object is source and destination of each message?

  5. Objects included in Look Up Item Availability

  6. First-Cut Sequence Diagram for the Look Up Item Availability Use Case

  7. Guidelines for Preliminary Sequence Diagram Development • Take each input message and determine internal messages that result from that input • For that message, determine its objective • Needed information, class destination, class source, and objects created as a result • Identify complete set of classes affected by each input message • Select objects from domain class diagram • Flesh out components for each message

  8. Developing a Multilayer Design for Look up item availability • First-cut sequence diagram – classes in domain layer • Add design for user-interface classes – view layer • Forms added as windows classes to sequence diagram • Add design for data access classes – data access layer with separate classes for database • Tools build GUI and problem domain classes • Java and Visual Studio.NET

  9. Look Up Item Availability Use Case with View Layer and User-Interface Object

  10. Partial Three-Layer Design forLook Up Item Availability

  11. Updating the Design Class Diagram • Design class diagrams developed for each layer • New classes for view layer and data access layer • New classes for domain layer use case controllers • Sequence diagram’s messages used to add methods • Constructor methods, • Data get and set method • Use case specific methods

  12. Design Class, with Method Signatures, for the Order class

More Related