top - download
⟦eaae9a6ca⟧ Wang Wps File
Length: 42209 (0xa4e1)
Types: Wang Wps File
Notes: ACDN/PIP/001 (0.0)
Names: »2637A «
Derivation
└─⟦46c7b66fa⟧ Bits:30006139 8" Wang WCS floppy, CR 0233A
└─ ⟦this⟧ »2637A «
WangText
…0b……00……00……00……00……0e……0a……00……00……0e……0b……0e……0c……0e……02……0e……07……0d……0b……0d……01……0d…
…0d……05……0d……06……0c……0b……0c……01……0c……06……0b……08……0b……0f……0b……01……0b……02……0b……07……0a……0f……0a……07……09……0a……09……0d……09……0e……09… …08……0a……08……0e……08……05……86…1 …02… …02… …02…
…02…ACDN/PIP/0001
…02…820920 …02……02…#
ACDN PRELIMINARY
PROGRAM IMPLEMENTATION PLAN…02…issue 0.0…02… ACDN
ACDN/0110/PIP/0001
ACDN PRELIMINARY…01…PROGRAM IMPLEMENTATION PLAN
L̲I̲S̲T̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1. INTRODUCTION
1.1 Scope
1.2 Applicable Documents
1.3 Abbreviations
2. ORGANISATION
2.1 Christian Rovsing Organisation
2.2 The ACDN Organisation
2.2.1 Program Management
2.2.2 System Engineering
2.2.3 Hardware Development and Production
2.2.4 Software Development
2.2.5 Integration and Acceptance Tests
2.2.6 Integrated Logistics Support
2.2.7 QA and Configurations Management
2.2.8 General Line Management Responsibilities
3. CHRISTIAN ROVSING/AIR CANADA LIAISON
3.1 Authority
3.2 Reporting
3.3 Approval and Submittal of Documentation
3.4 Progress Reports and Meetings
4. SUMMARY OF DEVELOPMENT ACTIVITIES
4.1 Contractual Milestones
4.1.1 Project Contractual Milestones
4.1.2 Statement of Work
4.2 Overall Work Breakdown Structure
4.3 Master Schedule
4.4 Documents to be produced
4.5 Development Approach
4.6 System Development Baselines
4.6.1 System Requirement Baseline
4.6.2 System Design Baseline
4.6.3 Software Detailed Design Baseline
4.6.4 Implementation Baseline
4.6.5 System Verification Baseline
4.6.6 Network Acceptance Baseline
4.7 Implementation Approach
4.8 Development and Migration Strategy
5. PROGRAM MANAGEMENT
5.1 Objective
5.2 Organisation
5.3 Work Break-down Structure (WBS)
5.4 Deliverable Items and Documents List
5.5 Schedule
6. SYSTEM ENGINEERING
6.1 Objective
6.2 Organisation
6.3 Work Break-down Structure (WBS)
6.4 Deliverable Items and Documents List
6.5 Schedule
7. HARDWARE DEVELOPMENT AND PRODUCTION
7.1 Development Approach
7.2 Organisation
7.3 Work Break-down Structure (WBS)
7.4 Block Diagrams and Deliverables
7.4.1 Toronto Node
7.4.2 Montreal Node
7.4.3 Winnipeg Node
7.4.4 Network Management Host
7.4.5 Electronic Mail Host
7.5 Schedule
8. SOFTWARE DEVELOPMENT
8.1 Software Development Approach
8.2 Organisation
8.3 Work Break-down Structure (WBS)
8.4 ACDN Software Documentation Tree
8.5 Schedule
9. INTEGRATION AND ACCEPTANCE TESTS
9.1 Objective
9.2 Organisation
9.3 Work Break-down Structure (WBS)
9.4 Deliverable Items and Documents List
9.5 Schedule
10. INTEGRATED LOGISTICS SUPPORT
10.1 Objective
10.2 Organisation
10.3 Work Break-down Structure (WBS)
10.4 Deliverable Items and Documents List
10.5 Schedule
11. APPLICABLE STANDARDS
1. I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
1.1 S̲C̲O̲P̲E̲
The purpose of this document is to define the overall
plan for the development of the Air Canada Data Network
(ACDN).
The plan addressses all tasks through definition, implementation
and delivery of hardware and software components to
integration of these components into identified subsystems.
Furthermore, is addresses installation, training and
subsequent system maintenance support.
The emphasis is on the following major activities,
which are managed by Christian Rovsing:
- Project Management
- System Engineering
- Hardware Development and Production
- Software Development
- Integration and Factory Acceptance Test
- Transportation
- Site Installation and Test
- Site Acceptance
- Network Acceptance
- Documentation
- Logistics Support
- System Maintenance
- Implementation and Migration Plans
1.2 A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
The below references are listed in reverse order
of precedense:
- CEP2026 Rev 1 Sealed Tender
- ACDN/PRO/0002 Air Canada Data Network proposal
1. ACDN/001/DCN0001 May 14, 1982
2. Telex 82539 May 27, 1982
3. ACDN/001/DCN/0002 May 29, 1982
4. ACDN/CLN/0001, Issue 01 May 29, 1982
5. Letter June 16, 1982 June 16, 1982
6-25. ACDN/CLN/0002-21, Issue 01 June 16, 1982
26. Telex 82401 June 22, 1982
27. ACDN/CLN/0024, Issue 01 July 2, 1982
28. Telex 82447 July 7, 1982
29. ACDN/CLN/0016, Issue 02
30. ACDN/CLN/0020, Issue 02
31. ACDN/CLN/0022, Issue 01
32. ACDN/CLN/0023, Issue 01
33. Telex 82449 July 8, 1982
34. Telex 82450 July 9, 1982
35. Telex 82464 July 20, 1982
36. Telex 82467 July 23, 1982
37. Letter July 23, 1982 July 23, 1982
38. Telex 82503 August 9, 1982
39. Letter Sep. 7, 1982 Sep. 7, 1982
40. CN No. 20, Issue 03 Revised Price
Quotation
41. CN No. 25, Issue 04 Milestone and
payment Plan
42. CN No. 26, Issue 01 Hardware Reconfiguration
43. CN No. 27, Issue 02 Maintenance Charges,
1983-85
44. CN No. 28, Issue 01 Exchange Rate
45. CN No. 29, Issue 011 Major Software
Milestones
1.3 A̲B̲B̲R̲E̲V̲I̲A̲T̲I̲O̲N̲S̲
ACDN Air Canada Data Network
ACNC Current Air Canada Collins Network Controller
CI Configuration Item
CPCI Computer Program Configuration Item
PIP Program Implementation Plan
PMS Protected Message Service
WBS Work Break-down Structure
2. O̲R̲G̲A̲N̲I̲S̲A̲T̲I̲O̲N̲
2.1 C̲H̲R̲I̲S̲T̲I̲A̲N̲ ̲R̲O̲V̲S̲I̲N̲G̲ ̲O̲R̲G̲A̲N̲I̲S̲A̲T̲I̲O̲N̲
2.2 T̲H̲E̲ ̲A̲C̲D̲N̲ ̲O̲R̲G̲A̲N̲I̲S̲A̲T̲I̲O̲N̲
2.2.1 P̲r̲o̲g̲r̲a̲m̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
2.2.2 S̲y̲s̲t̲e̲m̲ ̲E̲n̲g̲i̲n̲e̲e̲r̲i̲n̲g̲
2.2.3 H̲a̲r̲d̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲a̲n̲d̲ ̲P̲r̲o̲d̲u̲c̲t̲i̲o̲n̲
2.2.4 S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲
2.2.5 I̲n̲t̲e̲g̲r̲a̲t̲e̲d̲ ̲L̲o̲g̲i̲s̲t̲i̲c̲s̲ ̲S̲u̲p̲p̲o̲r̲t̲
2.2.6 Q̲A̲ ̲a̲n̲d̲ ̲C̲o̲n̲f̲i̲g̲u̲r̲a̲t̲i̲o̲n̲s̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲
2.2.7 G̲e̲n̲e̲r̲a̲l̲ ̲L̲i̲n̲e̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲R̲e̲s̲p̲o̲n̲s̲i̲b̲i̲l̲i̲t̲i̲e̲s̲
3. C̲H̲R̲I̲S̲T̲I̲A̲N̲ ̲R̲O̲V̲S̲I̲N̲G̲/̲A̲I̲R̲ ̲C̲A̲N̲A̲D̲A̲ ̲L̲I̲A̲I̲S̲O̲N̲
3.1 A̲U̲T̲H̲O̲R̲I̲T̲Y̲
3.2 R̲E̲P̲O̲R̲T̲I̲N̲G̲
3.3 A̲P̲P̲R̲O̲V̲A̲L̲ ̲A̲N̲D̲ ̲S̲U̲B̲B̲M̲I̲T̲T̲A̲L̲ ̲O̲F̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲A̲T̲I̲O̲N̲
3.4 P̲R̲O̲G̲R̲E̲S̲S̲ ̲R̲E̲P̲O̲R̲T̲S̲ ̲A̲N̲D̲ ̲M̲E̲E̲T̲I̲N̲G̲S̲
4. S̲U̲M̲M̲A̲R̲Y̲ ̲O̲F̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲A̲C̲T̲I̲V̲I̲T̲I̲E̲S̲
4.1 C̲O̲N̲T̲R̲A̲C̲T̲U̲A̲L̲ ̲M̲I̲L̲E̲S̲T̲O̲N̲E̲S̲
4.1.1 M̲i̲l̲e̲s̲t̲o̲n̲e̲s̲
Milestones month
---------------------------------------------------
program management
1 Down-payment
0
2 Program
Implementation
Plan
2
3 DEF Contract
3
equipment development and production
6 EMH,
Test
Environment,
FAT
6
7 EMH,
Spares
6
8 Hardware
Development 11
9 Toronto
Node,
FAT 10
10 Montreal
Node,
FAT 11
11 Winnipeg
Node,
FAT 13
12 Toronto
Node,
spares
+ consumeables 16
13 Depot,
Spares
and consumeables 17
14 Montreal
Node,
spares
and consum. 25
15 Winnipeg
Node,
spares
and consum. 29
system engineering
5 System
Requirement
Specification
5
16 System
Design
Specification 11
17 RMA Report 12
18 Test
Procedures 13
software development
19 BCS,
detail
design
7
20
unit
test 10
23 Prel
TAS/AC40x,
detail
design
8
24
unit
test 12
25 Prelim
INAS,
detailed
design
7
26
unit
test 11
27 Prelim
NCS,
detailed
design
8
28
unit
test 13
29 .............................VERSION
1 16
Milestones month
----------------------------------------------------
30 Prel. IBM VTAM/AC 40x, detail design 14
31 unit test 16
32 .............................VERSION 2 17
35 Prel. IBM VTAM/3270, detail design 15
36 unit test 19
.................................VERSION 3 19
21 NSS, detailed design 16
22 unit test 20
33 TAS, detail design 17
34 unit test 21
37 UNIVAC CMS, detail design 17
38 unit test 21
41 SCS, prelim design 17
42 unit test 21
43 NCS, prelim design 21
44 detail design 21
45 EMS, detail design 21
46 unit test 25
50 INAS, prelim design 17
51 detail design 21
47 .............................VERSION 4 25
39 UNIVAC VIA, detail design 19
40 unit test 24
48 ENAS, detail design 19
49 detail design 24
52 NMS, preliminary design 16
53 NMS, nmh/ncc 22
54 NMS, inventory control 22
55 NMS, statistical acquisition 22
56 NMS, network modelling 22
57 NCS, geo back-up, detail design 20
58 unit test 24
59 .............................VERSION 5 28
60 Volume Generator, prelim design 8
61 unit test 12
62 Message gen, detail design 11
63 unit test 14
Milestones month
----------------------------------------------------------
documentation
64 documentation plan 6
65 sys descrip manual 11
66 instal manual 15
67 operating manual 15
68 network operator manual 22
69 technical manuals 15
70 peripheral equip manual 15
71 programming and development tools 25
72 s/w description 25
training
73 training plan 2
74 maintenance course, prep 7
75 conduct 10
76 gen system course, prep 7
77 conduct 10
78 network course, prep 15
79 conduct 24
80 network oper course, prep 17
81 conduct 25
82 s/w course, prep 2
83 conduct 4
implementation
4 Site Survey Report 4
- EMH transportation and installation 6
84 Toronto Node, trans and installation 15
85 ..............SAT 15
86 Montreal Node, trans and installation 25
87 ..............SAT 26
88 Winnipeg Node, trans and installation 29
89 ..............SAT 30
90 Network Acceptance Test 34
91 Retension 34
4.1.2 S̲T̲A̲T̲E̲M̲E̲N̲T̲ ̲O̲F̲ ̲W̲O̲R̲K̲
This section contains a statement of work (SOW)
for each of the milestones identified in Section
4.1.1.
Each SOW shall contain as a minimum
- description
- schedule
- results
- dependencies
4.2 O̲V̲E̲R̲A̲L̲L̲ ̲W̲O̲R̲K̲ ̲B̲R̲E̲A̲K̲-̲D̲O̲W̲N̲ ̲S̲T̲R̲U̲C̲T̲U̲R̲E̲
This section presents the ACDN WBS in form summary
work break-down structures.
W̲B̲S̲ ̲ ̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1.0 Program Management
2.0 System Engineering
3.0 Equipment
4.0 Equipment Development
5.0 Standard Software
6.0 Software Development
7.0 Acceptance Tests
8.0 Documentation
9.0 Training
10.0 Transportation
11.0 Installation
12.0 Equipment Mtce
13.0 Software Mtce
The WBS consists of all work packages required to implement
a given task/program.
The WBS is defined by means of Work Package Description
(WPD). The WPDs are constructed by performing a preliminary
design of the system. However, the WPDs do not represent
a design, but is used by the management team as a planning
tool to obtain enough visibility in order to control
what to produce, resource allocation, schedule, and
cost.
WPDs can at any time be updated and will be updated
prior to turn over to a developer.
The WBS is constituted by Summary Work Packages, Work
Packages and Work Units.
Summary work packages shall satisfy the same requirements
as a work package. A summary work package will typically
be assigned a department/division.
Each work package (WP) shall satisfy the following:
- object or product oriented whereiever feasible,
or cover a destinit, clearly identifiable functional
task, e.g. project control, project administration
- qualify for assignment to one specific person (WP
manager), who will be responsible for its tecnical
content, schedule and cost
- clearly defined start and end.
The lowest level of the WBS-structure is the work unit.
Each work unit will satisfy the following:
- identify a specific task, which one person may
perform in a reasonable period
- clearly defined start and end.
4.3 M̲A̲S̲T̲E̲R̲ ̲S̲C̲H̲E̲D̲U̲L̲E̲
4.4 D̲E̲L̲I̲V̲E̲R̲A̲B̲L̲E̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲S̲
This section identifies the documents to be produced
as part of the AADN project.
For each document identified the following shall be
stated:
- short description
- schedule (due date)
- quantity
- dependencies
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲o̲c̲-̲i̲d̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
2.1.1 ACDN/SRS/0001 System Requirement Specification
2.2.1 ACDN/ICD/0001 Network Supervisor Procedures
and Generic Formats
2.2.2 ACDN/ICD/0002 User Producedures and Generic
Formats
2.2.3 ACDN/ICD/0003 ICC Access line Interface
2.2.4 ACDN/ICD/0004 ACNC Interface (gateway)
2.2.5 ACDN/ICD/0005 IBM VTAM SUpport
2.2.6 ACDN/ICD/0006 Univac CMS Support
2.2.7 ACDN/ICD/0007 Univac VIA Interface
2.2.8 ACDN/ICD/0008 SITA and ARINC Interface
2.2.9 ACDN/ICD/0009 CNT Interface
2.2.10 ACDN/ICD/0010 NMH Operator Procedures and
Generic Formats
2.2.11 ACDN/ICD/0011 EMH operator Procedures and
Generic Formats
2.2.12 ACDN/IDC/0012 Standard TAS
2.3.1 ACDN/SDS/0001 System Design Specfication
2.4.1 ACDN/TPR/0001 System Test Specs and Procedures
4.5 D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲A̲P̲P̲R̲O̲A̲C̲H̲
The implementation of the ACDN has three major objectives:
- based on top-down development and baseline management
provide an efficient overall technical control
of the ACDN development
- development to take place by means of an incremental
implementation where software is developed through
a number of builds
- migration from the existing ACNC network to the
new ACDN network aimed at meeting ACs objectives.
The baselines and development approach are further
described in the remainder of this section while section
4.7 describes the migration approach.
The following baselines have been established for the
ACDN program:
- system requirement specification
- system design
- preliminary (subsystem) design
- detailed design
- production (coding and unit test)
- system integration and test
- system acceptance
- network acceptance
At any time, during the ACDN program development cycle,
all previously established baselines together with
approved changes to the baselines, constitute the contractual
identification of the system.
To assure correctness and completeness of a baseline,
series of reviews/inspections are established, during
which the produced documents/components are evaluated.
A subsequent baseline will only be initiated when
the previous baseline has been approved.
The use of early validation and verification accomplished
via reviews, walk throughs, and inspections will furthermore
contribute to secure that the final product meets its
requirements. Furthermore, it provides management
with better tools to measure progress - and thus serves
to ensure proper attention to critical items providing
the most important tool for schedule control.
The development strategy adhered to by CR on the ACDN
program is that of incremental implementation.
This implies that the following activities take place
in distinct, sequential phases:
- system requirement specification,
- system design,
- preliminary (subsystem) design.
The Requirements Specification phase is a refinement
of the commitments presented by the proposal augmented
by the requirements of the Sealed Tender. The outcome
of this phase is a specification for ACDN network functional
and physical capabilities; a document which consists
of contractual commitments of exactly what is to be
provided presented in an unambiguous way; a document
which forms the baseline for the design and subsequent
validation processes; thus, an important aspect of
the document is to present commitments in a form which
is verifiable.
The System Design phase is a refinement and consolidation
of the design presented in the proposal. An important
part in this phase is that of establishing the exact
functions to be provided by a given package together
with the exact interfaces between packages. Once this
has been established and verified against the requirements,
the preliminary and detailed design can proceed leading
to the coding and testing phase implementing and final
verification the fulfillment of requirements.
Subsequent phases of the ACDN program are broken down
in a number of builds. The following activities take
place for each build:
- detailed design
- code
- unit test
- integration
- acceptance testing
The final Network Acceptance Test constitutes the last
phase of the ACDN development.
Builds serve as the vehicle for an ordered, manageable
software development.
Builds enable segmentation of a complex software development
into smaller, functionally oriented sections.
Thus, the build is a significant partial subset of
the system and consists of one or more software modules.
Generally, a software module implements one function.
An equal important aspect of a build is that it demonstrates
a significant, partial functional capability of the
system. It culminates in a demonstration of the full
system in form of the Network Acceptance Test, which
occurs as a neutral concluding step of integrating
the last build to the accumulation of previous builds.
4.6 S̲Y̲S̲T̲E̲M̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲B̲A̲S̲E̲L̲I̲N̲E̲S̲
The following sections describe the baselines applicable
at the system level.
At lower levels than the system level a number of baselines
are defined.
The hardware and software implementation will be divided
into a number of sub-phases where each completed subphase
will establish a baseline.
The system development cycle is presented in figure
4.6-1.
Whenever this section specifies CR internal reviews,
AC participation is assumed.
Figure 4.6-1
SYSTEM DEVELOPMENT CYCLE
4.6.1 S̲y̲s̲t̲e̲m̲ ̲R̲e̲q̲u̲i̲r̲e̲m̲e̲n̲t̲ ̲B̲a̲s̲e̲l̲i̲n̲e̲
The system requirement definition phase will be completed
by a System Requirements Review (SRR). The objective
of this review is to ensure the compliance and completeness
of the system requirements. After ACs approval of the
System Requirements Specification, and associated Interface
Control Documents, these will establish the baseline
for all subsequent development activities.
4.6.2 S̲y̲s̲t̲e̲m̲ ̲D̲e̲s̲i̲g̲n̲ ̲B̲a̲s̲e̲l̲i̲n̲e̲
During the system design phase, the system requirements
are broken down into subsystems and components of hardware
and software to ensure
a) that the system design specification represents
a complete and optional synthesis of the system
requirements
b) that the system is complete and feasible, and
c) that a technical direction is provided to the implementation
An internal Christian Rovsing A/S System Design Review
(SDR) will be scheduled.
After approval of the system design specification by
the ACDN program management, this will establish the
design requirement baseline.
4.6.3 P̲r̲e̲l̲i̲m̲i̲n̲a̲r̲y̲ ̲D̲e̲s̲i̲g̲n̲ ̲B̲a̲s̲e̲l̲i̲n̲e̲
The actual design of subsystems and hardware and software
components identified during the system design will
be divided into two phases; the preliminary phase,
and the detailed design phase
The preliminary design baseline (subsystem design)
is established prior to detailed design in order to
a) evaluate the progress and technical adequacy of
the selected design approach
b) determine its compatibility with the requirements,
and
c) establish the existence and compatibility of the
physical and functional interfaces between system
components (i.e. hardware, software, peripherals,
or facilities)
An internal Christian Rovsing A/S Preliminary Design
Review (PDR) will be conducted to ensure correctness
and adequacy of the preliminary design baseline.
4.6.4 D̲e̲t̲a̲i̲l̲e̲d̲ ̲D̲e̲s̲i̲g̲n̲ ̲B̲a̲s̲e̲l̲i̲n̲e̲
Before the actual implementation is initiated, a Detailed
Design Review (DDR) internal Christian Rovsing A/S
will be conducted to
a) determine that the detailed design satisfies the
design requirement baseline.
b) establish the exact interface relationship between
the system components
After approval the detailed design forms the baseline
for implementation of the actual hardware or software
components.
4.6.5 I̲m̲p̲l̲e̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲B̲a̲s̲e̲l̲i̲n̲e̲s̲
When the Hardware/Software components have been produced
these shall be tested and integrated into subsystems.
The baselines are established when the subsystems have
been approved by the CR A/S QA Department.
4.6.6 S̲y̲s̲t̲e̲m̲ ̲V̲e̲r̲i̲f̲i̲c̲a̲t̲i̲o̲n̲ ̲B̲a̲s̲e̲l̲i̲n̲e̲
At the time of completion of system integration and
verification, a System Verification Review is conducted
to verify that the system performes as required, and
that product specification, manuals, and handbooks
are accurate.
4.6.7 S̲y̲s̲t̲e̲m̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲B̲a̲s̲e̲l̲i̲n̲e̲s̲
The formal system acceptance phase has been separated
into a number of sub-phases each resulting in a baseline.
The Acceptance baselines are:
- DSMT System Test baseline
- In Plant Software Test baseline
- Factory (H/W) Acceptance baseline
- Software functional baseline
- Software operational baseline
- Site Provisional Acceptance baseline
For further details please refer to ACDN Acceptance
Test Plan
4.6.8 N̲e̲t̲w̲o̲r̲k̲ ̲A̲c̲c̲e̲p̲t̲a̲n̲c̲e̲ ̲B̲a̲s̲e̲l̲i̲n̲e̲
TBD
4.7 I̲M̲P̲L̲E̲M̲E̲N̲T̲A̲T̲I̲O̲N̲ ̲A̲P̲P̲R̲O̲A̲C̲H̲
This section will address the strategy to be applied
in order to assure that all requirements will be implemented
accordingly.
In order to assure that all requirements are identified
the ACDN system requirements identified in the ADCN
System Requirements Specification and associated ICDs
will be allocated to the pertinent hardware and software
subsystems. This is done during system design and will
be contained in a Verification Control Document.
To assure that the requirements are implemented in
the software subsystems/packages the requirements will
be allocated to each package/module in Unit Development
Folders (UDF). Refer to UDF Standard SD/STD/006.
The above requirement allocation will be verified during
the preliminary/detailed design reviews.All the unit/packages
test cases shall include testing of these requirements.During
system integration and verification the Verification
Control Document will be used to track the requirements
via the test procedures and results.
To assure that the requirements are implemented in
the hardware sybsystems/items the requirements will
be allocated to each subsystem/item in the Product
specifications or the Subsystem Specifications. The
detailed design review will verify that the requirements
are accounted for. The test cases developed for the
items and subsystems will test the allocated requirements.
During the system integration and verification the
VCD will be used to track the requirements.
4.8 D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲A̲N̲D̲ ̲M̲I̲G̲R̲A̲T̲I̲O̲N̲ ̲S̲T̲R̲A̲T̲E̲G̲Y̲
The development activities and the migration of AC
terminals and hosts, existing as new, to the new ACDN
data network will be parallel activities. Furthermore,
it is envisaged that some of the development activities
take place at AC in Canada.
A number of measures have been taken to meet these
targets:
- an initial development and test system is made
available at AC facilities, Toronto early 1984
- part of the network equipment is used by CR for
in-house development and test in Copenhagen
- software developed in builds aimed at satisfying
AC migration plans
- hardware reconfigured to meet development and test
needs; refurbishment to final configurations take
place at AC facilities, Canada.
4.8.1 S̲t̲a̲g̲e̲s̲
The equipment is seen as stable configurations through
a number of phases identified as stages.
a. C̲R̲ ̲C̲o̲p̲e̲n̲h̲a̲g̲e̲n̲
1. May-Jun 83 CR/stage 1
- NMH and Toronto Node
2. Jun-Aug 83 CR/stage 2
- NMH, Toronto Node and
Montreal Node
3. (Aug 83 - Sep 84) CR/stage 3
- NMH and Montreal Node
- Winnipeg Node configurated
as development system
4.( Sep - Dec 84) CR/stage 4
- NMH and Winnipeg Node
b. A̲C̲,̲ ̲T̲o̲r̲o̲n̲t̲o̲ ̲(̲Y̲Y̲Z̲)̲
1. (Feb - Oct 83) AC/stage 1
- Development and Test System
(EMH equipment)
2. (Oct 83 - Jan 84) AC/stage 2)
- Development and Test System
(EMH equipment Toronto
Node (GWY only)
3. (Jan - Sep 84) AC/stage 3
- Development and Test System
- Toronto Node (GWY ? FEP)
4. (Sep - Dec 84) AC/stage 4
- Toronto Node
- Montreal Node
- Electronic Mail Host
5. (Dec 84 -) AC/stage 5
- Toronto Node
- Montreal Node
- Winnipeg Node
- Network Management Host
- Electronic Mail Host
4.8.2 D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲A̲c̲t̲i̲v̲i̲t̲i̲e̲s̲
This section outlines the development activities of
each stage.
a. C̲R̲,̲ ̲C̲o̲p̲e̲n̲h̲a̲g̲e̲n̲
1,2. CR/stage 1 and 2
- initial development of software version
1 for
- gateway (GWY)
- front-end (FEP)
- monitoring and control with ICC-environment
capacity for some 6 simultaneous users
- test
3. C̲R̲/̲s̲t̲a̲g̲e̲ ̲3̲
- completion of version 01 (GWY)
- development of version 2 and 3 (FEP) capacity
some 20 simultaneous users
- development of version 4
- build 1 through TBD1
- initial development of version 5
- build TBD1 through TBD2
4. CR/stage 4
- completion of version 5
b. A̲C̲,̲ ̲T̲o̲r̲o̲n̲t̲o̲
1. AC/stage 1
- development of test utilities
capacities for some 6 simultaneous users
- parallel development on version 1
- control
- gateway
- test with ACNC
2. AC/stage 2
- integration with ACNC and ICC network
- control
- GWY
- integration of AC terminals (stabilization)
to new network
3. AC/stage 3
- integration with new OPNS/CGO host
- integration with new host terminals
- integration of AC terminals (cont'd)
- parallel development on version 4
4. AC/stage 4
- integration with RCCSH, Montreal
- integration with RCCS terminals, Montreal
- integration with ICC network, Montreal
- migration of AC terminals (cont'd)
- parallel development on version 5
5. AC/stage 5
- integration of ICC network, Winnipeg
- migration of AC terminals (cont'd)
- network acceptance test
4.8.2.1 V̲e̲r̲s̲i̲o̲n̲ ̲1̲:̲ ̲L̲i̲m̲i̲t̲e̲d̲ ̲G̲a̲t̲e̲w̲a̲y̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
This software version will provide access of AC 40x
type of devices connected to the new ACDN to following
resources of the existing ACNC:
- RES
- VIA
- Dorval
- PMS
Multi sign-on like the current ACNC sign-on will be
supported.
Furthermore, limited monitoring and control facilities
will be provided by this software version to support
an operating network. These facilities will allow configuration
changes to be made to enable migration of terminals
to the ACDN.
This software version is constitured of subsets of
the following packages:
- INAS
- NCS
- NSS, internal transport
- SCS, single NSP
- TAS, AC40x handling
4.8.2.2 V̲e̲r̲s̲i̲o̲n̲ ̲2̲:̲ ̲L̲i̲m̲i̲t̲e̲d̲ ̲I̲B̲M̲ ̲V̲T̲A̲M̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
This software version will add access of AC 40x type
of terminals access to an IBM VTAM host to the capabilities
of Version 1. The terminals may be connected to either
the new ACDN or the existing ACNC.
This software version is constituted of subsets of
the following software elements:
- HAS I, IBM VTAM
- SCS, multiple NSPs
- TAS, AC 40x to IBM emulation
4.8.2.3 V̲e̲r̲s̲i̲o̲n̲ ̲3̲:̲ ̲L̲i̲m̲i̲t̲e̲d̲ ̲I̲B̲M̲ ̲3̲2̲7̲0̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
This software version will add access of IBM 3270 type
of terminals access to one IBM VTAM host to the capabilities
of Version 2.
This software version is constituted of a subset of
the software elements:
- HAS I, IBM VTAM
- TAS, IBM 3270 terminal support
A single node is supported.
4.8.2.4 V̲e̲r̲s̲i̲o̲n̲ ̲4̲:̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲a̲n̲d̲ ̲P̲r̲o̲t̲e̲c̲t̲e̲d̲ ̲M̲e̲s̲s̲a̲g̲e̲ ̲S̲e̲r̲v̲i̲c̲e̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
This major software version completes four major ACDN
capabilities.
- transport network between multiple nodes
- network control capabilities
- protected message service (PMS)
- full gateway capability to ACNC
This software version constitutes the completion of
the following packages or elements:
- multiple Hosts at each node
HAS I, IBM VTAM
- HAS II, Univac CMS
- TAS, AC 40x to any host
- NCS, exclusive geographical back-up
- SCS
- INAS
- NSS
- EMS
4.8.2.5 V̲e̲r̲s̲i̲o̲n̲ ̲5̲:̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲,̲ ̲E̲x̲t̲e̲r̲n̲a̲l̲ ̲N̲e̲t̲w̲o̲r̲k̲ ̲A̲c̲c̲e̲s̲s̲
̲a̲n̲d̲ ̲V̲I̲A̲ ̲H̲o̲s̲t̲ ̲A̲c̲c̲e̲s̲s̲ ̲C̲a̲p̲a̲b̲i̲l̲i̲t̲y̲
This major software version represents completion of
the ACDN capabilities, specifically the following:
- Network Management
- Geographically backed up Network Control
- Access to VIA host
- Access to external networks, e.g.
o SITA,
o ARINC,
o CNT
- Virtual Terminal Capability
5. P̲R̲O̲G̲R̲A̲M̲ ̲M̲A̲N̲A̲G̲E̲M̲E̲N̲T̲
5.1 O̲b̲j̲e̲c̲t̲i̲v̲e̲
5.2 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
5.3 W̲o̲r̲k̲ ̲B̲r̲e̲a̲k̲-̲d̲o̲w̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲W̲B̲S̲)̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1.1 Project Implementation Plan
5.4 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲ ̲I̲t̲e̲m̲s̲ ̲a̲n̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲ ̲L̲i̲s̲t̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲o̲c̲-̲i̲d̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
1.1 ACDN/PIP/0001 ACDN Program Implementation
Plan
5.5 S̲c̲h̲e̲d̲u̲l̲e̲
6. S̲Y̲S̲T̲E̲M̲ ̲E̲N̲G̲I̲N̲E̲E̲R̲I̲N̲G̲
6.1 O̲b̲j̲e̲c̲t̲i̲v̲e̲
6.2 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
6.3 W̲o̲r̲k̲ ̲B̲r̲e̲a̲k̲-̲d̲o̲w̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲W̲B̲S̲)̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
2.0 System Engineering
2.1 Requirements Definition
2.1.1 System Requirements Specification
2.2 Interface Control
2.2.1 Network Supervisor Procedures and Generic Formats
2.2.2 User Procedures and Generic Formats
2.2.3 ICC Access Line Interface
2.2.4 ACNC (gateway) Interface
2.2.5 IBM VTAM Support
2.2.6 Univac CMS Support
2.2.7 Univac VIA Interface
2.2.8 SITA and ARINC Interface
2.2.9 CNT Interface
2.2.10 NMH Operator Procedures and Generic Formats
2.2.11 EMH Operator Procedures and Generic Formats
2.2.12 Standard TAS
2.3 System Design
2.3.1 Network Control Software Spec.
2.3.2 System Control Software Spec.
2.3.3 Basic Comm. Service Spec.
2.3.4 Nodal Switch Software Spec.
2.3.5 Terminal Access Software Spec.
2.3.6 Host Access Software Spec.
2.3.7 Internal Network Access Software Spec.
2.3.8 External Network Access Software Spec.
2.3.9 Network Management Software Spec.
2.3.10 Electronic Mail SOftware Spec.
2.3.11 Test Software Spec.
2.3.12 ACDN Data Description Document
2.4 System Integration and Test
2.4.1 Acceptance Test Specification and Procedures
6.4 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲ ̲I̲t̲e̲m̲s̲ ̲a̲n̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲ ̲L̲i̲s̲t̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲o̲c̲-̲i̲d̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
2.1.1 ACDN/SRS/0001 System Requirement Specification
2.2.1 ACDN/ICD/0001 Network Supervisor Procedures
and Generic Formats
2.2.2 ACDN/ICD/0002 User Procedures and Generic
Formats
2.2.3 ACDN/ICD/0003 ICC Access line Interface
2.2.4 ACDN/ICD/0004 ACNC Interface (gateway)
2.2.5 ACDN/ICD/0005 IBM VTAM Support
2.2.6 ACDN/ICD/0006 Univac CMS Support
2.2.7 ACDN/ICD/0007 Univac VIA Interface
2.2.8 ACDN/ICD/0008 SITA and ARINC Interface
2.2.9 ACDN/ICD/0009 CNT Interface
2.2.10 ACDN/ICD/0010 NMH Operator Procedures and
Generic Formats
2.2.11 ACDN/ICD/0011 EMH Operator Procedures and
Generic Formats
2.2.12 ACDN/ICD/0012 Standard TAS
2.3.1 ACDN/SDS/0001 System Design Specification
2.4.1 ACDN/TPR/0001 System Test Specs and Procedures
6.5 S̲c̲h̲e̲d̲u̲l̲e̲
7. H̲A̲R̲D̲W̲A̲R̲E̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲ ̲A̲N̲D̲ ̲P̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
7.1 D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲A̲p̲p̲r̲o̲a̲c̲h̲
7.2 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
7.3 W̲o̲r̲k̲ ̲B̲r̲e̲a̲k̲-̲d̲o̲w̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲W̲B̲S̲)̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
3.0 Equipment
3.1 Development System
3.2 Network Nodes
3.2.1 Toronto Node
3.2.2 Montreal Node
3.2.3 Winnipeg Node
3.3 Network Control Centres
3.4 Network Management Host
3.5 Electronic Mail Host
4.0 Equipment development
7.4 B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲s̲ ̲a̲n̲d̲ ̲D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲s̲
7.4.1 T̲o̲r̲o̲n̲t̲o̲ ̲N̲o̲d̲e̲ (incl. NCC)
7.4.1.1 B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
7.4.1.2 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲s̲
o Watchdog Subsystem
- Watchdog with associated operator's position
(CRT and matrix printer)
- Crate Control Adaptors in each Unit of Toronto
Node
o System Control Subsystem (SCPs)
- 2 Processor Units, each with
o 2 CPUs
o 768 Kwords of memory
o System Control CU Subsystem (SCUs)
- 2 80 Mbytes MMD with 2 Mbytes fixed head disks
and associated CR80 modules (2 32K disk controllers
and 2 associated adaptors)
(NCC) - 4 Colour Graphical Terminals and associated
CR80 termination modules
(NCC) - 1 TI810 150 cps matrix printer and associated
CR80 termination module
- Channel Units, etc. as required to connect
above
o Nodal Switch PU Subsystem (NSPs)
- 3 Processor Units, each with
o 4 CPUs
o 512 Kwords of memory
o Nodal Switch CU Subsystem (NCUs)
CR80 device controller and adaptors required to
connect:
- 2 host channels (IBM or Univac)
- 5 56 Kbps internodal trunks
- 69 2.4 Kbps ICC access lines
- 5 9.6 Kbps ACNC access lines
- 2 2.4 Kbps ARINC lines
- 1 2.4 Kbps ICC type to SITA
- 2 150 bps CNT (AES weather)
- 3 150 bps CNT (Airline switching)
- 2 250 bps CPAIR/BA
- 4 low speed connections
o S-net Subsystem
- 2 suprabusses and associated CR80 modules
- 2 suprabus connection to EMH complex
o Rack, cables, fans, etc. required by above CR80
units and modules.
7.4.2 M̲o̲n̲t̲r̲e̲a̲l̲ ̲N̲o̲d̲e̲ (incl. NCC)
7.4.2.1 B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
7.4.2.2 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲s̲
o Watchdog Subsystem
- Watchdog with associated operator's position
(CRT and matrix printer)
- Crate Control Adaptors in each Unit of Toronto
Node
o System Control Subsystem (SCPs)
- 2 Processor Units, each with
o 2 CPUs
o 768 Kwords of memory
o System Control CU Subsystem (SCUs)
- 2 80 Mbytes MMD with 2 Mbytes fixed head disks
and associated CR80 modules (2 32K disk controllers
and 2 associated adaptors)
(NCC) - 4 Colour Graphical Terminals and associated
CR80 termination modules
(NCC) - 1 TI810 150 cps matrix printer and associated
CR80 termination module
- Channel Units, etc. as required to connect
above
o Nodal Switch PU Subsystem (NSPs)
- 3 Processor Units, each with
o 4 CPUs
o 512 Kwords of memory
o Nodal Switch CU Subsystem (NCUs)
CR80 device controller and adaptors required to
connect:
- 2 host channels (IBM or Univac)
- 5 56 Kbps internodal trunks
- 81 2.4 Kbps ICC access lines
- 17 9.6 Kbps IBM access lines
- 16 4.8 Kbps IBM access lines
o S-net Subsystem
- 2 suprabusses and associated CR80 modules
o Rack, cables, fans, etc. required by above CR80
units and modules.
7.4.3 W̲i̲n̲n̲i̲p̲e̲g̲ ̲N̲o̲d̲e̲
7.4.3.1 B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
7.4.3.2 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲s̲
o Watchdog Subsystem
- Watchdog with associated operator's position
(CRT and matrix printer)
- Crate Control Adaptors in each Unit of Toronto
Node
o System Control Subsystem (SCPs)
- 2 Processor Units, each with
o 2 CPUs
o 768 Kwords of memory
o System Control CU Subsystem (SCUs)
- 2 80 Mbytes MMD with 2 Mbytes fixed head disks
and associated CR80 modules (2 32K disk controllers
and 2 associated adaptors)
o Nodal Switch PU Subsystem (NSPs)
- 4 Processor Units, each with
o 4 CPUs
o 512 Kwords of memory
o Nodal Switch CU Subsystem (NCUs)
CR80 device controller and adaptors required to
connect:
- 2 host channels (IBM or Univac)
- 6 56 Kbps internodal trunks
- 58 2.4 Kbps ICC access lines
- 4 9.6 Kbps IBM access lines
- 4 4.8 Kbps IBM access lines
o S-net Subsystem
- 2 suprabusses and associated CR80 modules
o Rack, cables, fans, etc. required by above CR80
units and modules.
7.4.4 N̲e̲t̲w̲o̲r̲k̲ ̲M̲a̲n̲a̲g̲e̲m̲e̲n̲t̲ ̲H̲o̲s̲t̲ ̲S̲y̲s̲t̲e̲m̲
7.4.4.1 B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
7.4.4.2 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲s̲
o Watchdog Subsystem
- Crate Control Adaptors in each Unit of NMH
System
o Processor Unit Subsystem (NMP)
- 1 PU with
o 2 CPUs
o 768 Kwords of memory
o Channel Unit Subsystem (NCUs)
- 2 80Mbytes MMD with 2 Mbytes fixed head disks
and associated CR80 modules (2 32K disk controllers
and 2 associated adaptors)
- 1 300 Mbytes SMD disk and associated CR80 modules
(1 32K disk controller and associated adaptor)
- 2 FT9000 Tape deck and deck and associated
CR80 modules
- 3 Infoton VDUs and associated CR80 termination
modules
- 1 high speed printer (600 lpm) and associated
CR80 termination module
- Channel Units as required to connect above
o S-net Subsystem
- 2 suprabusses and associated CR80 modules
o Rack, cables, fans, etc. required by aove CR80
units and modules.
7.4.5 E̲l̲e̲c̲t̲r̲o̲n̲i̲c̲ ̲M̲a̲i̲l̲ ̲H̲o̲s̲t̲ ̲S̲y̲s̲t̲e̲m̲
7.4.5.1 B̲l̲o̲c̲k̲ ̲D̲i̲a̲g̲r̲a̲m̲
7.4.5.2 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲s̲
o Watchdog Subsystem
- Watchdog with associated operator's position
(CRT and matrix printer)
- Crate Control Adaptors in each Unit of the
EMH
o Processor Unit Subsystem (EMPs)
- 2 Processor Units, each with
o 2 CPUs
o 512 Kwords of memory
o Channel Unit Subsystem (ECUs)
- 2 80 Mbytes MMD with 2 Mbytes fixed head disks
and associated CR80 modules (2 32K disk controllers
and 2 associated adaptors)
- 2 300 Mbytes SMD disks and associated CR80
modules (2 32K disk controllers and 2 associated
adaptors)
- 1 FT9000 Tape Deck and associated CR80 modules
- 4 Infoton VDUs and associated CR80 termination
modules
- 1 TI810 150 cps matric printer and associated
CR80 termination module
- Channel units as required to connect above
o S-net Subsystem
- 2 Suprabusses and associated CR80 modules
o Rack, cables, fans etc. required by above CR80
units and modules
7.5 S̲c̲h̲e̲d̲u̲l̲e̲
8. S̲O̲F̲T̲W̲A̲R̲E̲ ̲D̲E̲V̲E̲L̲O̲P̲M̲E̲N̲T̲
8.1 S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲e̲v̲e̲l̲o̲p̲m̲e̲n̲t̲ ̲A̲p̲p̲r̲o̲a̲c̲h̲
8.2 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
8.3 W̲o̲r̲k̲ ̲B̲r̲e̲a̲k̲-̲d̲o̲w̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲W̲B̲S̲)̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
5.0 Standard Software
5.1 Toronto Node
5.2 EMH
5.3 NMH
5.4 Montreal Node
5.5 Winnipeg Node
6.0 Software Development
6.1 Network Control Software
6.2 System Control Software
6.3 Basic Communication Service
6.4 Nodal Switch Software
6.5 Terminal Access Software
6.6 Host Access Software
6.6.1 HAS I/IBM VTAM
6.6.2 HAS II, Univac CMS
6.6.3 HAS III, Univac VIA
6.7 Internal Network Access Software
6.8 External Network Access Software
6.9 Network Management Software
6.10 Electronic Mail Software
6.11 Test Software
8.4 A̲C̲D̲N̲ ̲S̲o̲f̲t̲w̲a̲r̲e̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲a̲t̲i̲o̲n̲ ̲T̲r̲e̲e̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲o̲c̲-̲i̲d̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲
8.5 S̲c̲h̲e̲d̲u̲l̲e̲
9. I̲N̲T̲E̲G̲R̲A̲T̲I̲O̲N̲ ̲A̲N̲D̲ ̲A̲C̲C̲E̲P̲T̲A̲N̲C̲E̲ ̲T̲E̲S̲T̲S̲
9.1 O̲b̲j̲e̲c̲t̲i̲v̲e̲
9.2 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
9.3 W̲o̲r̲k̲ ̲B̲r̲e̲a̲k̲-̲d̲o̲w̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲W̲B̲S̲)̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
7.0 Integration and Acceptance Tests
7.1 Factory Acceptance Tests (FAT)
7.1.1 EMH, Development System
7.1.2 Toronto Node
7.1.3 Montreal Node
7.1.4 Winnipeg Node
7.2 Site Acceptance Tests (SAT)
7.2.1 EMH, Developmnet System
7.2.2 Toronto Node
7.2.3 Montreal Node
7.2.4 Winnipeg Node
7.3 Software Builds Acceptance Tests
7.3.1 Build I
7.3.2 Build II
7.3.3 Build III
7.3.4 Build IV
7.3.5 Build V
7.4 Network Acceptance Test
9.4 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲ ̲I̲t̲e̲m̲s̲ ̲a̲n̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲ ̲L̲i̲s̲t̲
9.5 S̲c̲h̲e̲d̲u̲l̲e̲
10. I̲N̲T̲E̲G̲R̲A̲T̲E̲D̲ ̲L̲O̲G̲I̲S̲T̲I̲C̲S̲ ̲S̲U̲P̲P̲O̲R̲T̲
10.1 O̲b̲j̲e̲c̲t̲i̲v̲e̲
10.2 O̲r̲g̲a̲n̲i̲s̲a̲t̲i̲o̲n̲
10.3 W̲o̲r̲k̲ ̲B̲r̲e̲a̲k̲-̲d̲o̲w̲n̲ ̲S̲t̲r̲u̲c̲t̲u̲r̲e̲ ̲(̲W̲B̲S̲)̲
W̲P̲-̲i̲d̲ ̲ ̲ ̲D̲e̲s̲c̲r̲i̲p̲t̲i̲o̲n̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲
8.0 Documentation
9.0 Training
10.0 Transportation
11.0 Installation
12.0 Equipment Mtce
13.0 Software Mtce
10.4 D̲e̲l̲i̲v̲e̲r̲a̲b̲l̲e̲ ̲I̲t̲e̲m̲s̲ ̲a̲n̲d̲ ̲D̲o̲c̲u̲m̲e̲n̲t̲s̲ ̲L̲i̲s̲t̲
10.5 S̲c̲h̲e̲d̲u̲l̲e̲
11. A̲P̲P̲L̲I̲C̲A̲B̲L̲E̲ ̲S̲T̲A̲N̲D̲A̲R̲D̲S̲
