[epf-dev] Agile 2007 Abstract: OpenUP Architecture

[Jim Ruehlin <jruehlin@xxxxxxxxxx>]

Hello all,

 

I'm considering submitting the following abstract for Agile 2007. Any
comments you have are welcome. I have to submit this by Friday so please
respond before then.

 

Thanks,

Jim

 

 

Architecture the OpenUP Way: An Agile and Unified Approach to
Architecture

 

Topic Summary

The purpose of a good architecture is to assure you can keep delivering
business value in your software far into the future. However, Agile
teams often have difficulties defining what the architecture is and how
to produce it. It seems like a proper Agile method would allow the
architecture to emerge over the course of development. But experienced
practitioners have encountered serious problems in later iterations when
a defined architecture isn't created in early iterations. From a
practical perspective, experienced developers tend to work on
architectural issues in early iterations to achieve overall system
stability. But how much architecture is enough? How does a team create a
robust system without over-analyzing the architecture in early
iterations? How can long-term business value be supported without
sacrificing the delivery of value in the next iteration?

This presentation illustrates how to build architectures in an agile way
by leveraging OpenUP/Basic architectural guidelines. The presentation
describes how to focus on architecture in early iterations without
sacrificing business value. It defines what architecture is in an agile
context, how to define just enough architecture, and how to evaluate
when the architecture is complete and verified. Attending this
presentation will provide context for creating just enough architectural
information to support the long-term delivery of business value.

OpenUP/Basic is available for free download from www.eclipse.org/epf.

 

This presentation is geared towards developers tasked with defining
robust systems, and the developers who use those definitions to fully
realize the system. Developers of all experience levels will find it
useful.

 

Attendees will benefit from understanding OpenUP/Basic architectural
guidelines by:

*	Increasing their ability to judge how much architectural
description is useful without getting stuck in architectural analysis.
*	Learning how to create and describe architectural mechanisms
that solve architecturally significant requirements such as persistence,
logging, and security.
*	Understanding what kinds of architectural representations can be
useful in an agile context.
*	Learning which architectural representations are appropriate for
different circumstances.
*	Gaining a context that makes defining the architecture a
first-order goal.
*	Acquiring insight into identifying architecturally significant
requirements.

 

Outline

*	Architecture in an agile context
*	Identifying architecturally significant requirements
*	Reaching the initial architectural state (proof of concept)
*	Choosing the right architectural descriptions
*	Identifying and evolving architectural mechanisms
*	Balancing architectural value with business value
*	Validating the architecture
*	Knowing when the architecture is complete

 

 

____________________

Jim Ruehlin, IBM Rational

RUP Content Developer

Eclipse Process Framework (EPF) Committer www.eclipse.org/epf

email:   jruehlin@xxxxxxxxxx

phone:  760.505.3232

fax:      949.369.0720