Software Architecture Decisions - how to do it wrong the hard and the easy way
When it comes to software architecture, stuff gets funny.A
First we learn everything about it at university. We learn to use it as a part of our main project plan. We learn how to do risk evaluation. And, as a matter of fact, we learn how to create a lot of different UML diagrams:A
- component diagrams
- data flow diagramsA
- package diagrams
- deployment diagrams
- sequence diagrams
- state chartsA
- etc ...A
Since we didn't have a lot of experience with software back then, the resulting architecture is a badly done, but well documented. This style of software architecture is called "Enterprise Architecture" and usually done by consultants.
Continue reading "Software Architecture Decisions - how to do it wrong the hard and the easy way"