CoreLinux++ Functional Requirement Document
Revision $Revision: 1.3 $
Last Modified : Saturday, May 13, 2000

Title : Strategy Pattern

Requirement ID: 6595
Analysis References:
Design References:
Cross References: AbstractFactory

1. Introduction

Define a family of algorithms, encapsulate each one, and make them interchangeable.

1.1 Deliverables Overview

The participants in the Strategy pattern include:

Strategy

Declares an interface common to all supported algorithms. A client uses this interface to call the algorithm defined by a concrete Strategy subclass.

CoreLinux++ team will provide a abstract Strategy type and any relevant exception types.

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