Introduction to Software Engineering

More documents

Recommendations

Info

$(Microsoft PowerPoint - Topic 4.ppt [Mode de compatibilit\351])$

What is the ―dynamic‖ model • A model that captures behaviour • Diagrams for dynamic modeling ● Interaction diagrams describe the dynamic behavior between objects ● State charts describe the dynamic behavior of a single object • Interaction diagrams ● Sequence Diagram: • Dynamic behavior of a set of objects arranged in time sequence • Good for real-time specifications and complex scenarios • State Charts ● A state machine that describes the response of an object of a given class to outside input (events) Winter 2009, Maheswaran Introduction to Software Engineering – ECSE321 Unit 6 – Analysis /54
Why do we need a dynamic model? • Understand the flow of events • Understand lifespan of classes • Refine the static model ● Add classes: •Events •Sequence diagrams are a source for more objects • Identify operations for the object model • Dynamic model will typically be incomprehensible to the customer! Winter 2009, Maheswaran Introduction to Software Engineering – ECSE321 Unit 6 – Analysis /55
Page 1 and 2:
Introduction to Software Engineerin
Page 3 and 4: What Is Design? •Design is the cr
Page 5 and 6: Analysis Goals, Inputs, and Activit
Page 7 and 8: Analysis Models An analysis model i
Page 9 and 10: Types of Class Models • Analysis
Page 11 and 12: Classes and Objects • An object i
Page 13 and 14: A Brief UML Review - Names •A nam
Page 15 and 16: Attribute Specification Format name
Page 17 and 18: Operation Specification Format name
Page 19 and 20: Association Lines manages subordina
Page 21 and 22: Class Diagram Rules •Class diagra
Page 23 and 24: Class Diagram Heuristics… • Sti
Page 25 and 26: Object Diagrams •Object diagrams
Page 27 and 28: Object Attribute Format attribute-n
Page 29 and 30: Object Links •Show that particula
Page 31 and 32: Brief Recap •Engineering design b
Page 33 and 34: Conceptual Modeling •What is conc
Page 35 and 36: Uses of Conceptual Models •In pro
Page 37 and 38: Caldera Example Caldera is a smart
Page 39 and 40: Identifying Classes-Rationalizing
Page 41 and 42: Caldera Example - From Description
Page 43 and 44: Adding Attributes 1 •Study the SR
Page 45 and 46: Caldera Example, Draft 2 Homeowner
Page 47 and 48: Adding Associations- Rationalizing
Page 49 and 50: Caldera Example, Draft 3 Homeowner
Page 51 and 52: Caldera Example, Final Draft Homeow
Page 53: Summary… •There is a process fo
Page 57 and 58: Sequence Diagrams • From the flow
Page 59 and 60: Notations 1. Columns = objects 1. L
Page 61 and 62: submitReportToDispatcher() Mange Em
show all

Introduction to Software Engineering

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?