Building a new car requires the input of both a design team and an engineering team. Each team contributes to specific requirements. For example, the design team is responsible for understanding what the consumer wants in the look and feel of the car. The engineering team applies the required mechanics and functionality to the car. Both teams serve distinct purposes, however both teams need to eventually come together to produce what we will eventually drive down the road. Read More
Tag Archives: view
Software Architecture – The 4 + 1 View Model
Effectively communicating the same message to the many types of stakeholders in a software development project can be a challenge. Semantics used in a communication, such as that of a software requirement for example, can be received and interpreted differently from one person to the next. Often times each recipient will receive a communication however not everyone will have the same common understanding of what is being said.
There are many methodologies, models, and templates that attempt to provide a more cohesive understanding of a software solution design. The 4 + 1 View Model is one such way of describing a software system. Developed by Philippe Kruchten , currently a professor of software engineering at the University of British Columbia, the 4 + 1 View Model is a framework for presenting a consistent look at the design of a software system.


