CoreLinux++ Functional Requirement Document
Revision $Revision: 1.4 $
Last Modified : Thursday, April 27, 2000

Title : Chain of Responsibility Pattern

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

1. Introduction

Avoid coupling the sender of a request to its receiver by giving more than one object a chance to handle the request. Chain the receiving objects and pass the request along the chain until an object handles it.

1.1 Deliverables Overview

The participants in the Chain of Responsibility pattern include:

Handler

Defines an interface for handling requests, accessing successors, and optionally implements the successor link.

CoreLinux++ team will provide base Handler and Handler 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