next up previous contents
Next: 2. Development and Execution Up: Status Server Detailed Design Previous: List of Figures   Contents

Subsections

1. Introduction

1.1 Purpose

The purpose of this document is to define the detailed design specification for the Status Server. The detailed design specification documented here is based on a set of previously defined requirements and functional specification. The implementation of the Status Server will be based on the design outlined in this document. While the Client API is mentioned in some detail, this document does not adequately cover the detailed design of the Client API. Either this document will be amended to fully cover the Client API, or the detailed design of the Client API will be covered in a separate document.

The first draft of this document must be reviewed by the members of the software group and will be amended following review. The implementation stage will not start until this review has been completed and the document updated.

1.2 Scope

Unless otherwise noted, the detailed design specifications identified in this document are intended to be implemented in the first release of the Status Server. However, release requirements may dictate the priority and staging of functionality.

1.3 References

The design of the Status Server is based on a previously established set of requirements and functional specification. In addition, the Status Server will utilize a previously written CFHT Socket Library, which is often referred to as ``sockio'' in this document. More details regarding the requirements, functional specification, and sockio library can be found at the following locations on the CFHT intranet.


next up previous contents
Next: 2. Development and Execution Up: Status Server Detailed Design Previous: List of Figures   Contents
Tom Vermeulen
2011-01-26