Overcoming operational blindness in Software Architecture 2020-01-1336
A lesson learned on why software architects fall short of expectations and how to fix it by setting the scope.
Detailing the design that is already clear in the head comes natural to an architects. Afterall most architects are basically just aged developers. Consequently, this haste and even excitement about the technical challenge prevent them from being effective. Being an architect is - to great bits - about software instinct which grows out of development practice. This paper is about the two small parts which make a developer become an architect: Discipline and Scope.
The proposed technical paper covers the challenges as well as the lessons learned in the development of an embedded automotive software architecture. Based on the experience from different embedded application the following structure will be followed:
Part 1: Where to start with a new design
This is the main questions asked by new software architects. A good design starts with a clear value proposition. What is the goal and scope of the architectural design? Different answers are discussed and a good example how to start software architecture is shown
Part 2: How to make the project content obvious to developers and stakeholders alike
Software Architecture needs to provide all kinds of information for numerous people. From developer over safety manager to client. With a few simple steps, the number of diagrams and views can be reduced to an expressive minimum.
And Part 3: Which decisions improve agility the most
The biggest challenges of all is to postpone decisions to the time when all information is at hand. When practiced this discipline might become the motor of a fast, high quality delivery. A strategy is presented to find the ideal time for decisions.