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
>
RmMeetings20100125
(26 Jan 2010,
ScottBosworth
)
(raw view)
Agenda Meeting 25th Jan 2010 (4PM UTC) Agenda * RM 1.0 finalization * Action follow-ups * Where do we put planning and progress information? * Flesh out scenarios (RmScenarios) * Pick scenarios we feel look tractable, useful * Homework to elaborate, feedback to the workgroup * Specification 2.0 AOB Apologies: SimonWills, JimConallen Attendees: IanGreen, DominicTulley, TorgeKummerow, RainerE, ScottBosworth, PaulMcMahan, DaveJohnson, MatthewStone Minutes Torge: three major. - eclipse incubator - "useme" for structured requirements. has been accepted, currently incubator. open-source requirement management tool: sourceforge project (march 2007 last activity; two participants) tigris, req engine: "2nd generation" rm tool. requirements.tigris.org. same message as oslcrm. (14 participants). Try to learn more about these, then we can follow-up to share information both ways. Need to know that there would be value before reaching out to them. IanGreen to pursue tigris.org and TorgeKummerow to pursue eclipse project. Both to report back at next conf. call. Rainer: are we limited to open source - no, we're not. Do we want to wait for, e.g., more maturity in the workgroups before we approach a commercial enviroment. What about DOORS implementation? Ian to talk with Rainer offline about how this can go? Is this the right time? Scott - any other commercial interests?> eg CESAR? ---+++ Scenario discussion We took end of Feb. as date by which scenarios to take forward into specification will be defined. We will assess where we are at end of February, but there is a strong desire to reach a V2.0 specification by June 2010. IanGreen expressed that this was required to be able to ship V2.0 specification in Rational products in Q3. We agreed to spend until end of February fleshing out various scenarios: * Traceability (SimonWills; BrendaEllis and TorgeKummerow to contribute specific scenarios) * Baselining (RainerE to elaborate on Siemen's baselining scenario) * Reporting - Desire to ensure that reporting scenarios being explored by the Reporting workgroup account for RM-like reporting needs. IanGreen to ask TackTong to present OSLC Reporting approach. * PLM scenarios. BrendaEllis to write up PLM scenario - this would connect with OSLC workgroup in this area (currently being considered by OSLC steering group). * RM/AM scenarios. BrendaEllis to write up modelling scenarios. BrendEllis expressed concern that many hard integration challenges might be falling between the gaps - for example, RainerE suggested an extension of his baselining requirements scenario (S1) in which the baseline contains a heterogeneous collection of things - requirements, models, test cases etc. How would this be supported by OSLC? ScottBosworth to schedule follow-up with BrendaEllis, IanGreen, DavidJohnston, and himself. See RmMeetingActions.
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r5
<
r4
<
r3
<
r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r5 - 26 Jan 2010 - 13:36:25 -
ScottBosworth
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