RUP Use-Case Design




1.       Identify participating design classes: derived from analysis classes in analysis-level use-case realization, derived from special requirements on a use-case realization, or discovered during design


2.       Describe design object interactions as one or more diagrams of sequences of messages among actor instances and design objects

·          Use case invoked by a message from an actor to a design object

·          Each participating design class should have an object in at least one diagram

·          Messages should be (or become) operations on the receiving object’s class

·          Use labels and textual flow-of-events to complement the diagrams

·          Sequence diagram should handle all use case relationships (generalizes, extends, etc.)


3.       Identify all alternative paths, especially new ones

·          Time-outs when nodes or connections fail

·          Erroneous input

·          Error messages and exceptions


4.       Identify participating subsystems and interfaces and show interactions at sub-system level

·          more coarse granularity than classes/objects

·          Identify bottom-up and/or top-down

·          Fine-grained ßà Coarse-grained

·          Capture implementation requirements


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s