OpenUP - authoring/submission process (and Subversion)? [message #566786] |
Thu, 12 October 2006 15:49 |
Scott Dunn Messages: 10 Registered: July 2009 |
Junior Member |
|
|
We're embarking on a pilot project that will use the EPF Composer to
author various engineering processes. One of the issues I need to resolve
up front is the authoring process itself. Obviously there needs to be a
submit-review-accept cycle and on the face of it this needn't be so
different from any process for policing source code submissions, however
the creation of IDs for process elements, and the structured form of the
underlying versioned artifacts will likely complicate the merging of
multiple submissions.
As the OpenUP maintainers must have dealt with multiple submissions from
various authors and the review, acceptance and merging of content into a
single branch, I'd appreciate understanding the OpenUP development process.
Do authors work in private branches? Can individual contributors work in
the same packages or is exclusive ownership assigned? If shared ownership,
how are merges of the XMI files effected (aside from very very carefully!)?
Related to the above, Subversion is our chosen repository so we need to
work with this. The document 'Using EPF Composer with a VCS' talks about
Clearcase and CVS. I can't imagine there would be any issues, but aside
from not having tighter integration into the EPF Composer are there any
known issues (or best practices) when using Subversion?
Thanks,
Scott.
|
|
|
Powered by
FUDForum. Page generated in 0.02642 seconds