Different types of Architecture in Software Engineering

October 2, 2013
Network which allows clients

There is no proof that so many architectures are needed. It's just that too many people believe they can come up with a new perfect architecture that will solve all the world problems. You have people in standard committees, R&D departments of companies, university departments that try to gain momentum in the scientific community be continuously inventing... well just about anything really.

I will probably get downvoted for overciting Joel, but he keeps writing great stuff. Read this article, it will provide much insight into what's going on.

Think of the history of data access strategies to come out of Microsoft. ODBC, RDO, DAO, ADO, OLEDB, now ADO.NET - All New! Are these technological imperatives? The result of an incompetent design group that needs to reinvent data access every goddamn year? (That's probably it, actually.) But the end result is just cover fire. The competition has no choice but to spend all their time porting and keeping up, time that they can't spend writing new features. Look closely at the software landscape. The companies that do well are the ones who rely least on big companies and don't have to spend all their cycles catching up and reimplementing and fixing bugs that crop up only on Windows XP. The companies who stumble are the ones who spend too much time reading tea leaves to figure out the future direction of Microsoft. People get worried about .NET and decide to rewrite their whole architecture for .NET because they think they have to. Microsoft is shooting at you, and it's just cover fire so that they can move forward and you can't, because this is how the game is played, Bubby. Are you going to support Hailstorm? SOAP? RDF? Are you supporting it because your customers need it, or because someone is firing at you and you feel like you have to respond? The sales teams of the big companies understand cover fire. They go into their customers and say, "OK, you don't have to buy from us. Buy from the best vendor. But make sure that you get a product that supports (XML / SOAP / CDE / J2EE) because otherwise you'll be Locked In The Trunk." Then when the little companies try to sell into that account, all they hear is obedient CTOs parrotting "Do you have J2EE?" And they have to waste all their time building in J2EE even if it doesn't really make any sales, and gives them no opportunity to distinguish themselves. It's a checkbox feature - you do it because you need the checkbox saying you have it, but nobody will use it or needs it. And it's cover fire.

Source: stackoverflow.com
Model Based Software and Systems Engineering: Elements of
Model Based Software and Systems Engineering: Elements of ...
Software Engineering 2 - Live Lecture 10 on 4-6-2011
Software Engineering 2 - Live Lecture 10 on 4-6-2011
Introduction to Software Architecture
Introduction to Software Architecture
Share this Post