In my last post, I suggested approaching a project using modeling to plan our path forward. Modeling could be thought of as a way of looking at the “big picture”, allowing us to more fully wrap our minds around what we need to do. When used most effectively, it also provides us with a natural layout of scope and related tasks. Our model could be a representation of our entire project, but we may also choose to model only certain aspects of a project, especially those which pose a greater risk than others.
We can choose to model using methods we are already familiar with, such as flow charting or pseudo code; or we can use tools specifically designed for the job. One tool we can use in modeling is the UML (Unified Modeling Language). The UML provides a standard syntax to represent aspects of our system. This standard syntax is designed to be user-friendly, and can be effectively used to coordinate and document project requirements with both technical and non-technical stakeholders.
Regardless of the method we choose to model our project, the important thing we want to remember is that we want modeling to simplify our work flow. Our intention is that, by modeling first, our time will be spent more efficiently.