Visualization an alternative approach to developing requirements. Bo Lora firstname.lastname@example.org 210-259-3020 February 2008. The Importance of Requirements. Requirements… Communicate the needs of the end user. Assure that business objectives are stated.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Visualizationan alternative approach to developing requirements
Bo Lorabo.email@example.comFebruary 2008
Developing solid business requirements is at the heart of any project and it’s success.
Requirements development involves multiple stakeholders working together to define and design business solutions through a standard documentation framework.
Today, organizations routinely tap the global talent pool for low-cost, high-quality system and software development. Effectively leveraging these resources requires a robust requirements development process and sound project management oversight.
Technical teams must be clear on the project objectives and development approach. They then must apply templates and code consistently, whether they’re in Boston, Bangalore or Beijing.
Often, however, organizations stumble in developing business requirements. The problems can occur in three areas:
The average project cost overrun was 56 percent, and the average time overrun was 84 percent. Source: “Overdue and Over Budget, Over and Over Again,” The Economist, June 9, 2005.
Leonardo da Vinci understood the power of visualization.
How could he possibly describe many of his innovations without drawings?
Static forms of requirements documentation offered by business analysts, such as word processing documents, screen shots and process flows, often provide an incomplete or foreign view of the system during technology development.
Because static documents are focused on giving technologists a view of business needs, they can be misinterpreted when translated into technology specifications or developer code.
Static formats also may not provide business users with a full or easily understood summary of the system. Moreover, such forms can be long and difficult to maintain as requirements evolve.
Is this really normal?
When you buy a car, would you know that it is right for you just by looking at a list of it’s features or would you want to test drive it first?
Visualization stimulates scope and requirements
Scope and requirements drive visualization
Agility – The team will be able to more easily respond to changes.
Efficiency – More effective requirements communication will reduce post development rework.
Speed – Development teams can get involved sooner and work faster.
Accuracy – A greater level of accuracy reduces overall cost.
Collaboration – Visualization allows everyone to have more input.
Visualization can be the driver of common objectives
Over 50% 0f customers who order service by phone say they started online but could not finish.
Cause and Effect
Voice of Customer
Rapid User Model
Access to related documents
Access to all prototype pages
Access to all technical design documents
Functional requirement reference
Prototypes are in HTML and 40-60% of code is reusable in development phase
Visualization supports better systems
A strong requirements development process can help mitigate the risks associated with large-scale system implementations.
Visualization is emerging as a powerful tool for increasing the quality and efficiency of a firm’s requirements development program.
Before adopting visualization, organizations must understand the key considerations in using visualization and determine how to best integrate it into their existing requirements program to capitalize on this promising new solution.