Mapping Requirements to Functionality
After the business requirements are defined, it is necessary to map those business requirements to functionality. It is also necessary to assign a priority to each business requirement. This priority is used when multiple business requirements are considered in the design as a particular aspect of Active Directory. The best example of this is the organizational unit (OU) structure within a domain. Administrative requirements, end user requirements, and group policy requirements must all be considered when designing the OU structure. The priority helps determine which design consideration, or requirement, takes precedence over the others.
Table 4.1 summarizes the business requirements accumulated thus ...
Get Windows® 2000 Active Directory™ now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
