{"id":38030,"date":"2016-10-25T09:50:00","date_gmt":"2016-10-25T14:50:00","guid":{"rendered":"https:\/\/kenscourses.com\/tc1019fall2016\/?guid=5b1798605e6239faeb3175edff57593b"},"modified":"2016-10-25T09:50:00","modified_gmt":"2016-10-25T14:50:00","slug":"floreths-blog-2016-10-25-095000-2","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/floreths-blog-2016-10-25-095000-2\/","title":{"rendered":"Floreth's Blog 2016-10-25 09:50:00"},"content":{"rendered":"
What is software design?<\/span><\/b><\/div>

<\/span><\/b><\/div>
<\/a><\/div>

<\/div>
Moraru, S. (2016). <\/span>Question the software design \u2013 Part 5 \u2013 Big project <\/i> [Ilustraci\u00f3n]. Recuperado de <\/span>http:\/\/mozaicworks.com\/blog\/question-software-design-part-5-big-projects\/<\/span><\/div>

<\/span><\/span><\/div>

<\/span><\/span><\/div>
\"Software design is the process of defining software methods, functions, objects, and the overall structure and interaction of your code so that the resulting functionality will satisfy your users requirements\" (UCAR, 2016). So software design is a break down of the architecture of your program, which should include databases, frameworks and hardware that your program will use or interact with. You should also include API's that your code has or that your code calls, because once it's used it is very difficult to change it without breaking other people's code.<\/span><\/div>
They're actual flaws that programmers make when they're trying to design software:<\/span><\/div>
<\/div>
  1. Writing code that isn't needed: It's not about whether you're going to need it in the future, it's about good design.<\/span><\/li>
  2. Not making the code easy to change: Also called \"Rigid design\". They're two ways to accomplish this: the first one is the failure to understand that the requirements will change and number two writing code without enough design.<\/span><\/span><\/li>
  3. Being too generic: AKA Over engineering. It's a flaw that senior developers fall into, too much effort for too little value.<\/span><\/span><\/li><\/ol>
    Videos about the three flaws explained by Max Kanat-Alexander the author of <\/span>Code Simplicity: The Fundamentals of Software.<\/span><\/span><\/div>

    <\/span><\/span><\/div>
    Part 1:<\/span><\/span><\/div>