Requirements for discussion
These are high-level ideas and issues, for example stakeholder requirements, that will typically be used to drive the development of requirements and scenarios.
- Provide ability to capture blob requirement data such as process diagrams from ARIS Business Architect or simulations from Axure. This is similar to functionality allowing capture of Word content. This will allow disparate file types to be captured in a central repository that users will use as the single source of content.
- Provide ability to share common elements such as glossary and reporting.
- Provide ability to share requirement detail such as associating a requirement text to a button on an Axure simulation or node on an ARIS Business Architect process model. This is similar to the functionality available in RRC today that allows discrete requirement text to be associated to an RRC storyboard or process sketch element. The intent is to allow linkages between tools/editors at a granular level.
Topic revision: r2 - 20 May 2009 - 15:44:07 -
RandyVogel