Home | Login | Recent Changes | Search | All Pages | Help

SoftwareArchitectureSessionFramework

Session Objective: to identify and discuss the components of a working definition of what the role of a software architect is.

This session is a combination of small group and panel discussion. The panel consists of Bob King, Kevin Fjelsted, Brian Pioreck, Dave Smith and Nynke Fokma and will be moderated by Steve Smith.

Agenda

• Develop the premise

The role on software projects of experienced technical people who do not code is hard to explain. Yet, it is a critical role for a successful project. Is it simply design? If so, why do we make a distinction between architecture and design? If not, what are the pieces of work that are done in the process of software architecture?

In smaller groups:

• Identify and discuss the components of an initial working definition
• Use real life "mini-cases" to examine our working definition

   Some examples from my experience follow; we will use many more in the session.  Please add your own.  Ask yourself if you think "software achitecture" is happening, who is doing it and what it is that they are doing.
     AddingStructureToDevelopmentProcess
     WhenToBeginTesting
     ArbitraryDocumentation
     ProjectCharterApproachCreation
     [add your own here]
  

• Modify components of the working definition

• Reconvene into panel discussion to present and discuss components of the working definitions

BobKing