Architecture - Lets Not Forget It
How many of us, system engineers and/or architects still use the 4 + 1 views of architecture and practice subscribing and adhering to them when developing complex systems? The Use Case View, Logical View, Process View, Implementation View and the Deployment View still stands as the foundation for any complex systems design.
In a conversation with the erstwhile Grady Booch earlier this week, this topic came up and it made me take a step back and think.
I think that is is paramount that we stick to the basics and fundamentals of systems architecture and assess its resiliency to external forces of variability, on each of these architecture viewpoints.
Without architecture there is no security. This is something that many software designers forget very often. That is why I do not believe in agile methods.
Sr. Technical Architect at Northern Trust |TOGAF Certified Enterprise Architect | AWS Certified Solution Architect
8 å¹´Sometime I doubt, if an architect is an architect who can't explain or view his/her architecture in 4+1 view! Though we create abstraction, but if view is missing then connectivity is lost. How do we explain that a working architecture/solution is aligned to some need! And need could be for associated stakeholders who expect something out of the architecture/solution. So ambiguity is for what? - I assume its due to the difference between basic and smart usage. People don't want to spend time on basic stuff, they want some sugar coated wrapper which can help them in creating building blocks/solution something similar to prototype or template patterns. No one has time to read books or to know basic...Books become dictionary, if one needed something, open dictionary search information based on index.