CoreLinux++ Functional Requirement Document
Revision $Revision: 1.3 $
Last Modified : Friday, May 5, 2000

Title : Mediator Pattern

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

1. Introduction

Define an object that encapsulates how a set of objects interact. Mediator promotes loose coupling by keeping objects from referring to each other explicitly, and it lets you vary their interaction independently.

1.1 Deliverables Overview

The participants in the Mediator pattern include:

AbstractMediator

Defines an interface for communicating with Colleague objects.

AbstractColleague

Knows its AbstractMediator object, communicates with its mediator whenever it would have otherwise communicated with another Colleague.

CoreLinux++ team will provide AbstractMediator and AbstractColleague classes.

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