ReadySET design-components

[edit] Design > Architecture > Components

[edit] Release Information

TODO: Briefly describe each component in the system. Focus on architectural issues such as communication mechanisms, environmental concerns that affect deployment options, and concurrency. Note key aspects of each interface, but avoid duplicating details of interfaces that are specified in the UML class diagrams or other documents.

Each interface can be an API (application program interface), standard protocol (e.g., HTTP), config files, input data file format, or interactive user interface (e.g., command-line or GUI). One component may have multiple interfaces: e.g., a server may handle requests in a standard protocol, but also have a config file, command-line options, an administrative control panel GUI, and a performance monitoring API.

TIP: Use an HTML anchor for each component so that a direct link can be made from other documents, issues, and email messages.

[edit] C-00: COMPONENT NAME

[edit] C-01: COMPONENT NAME

[edit] C-10: COMPONENT NAME

[edit] C-11: COMPONENT NAME

[edit] C-12: COMPONENT NAME

[edit] C-20: COMPONENT NAME

TODO: Check for words of wisdom and discuss ways to improve this template. Or, evaluate the ReadySET Pro professional design components template.

Company Proprietary

Copyright © 2003-2004 Jason Robbins. All rights reserved. License terms. Retain this copyright statement whenever this file is used as a template.