top - download
⟦f916272d5⟧ Wang Wps File
Length: 12972 (0x32ac)
Types: Wang Wps File
Notes: Spelunked
Names: »~ORPHAN75.08«
Derivation
└─⟦c2ca659c9⟧ Bits:30006002 8" Wang WCS floppy, CR 0037A
└─ ⟦this⟧ »~ORPHAN75.08«
WangText
…00……00……00……00……00…K…0a……00……00…K…0b…K…00…K…05…J…09…J…0a…J…0e…J…0f…J…02……86…1 …02… …02… …02…
…02…CPS/SDS/001
…02…HKI/810115…02……02…
CAMPS SYSTEM DESIGN SPECIFICATION
…02……02…CAMPS
4.5 CAMPS SYSTEM SUPPORT FUNCTIONS ...........
4.5.1 System Support Functions only at
Factor ..............................
4.5.1.1 Hardware Test Package ............
4.5.1.2 Standard Software Test Package ...
4.5.1.3 System Software Test Package .....
4.5.1.4 Factory Test Simulator Configura-
tion (TDS) .......................
4.5.2 System Support Functions at the CSSI
Site, but not at all Sites ...........
4.5.2.1 Software Maintenance .............
4.5.2.2 Data Base Generation .............
4.5.2.3 System Generation ................
4.5.2.4 Configuration Control ............
4.5.3 System Support Functions at all Sites
4.5.3.1 M&D Software .....................
4.5.3.2 Off-Line Utilities ..............
4.5.4 Generalized Test Monitor .............
4.5 C̲A̲M̲P̲S̲ ̲S̲Y̲S̲T̲E̲M̲ ̲S̲U̲P̲P̲O̲R̲T̲ ̲F̲U̲N̲C̲T̲I̲O̲N̲S̲
The CAMPS System Support Functions are non-operational
tools used in the development, test, and verification
of the operational CAMPS Hardware nd Software.
They are grouped in:
System Support Functions only at factory (described
in 4.5.1).
System Support Functions at CSSI site, but not at all
sites (4.5.2).
System Support fFnctions at sites (4.5.3).
Common for these are a generaized test monitor described
in 4.5.4.
4.5.1 S̲y̲s̲t̲e̲m̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲o̲n̲l̲y̲ ̲a̲t̲ ̲F̲a̲c̲t̲o̲r̲y̲
The System Support Functions at Factory are tools develped
to:
- test the CAMPS hardware configuration
- Hardware Test Package
- test the CAMPS modifictions to standard system
software
- Standard Software Test Package
- test the CAMPS defined system software
- System Software Test Package
- test performance of the integrated CAMPS hardware
and software
- Factory Test Simulator
The evelopment tools for application and system software
are identical to those described for the CSSI site
below except for a Factory based Z80 micro processor
Software/firmware development and test equipment.
4.5.1.1 H̲a̲r̲d̲w̲a̲r̲e̲ ̲T̲e̲s̲t̲ ̲P̲a̲c̲k̲a̲g̲e̲
The Hardware Test Package consists of software to support
the integration of DSMT hardware and hardware for sit
1-16.
The structure of the softwar is shown in fig. 4.5.1.1-1.
For each HW module a Test Module is defined. The Test
Module is capable of execution of all specified functions
of the HW module. Test modules return their result
to a calling test program.
Test module are integrate into testers.
Testers implement sequences of tests. Input is obtained
from disc and VDU, output is made on disc, line printer
and VDU.
Testers are executed under the test monitor (sec. 4.5.4).
They may be executed one by one (interactive or auomatic
testers) or in sequences (automatic testers only).
Figure 4.5.1.1-1…01…HARDWARE TEST PACKAGE STRUCTURE…86…1 …02… …02… …02… …02…
4.5.1.2 S̲t̲a̲n̲d̲a̲r̲d̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲T̲e̲s̲t̲ ̲P̲a̲c̲k̲a̲g̲e̲
The standard software test package consists of software
to support the test of standard DAMOS software i.e.:
Kernel
I/O Control (minus Dvice and Line Control)
Storage and File Management
The structure of the software is shown in figure 4.5.1.2-1.
For each SW module a Test Module is defined. The Test
Module is capable of execution of all specified single
functions of the SW modle. Test of sequences (e.g.
send + receive in process communication) involves execution
of more than one Test Module.
Test modules are integrated into testers. Testers consist
of one or more processes (in DAMOS sense) in order
to exercise the sofware components.
Tester are executed under the test monitor (see 4.5.4).
They may be executed one by one 8interactive or automatic
testers) or in sequences (automatic testers only).
Figure 4.5.1.2-1…01…Standard Software Test Package Structure…86…1 …02… …02… …02… …02…
4.5.1.3 S̲y̲s̲t̲e̲m̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲T̲e̲s̲t̲ ̲P̲a̲c̲k̲a̲g̲e̲
The System Software Test Package consists of software
to support the test of CAMPS extensions to system software
i.e.:
I/O Control (Device nd Line Control)
CAMPS System Functions
SSC Software
The structure of the software is shown in figure 4.5.1.3-1
and 2.
Figure 4.5.1.3-1 shows the configuration for test of
CAMPS System Functions and device and Line Control.
For the device andLine Control test a line test interface
is implemented transporting the data to/from the closed
loop connected line.
Figure 4.5.1.3-1…01…System Software Test Package Structure (-SSC Part)…86…1 …02… …02… …02… …02…
Figure 4.5.1.3-2…01…System Software Test Package Structure of SSC Part…86…1 …02… …02… …02… …02…
4.5.1.4 F̲a̲c̲t̲o̲r̲y̲ ̲T̲e̲s̲t̲ ̲S̲i̲m̲u̲l̲a̲t̲o̲r̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲ ̲(̲T̲D̲S̲)̲
The Factory Test Simulator Configuration consists of
softwar and hardware to support test of the operational
CAMPS. The test isperformed by emulating the operational
CAMPS environment.
The configuration is shown in figure 4.5.1.4-1. The
Test Drive System (TDS) emulates the terminal and external
interfaces of CAMPS.
The TDS is used in 3 phases (see figure 4.5.1.4-2).
r̲e̲-̲T̲e̲s̲t̲ Prepare test sequences and analyse by script
compiler
T̲e̲s̲t̲ Execute test with logged output
P̲o̲s̲t̲-̲T̲e̲s̲t̲ Print out of related test results
Details of the On-Line Test Controller is shown in
figure 4.5.1.4-3.
Figure 4.5.1.4-1…01…Factory Test Simulator Configuration…86…1 …02… …02… …02… …02…
Figure 4.5.1.4-2…01…Test Drive System Use…86…1 …02… …02… …02… …02…
Figure 4.5.1.4-3…01…TDS On-Line Controller…86…1 …02… …02… …02… …02…
4.5.2 S̲y̲s̲t̲e̲m̲ ̲S̲u̲p̲p̲o̲r̲t̲ ̲F̲u̲n̲c̲t̲i̲o̲n̲s̲ ̲a̲t̲ ̲C̲C̲S̲I̲ ̲S̲i̲t̲e̲,̲ ̲b̲u̲t̲ ̲n̲o̲t̲ ̲a̲t̲ ̲a̲l̲l̲
̲S̲i̲t̲e̲s̲.̲
At the CSSI site development and test of all application
software are supported. The configuration is shown
in igure 4.5.2-1 for hardware and figure 4.5.2-2 for
software.
The Terminal Operating System controls the execution
of processes in the CSSI development PU. At start up
and for resource allocation the TOS is commanded from
the system cosole, where lad and execution of processes
in a variable configuration, it may be commanded form
either the VDU or the System Console.
The configurations in question are:
a) Software Maintenance with
1) Software Development
2) Software Unit Test
3) Sftware Operational Test
b) Data Base Generation
c) System Generation
d) Configuration Control
Figure 4.5.2-1…01…CSSI Development Configuration…86…1 …02… …02… …02… …02…
Figure 4.5.2-2…01…CSSI Software Configuration…86…1 …02… …02… …02… …02…
4.5.2.1 S̲o̲f̲t̲w̲a̲r̲e̲ ̲M̲a̲i̲n̲t̲e̲n̲a̲n̲c̲e̲
The Software Maintenance Function consists of 3 major
tasks:
- Software Development
- Software Unit Tests
- Software Operational Tests
The Sotware Development configuration is presented
in figure 4.5.2.1-1.
It consists of:
- An editor manipulated from a VDU for modification
of and introduction of new software
- A compiler directed by edited compiler directives.
Files containing stndard lay out of tables, data
elements, error codes etc. are merged-in at compile
time.
- A linker resolving external references for all
modules including definition of segmentation for
shared modules. Link is directed by the VDU controlled
link irective file.
- A Test System Generator being able to generate
load modules for Operational Software for Unit
Test, Operational Software for Operational Test
and testers for Unit Tests and Operational Tests.
All Output produced by the SoftwareDevelopment Configuration
is kept in Listing Libraries hardcopies upon request.
The Source is kept in 3 levels of libraries (figure
4.5.2.1-2) one for each of
Released Modules
Tested Modules
Development Modules
Released Modules are modules aving passed a formal
test. They are placed in a library of software under
configuration control.…86…1 …02… …02… …02… …02…
Figure 4.5.2.1-1…01…CSSI Software Development…86…1 …02… …02… …02… …02…
Tested Modules are modules having passed a sub system
test conducted by the responsible for software development.
They are kept in a library for tested modules.
Development modues are administrated by individuals
performing software developmentj. They are kept as
development libraries.
Software unit test is performed in the configuration
shown in figure 4.5.2.1-3.
The TESTER1 and TESTERN functions as environment appliations.
The TESTER1 may via the DEBUGGER insert breakpoints
in the Software Linker Test. Furthermore, the TESTER1
to N may access disk files for input and output and
system software for operational interfaces to the software
under test.
Software perational test is performed in a configuration
similar to te one shown in figure 4.5.2.1-3. The "Software
under test" is an integrated subsystem and the Testers
must be so designed that this integrated subsystem
can interface only via operational nterfaces. The Debugger
is in this case only used as trouble shooter.
Figure 4.5.2.1-2…01…Software Libraries…86…1 …02… …02… …02… …02…
Figure 4.5.2.1-3…01…Unit Test Configuration…86…1 …02… …02… …02… …02…
4.5.2.2 D̲a̲t̲a̲ ̲B̲a̲s̲e̲ ̲G̲e̲n̲e̲r̲a̲t̲i̲o̲n̲
The initial data base for each site is generated at
the CSSI site (or initially at factory).
Data base generation is at two levels. First level
is generation of all common data for all sites. This
is shown in figure 4.5.2.2-1. The common data base
generation consists of Table Generator, VDU Format
Generator and Predefined Message Generator.
The Table Generator operates on a card formatted nput.
At the CSSI site the input is from VDU, at factory
it may be from punched cards as well. The Table Generator
outputs tables in the format used in the operational
software, maintenance SW being able to modify and print
tables as at operationalsites.
The VDU Format Generator supports generation of VDU
formats for use by the Format Handler of the IO control
SW.
The Predefined Message Generator supports generation
of predefined messages for use by operational software.
Figure 4.5.2.2-1…01…Data Base Generation Common System Data…86…1 …02… …02… …02… …02…
The Common System Data generated are:
PLA table
AIG table
SIC table (without SDLs)
VDU formats
Predefined Messages
Second level of Database generation is generation of
Sit Specific Data partly by adaptation of Common System
Data. Figure 4.5.2.2-2.
The PLA table, the AIG table and the SIC tables are
copied to an intermediate version for update by table
maintenance software (similar to on-line SW).
The RI table, SL table, SCD table, user profiles and
terminal profiles are input via the Input file for
the Table generator. Table generation is performed
into the above intermediate version.
The Configuraton Table Generator generates tables with
definitions of
External Channels
Terminals
Other peripherals
Memory Administration
Disk Storage Administration
Software Configuration
VDU Formats and Predefined Messages are copied form
the Common Data.
Figure 4.5.2.2-2…01…Data Base Generation Site Specific Data
