A Development Process

1
A Development Process

• Lecture OO07
• An Iterative Development Method

2
References

• Booch, et al, The Unified modeling Language
  Users Guide, AWL, 1999, Chapt 2, Appendix C

3
Teaching Points

• Macro Process
• Micro Process
• Work Products

4
Review

• How do we build a Use Case Diagram?
• What is a software engineering method?

5
The Method

• Process (Macro/Micro)
• Notation (UML)
• Tool (Rational Rose)

6
Macro ProcessBased on Objectory process

• Establish business rational and scope (Inception)
• High level requirements analysis, architectural
  design (Elaboration)
• Evolve the implementation (Construction)
• Performance tuning, user training, beta test
  (Transition)

7
Micro Process

• Identify the classes and objects at a given level
  of abstraction
• Identify the semantics of these classes and
  objects
• Identify the relationships among these classes
  and objects
• Specify the interface and then the implementation
  of these classes and objects

8
Iteration

• The process of elaboration/construction is a
  repetitive application of the micro process

9
Inception (Purpose)

• Establish roughly how much it will cost and what
  the benefit will be.
• Establish a vision for the system and validate
  its assumptions
• Initial analysis to get sense of the projects
  scope

10
Inception (Products)

• Preliminary business case
• Initial Use Case diagrams

11
Elaboration (Purpose)Domain Analysis

• Provide a description of the problem
• Elaboration focuses on behavior, not form
• NOT an exhaustive understanding of the systems
  behavior.
• It is sufficient to accomplish an Elaboration of
  all the primary behaviors of the system, with
  some secondary behaviors considered as well to
  ensure that no essential patterns of behavior are
  missed.

12
Elaboration (Products)Domain Analysis

• Use Case Diagrams
• Object interaction diagrams to denote each use
  case.
• Class diagrams to show associations among object
  classes
• Rudimentary class specifications
• STDs

13
Elaboration (Purpose)Architecture and planning

• To create an architecture for the evolving
  implementation
• To establish common tactical policies that must
  be used by disparate elements of the system
• localized mechanisms that appear throughout the
  system (eg. Error detection/handling, memory
  management, data storage management, approaches
  to control, domain specific tactics, etc.)

14
Elaboration (Products)Architecture and planning

• Class/Package diagrams
• Executable release plan
• Executable release prototype

15
Construction (Purpose)

• To grow and change the implementation through
  successive refinement, ultimately leading to the
  production system

16
Construction (Products)

• A stream of executable releases representing
  successive refinement to the initial
  architectural release.
• Releases every 6-8 weeks, depending on
  complexity.
• Who gets an executable release?
• Behavioral prototypes
• Evolving system documentation

17
Transition (Purpose)

• No new development to add functionality
• There is development to correct faults found
• Product tuning
• Optimization

18
Transition (Products)

• Maintain Analysis/Design documentation

19
Maintenance (Purpose)

• Is the activity of managing post delivery
  construction
• Similar to construction phase, but
• Architectural innovation is less of an issue.
• Localized changes are made as new requirements
  are added and lingering bugs fixed.

20
Maintenance (Products)

• Similar to construction

21
Teaching Points

• Macro Process
• Micro Process
• Work Products