3 ms·
To me, a software architecture is an implementation of the decisions made (amongst competing choices) in meeting its requirements, both functional and non-funct
by aryehof 6y ago
To me, a software architecture is an implementation of the decisions made (amongst competing choices) in meeting its requirements, both functional and non-functional.
I simply don't find the article to provide a grand unified theory across different genres of software at all. What worries me is that newcomers to the industry will, until they move to the next discovered silver bullet unified theory.
- brabel 6y agoIt's a good theory for writing general code that can be easily tested and modified in the future. This is the first thing you need if you want to meet any business requirement at all.
- Cthulhu_ 6y agoWhile I agree there is no silver bullet, most applications will have a lot of similar nonfunctional requirements - API, data processing, and i/o. Having a common basis to go to - then evolving it - is a good practice. Cowboying or reinventing the wheel is not a good practice.