Visual Requirements

You are creating requirements for a new product 1

You are designing a website 1

You are writing code. 1

You are organizing ideas 2

You are adding an enhancement to an existing system 2

You are organizing your reference base. 2

You are modeling a business process 2

You are describing a technical  system. 2

You are creating requirements for a new product

This product is a software system, or a technical device, or something else. You need to build a set of requirements that are
- easy for you to read, add and change
- easy for a business client to understand
- exact for a systems analyst to explore while working on design
- accurate and complete for a tester to prepare test plans
- complete for a technical writer to prepare technical documentation
- etc.
For that, VR supports:


USE CASE VIEW
  use case example 1

prepare order use case

SCREEN MOCKUP VIEW
sign on diagram


NAVIGATION VIEW
navigation map sample
     
CONCEPT VIEW
concepts map sample   

ARCHITECTURE VIEW
architecture sample


VR also provides
- efficient, flexible structure for requirements
- links between requirements
- reuse of existing solutions, including pre-packaged ones
- instant queries
- comparison of texts of requirements
- search for requirements textually similar to a given one
- search for elements that are nor linked to anything
- size/effort estimation functionality
- etc.

You are designing a website

and for the next meeting with your customer you need to present a general concept of the website: draft requirements together with a logical structure of the screens.
For that, VR provides
- use cases support, so you can demonstrate how the website will be used - screen mockup tools
- tools to express the business entities and their properties right on these screens.

You are writing code

according to requirements that are given you as a VR model. You need to understand
- how the system or its part will work
- what are the screens that you need to implement
- what are the properties of the business entities
- which business rules you should implement
- etc.
For that, VR supports
- instant information about all places where a given entity or requirement is used
- instant information about relationships between a given requirement and other elements
- properties of business entities, that are present on the diagrams attached to these entities
- color coding to emphasize your questions for the next meeting with the business analyst
and many other efficient tools

You are organizing the ideas

that submits your staff about further improvements of the products produced by your company.
You are organizing these ideas using
- the use case view that defines the overall purpose of the product
- the conceptual model where you organize ideas around concepts
- the architectural view where you map requirements to components of products
and other aspects that are appropriate to your task

You are adding an enhancement to an existing system

and you need to know how the existing system works. You also need means to add descriptions of new functionality to the existing ones. You can incrementally add to the description of the existing system the pieces relevant to the current enhancement. Because you do that starting at use case and genenal architecture overview, over some time you get a  reasonably detailed description of the system.
If the requirements for existing system were developed in VR, you have access to
- a concept map of the problem domain
- instant answers about places where elements (requirements, fields, etc.) are used, components they are allocated to and their properties
- navigation paths through the system
- screen comparison, when you need to understand the differences between screens
- etc.

You are organizing your reference materials

You have many artifacts - documents, hyperlinks, records, etc. - that you need to organize for easy access in the future. In VR, you put all these elements on diagrams; you build from these diagrams the structure that suits you in the best way - a tree, or more complex structure. You add comments to them, and keywords, if needed. The same element, such as a  book title, can be placed on several diagrams, if it belongs to several areas. Later you will just open the required diagram to see the set of artifacts you need; or you can find the required element by sub-string, etc. Actually, for a set of files you can have in VR much more efficient and easy structure than you normally have in Windows.

You are modeling a business process 

creating diagrams with roles, activities, artifacts, etc. Each of these things can be present on many diagrams, but in VR, when you need to change something, you don’t have to deal with each and every instance - VR deals with them for you. If you need to find out where a particular role is used, you get that answer in a moment. And you can hide the details, so your diagrams do not get overcrowded and hard to read - each level represents exactly what is should represent.


Sample process"Creating vision of the system"

process sample

You are describing a technical system

that will contain servers, firewalls and other parts of the technical system. In VR, you build simple descriptions organizing these elements in layers, and hiding the details that are not necessary at a particular level. The reader can easily open the corresponding diagram when s/he needs it. If the same element is used on several diagrams, the reader can get to these diagrams  in a moment.

Copyright © Lucid Models Software