The following table has the guidelines to determine whether to adopt a model with the Adopt All option or to adopt selected objects in a model with the Adopt Selected option:
|
Select option: |
If the source and destination models |
|---|---|
|
Adopt All |
Meet ALL of these criteria: Are considered the same (contain all or nearly all objects in common) Contain all or many objects that are logically the same, but that do not share common ancestry Contain no objects that are NOT designed to be equivalent, but have the same name and are of the same type |
|
Adopt Selected |
Meet ANY of these criteria: Are considered partially the same (contain only some objects in common) Contain one or more objects that are logically the same but that do not share common ancestry Contain objects that preclude using Adopt All (Objects that are not adoption candidates even though they are named the same.) |
The third criteria for Adopt All is critical. Adopt All means all objects meeting adoption criteria will be adopted. Adoption criteria for most object types is having the same name. If the models contain any objects with the same names that have no similarity in purpose, you want to avoid selecting those objects during an adoption. When using adoption with such models, be sure to use the Adopt Selected and avoid selecting the identified object(s). For examples, see Identify Objects to Avoid Adopting.
The guideline to choose Adopt All when the two models are considered the same, and to choose Adopt Selected when the two models are considered only partially the same, is not a hard and fast rule. For example, consider the scenario where two models are the same, but Technical Design transformation was performed. This process deletes and recreates objects, so the TD objects do not share common ancestry. In this situation, it can be easier to use the Adopt All Objects option rather than to manually select all TD objects to be adopted.
There are many situations where you will want to weigh the advantages of each option. Consider the following:
|
Adopt All |
Adopt Selected |
|---|---|
|
No object selection time needed No chance of missing an object you wanted to adopt |
Less processing time needed Less chance of adopting an object you do not want to adopt, since verifying a limited list is easier to do with accuracy |
|
|
|
If you choose adopt selected, consider creating an aggregate set that you can reuse. You can use Compare Report results to identify objects to include in an aggregate set for trial adoption. You can use Trial Adopt Report results to modify the set, if needed.
The following table has the guidelines to determine whether to add, use, or modify an aggregate set:
|
Consider This Aggregate Set Usage |
If the Model Comparison |
|---|---|
|
Add a set |
Is being performed with objects you plan to adopt or migrate, and no appropriate set exists |
|
Use an existing set |
Is to focus on only the objects identified in the set |
|
Modify a set |
Is to focus on many objects already defined with or without additional objects |
|
Copyright © 2013 CA.
All rights reserved.
|
|