Architecture Driven OO Development

1
Architecture Driven OO Development

• Paul Sorenson
• Dept. of Computing Science
• University of Alberta

Special Acknowledgements Jim Hoover and Tony
Olekshy I much of this from a course they offer
2
Introduction

• Short-term Goal Provide you with guidelines on
  how you might go about your product/project
  development
• Long-term Goal Give you real experience using a
  good method with associated tools.

3
Software Project Culture
Every software project follows one of several
cultural styles Booch96.

• Calendar-driven obsessive focus on schedule
• Requirements-driven rigid focus on outwardly
• observable behaviour of system
• Documentation-driven degenerate form of
  requirements-driven style with software process
  gone mad
• Quality-driven obsessive focus on specific
  quantifiable
• measures scalability, extensibility,
  portability, reusability
• can't be measured

4
Architectural Driven

• Architecture-driven natural evolution of
  requirements-driven focus is on creating
  framework that satisfies all known hard
  requirements, yet is resilient enough to adapt to
  poorly understood or unknown requirements
  scalability, extensibility, portability,
  reusability are major concerns decisions are
  based on satisfying immediate concerns, while
  also giving reasonable flexibility for future
  issues incremental and evolutionary.

5
Architectural Driven (continued)

• Architecture-driven development uses software
  process and technology to support an incremental
  and evolutionary approach to delivering
  solutions. This "release early and often"
  approach provides one of the best ways of
  managing risk in an environment where there is
  incomplete and changing understanding of the
  problem to be solved and the technology available
  to solve it.

6
System Development Views
vocabulary functionality
vocabulary functionality
Design View
Implementation View
Use Case View
behaviour
Process View
Deployment View
distribution deliver installation
performance scalability throughput
7
Topic Two

• Details about this topic
• Supporting information and examples
• How it relates to your audience

8
Topic Three

• Details about this topic
• Supporting information and examples
• How it relates to your audience

9
Real Life

• Give an example or real life anecdote
• Sympathize with the audiences situation if
  appropriate

10
What This Means

• Add a strong statement that summarizes how you
  feel or think about this topic
• Summarize key points you want your audience to
  remember

11
Next Steps

• Summarize any actions required of your audience
• Summarize any follow up action items required of
  you