Architects ó the acid test
(10 ways to tell if you are a good architect)
Proposal for a think tank session at Object Technology 98
Jan Purchase
12 February, 1998
A session at OT97 concluded that Architecture is a set of patterns applied across the structure of a development project. Agree or not with that definition, many people feel that there is still no consensus definition of the terms architecture or architect, even if most people have an ëinstinctiveí feel for what the terms mean. Perhaps more importantly, there is no clear definition of what makes a good architect. Consequently, while there are commercial available C++, Java and even OO design tests with which companies can grade perspective employees, there remains no such test for architects. The goal of this session is to devise such a test.
Objectives
-
To reach a consensus, among the participants, on what skills are required to be a good architect
-
To determine which of these skills can be measured in a one hour job interview test
-
To design such a test
Who Should Attend?
Anyone who considers themselves to be, or to know, a good architect. Anyone faced with the task of recruiting architects into their business. Anyone who feels that the job title 'architect' is too easily awarded. Anyone looking for a new job as an architect!
Output
Participants will be encouraged to think of two skills that they consider important for architects before attending the think tank. As the session runs we will build a poster enumerating key architect skills and how they can be measured. Finally an outline architectís test will be devised from the brainstorming session and this too will form the basis of a poster. If enough interest is shown, a BOF might be called later to refine the test and architects invited to take it.
Structure of the Session
The session will be split into four activities
-
An introduction of the problem and some initial guidelines. (10min)
-
A quick brainstorming session (in small teams) to determine which skills are important and which of them can be measured (15min)
-
A brief round robin presentation of conclusions and preparation of a shortlist (10min)
-
A longer brainstorming session (in small teams) to devise tests for each skill (25min)
-
A round robin presentation of test questions and a vote to determine which are worthy (15min)
Session Leader
Jan Purchase has been designing and implementing object systems since 1988. He has extensive experience of mentoring, teaching and above all using object design and implementation skills within banks and the public service industries in UK and the US. Since 1994 he has enjoyed leading roles in financial institutions involving the design and development of extensible and flexible software structures. He is currently designing just such a framework for Bankers Trust's Derivatives Trading department. His job title has featured the word 'architect' for four years.