To see the general guidelines for deciding whether to use one model or multiple models, click Table.
The following table shows guidelines for deciding to use one model or multiple models.
|
Factors Favoring Use of |
One Model |
Two or More Models |
|---|---|---|
|
Project size |
1 to 100 entity types |
over 100 entity types |
|
Project team size |
1 to 50 members |
over 50 members |
|
Degree of sharing |
high |
low |
|
Release strategy |
all at once |
phased |
When deciding whether to divide a project into multiple models, weigh the cost of increased version control against the benefit of more flexible development and the reduced subsetting activity against each model.
Note: For more information, see the “Checking a Subset In or Out of the Encyclopedia” chapter in this guide.
If you decide to use multiple models, it is best to delay splitting up the initial project model as long as possible to minimize the cost of the versioning. As stated earlier, subsetting usage does not reach its peak until the Procedure Action Diagram building stage of Design.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|