Skip to main content

The OO Design Pyramid

A great article on what Gene Shadrin calls the OO Design Pyramid: [sys-con.com]

The references of this articles might not be enough to infer Shadrin's concept of the OO Design Pyramid, and I'm not sure where he obtained his data for Figure 3 (Design Time vs. Design Flaw), but on the surface I believe this is a fantastic representation of Object Oriented Design in an easy to understand, structured form.

Shadrin present a number of plausible ideas here. Using basic concepts without patterns will probably cause an architect to eventually design to patterns, which takes much longer. Designing with patterns but without the basic concepts typically leads to confusion and no "glue" between the patterns. I have read the Gang of Four books, several Fowler books, and others, and have seen them demonstrate the necessity of lower layer concepts with design patterns, but not the other way around. I really feel Shadrin has something here.
Labels:

Comments

Post a Comment

Popular posts from this blog

C++ Development Environment

Trolling through some forums today, I found some great resources for C++, so I expanded on it and inserted some annotations. Categories are Integrated Development Environment (IDE), UML Interface, Team Collaboration, Coding Standards, Bug Tracking, Version Control, Unit Test Library, and Performance Testing. A bracket sits next to the resource which contains a W for Windows support, L for Linux, and M for Mac. A $ indicates that a standard version of the software will require a purchased license. IDE: Eclipse CDT ( eclipse.org ) [WLM] Visual SlickEdit ( slickedit.com ) [WLM$] UML: Eclipse MDT ( eclipse.org ) [WLM] Team Collaboration: Skype [WLM] Zoho [WLM] Sharepoint [W$] SourceForge [WLM] Coding Standards (Platform Agnostic): The Lockheed Martin Joint Strike Fighter C++ coding standards ( att.com ) The MISRA C++ coding standards [$] ( misra-cpp.org ) Bug Tracking: Bugzilla ( bugzilla.org ) [WLM] Unfuddle ( unfuddle.com ) [WLM] Version Control: mercurial subversion mercurial git cvs ...
Post a Comment
Read more

The TL;DR guide to git

While in the past I've held a pretty high opinion to using mercurial for version control, the majority of version control these days seems to done in git.  Here were the commands I found most useful to get productive with git right away. # Clone a repository from an origin, i.e. my github MaskingUtils repository git clone git@github.com:caelumvox/masking-utils.git # Add a file after it's been updated to stage it for commit, or add a new file git add filename # Commit the file to local repo git commit # Push the file to the origin so the rest of the team can see it git push # List all locally tracked branches git branch git branch --list # Get a list of all branches from the remote git branch -r # Create branch locally git branch develop # Push the branch to the origin repository to make sure it is tracked there git push --set-upstream origin develop # Pulls latest from all local branches tracked from origin; won't pull non-tracked branches git pull --all # Fetch the branch ...
Post a Comment
Read more

Software Design Principles - SOLID

The SOLID software design principles weren't called SOLID while I was in grad school, but the concepts were there in my Object Oriented Design course. They're worth mentioning here, primarily because I think once you start coding and become dangerous, it's one of the best ways to stay organized once you incorporate it into your daily coding routines, and it even changes your way of thinking for the better: https://en.wikipedia.org/wiki/SOLID
3 comments
Read more