|
Requirements Specification Data Server
Revision A - 28 MARCH 1996
|
| Name | Position | E-mail address |
---|
Author(s): | Peter Mattsson | Team Member | pt93pm@pt.hk-r.se |
Responsible: | Martin Puhv | Team Manager | pt93mp@pt.hk-r.se |
To: | Hans Ottosson Anders Angelhag | Customer Customer | hans.ottosson@sydkraft.se anders.angelhag@telecom.sydkraft.se |
Cc: | SAGA Marcus Ingemansson Fredrik Ygge Peter Molin | SAIDA Team Project Manager Technical Advisor Head of Department | pt93mi@pt.hk-r.se fredrik.ygge@ide.hk-r.se peter.molin@ide.hk-r.se |
Approved by | Signature | Date |
---|
Anders Angelhag | | |
Marcus Ingemansson | | |
Abstract
The Data Server subsystem of the SAIDA project is intended to provide a uniform interface to network variables.
1 Introduction
1.1 Purpose
The Data Server is the central component for most interfaces, including the data navigator, the mail command interpreter and the WWW interface.
1.2 Scope
- The scope of this requirements specification is the data server.
- The data server provides a framework for named variables that can be accessed in a uniform way, regardless of how the variable is implemented.
- Examples of variables that can be accessed through this mechanism include LonWorks network variables and SAIDA-implemented logs.
1.3 Testing
All requirements will be tested according to [SAIDA 96-2].
2 General Description
2.1 Product's Functions
Every variable handled by the data server has an external name, a type and access functions for getting/setting it's current value. In addition, logged variables have access methods to allow access to the most recent value, indexed access, value at a specific time, time for last change etc.
2.2 User Characteristics
The data server will be used by most other parts of the SAIDA system. The data server will not be used directly by human users; they will only access it indirectly via other parts of the SAIDA system.
2.3 General Constraints
The data server's type system should build on existing standards, possibly extended to allow the log types needed by SAIDA.
3 Deliveries
The first delivery on 1996-04-11 of the data server will fulfil all requirements in this document.
4 System Requirements
4.1 Top-level Requirements
The data server shall...
DS_F1 ...export named variables (see [2.1], "Product's Functions") to remote users. [DS_F2, DS_F4, DS_F5]
DS_F2 ...organize variables in a hierarchy. [DS_F6, DS_F9]
DS_F3 ...use LCA's existing type system.
4.2 Bottom-level Requirements
The data server shall...
DS_F4 ...bind variables to a value.
5 Interface Requirements
5.1 Data Server Interface
The data server interface shall...
DS_F5 ...provide access to get/set functions via a variable name.
DS_F6 ...provide navigation primitives for moving in the variable hierarchy and listing variables.
DS_F7 ...allow creation of variables.
DS_F8 ...allow deletion of variables.
DS_F9 ...provide primitives for changing the structure of the variable hierarchy.
Appendix A: Terminology
LCA - LonWorks Component Architecture
Appendix B: Literature
[SAIDA 96-1] Grahm M., "Solution Decomposition" - University of Karlskrona/Ronneby, 1996.
[SAIDA 96-2] Puhv M., "Data Server Test Specification" - University of Karlskrona/Ronneby, 1996.
[SAIDA 96-3] Requirements Team, "Requirements Specification" - University of Karlskrona/Ronneby, 1996.
[SAIDA 96-4] Grahm M., "Deviations from the Requirements Specification" - University of Karlskrona/Ronneby 1996.
- Requirements Specification
-
- Data Server
-
- Abstract
-
- 1 - Introduction
-
- 1.1 - Purpose
-
- 1.2 - Scope
-
- 1.3 - Testing
-
- 2 - General Description
-
- 2.1 - Product's Functions
-
- 2.2 - User Characteristics
-
- 2.3 - General Constraints
-
- 3 - Deliveries
-
- 4 - System Requirements
-
- 4.1 - Top-level Requirements
-
- 4.2 - Bottom-level Requirements
-
- 5 - Interface Requirements
-
- 5.1 - Data Server Interface
-
- Appendix A: Terminology
-
- Appendix B: Literature
-
Info
Team
WebCam
Documents
Schedule
CustomerOnly
© 1996, The SAIDA Project