CoreLinux++ Functional Requirement Document
Revision $Revision: 1.4 $
Last Modified : Tuesday, May 2, 2000

Title : Command Pattern

Requirement ID: 6588
Analysis References: Use Case Report , Analysis Diagrams
Design References: Class Report , Design Diagrams
Cross References:

1. Introduction

Encapsulates a request as an object, thereby letting you parametize clients with different requests, queue or log requests, and support undoable operations.

1.1 Deliverables Overview

The participants in the Command pattern include:

AbstractCommand

Declares an interface (execute) for executing an operation.

ConcreteCommand

Implements the AbstractCommand execute interface, defines a binding between a Receiver object and an action.

CoreLinux++ team will provide the Command abstractions and general exceptions.

2. Functional Requirements

The requirements will vary based on your domain solution.

2.1 User Interface Specifications

Domain defined

2.2 Product Services

Domain defined

2.3 External Interfaces and Database Requirements

Domain defined

2.4 Error Handling

Domain defined

2.5 Foreseeable Functional Changes and Enhancements

NA

3. Non-Functional Requirements

Precondition constraints: None

Postcondition constraints: None

Invarient constraints: None

3.1 Performance Requirements

NA

3.2 User Documentation and Other User Aids

This Document

Analysis Use-Case diagrams

Design class diagrams

3.3 Development Requirements

Standards: CoreLinux++ C++ Standards and Guidelines

3.4 Foreseeable Non-Functional Changes

NA

4. Remarks and Guidelines for Later Life Cycle Phases

TBD

5. Term Glossary

TBD