Glossary

Modules.
A part of an application that contains views, support services, business logic, and configuration information.
It contain functionally discrete pieces, but they integrate with the user interface, communicate with the shell, and communicate with each other.

Shell.
A container application that hosts user interface elements and services; it also manages the bootstrap process.
provides the overall user interface structure.
shell provides access to smart client services required by modules throughout the application.
In addition to the overall UI structure, the shell provides key smart client capabilities, such as deployment, update, data caching, and offline support.

UIElement.
A control that is hosted in the shell and shared between multiple modules, such as a toolbar button, menu item, or status panel.

workspace.
A component that encapsulates a particular visual layout of controls, such as within tabbed pages.

Service-Oriented Architecture
An organization will define their Web service.
This means that there will be a family of Web services for the ERP system, the CRM system, the inventory systems, and so on.
Solutions are then built on top of these services, or on composites of these services, leading to form "composite solutions."
The client-side piece of logic that handles these service is known as a service agent.

Software assets
include reusable code components, documentation, and reference implementations.

Software tools
include wizards, code generators, and visual designers.

Event Broker.
A pattern that enables loosely coupled components to communicate using a publish/subscribe system.

Model-View-Presenter(MVP).
View passes user interactions to the presenter, which updates the data model.
The presenter is responsible for updating the view.

WorkItem.
A run-time container of the components and services that are collaborating to fulfill a use case.