Solving the problems of a software architect

EuroPLoP Workshop

Leader: Charles Weir

 

Introduction

We don't really understand yet how to be Software Architects. So far there's only a tiny body of literature describing the knowledge and experience of those who've made a success of the job.

Yet the role of software architect does exist. Most of the delegates to EuroPLoP 1998 will, at least some of the time, fulfil this role. This workshop will share experience and knowledge between us; the output may be a basis for hatching patterns of successful architectural practice for the future.

In this workshop we'll concentrate on some of the problems we may all have faced doing this role, and see what solutions have worked for us. Some groups may choose to look at technical architectural issues; others at organisational issues. We'll expect interesting results from both.

Why attend?

You'll learn:

 Techniques for tackling some of the problems of an architect.

 Experience of other the strengths and failures of other projects.

 ... and it'll be fun!

Workshop format

Please bring along suggestions of one or two problems to analyse. Make them types of problems you've encountered more than once, which are likely to be familiar to others in the workshop.

To start the workshop, we'll collect some of these, and vote on a subset to analyse in more detail.

We'll work in teams of four or so. Each will examine a specific one of these problems. We'll work in phases, as follows:

  1. Identify and write down specific 'war stories' where the group members - or other teams we may know of - have encountered the issue. This 'grounds' the discussion, helping us to agree on terms and what we mean by the problem. It'll be important to be fairly disciplined about this, and not to move onto discussing possible solutions until the next step.
  2. Discuss possible solutions to the problems. What solutions were tried? Which ones worked? Which alternatives might have worked better?
  3. Collect the successful solutions, together with examples of their use, for possible patterns in future.
  4. Identify conclusions, and write them up on flip-chart sheets to share with other workshop teams.
  5. Discuss the results, whether formally or less so, with the whole group.

What we'll produce

The facilitator will take notes of the proposed solutions to write up for the web site and newsletter. They'll be a basis for anyone writing patterns on the subject.

EuroPLoP Home Page | Charles Weir's Home Page