When you read the phrase "visual software requirements" what immediately comes to mind?
1) user interface requirements
2) visualizing requirements such as traceability
3) visual models for software requirements
4) other
Hi Anthony,
Great question!
The first thing that comes to mind is "Requirements Visualization" which is a way to "show the requirements" to the stakeholders by using functional prototypes. So it would be a combination of user interface requirements, functional requirements (since prototype is working), and traceability since good requirements visualization tools such as iRise can also capture requirements as text and trace them to the prototype features that shows those.
Adrian
I agree, the first thing I think of is seeing interfaces, working prototypes (or not).
I just think everyone should be aware that this is good stuff, but it will not be all you need, and may or may not be the place to start discovering requirements. For example, most business systems do a lot of other things that don't require a user interface. It can depend on the business people involved, some like to theink visually first, others think process, etc...
Adrian mentions iRise, which I have heard a lot about but have not had a chance to use. Has anyone here on MA used it on a real project? And if you are allowed to, can you tell us how it went?
David Wright
brought to you by enabling practitioners & organizations to achieve their goals using:
enabling practitioners & organizations to achieve their goals using: