top - download
⟦12d22d237⟧ Wang Wps File
Length: 10677 (0x29b5)
Types: Wang Wps File
Notes: SW Preliminary Design
Names: »1009A «
Derivation
└─⟦ecb9329a3⟧ Bits:30006006 8" Wang WCS floppy, CR 0041A
└─ ⟦this⟧ »1009A «
WangText
…02…CPS/AUX/013
…02…KNN/810617…02……02…#
SOFTWARE PRELIMINARY DESIGN - REVIEW PLAN
…02…810601…02…CAMPS
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 INTRODUCTION ................................
4
2 ACTIVITIES/SCHEDULES ........................
6
3 RESPONSIBILITIES ............................
9
4 DISCREPANCY NOTES (DNs) AND THEIR PROCESSING 11
4.1 DISCREPANCY NOTES DESCRIPTION ............. 11
4.2 ACCOUNTABILITY OF DNs ..................... 13
1̲ ̲ ̲I̲N̲T̲R̲O̲D̲U̲C̲T̲I̲O̲N̲
The purpose of this plan is to establish specific procedures
to be followed during the Preliminary Design Review
(PDR).
A general standard for design reviews can be found
in ED/SPC/0001.
This plan presents the plans for Preliminary Design
Review activities related to review of the CAMPS Application
Software Packages, Data Base Design Document, and Software
Interface Control Document.
This plan has been prepared according to AQAP 13, para.
207, January 81.
Chapter 2 contains a schedule for review related activities
and an activity description.
Chapter 3 defines the responsibilities of the review
participants.
Chapter 4 describes the Discrepancy Notes DNs and how
these are going to be generated and accounted for.
The success of the PDR is closely related to the degree
thoroughness by which each participant has prepared
himself to the review he has been assigned to.
The purpose of the PDR is to determine the adequacy
of the basic design approach.
The reviewers should assure that:
- the software packages functional flow, summarize
flow of information for the complete software package
and identifies/defines subpackages, their relationship
within the software package, and with the software
package external interfaces.
- the software package contains a computer storage
allocation. The intent of this part is to ensure
the compability between packages and available
computer storage.
- the requirements defined in the CAMPS System Requirements
Specification CPS/210/SYS/0001 and associated Interface
Control Documents CPS/ICD/001 - CPS/ICD/008 are
fulfilled.
- the structure and organization of Data Base is
defined. This is a description of the structural
layout and the allocation of storage requirements
of the data base, identifying the types and characteristics
of data.
- the Interface Requirements are defined. Although
these were identified in the SW package specification
and approved, it is important that they be reviewed
again at this time. Interface requirements include
such things as definitions of word length, message
formats, available computer storage, and timing
considerations.
- the ECP Status is reflected. Review the configuration
management accounting records to determine which
approved ECPs should be reflected in the design
presented at PDR and to ensure that they are included.
2̲ ̲ ̲A̲C̲T̲I̲V̲I̲T̲I̲E̲S̲/̲S̲C̲H̲E̲D̲U̲L̲E̲S̲
This chapter defines the overall activities and schedules
for the PDR.
Detailed information such as review participants, meeting
rooms, detailed agenda will be contained in separate
"Invitation for Review."
A maximum of 8 persons will be invited to each review.
The PDR will consist of series of reviews. One review
will be scheduled for each design package. The packages
are listed below.
CAMPS System Functions CPS/SDS/002
Message Management CPS/SDS/003
System Status and Control CPS/SDS/004
Table Management CPS/SDS/005
Input/Output Control CPS/SDS/006
Storage and Retrieval CPS/SDS/007
Statistics CPS/SDS/008
Logging CPS/SDS/009
Traffic Handling CPS/SDS/010
Message Distribution Package CPS/SDS/011
Terminal Package CPS/SDS/012
Data Base Design Document CPS/DBD/001
CAMPS Software Interface Control Document CPS/ICD/009
For each of the packages the following activities shall
take place:
1) book captain submits design package to reviewers,
possibly with a kick-off presentation.
2) book captain collects DNs from reviewers.
3) book captain coordinate DNs (i.e. provide answers,
state his position and by the DN (refer chapter
4))
4a) review team makes a walk-through of the DNs and
the document.
4b) review team makes decisions as how to update the
document and approves/disapproves the document.
5a) book captain updates document.
5b) actionees close open actions generated during review.
6) document is proofread to ensure all decisions have
been implemented.
REVIEW SCHEDULE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
DOCUMENT DOC. TO DNs FROM UPDATE
REVIEWERS REVIEWERS REVIEW DOCUMENT
DUE DATE DUE DATE DATE DUE
DATE
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
CAMPS System Functions 19/6 25/6
29/6
10/8
Message Management 1/7 6/7
7/7
10/8
System Status and Control 30/6 3/7
9/7
1/8
Table Management 26/6 1/7
3/7
10/8
Input/Output Control 26/6 30/6
1/7
5/8
Storage and Retrieval 3/7 11/7
14/7
1/8
Statistics 7/7 14/7
20/7
1/8
Logging 9/7 16/7
22/7
5/8
Traffic Handling 16/6 22/6
24/6
1/8
Message Distribution 30/6 7/7
11/7
1/8
Terminal Package 8/7 14/7
16/7
10/8
Data Base Design Doc. 11/7 17/7
23/7
5/8
CAMPS SWICD 11/7 17/7
24/7
5/8
3̲ ̲ ̲R̲E̲S̲P̲O̲N̲S̲I̲B̲I̲L̲I̲T̲I̲E̲S̲
This section will describe the responsibilities in
relation to the PDR.
Responsibilities will be described for the following
review personnel.
- reviewers
- book captains
- review chairman
- review secretary
- project review board
for each of the phases:
- prereview
- review
- post review
A reviewer is a person who is reviewing the design
and produce DNs against the design.
The book captain is the person who has produced the
design document.
The review chairman is responsible for organizing and
conducting the reviews.
The review secretary assists the review chairman in
producing minutes of meeting and keeps accountability
of all DNs generated against the review package.
The project review board consists of the CAMPS management
team, which in case of non-consensus between review
team members has the final authority to resolve problems.
The responsibilites of the above categories are defined
overleaf.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
REVIEW PRIOR TO DURING AFTER
PHASE REVIEW REVIEW REVIEW
REVIEW
PERSON
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1) Generate DNs 1)
Evaluate
book
Reviewers and forward
captains
to book capt.
response.
2)
Generate
DNs
ad
hoc
as None
required.
3)
Participate
in
review
decision
team
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1) Collect DNs 1)
Update
accor-
Book from reviewers
ding
to
DNs
Captain 2) Log DNs (refer Refer
to
(review
team)
section 4.2) review 2)
Solve
action
3) Produce ans- secretary
items.
wers to DNs
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
1)
Update
log
Review
of
DNs
(re-
Secretary None
fer
section Refer
to
4.2). book
captain
2)
Produce
mi-
nutes
of
meeting.
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Project 1)
Make
de- 1)
Approve
Review None
cision
on
re-
updates
Board
view
issues
coming
from
review
team
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲ ̲
Figure 3-1
4 D̲I̲S̲C̲R̲E̲P̲A̲N̲C̲Y̲ ̲N̲O̲T̲E̲S̲ ̲(̲D̲N̲s̲)̲ ̲A̲N̲D̲ ̲T̲H̲E̲I̲R̲ ̲P̲R̲O̲C̲E̲S̲S̲I̲N̲G̲
This chapter describes procedures for generating a
discrepancy note and how to establish accounting control
of the DNs.
4.1 D̲I̲S̲C̲R̲E̲P̲A̲N̲C̲Y̲ ̲N̲O̲T̲E̲S̲ ̲D̲E̲S̲C̲R̲I̲P̲T̲I̲O̲N̲
Overleaf is presented a CAMPS Discrepancy Note (DN).
During review preparation the reviewers fill out the
following fields on the DN page.
- Reviewers Name
- Document Title
- Paragraph and Page No. (of findings)
- Findings
- Recommended Action (related to finding)
Findings are the only of the above fields which will
be discussed further.
Considering the attributes outlined in chapter 1, the
reviewer might/will find portions of the specifications
which does not satisfy these attributes. In such case
DNs shall be generated.
Comments shall not be limited to generality, but address
specific areas.
To make life easier for the reviewer to write a DN,
it is acceptable to attach a copy of the page/section
from the specification with corrections to the DN.
CAMPS DISCREPANCY NOTE
4.2 A̲C̲C̲O̲U̲N̲T̲A̲B̲I̲L̲I̲T̲Y̲ ̲O̲F̲ ̲D̲N̲s̲
In order to ensure accountability of the DNs being
generated and processed during the P̲reliminary D̲esign
R̲eview (PDR) a DN record shall be maintained for each
document being reviewed.
The PDR DN record shall be kept up to date reflecting
the status of all DNs.
Overleaf is presented a PDR DN record.
Column 1-3 are self explanatory, therefore only column
4-13 will be described in the following.
In column 4-6 it shall be indicated which disposition
the DN coordinator has taken (accepted, accepted with
modification or rejected).
In column 7-9 it shall be indicated which disposition
the review has taken (accepted, rejected or action
item (further study)).
In column 10-13 all action items indicated in column
9 shall be logged by actionee, due date, action number,
and completion date.
