Architecting Management Tools 

This section guides you through the process of identifying and collecting the data you need to design a Management Tool for Windows Server. The following sections will show specifically how to use this data to construct an MMC snap-in. The reason for separating the data collection step from the design guidelines is to help focus the management tool design process on the principles that help create a good management user experience:

  • Strong user orientation
  • Easily discoverable management activities
  • Consistent, helpful, and predictable results of user actions

The first topic (Architecting the Management User Experience) will give you the skills you need to analyze the management requirements of your feature. The second topic (Making Hard Decisions About What to Include) helps prioritize the attributes of a good user experience against available design resources, and the third topic (Designing for Operations) shows how a good user experience fits into overall feature design. The guidelines included in this section apply to any Management User Experience, including a command line experience available from products like Windows PowerShell.

In the Constructing Snap-ins section, Mapping Feature Functionality to the User Experience illustrates the ways in which the information collected in the Architecting Management Tools section can be displayed in the navigation tree, the results pane, and the Actions pane of the MMC framework.