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

Title : Memento Pattern

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

1. Introduction

Without violating encapsulation, capture and externalize an object's internal state so that the object can be restored to this state later.

1.1 Deliverables Overview

The participants in the Memento pattern include:

Memento

Stores internal state of an originating object. The Memento may store as much or as little of the originator's internal state as necessary at it's originator's discretion.

Originator

Creates a memento containing a snapshot of its current internal state, uses the memento to restore its internal state.

Caretaker

Is responsible for the memento's safekeeping, never operates on or examines the contents of a memento.

CoreLinux++ team will provide abstracted types for Memento and Originator, along with 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