[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [epf-dev] https://bugs.eclipse.org/bugs/show_bug.cgi?id=162639
|
Option #2 expresses the intent without
messing the relationships. I vote for it.
Ricardo Balduino
Senior Software Engineer
IBM Rational (www.ibm.com/rational)
EPF Committer (www.eclipse.org/epf)
*My new office phone: 408-463-5264
"Chris Sibbald"
<Chris.Sibbald@xxxxxxxxxxxxx>
Sent by: epf-dev-bounces@xxxxxxxxxxx
12/08/2006 01:14 PM
|
Please respond to
Eclipse Process Framework Project Developers List
<epf-dev@xxxxxxxxxxx> |
|
|
To
| "Eclipse Process Framework Project
Developers List" <epf-dev@xxxxxxxxxxx>
|
|
cc
| External Chris Sibbald <csibbald@xxxxxxxx>
|
|
Subject
| [epf-dev] https://bugs.eclipse.org/bugs/show_bug.cgi?id=162639 |
|
Hi Folks,
I just added the following entry to the subject
bug:
We did not discuss the comments on the Glossary
during the Nov. 20th review.
There are no contentious issues, however there is a technical difficulty.
It is generally agreed that the Glossary could be updated at any time,
by any
role, as new terms are identified (those that may be ambiguous or domain
specific). Unfortunately, the "Modified By" field cannot
be set (it is derived
based on tasks that have this artifact as an output). I can think
of three
options:
1)We could add the Glossary as an output of every task, which would result
in
the "Modified by" field displaying all roles and the "Output
From" field having
all tasks displayed. However, it is generally agreed this is pretty messy.
2) We could leave the relationships as is, but add the text "Note:
although
listed as the output of the requirements tasks, the glossary may in fact
be
updated at any time, by any role as new terms are identified" to the
Key
Considerations section.
3) A third option is to create a task "Update Glossary", which
is performed by
"Any Role". But that is also a bit of a kludge as well
(I don't think this is
important enough to warrant a task).
I prefer option 2. If there are no objections by COB Dec. 12 I will
implement
option 2.
If you are fine with Option 2, no action.
Otherwise add your concern or another option to the bug by COB Dec.
12.
Have a good week-end.
Cheers,
Chris
--------------------------------------------------------------------------------
Telelogic Lifecycle Solutions:
Helping You Define, Design & Deliver Advanced Systems & Software
Learn More at www.telelogic.com
Chris Sibbald
Vice President, Standards and Technology
Telelogic North America Inc.
255 Albert Street, Suite 600
Ottawa
Ontario K1P 6A9
Canada
Phone: +1 (613) 266 5061
Fax: +1 (613) 482 4538
Mobile phone: +1 (613) 266 5061
Chris.Sibbald@xxxxxxxxxxxxx
http://www.telelogic.com
Telelogic - Requirements-Driven Innovation!
-------------------------------------------------------------
The information contained
in this e-mail, including any attachment or enclosure, is intended only
for the person or entity to which it is addressed and may contain confidential
material. Any unauthorized use, review, retransmissions, dissemination,
copying or other use of this information by persons or entities other than
the intended recipient is prohibited. _______________________________________________
epf-dev mailing list
epf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epf-dev
