1
Page
235 Review Notes of Analysis and Design Models
Design Class Diagram
Shows: Façade Class/Object
Classes with Attributes and Operations
Visibilities between classes (links with multiplicities)
Operations are for object as a receiver/server of messages
Visibilities show to which objects those in this class can send messages
May show: Visibilities of attributes and operations
Qualified associations
Does not show: what messages are sent to other objects or who the receiver would
be. Must look at an interaction diagram to see that.
Interaction diagram:
System Sequence Diagram
Shows: Sequence of messages from actor(s) to the system (façade object)
May show: Return messages (output) from system to actor(s)
Does not show: Any messages internal to the system
Sequence Diagram
Shows: Sequence of messages from actor(s) to the system (façade object)
Sequence of internal messages in response to receipt of a system
operation message
May show: Return messages (output) from system to actor(s)
System Operation Contract
Shows: Pre- and post-conditions for one system operation
What input parameters must be validated or verified.
What objects must be created
What associations must be created
Domain Model
Shows: Concepts in the application domain with their attributes
Associations between concepts with multiplicities
Generalization-specialization hierarchies
May show: Whole-to-part associations (aggregation and composition)
Does not show: operations
An attribute is an attribute of one and only one concept
Show relationships with associations, not attributes
A subtype has all the attributes and associations of its supertype(s)
Expanded Essential Use Case Narrative
Shows: Verbal description of the interaction sequence between an actor and the
system for a use case
The actor’s action, the expected system response, and exceptions.
Pre-conditions and postconditions for the use case.
Should show the structure of the messages from the actor
Should show explicitly all the input parameters of each message.
Should show explicitly what the actor receives at the conclusion of the use
case.
May show: Other requirements (see the textbook)
Does not show: Any specific implementing technology
Use Case Diagram
Shows: All the use cases in the scope of the system
All the actors who participate in each use case
May show: Who is the initiating actor for each use case
Does not show: Any messages or information flow between actors and use cases
Events, shows use cases
Event Table
Shows: All the business events in the scope of the system
All the actors who provide inputs and outputs for each event
A name describing each input and output
Whether an event is temporal or external may be inferred from its pattern
of inputs and outputs
May show: Which is the initiating actor for each use case
Does not show: The composition of inputs or outputs, i. e., the data elements
contained in these information flows