CoreLinux++ Functional Requirement Document
Revision $Revision: 1.4 $
Last Modified : Thursday, May 18, 2000

Title : State Pattern

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

1. Introduction

Allow an object to alter its behavior when its internal state changes. The object will appear to change its class.

1.1 Deliverables Overview

The participants in the State pattern include:

StateContext

Defines the interface of interest to clients, maintains an instance of State subclasses that defines the current state.

State

Defines an interface for encapsulating the behavior associated with a particular state of the StateContext.

CoreLinux++ team will provide abstracted types for State and StateContext, as well as 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