{"id":37702,"date":"2016-10-14T09:24:58","date_gmt":"2016-10-14T14:24:58","guid":{"rendered":"http:\/\/rmzkrieg.wordpress.com\/2016\/10\/14\/software-design-patterns\/"},"modified":"2016-10-14T09:24:58","modified_gmt":"2016-10-14T14:24:58","slug":"software-design-patterns-4","status":"publish","type":"post","link":"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/software-design-patterns-4\/","title":{"rendered":"Software Design: Patterns"},"content":{"rendered":"<div class=\"wpcom-reblog-snapshot\"> <div class=\"reblog-post\"><p class=\"reblog-from\"><span class=\"avatar-container\"><img alt='' src='https:\/\/2.gravatar.com\/avatar\/80b12ed4336e8eb8907fdfb9462a1aa2?s=32&#038;d=identicon&%23038;r=G' class='avatar avatar-32' height='32' width='32' \/><\/span><a href=\"https:\/\/charpple.wordpress.com\/2016\/10\/14\/software-design-patterns\">Carlos Pe.<\/a><\/p><div class=\"reblogged-content\">\n<p>As we know, software design isn\u2019t the code itself but the way that code must be structured in order to have a higher level of control over it. Patterns themselves are repeatable solutions to problems that occur constantly in software design. These type of structured ways of designing software aren\u2019t finished designs that can be already transformed into code but they are descriptions that show how to solve certain problems. They are normally templates used in order to have a richer idea on what it will be developed in the future.<\/p>\n\n<p>There are mainly 3 types of design patterns:<\/p>\n\n<ul><li>\n<h3>Creational design<\/h3>\n<p>These patterns approach design by the\u00a0instantiation\u00a0of classes. They are divided in class creation which inherit in the instantiation step and object creational patterns that use delegation as it should be in order to achieve certain task. Some of these are:<\/p>\n<ul>\n<li>Abstract Factory<\/li>\n<li>Builder<\/li>\n<li>Factory Method<\/li>\n<li>Object Pool<\/li>\n<li>Prototype<\/li>\n<li>Singleton<\/li>\n<\/ul>\n<\/li><\/ul>\n<\/div><p class=\"reblog-source\"><a href=\"https:\/\/charpple.wordpress.com\/2016\/10\/14\/software-design-patterns\">View original post<\/a> <span class=\"more-words\">114 more words<\/span><\/p><\/div><\/div><br \/>  <a rel=\"nofollow\" href=\"http:\/\/feeds.wordpress.com\/1.0\/gocomments\/rmzkrieg.wordpress.com\/444\/\"><img alt=\"\" border=\"0\" src=\"http:\/\/feeds.wordpress.com\/1.0\/comments\/rmzkrieg.wordpress.com\/444\/\" \/><\/a> <img alt=\"\" border=\"0\" src=\"https:\/\/pixel.wp.com\/b.gif?host=rmzkrieg.wordpress.com&#038;blog=115197112&%23038;post=444&%23038;subd=rmzkrieg&%23038;ref=&%23038;feed=1\" width=\"1\" height=\"1\" \/>","protected":false},"excerpt":{"rendered":"<p>Carlos Pe. As we know, software design isn\u2019t the code itself but the way that code must be structured in order to have a higher level of control over it. Patterns themselves are repeatable solutions to problems that occur constantly in software design. These type of structured ways of designing software aren\u2019t finished designs that &hellip; <a href=\"https:\/\/kenscourses.com\/tc1019fall2016\/syndicated\/software-design-patterns-4\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Software Design: Patterns<\/span><\/a><\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,4],"tags":[44],"class_list":["post-37702","post","type-post","status-publish","format-standard","hentry","category-blogs","category-syndicated","tag-sin-categoria"],"_links":{"self":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37702","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/comments?post=37702"}],"version-history":[{"count":1,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37702\/revisions"}],"predecessor-version":[{"id":37703,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/posts\/37702\/revisions\/37703"}],"wp:attachment":[{"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/media?parent=37702"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/categories?post=37702"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kenscourses.com\/tc1019fall2016\/wp-json\/wp\/v2\/tags?post=37702"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}