top - download
⟦3985e6929⟧ Wang Wps File
Length: 7844 (0x1ea4)
Types: Wang Wps File
Notes: PC/AUX/001
Names: »2467A «
Derivation
└─⟦62d458081⟧ Bits:30006246 8" Wang WCS floppy, CR 0154A
└─ ⟦this⟧ »2467A «
└─⟦9fe574faa⟧ Bits:30006242 8" Wang WCS floppy, CR 0334A
└─ ⟦this⟧ »2467A «
WangText
…02…PC/AUX/001
PROTOCOL CONVERTER…02…SN[/820714…02……02…#
SOFTWARE DESIGN - REVIEW PLAN
…02……02…PC
T̲A̲B̲L̲E̲ ̲O̲F̲ ̲C̲O̲N̲T̲E̲N̲T̲S̲
1 INTRODUCTION ................................
4
2 ACTIVITIES/SCHEDULES ........................
5
3 RESPONSIBILITIES ............................
6
4 DISCREPANCY NOTES (DNs) AND THEIR PROCESSING
8
4.1 DISCREPANCY NOTES DESCRIPTION .............
8
4.2 ACCOUNTABILITY OF DNs ..................... 10
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 Design Review (DR).
This plan presents the plans for Design Review activities
related to review of the PC System Specification..
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 purpose of the DR is to determine the adequacy
of the basic design approach and to ensure that the
requirements defined in PC System Requirements Specification
(Appendix G of Protocol Converter Contract SHNMO-82-9205-INF)
are fulfilled.
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 DR.
Mandatory reviewers in review team are:
- 1 SHAPE representative
- 1 participant from QAD
- 1 participant from PC System Engineering.
A̲c̲t̲i̲v̲i̲t̲i̲e̲s̲
1) book captain submits the document subject to review
to SHAPE.
2) book captain collects DNs from reviewers.
3) book captain coordinate DNs (i.e. provide answers,
state his position).
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.
S̲c̲h̲e̲d̲u̲l̲e̲
D̲a̲t̲e̲
Delivery of Document
PC Syustem Specification
(PC/SDS/001) 14 July,1982
CR collect of DN's from
reviewers (DN contents sent
by telex) 26 July, 1982
Review meeting at CR, Ballerup 29-30 July,
1982
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 DR.
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 PC 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 PC 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. DN's shall be categorized and
marked accordingly into the below three categories.
a) Discrepancies (Requires a document update, which
is not only an editorial.)
b) Clarifications (Requires no update.)
c) Editorials
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.
PC 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 D̲esign R̲eview (DR)
a DN record shall be maintained for the document being
reviewed.
The DR DN record shall be kept up to date reflecting
the status of all DNs.
Overleaf is presented a DR 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.
DN's shall be grouped into the three categories specified
in section 4.1. The category to which a DN belongs,
shall be marked in the "Title" column by
D, Discrepancy
E, Editorial
C, Clarification
DN RECORD
