{"id":38153,"date":"2016-10-28T22:07:46","date_gmt":"2016-10-29T03:07:46","guid":{"rendered":"http:\/\/juliap17.wordpress.com\/?p=488"},"modified":"2016-10-28T22:07:46","modified_gmt":"2016-10-29T03:07:46","slug":"software-architecture-15","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/software-architecture-15\/","title":{"rendered":"Software Architecture"},"content":{"rendered":"

\"3481530\"Software architecture is the process of defining a structured solution that meets all of the technical and operational requirements, while optimizing common quality attributes. As many other definitions, it seems simple and irrelevant, but what’s the real meaning of this this concept?<\/p>\n

It’s easy to explain what software architecture is. I bet all of us think about houses and buildings when we read the word “architecture”, and I think it’s an adequate analogy. Before you build a house, you have to design the structure and consider all the elementss you need to acomplish the building, and don’t forget about the environment. Well, that’s the same thing with software, before you build it, you need to have a base.<\/p>\n

Software must have a solid foundation, it’s important to think about key scenarios, common problems, long term consequences. You must consider RISKS. A poor architecture will take your software to failure.<\/p>\n

Build to change instead of building to last!!!<\/strong><\/p>\n

In this industry, everything changes soooooo fast. And your software must be flexible enough to support those changes. I mean, nobody’s perfect, duh. Also, people love updates, specially if they’re curious (like me).<\/p>\n

Source:<\/strong><\/p>\n