Author Archives: Heidi


According to Carnegie Mellon studies in 2010, 25%-40% of all spending on projects is wasted as a result of re-work, and that 70% - 85% of all project rework costs are due to errors in requirements.

Other studies also show that less than around 50% only of projects are successful, and that a major source of project failure is incomplete, inaccurate, and misunderstood requirements.

As the definition of the Requirements analysis states:

Requirements analysis in systems engineering and software engineering, encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking into account the possibly conflicting requirements of the various stakeholders analyzing, documenting, validating and managing software or system requirements”.File:SE Process.jpg


Considering all the previous facts, we perceive the importance and criticality of requirements understanding and acceptance among all the direct/indirect and technical/non-technical stakeholders.


On the other hand, studies found that the human brain deciphers image elements simultaneously, while language is decoded in a linear and sequential manner taking more time to process.

Our minds react differently to visual stimuli.

People think using pictures. Dr. Lynell Burmark, Ph.D. Associate at the Thornburg Center for Professional Development and writer of several books and papers on visual literacy, said, "...unless our words, concepts, ideas are hooked onto an image, they will go in one ear, sail through the brain, and go out the other ear. Words are processed by our short-term memory where we can only retain about 7 bits of information (plus or minus 2). Images, on the other hand, go directly into long-term memory where they are permanently etched." Therefore, it is not surprising that it is much easier to show a circle than describe it.

There is no wonder that the poor boring pure text software requirements documents dis-engaged are neglected among different stakeholders, especially business stakeholders; thus causing the re-work after they saw a visual representation of the text requirements. Here comes the importance of visual project requirements, by incorporating a number of visual elements that increases the value of the requirements analysis and serves the project success such as:

·Visual requirements models using RML which categorizes the models into objectives models, people models, systems models, and data models, known collectively as OPSD.

·Business process

·Domain diagrams

·UI mockups

And a lot more of visual requirements models that we will discuss in future articles….