IT Architecture needs to be taken more seriously than it usually is. This workshop will show you how to use quantified architecture requirements in order to quantify the effectiveness of all architecture ideas, as well as to quantify all related costs. This we call ‘architecture engineering’ It gives us a basis for evaluation, presentation, and agile followup of architecture. The workshop will gradually build up a practical understanding of, and ability to specify quality and value requirements, quantitatively. Then we will learn to specify and decompose architecture, so that we can estimate how good the architecture ideas are for our stated purposes and resource constraints.
Things You Can Expect to Learn:
- how to plan architecture as a team
- how to quantify all critical values and qualities
- how to estimate the values and costs of all architecture
- the meaning of ‘engineering’ in the architecture context
- how to present architecture ideas to other people, convincingly
- how to decompose large architecture ideas into smaller implementable ones (agile delivery)
- how to compare and evaluate competing architecture ideas quantitatively
- how to deal with architecture risk and uncertainty
- how to prioritize cost effective architecture
- how to relate many requirements to many architecture ideas
Limitations: There will be a stream of ‘new’ architecture concepts, at a very high rate, over ten per day, which are all interconnected. So you will be slightly overloaded. But at least you will have practiced the ideas, and worked on a team, building a complete system of requirements and architecture. You will be given documentation for further self study.
Workshop Mode: The class will form teams of 2 people, and work together on a self chosen architecture problem. The class teams will work in parallel on the same problem. The emerging requirements and architecture will be visible, and available, to all participants in real time. We will use an architecture engineering tool called app.Needsandmeans.com, to learn a specification language called ‘Planguage’ (Planning Language) which is a rich architecture modelling language, free and open.
Instructor: Tom Gilb
Tom Gilb has written 10 published books in the IT sector. His main focus is to introduce real engineering methods to IT, so that it can successfully tackle large and complex systems, with 10x higher success rates. More information at gilb.com where you also can sign up for the free blog to get some sense of detail.
Tom is an Honorary Fellow of the British Computer Society. His Planguage methods have been adopted by over 20,000 Intel Engineers, and are scheduled to be used by the USA IEEE to teach ‘Requirements’. He lives in Kolbotn and London, and is both US and Norwegian Citizen.
Har du spørsmål kontakt Elisabeth Kras