Unit 7 Flashcards
Dynamic Modeling
Dynamic modeling represents the interaction of the building blocks of the information system with each other and with the outside world to satisfy the behavioral requirements of the system.
Dynamic Modeling (interactions, messages, objects, time, order)
Dynamic modeling is also interaction. Unlike the real world in which objects interact in many different ways, residents of a virtual world can only interact through messages
.Dynamic modeling features objects.
Interactions happen in time. Therefore, dynamic modeling must show not onlywho interacts with whom and how, but in whatorder.
Review Methods & Messages Graphic
Do it
Accessor Operations
Accessor operations change or return the value of an attribute.
•The get operation returns the value of the attribute to the public.
•The set operation changes the value of the attribute.
The syntax of an accessor operation is different from that of a normal operation.
•getName()
Parameters and Value
Parameters, or arguments, specify the data that must be supplied to an object to carry out a specific operation:Examples:
•orderDrink(drink, quantity)
•orderAppetizer(Appetizer)
•getMenu()
•orderMainCourse(whisky, on the rocks, many)Return value is the reply that a message may invoke from the receiving object after an operation is complete.
Syntax for Method Specification
The exact syntax for declaring operations and sending messages is language dependent.
[Visibility] [Return Type] Name
Public Currency payBill(amount, paymentType)
Dynamic Diagrams
Sequence diagram
Emphasizes the order of interactions in time.
Collaboration diagram
Focuses on how the object are organized and what set of messages they must exchange to satisfy a certain behavior.
Statechartdiagram
Traces the results of interactions on the state of objects belonging to a specific class.
Sequence Diagram
Sequence diagram represents the interaction between objects, or between actors and objects ordered in time.
A sequence diagram is composed of a timeline, objects that interact across this timeline, and the messages that they exchange.
System Sequence Diagram (SSD)
A UML sequence diagram at a high (system) level
Special case for a sequence diagram
Only shows actor and one object
The one object represents the complete system
Shows input & output messaging requirements for a use case
Review System Sequence Diagram (SSD) Notation Graphic
Do it
Internal Sequence Diagram
An internal sequence diagram at a detailed level
shows actor and all internal objects that make up the system
shows interactions between the objects to implement a use case
Review Sequence Diagram Graphic
Do it
Sequence Diagram
The objectsacross the top of the diagram are interacting with each other by passing messagesback and forth (horizontal).
An actor is the user whose interactions with the system are described in each of the use cases (horizontal).
The object lifetimerepresents time and starts with the top-most message (vertical).
Elements of Sequence Diagram
Actor Instance: outside the system
.Instance Name:ActorName
aCustomer:Customer
Class Instance: inside the system
Instance Name:ClassName
Timeline—dotted vertical line.
Message & Timeline Forking: Specifies alternates.
Message to Self & Looping: Specifiesrepeats.
Review Appointment Use Case Graphic & Sequence Diagram
Do it