Discussion Questions Chapter 2 ObjectOriented Software Engineering Bruegge
Discussion Questions Chapter 2 Object-Oriented Software Engineering Bruegge and Dutoit Jay Fenwick CS 4667
Chapter 2 • Why did text choose UML as notation? • What are the 3 system models we must develop? What is being modeled by each? How are they represented in UML? • How does text iteratively introduce UML? • What are the 5 primary UML diagrams we’ll use?
Chapter 2 • Use Case Diagrams • • When used What represent What is an actor What is figure 2 -1 “saying” Simple. Watch Read. Time Watch. User Set. Time Change. Battery Watch. Repair. Person
• Class Diagrams • When used • What represent • What are: class, object, association • What is figure 2 -2 saying Simple. Watch 2 Push. Button 1 Display 1 1 2 1 Battery Time
Chapter 2 • Interaction diagrams • • When used What represent Which specific kind of interaction diagram is used What is figure 2 -3 saying : Simple. Watch : Watch. User press. Button 1() blink. Hours() press. Button 1() blink. Minutes() press. Button 2() : Display increment. Minutes() refresh() press. Buttons 1 And 2() commit. New. Time() stop. Blinking() : Time
• Statechart diagrams • What represent • How different from sequence diagram • Activity diagrams • What represent
Chapter 2 • Terms and Concepts • • System, subsystem Modeling ↔Complexity Modeling↔Abstraction↔View↔Notation Datatype↔Class; ADT↔Abstract. Class; Instances Event, message Application & Solution Domains↔OOA & OOD Falsification: what, how done in software, limits
Chapter 2 • Use Case diagram details • What is difference between use case and scenario • When is an include relationship used • Class diagram details • Representation differences: class, object • Representation differences: association, link • Association concepts (what, how represented) – – Navigation, labeling (roles) Types (regular, aggregation, inheritance, qualified) Attributes/Operations (classes); diffs in figures 2 -25, 2 -26 Multiplicity
Emergency. Report reports. Generated 1 Incident 1. . * incidents. Generated Dispatcher Field. Officer name: String badge. Number: Integer * reports 1 author name: String badge. Number: Integer 1 initiator *
Chapter 2 • Interaction diagram details • • Types (sequence, collaboration) Differences between types Difference between figures 2 -11, 2 -34 How represent conditional, repetitive behavior • Statechart • Actions, internal transitions, activities • How reduce complexity • Differences with Interaction modeling
Chapter 2 • Complex systems have complex models • Packages • Stereotypes • Constraints • Exercises • All are good! • HOMEWORK: 2 -1, 2 -6: 2 -10, 2 -13 • References • http: //www-306. ibm. com/software/rational/uml/ • http: //www. agilemodeling. com/essays/uml. Diagrams. htm • http: //www. sparxsystems. com. au/UML_Tutorial. htm
- Slides: 11