Immature methodologies [2]
As I wrote earlier - the architecture methodologies are not mature. So what do we need? I think we need a simple protocol (with examples) for making inventories in the different stages of architecture development. For example:
- stage 1, list main drivers & objects, then create an architecture vision based on how architecture can contribute to achieving the main objectives
- stage 2, create a context diagram and list the core functions and related business services, assesss for each function or interface if it is an issue / improvement area and then prioritise, based on the key objectives from stage 1
- stage 3, list key functions & key data types, create a mapping matrix between the two, and check where the identified key issues of stage 2 should be address (e.g. through rationalisation of the architecture) ...
- etc.
My view is that a good architecture method should provide a simple cookbook - step by step - with some minimum standards for a few diagrams and decisions trees. Most methods I have seen try to do this, but go overboard with too much detail, too many different types of diagrams and a clear spill over into the system design space.
Labels: architecture, methodology
posted by Evert Ruijs @ 10:25 AM
0 Comments:
Post a Comment
<< Home