The 4+1 View Model

In the course of all my years of studying Computer Sciences, UML has been hammered religiously into my brain as the best (and sometimes only) modeling standard for Object Oriented Development. It has been a staple and core philosophy when it comes to documenting code (when it comes to documenting classes right after their coding, I am guilty as charged), so there's no other way I can imagine abstracting all the data that goes into my code.

Now, while 4+1 may seem a little more compact (less is more, right?), it actually does a very heavy lifting for the design. As far as the not so ancient tale of the 5 blind programmers go, every piece of TI-related concept or matter is subject to multidimensional analysis by different parties, but they ultimately hold water only as the dimension pertaining the eye of the beholder. 4+1 is a perfect way to analyze software components for what they represent in different fields.

4+1 presents a condensed multidisciplinary view of the components behind the design, coding, developing and planning of software pertaining software, proposals, hardware, and even makes space for user specification (the "1" in "4+1"), while delegating the corresponding responsabilities upon the acting agents.