If you want to try again, you revert your checked out ?¬?les to the versions in
version control (possibly also updating to newer versions of other ?¬?les).
With a repository, you open the models you want to work on. As you modify the
models or elements, or alternatively when you open them for editing, you are given the
lock on those models so that nobody else can change them. If the results of your
editing are satisfactory, you commit your transaction. This publishes your changes to
the repository, so other users can see them. It also updates your view of the repository
to include any changes committed by other users. If these changes were a bad idea, or
you want to try again, you abandon your transaction. This discards the changes, and as
with commit it also updates your view of the repository.
15.3.2 But How Do I Branch?
Branching is used in code-based development to handle variants. Normally, many ?¬?les
will need to be branched to support a pair of variants, and each of those ?¬?les must
proceed in two parallel version branches. Because of the large costs associated with
this, branching can only be used for a small number of variants.
With DSM, most situations that earlier required branching no longer occur. The
modeling language factors out these changes, sometimes into the generator or domain
framework and sometimes into small property or other changes in a top-level
con?¬?guration model.
Pages:
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783