This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
RmHome
>
RmRequirementsForDiscussion
(20 May 2009,
RandyVogel
)
(raw view)
---+ 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.
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 20 May 2009 - 15:44:07 -
RandyVogel
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback