Section 5, Analysis: Dynamic Modeling .

Uploaded on:
Section 5, Examination: Dynamic Displaying. Diagram. Dynamic displaying Grouping outlines State graphs Utilizing dynamic demonstrating for the configuration of client interfaces Investigation illustration Necessities examination archive layout. Illustration of utilization case position. Use case name ReportEmergency Passage condition
Slide 1

Part 5, Analysis: Dynamic Modeling

Slide 2

Outline Dynamic displaying Sequence graphs State charts Using dynamic demonstrating for the plan of UIs Analysis illustration Requirements examination archive layout

Slide 3

Example of utilization case design Use case name ReportEmergency Entry condition 1. The FieldOfficer initiates the "Report Emergency" capacity of her terminal. Stream of occasions 2. Companion reacts by exhibiting a shape to the officer... 3. The FieldOfficer fills the form.... 4. The Dispatcher surveys the data presented by the FieldOfficer ... Leave condition 5. The FieldOfficer gets the affirmation and the chose reaction.

Slide 4

How would you discover classes? From past addresses Application space examination: Talk to customer to distinguish deliberations Apply general world information and instinct Scenarios Natural dialect plan of a solid use of the framework Use Cases Natural dialect definition of the elements of the framework Textual investigation of issue articulation (Abbot) From this address Dynamic model Events: Candiates for operations to be offered by classes Sequence graphs as hotspots for articles From future addresses Design Patterns

Slide 5

Dynamic Modeling with UML Diagrams for element displaying Interaction outlines portray the dynamic conduct between items Statecharts depict the dynamic conduct of a solitary protest Interaction charts Sequence Diagram: Dynamic conduct of an arrangement of articles masterminded in time grouping. Useful for continuous particulars and complex situations Collaboration Diagram : Shows the relationship among items. Does not demonstrate time State Charts: A state machine that portrays the reaction of a protest of an offered class to the receipt of outside jolts (Events). Action Diagram: Special kind of statechart where all states are activity states

Slide 6

Dynamic Modeling Definition of element model: A gathering of various state graph outlines, one state outline chart for each class with vital element conduct. Reason: Detect and supply techniques for the question demonstrate How would we do this? Begin with utilize case or situation Model collaboration between items => arrangement chart Model element conduct of single articles => statechart outline

Slide 7

Start with Flow of Events from Use Case Flow of occasions from "Dial a Number" Use case: Caller lifts collector Dail tone starts Caller dials Phone rings Callee answers telephone Ringing stops ....

Slide 8

What is an Event? Something that occurs at a point in time Relation of occasions to each other: Causally related: Before, after, Causally disconnected: simultaneous An occasion sends data starting with one question then onto the next Events can be gathered in occasion classes with a various leveled structure. "Occasion" is regularly utilized as a part of two courses: Instance of an occasion class: "New IETM issued on Thursday September 14 at 9:30 AM". Occasion class "New IETM", Subclass "Figure Change" Attribute of an occasion class IETM Update (9:30 AM, 9/14/99) Car begins at ( 4:45pm, Monroeville Mall, Parking Lot 23a) Mouse catch down(button#, tablet-area)

Slide 9

Sequence Diagram From the stream of occasions in the utilization case or situation continue to the grouping outline A succession chart is a graphical depiction of articles partaking in an utilization case or situation utilizing a DAG documentation Relation to protest distinguishing proof: Objects/classes have as of now been recognized amid question demonstrating Objects are distinguished accordingly of element displaying Heuristic: An occasion dependably has a sender and a beneficiary. Discover them for every occasion => These are the articles taking an interest in the utilization case

Slide 10

An Example Flow of occasions in a "Get SeatPosition" utilize case : 1. Build up association between keen card and locally available PC 2. Build up association between locally available PC and sensor for seat 3. Get ebb and flow situate position and store on shrewd card Which are the items?

Slide 11

Sequence Diagram for "Get SeatPosition" Seat Onboard Computer Smart Card 1. Build up association between shrewd card and locally available PC 2. Set up association between locally available PC and sensor for seat 3. Get momentum situate position and store on brilliant card Establish Connection Establish Connection Accept Connection Accept Connection Get SeatPosition "500,575,300"

Slide 12

Heuristics for Sequence Diagrams Layout: first segment: Should compare to the performer who started the utilization case second section: Should be a limit question third segment: Should be the control protest that deals with whatever is left of the utilization case Creation: Control articles are made at the start of an utilization case Boundary items are made by control objects Access: Entity articles are gotten to by control and limit objects, Entity items ought to never call limit or control questions: This makes it simpler to share substance questions crosswise over utilize cases and makes element objects strong against innovation incited changes in limit objects.

Slide 13

Is this a decent Sequence Diagram? Situate Onboard Computer Smart Card Did the modeler take after the heuristics? Build up Connection Establish Connection Accept Connection Accept Connection Get SeatPosition "500,575,300"

Slide 14

UML Statechart Diagram Notation Event trigger With parameters Notation in view of work by Harel Added are a couple question arranged alterations An UML statechart chart can be mapped into a limited state machine State1 State2 Event1(attr) [condition]/activity do/Activity Guard condition passage/activity leave/activity Also: inner move and conceded occasions

Slide 15

Statechart Diagrams Graph whose hubs are states and whose coordinated bends are moves named by occasion names. Recognize two sorts of operations: Activity : Operation that sets aside opportunity to finish related with states Action : Instantaneous operation related with occasions related with states (decreases drawing multifaceted nature): Entry, Exit, Internal Action A statechart outline relates occasions and states for one class A question display with an arrangement of articles has an arrangement of state graphs

Slide 16

State A deliberation of the quality of a class State is the total of a few traits a class Basically a comparability class of each one of those property estimations and connections that do no should be recognized the extent that the control structure of the framework is concerned Example: State of a bank A bank is either dissolvable or wiped out State has term

Slide 17

Example of a StateChart Diagram coins_in(amount)/set adjust Collect Money Idle coins_in(amount)/add to adjust scratch off/discount mint pieces [item empty] [select(item)] [change<0] do: test thing and register change [change>0] [change=0] do: apportion thing do: roll out improvement

Slide 18

Nested State Diagram Activities in states are composite things signifying other lower-level state charts A lower-level state graph relates to a sequency of lower-level states and occasions that are imperceptible in the more elevated amount outline. Sets of substates in a settled state outline signifying a superstate are encased by an extensive adjusted box, likewise called form.

Slide 19

Example of a Nested Statechart Diagram coins_in(amount)/set adjust Collect Money Idle coins_in(amount)/add to adjust wipe out/discount currencies [item empty] [select(item)] [change<0] Superstate do: test thing and register change [change>0] [change=0] do: apportion thing do: roll out improvement

Slide 20

Expanding action "do:dispense thing" \'Administer thing\' as a nuclear action: [change=0] do: apportion thing \'Apportion thing\' as a composite action: do: push thing off rack do: move arm to segment do: move arm to column Arm prepared Arm prepared

Slide 21

Superstates Goal: Avoid spaghetti models Reduce the quantity of lines in a state chart Transitions from different states to the superstate enter the primary substate of the superstate. Moves to different states from a superstate are acquired by all the substates (state legacy)

Slide 22

Modeling Concurrency Two sorts of simultaneousness 1. Framework simultaneousness State of general framework as the accumulation of state graphs, one for each protest. Each state chart is executing simultaneously with the others. 2. Protest simultaneousness A question can be parceled into subsets of states (traits and connections) to such an extent that each of them has its own subdiagram. The condition of the question comprises of an arrangement of states: one state from each subdiagram. State outlines are partitioned into subdiagrams by spotted lines.

Slide 23

Example of Concurrency inside an Object Splitting control Synchronization Emitting Do: Dispense Cash taken Cash Ready Setting to r eset Up Ready Do: Eject Card taken

Slide 24

State Chart Diagram versus Sequence Diagram State outline outlines help to distinguish: Changes to objects after some time Sequence outlines help to recognize The fleeting relationship of between items over the long run Sequence of operations as a reaction to one metal more occasions

Slide 25

Dynamic Modeling of User Interfaces Statechart graphs can be utilized for the plan of UIs Also called Navigation Path States: Name of screens Graphical format of the screens related with the states helps while exhibiting the dynamic model of a UI Activities/activities are appeared as shots under screen name Often just the leave activity is indicated State moves: Result of leave activity Button click Menu determination Cursor developments Good for electronic UI outline

Slide 26

Navigation Path Example (15-499 Spring 96) Diagnostics User can move cursor to Control Panel or Graph User can choose information gathering and kind of diagram Control board User can choose usefulness of sensors Selection User chooses information aggregate Field site Car Sensor bunch Time go User chooses sort of chart timetable histogram pie diagram Define User characterizes a sensor occasion from a rundown of

View more...