CoreLinux++ Functional Requirement Document
Revision $Revision: 1.2 $
Last Modified : Saturday, February 12, 2000

Title : Singleton Pattern

Requirement ID: 5099
Analysis References: Use Case Report,Analysis Diagram
Design References: Class Report,Design Diagram
Cross References:

1. Introduction

Ensure a class only has one instance, and provide a global point of access to it.

1.1 Deliverables Overview

The participants in the Singleton pattern include:

Singleton

Defines an Instance operation that lets clients access its unique instance. Instance is a class operation.

CoreLinux++ team will provide a Singleton type controller.

2. Functional Requirements

The requirements will vary based on your domain solution, generally a C++ Singleton will hide it's constructors and only have static public methods.

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