An improperly defined subset results in too many or too few objects to complete a task. Users who do not have all objects needed to complete a task have a tendency to over define a subset and get more than is needed. Over defining a subset has a ripple effect of causing other users to get downgraded. The net effect is that subsets must be overridden, re-defined and downloaded. This incurs unproductive time.
You can usually improve subsetting practices by training one project member for the role of subsetting expert. This person should review each subset for the correct scoping objects, expansion, and protection needed for the task. Team members should be taught to use the subsetting documentation to scope their individual subsets. These subsets should then be reviewed with the subsetting expert. The subsetting expert should explain any requested changes so that each developer can gain a better understanding of the subsetting rules.
As team members become better at subsetting, the number of subsets that are incomplete or too large decreases. Well-scoped subsets reduce processing time and improve performance. The number of unnecessary objects included in each subset decreases, as does the number of multiple subsets being downloaded for a single task.
|
Copyright © 2013 CA.
All rights reserved.
|
|