The magazine dotnetpro I was asked about the future of software architect - and result in a joint glass ball published article (which also Stefan Edlich and Michael Wiedeking their views on non- SQL or programming state).
In short my thesis for the future of software architects:
- standardization of tasks and training: There are some promising approaches (such as iSAQB and the very enterprise-heavy TOGAF).
- requirements analysis is performed by software architects . In construction and much of the engineering disciplines, there are no requirements engineering , but designers. The software is in the future also be!
- project managers on administrative assistants of software architects. Who knows the project leader of the brilliant domed building on the Berlin Reichstag? No one. Most are from Sir Norman Foster , the architect, but have heard!
- Non-functional characteristics as an essential criterion for success . From setting as it works ... we have to get away quickly. It's quality and longevity!
- order of magnitude better and more complex tools . Only a few insiders will understand the internals of future development tools. They are incredibly wegabstrahieren many details before us ordinary people - a taste for children is the programming tool developed Scratch - the example of the complex topic of threading hides - and perfect!
As software architects we have a really exciting future ahead of us!
0 comments:
Post a Comment