Introduction to Software Engineering

More documents

Recommendations

Info

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

Conceptual Modeling Conceptual models are about real-world entities in the problem domain and not about software •Conceptual models are useful for: ● understanding the problem domain – identify important entities, their characteristics, relations to one another ● setting data requirements – data requirements can be extracted from conceptual models ● validating requirements Winter 2009, Maheswaran Introduction to Software Engineering – ECSE321 Unit 7 - Analysis/10
Classes and Objects • An object is an entity that holds data and exhibits behavior. • A class is an abstraction of a set of objects with common operations and attributes. • An attribute is a data item held by an object or class. • An operation is an object or class behavior. • An association is a connection between classes representing a relation on the sets of instances of the connected classes. 11 Winter 2009, Maheswaran Introduction to Software Engineering – ECSE321
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: Types of Class Models • Analysis
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 and 54: Summary… •There is a process fo
Page 55 and 56: Why do we need a dynamic model? •
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

Create successful ePaper yourself

Delete template?

Save as template?