Glossary of Terms
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies.
This section describes the terms that are used in the Web Client Software Factory and its accompanying documentation.
Web User Interface
presenter.****Contains the logic to respond to a view's events, and in turn, manipulates the state of the view base on changes in the application state.
view. An ASP.NET Web page. The view manages the controls on the page, and it forwards user interface events to a presenter class.
business module. Encapsulates one or more use cases for a particular application domain (for example, electronic funds transfers). It can include Web pages, user controls, or master pages.
composition container. A run-time container for services and managed objects. It uses ObjectBuilder to create instances of, and manage lifetimes of, both shared and independent components.
controller. Manages the flow of logic for in use cases by enforcing control flow, separating control and presentation logic, and providing state management capabilities.
foundational module. Provides services to the other modules in the application. For example, a foundational module can contain code that provides instrumentation, such as logging. A foundational module does not contain Web pages.
module. Encapsulates a set of concerns of your application and can be independently deployed to a Web site.
service. A supporting class that provides functionality to other components in a loosely coupled way.
action.** **An atomic unit of work called in a defined sequence by recipes. The sequence is specified in the recipe definition. An action accepts input either from arguments that have been gathered by the calling recipes or from output received from an action run earlier in the sequence. Recipe actions are specified in the recipe definition.
guidance package. A named collection of recipes, templates, value providers, type editors and converters, and actions, together with a configuration file.
Guidance Automation Toolkit. An extension to Visual Studio 2010 that allows architects to design and create rich, integrated user experiences for reusable assets including frameworks, components, and patterns.
Guidance Automation Extensions.A run-time component that must be installed to use the Guidance Automation Toolkit or to use any guidance packages built using the Guidance Automation Toolkit.
recipe.****A user-defined and executable sequence of actions that automates activities that developers would usually manually perform, often by following a series of instructions. You can use recipes to ensure that repetitive and often error-prone activities are performed in a consistent manner and to simplify complex or repetitive development tasks. Recipes can be run on particular solution elements or on a group of solution elements that share certain characteristics (for example, all C# projects).
recipe framework. The collection of classes in the Guidance Automation Extensions that supports the execution of recipes.
Visual Studio template. A template written in XML and used by Visual Studio to create solutions or add one or more projects or items to an existing solution. The templates are expanded by the Visual Studio template engine. Using the Guidance Automation Toolkit, you can associate Visual Studio templates with recipes. This association means that when a template is unfolded, the wizard extension calls the recipe to let it collect parameter values (arguments) for the expansion and then, after the template is unfolded, to execute actions that may further transform solution items created by the template.
wizard.****A value-gathering strategy used to gather values from recipe arguments. Any recipe can have a wizard associated with it. A wizard guides the developer through one or more steps, which are displayed as pages of the wizard.