OOD

1
OOD

• IEM - March 9-10, 2001Callahan

2
Big Picture

• Computer science
• Software engineering
• Systems engineering

3
SW Engineering Processes

• Waterfall method
• Evolutionary development
• Formal
• Assembly from components

4
Ch. 5 Booch

• Notation
• UML (modified Booch) and others are verbose
• use what works
• use what provides meaning only
• Design views
• logical vs. physical
• static vs. dynamic
• Modeling diagrams

5
Modeling diagramsCh. 5

• Class diagrams - pg. 176
• Object diagrams
• Module diagrams
• Process diagrams
• State transition diagrams - pg. 199
• explains thestate of a class - pg.. 203
• Interaction diagrams

6
Ch. 6 Booch

• Project needs
• strong architectural vision (takes time)
• well managed incremental development lifecycle
• Macro process
• overall design
• Micro process
• object (or other type) of code design

7
Macro Process

• 1. Establish core requirements
• 2. Develop a model of desired behavior
• 3. Create a design
• 4. Design loop (evolutionary development)
• 5. Manage post delivery

8
Micro Process

• 1. Identify classes and objects
• 2. Identify class and object semantics
• 3. Identify class and object relationships
• 4. Specify class and object interfaces and
  implementations
• These all happen together and evolve.

9
In any Process Used

• Each step should have
• Purpose
• Products
• Activities
• Measures

10
Ch. 7 Booch

• OO pros
• allows for continual development
• Encourages reuse of code
• OO cons (possible)
• performance of code
• startup costs

11
Software Quality Measures

• Defect discovery rate
• Defect density ( of defects per 1000 lines of
  code)
• Key issue - proper management
• who measures who
• accountability of accurate results