RE: [epf-dev] requirements openup work products

[Jim Ruehlin <jruehlin@xxxxxxxxxx>]

Hi Ronaldo,

 

The Collaboration package contains content elements that are
collaborative in nature and need to be referenced in other package. For
instance, use cases are used in Intent and Solution. Use cases are only
defined in the Collaboration layer and they contain minimal content.
Most of the content is contained in the contributing elements of the
Intent layer.

 

This was done to make the process more extensible. Intent, Solution, and
Management packages depend on the Collaboration package, but they don't
depend on each other. So if you want to use a different approach for
requirements and test cases, you can simply replace the Intent package.
The other packages have no dependency on that package, only on the
Collaboration package.

 

When you publish, all the different pieces of contributing content are
merged. So you could extend an item in the Collaboration package from
many other packages. The layered architecture (Collaboration, Intent,
Management, and Solution) isn't apparent when the process is published.

 

To answer your other question, you can use this email group to ask any
questions, but it's generally used for development discussions. The EPF
newsgroup (eclipse.technology.epf) is a good place for "How do I." type
of questions.

 

Thanks,

Jim

 

____________________

Jim Ruehlin, IBM Rational

RUP Content Developer

Eclipse Process Framework (EPF) Committer www.eclipse.org/epf

email:   jruehlin@xxxxxxxxxx

phone:  760.505.3232

fax:      949.369.0720

 

________________________________

From: epf-dev-bounces@xxxxxxxxxxx [mailto:epf-dev-bounces@xxxxxxxxxxx]
On Behalf Of "Ronaldo r" <ronaldorezende@xxxxxxxxx>
Sent: Wednesday, April 11, 2007 7:05 AM
To: epf-dev@xxxxxxxxxxx
Subject: [epf-dev] requirements openup work products

 

The work products rm_actor, rm_use_case, rm_vision and
rm_supporting_requirements are in the content package
intent/requirements. They contribute to work products  actor, use_case,
vision and supporting_requirements that are in the collaboration content
package. 
They are contributting with some guidance.
What's the purpose of this separation? Is there any document that can I
read to learn about this strategy of organization?
This is the right place for this kind of question? 

Thank you.
Ronaldo Luiz.
Brazil.

_______________________________________________ 
epf-dev mailing list 
epf-dev@xxxxxxxxxxx 
https://dev.eclipse.org/mailman/listinfo/epf-dev