| [epf-dev] Multiple Capability Patterns -- some unpublished? |
|
hiho, We want OpenUP to be an enactable process, but also it
should be a good example of usage of the Eclipse Process Framework. We have had some discussion about whether or not there is development
in Inception. The discussion has led us to not include development as the
“default” (i.e. the only supplied Inception iteration template)
while having some verbiage around possibly including additional activities for
development. The original 0.9 release didn’t enforce Test-driven
development. In discussions we noted that we wanted to push TDD because
it is a very valuable technique. The current Develop Solution activity is
strictly TDD. But TDD is something that some organizations are not applying. What do people think about including some additional
capability patterns in the OpenUP repository that would not be in the default published
OpenUP process? This gives us a stronger message of “This is the
default, but it is considered ‘valid’ to…” for some of
these expected variations. And this might make the repository a stronger
example of appropriate usages of EPF (the repository has information and some
amount of that is assembled into a published process).
------------ b |