top - download
⟦3d591790d⟧ Wang Wps File
Length: 5692 (0x163c)
Types: Wang Wps File
Notes: CPS sys spec content
Names: »0127A «
Derivation
└─⟦84647c47a⟧ Bits:30005817 8" Wang WCS floppy, CR 0014A
└─ ⟦this⟧ »0127A «
WangText
…02…CPS/SDS/0001
…02…801022 …02……02…#
CAMPS SYSTEM DESIGN SPECIFICATION
…02……02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 GENERAL ......................................
1.1 PURPOSE ..................................
1.2 PROJECT REFERENCES .......................
1.3 TERMS AND ABBREVIATIONS ..................
2 SUMMARY OF REQUIREMENTS ......................
2.1 SYSTEM DESCRIPTION .......................
2.2 SYSTEM FUNCTIONS .........................
2.3 ACCOUNTABILITY ...........................
2.4 AVAILABILITY AND MAINTAINABILITY .........
2.5 TIMING ...................................
3 ENVIRONMENT ..................................
3.1 STANDARD HARDWARE, FIRMWARE, AND SOFTWARE.
3.2 EXTERNAL INTERFACES ......................
3.3 LOCAL TERMINAL INTERFACES ................
3.4 AUXILIARY EQUIPMENT INTERFACES ...........
4 SYSTEM OVERVIEW ..............................
4.1 CONFIGURATION SUMMARY ....................
4.2 MESSAGE FLOW .............................
4.3 SYSTEM CONTROL ...........................
4.4 ACCOUNTING ...............................
4.5 DUAL OPERATION ...........................
5 SYSTEM BREAK-DOWN ............................
…02……02…5.i SUBSYSTEM i ..............................
5.i.1 Summary of Requirement ...............
5.i.1.1 Subsystem Description ............
5.i.1.2 Functional Requirements ..........
5.i.1.3 Accountability Requirements ......
5.i.1.4 Dual Operation ...................
5.i.1.5 Performance Requirements .........
5.i.2 Environment ..........................
5.i.2.1 Hardware, Firmware, and System
Software .........................
5.i.2.2 External Interfaces ..............
5.i.2.3 Subsystem Interfaces .............
5.i.2.4 Interfaces to CAMPS Monitors .....
6 HARDWARE BREAK-DOWN ..........................
(includes a matrix defining for each unit which
subsystems have functions executed partly by the
unit)
7 FIRMWARE BREAK-DOWN ..........................
(includes a matrix defining for each unit which
subsystems have functions partly executed by the
unit)
8 SOFTWARE BREAK-DOWN ..........................
(includes a matrix defining for each unit which
subsystems have functions partly executed by the
unit)
(CAMPS Monitors = Queue, log, Statistics, etc.)
P̲R̲E̲L̲I̲M̲I̲N̲A̲R̲Y̲ ̲C̲A̲M̲P̲S̲ ̲B̲R̲E̲A̲K̲D̲O̲W̲N̲
In the following a first guess on CAMPS breakdown into
subsystem is presented before the analysis for section
3 and 4 in CAMPS SYSTEM SPECIFICATION has been finalized.
I̲ ̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲A̲L̲ ̲L̲E̲V̲E̲L̲
1. MESSAGE TERMINAL SUBSYSTEM
Preparation, edit, coordination, release, and retrieval
of messages. Line by line ACP 127 verification
and generation. VDU, TP and medium speed TP handling
incl. output control.
2. CHANNEL INTERFACE SUBSYSTEM
Functional level of interface to CCIS, SCARS, TARE,
TRC, OCR, PTR, and PTP. This includes all levels
of protocols. ACP 127 analysis of complete messages.
Routing determination.
3. MESSAGE DISTRIBUTION SUBSYSTEM
Distribution of messages to groups of lines/terminals
based on SIC.
4. MESSAGE SUPPORT SUBSYSTEM
Message service, Message Distribution Supervisor
message handling (service mossage)
5. ARCHIVE AND RETRIEVAL SUBSYSTEM
Storage of all messages and non-messages following
requirements 3.2.7 (no log, no statistics)
I̲I̲ ̲ ̲O̲T̲H̲E̲R̲
6. SUPERVISOR CONTROL SUBSYSTEM
All supervisor functions except service message
processing.
7. MONITORING AND ACCOUNTING SUBSYSTEM
Survey of CAMPS functions e.g.
queue length
delivery times
Logging incl log analysis
Report control
Statistics
8. MESSAGE TRANSITION SUBSYSTEM
Queue - Message transition control
Possibly spooling
9. LINE INTERFACE SUBSYSTEM
Handles together with the system package Terminal
Handling System the security aspects of lines (access
control incl. sign-in, sign-out)
Handlers and low level firmware specific for the
electrical characteristics of lines/terminals.
VDU non-standard firmware.
Record control/ITA2 - ITA5 conversion.
Line Hardware
Terminal hardware modification
10. CONFIGURATION CONTROL SUBSYSTEM
SSC functions
Dual hardware control
Dual software operation (checkpoint etc.)
Controls Device allocation to PUs
Firmware init
Software init
Technical error handling
(Software errors, hardware errors but not operational
errors)
11. SYSTEM GENERATION SUBSYSTEM
This subsystem handles generation of software and
firmware from existing modules.
12. DATABASE SUBSYSTEM
This subsystem handles input of site specific data
and generation of data bases necessary for initialization
of CAMPS sites.
13. OFFLINE DEVELOPMENT SUBSYSTEM
This subsystem handles execution of Eidtor, Compiler,
control of software and firmware libraries. It
handles security problem concerning execution in
standby P.U. while CAMPS operations go on.
14. OFFLINE DIAGNOSTICS SUBSYSTEM
Hardware, firmware and software test equipment
as required for site repair.
