We would like to create "AS-IS" and "TO-BE" activity hierarchy diagrams, but we found that as we modified the TO-BE diagram, the relationships were automatically being updated between activities in the AS-IS diagram. It is great that the repository likes to maintain those relationships across diagrams, but in the event of an AS-IS and TO-BE comparisons, that functionality is getting in the way. Is there any way around this?
Kiran552 270006KJ803 Posts
Re: "AS-IS" and "TO-BE" Diagrams2014-01-15T13:50:19ZThis is the accepted answer. This is the accepted answer.
Im working on creating AS-IS and TO-BE Data Models for our project. Mutiple Data Modelers are working and we are not able figure out best way to manage this situation. Any help regarding this is appreciated.