GNM_RCS_Document_Index

• 1. .Introduction

     1. Purpose

This document is an index of system documentation that describes how O3 Team has built the RCS system (including SLM) at GNM.

It has been prepared to help scope out set of documents that are needed – agreeing what needs to be written in advance, and then writing it.

It will also be useful in the longer term to help find relevant documentation.

• 1. Scope

     1. What’s in scope

The document index falls into these categories:

• • Core documents that deal with system-wide considerations such as schema design, software architecture, security, standards, adopted techniques etc.

  • Functional specifications (FS)

  • Technical specifications (TS) that describe the implementation of the functional specifications

• 1. What’s out of scope

This index does not include any detailed program specifications, as the software modules already exist, and have been proven through years of use. The software has been written with good practice and development standards in mind, is self-documenting in most respects, and includes inline comments in areas of greatest complexity.

The following subject areas are out of scope as they are managed internally by the RCS Administrator:

• • Online help system;

  • Business Objects reports;

  • User training materials.

The following areas are also deliberately out of scope as they are owned by the GNM IT department and/or eDBA:

• • Server and network architecture;

  • Database implementation and architecture;

  • Database backups and recovery;

  • Application server (WebLogic) implementation & configuration;

  • Application server failover;

  • Client PC and Mac configuration (OS versions, browser versions, Java versions)

  • (NB Oracle maintains a list of certified OS/Browser/Java combinations on its website);

  • Software release methodology.

..

• 1. .Documents

     1. Core documents

The following documents have a bearing on the system as a whole. The document names are highlighted in blue if they have been written.

.

• 1. Functional & technical specifications

The documents listed below describe each significant functional area (functional specifications), and how they have been implemented technically (technical specifications). The document names are highlighted in blue if they have been written.

• 1. RCS

• 1. SLM

End of Document