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
>
RmMeetings
>
RmMeetings20110207
(07 Feb 2011,
IanGreen
)
(raw view)
Meeting 7th February 2011 Chair: Ian * Requirement Organization - discuss straw man proposal - RmRequirementsOrganizationScenarios Minutes Attendees: IanGreen, DominicTulley, SimonWills, AndyBerner, IanGiblett, JimConallen, DaveJohnson Minutes: SW: Two (AB said "more") related things: (i) Understanding - single requirement in isolation does not have context so it can't be understood. To understand several requirements they need to be logically structured. Unordered bag is not useful. This is practical, and perhaps soft. (ii) Parent/child in the hierarchy has meaning but might not be best represented as structure - we'd be better with tracelinks. AB: A headng serves a grouping role to aid understanding. Parent/child relationships where the parent is really a requirement. IG: are the realtionships orthogonal. AB: What is the notion of hierarchy? Eg one example: folder structure. "macro scale". another is "micro scale" - headings and sections. SW: how would you start from a requirement and discover its parent resource? Eg See the other requirements that are tested by the same test case; or the other performance related requirements? DJ: Agree that there are multiple hierachies that need to be expressed. AB: how can we focus on a folder hierarchy, for example? What's special about folders? SW: We could use the straw man, or we could use an explicit link. Concern over expense of link resources. We would need to decide on the behaviour in the following terms - multiplicity, lifetime, ownership, reuse etc. IG: What are the traits of a collection? SW: Could there be a query that returned some non-canonical heirarchy structure? AB: What might we learn from SCM/AM/AssetMgmt AB: Suggested that folder hierarchies have a "standard" set of traits and are fairly standard meaning. There is little semantic "leakage" from one resource in a folder to a sibling.
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 - 07 Feb 2011 - 17:03:42 -
IanGreen
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