| Question "What are Branches and how are they used in OSEE?" [message #5831] |
Tue, 22 April 2008 13:56 |
Eclipse User |
|
|
|
One of the problems OSEE intended to solve was to be able to manage
Variants or Product Lines. After a set of requirements is developed, it
may become the baseline for variant sets of requirements for similar
products. In other words, you may develop the same product for another
customer, but have slight changes to the requirements, code and test for
features specific to that customer. Historically, this would mean
maintaining completely separate "copies" of all the requirements and
other artifacts. This is costly to maintain when changes from the
baseline artifacts are required to be propogated to the other product
line. Add 5 or 10 more customers with different needs and this becomes a
major undertaking.
OSEE provides the capability to create these variant branches and
maintain not only the record of where these branches came from, but also
enables changes made to the baseline branches to be easily committed to
the variants. In addition, OSEE manages these variants in an efficient
manner such that only the changed requirements (or artifacts) are "copied".
|
|
|
Powered by
FUDForum. Page generated in 0.03310 seconds
Home