{"id":37716,"date":"2016-10-17T15:18:47","date_gmt":"2016-10-17T20:18:47","guid":{"rendered":"http:\/\/vanjrblog.wordpress.com\/?p=402"},"modified":"2016-10-17T15:18:47","modified_gmt":"2016-10-17T20:18:47","slug":"understanding-software-architecture","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/understanding-software-architecture\/","title":{"rendered":"Understanding Software Architecture"},"content":{"rendered":"

Software Architecture<\/strong> is the representation of the program that helps to understand how the software will behave<\/strong>. It serves as a guide for the design<\/strong> and the implementation teams. And is the first line of the system’s quality<\/strong>, such as\u00a0performance, modifiability, and security. None of these could be done without an architectural vision.<\/p>\n

<\/span><\/p>\n

\"61391451\"<\/p>\n

By building effective architecture, you can identify design risks<\/strong> and mitigate them early in the development process. It also gives an approach of the final design.<\/p>\n

Like any other complex structure<\/strong>, software should be done on a solid foundation<\/strong>. Any failure in the future could result a risk for the application.<\/p>\n

The most important part of it, is to always consider three things: The User, The System & The Business.<\/strong><\/p>\n

Finding a valance<\/strong> between the desire and specifications of each will result on a good architecture, and this will lead on a great application.<\/p>\n

But unfortunately there are major problems that are hard to decode. That’s why we always need to think about this major concerns<\/strong>:\"diossimpson20120507053705\"<\/p>\n