CoreLinux++ Functional Requirement Document
Revision $Revision: 1.3 $
Last Modified : Sunday, May 7, 2000

Title : Subject Observer Pattern

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

1. Introduction

Define a one-to-many dependency between objects so that when one object changes state, all its dependents are notified and updated automatically.

1.1 Deliverables Overview

The participants in the Observer pattern include:

Subject

Knows its observers, no limits to the number of Observer objects that may observe a subject.

Observer

Defines an updating interface for objects that should be notified of changes in a subject.

Context

Defines the context of the change in relationship to the subject.

CoreLinux++ team will abstracted types for Subject, Observer and Context 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