top - download
⟦c8c94ad28⟧ Wang Wps File
Length: 5723 (0x165b)
Types: Wang Wps File
Notes: APPENDIX A TIL UDF STD.
Names: »0330A «
Derivation
└─⟦89b9efcb1⟧ Bits:30006072 8" Wang WCS floppy, CR 0029A
└─ ⟦this⟧ »0330A «
WangText
…02…SD/STD/006
…02…SVO/801119…02……02…A-#
UDF STANDARD
…02……02…CAMPS
A̲P̲P̲E̲N̲D̲I̲X̲ ̲A̲
A.1 G̲E̲N̲E̲R̲A̲L̲
Section I of the UDF "control info" shall contain a
collection of formal information about the Unit and
the progress of the development.
This information must be kept in a clear an easy accessible
way and it is therefore recommended that the formsheets
enclosed herein are used for entering this information.
The following contains guidelines for filling in the
forms.
A.2 U̲N̲I̲T̲ ̲I̲D̲E̲N̲T̲I̲F̲I̲C̲A̲T̲I̲O̲N̲
In order to establish the identity of the unit, its
place in the system, and the responsibility for the
unit, fill in this form as follows:
a) enter both the short acronym and the full name
of the unit
b), c), and d)
enter the dates of the start, scheduled completion
and actual completion respectively
e) and f)
describe the units place in the system hiararchy
by entering the name of the next higher unit which
this is part of, and the names of the units which
the design has identified as subunits to this unit
h), i), and j)
It is assumed that there will always be one person
responsible for the development of a unit. Enter
the name of that person in column j) and the dates
of his appointment and the termination of responsibility
in columns h) and i) respectively.
A.3 S̲C̲H̲E̲D̲U̲L̲E̲
The development must always be scheduled firmly for
a period of at least 6 weeks ahead. Enter the activities
as follows:
a) enter the unit name
b) enter no. of sheets if more than one present
c) enter revision number of present schedule
d) enter date of latest revision
e) enter the week numbers for the schedule period
f) enter the Work Package identificaiion number
g) give a brief description of the Work Package
h) and i)
with a vertical bar mark the period in which the
work is planned and actually performed, respectively
i) state or reference any additional information.
A.4 M̲I̲L̲E̲S̲T̲O̲N̲E̲ ̲T̲R̲A̲C̲K̲I̲N̲G̲ ̲L̲I̲S̲T̲
Keep track of all officially defined milestones on
this form.
a) enter the identificaion number of the milestone
b) In larger projects scheduling and associated milestone
identification will be done in several levels.
Enter the level number in this column.
c) give a brief description of the milestone or its
official title (if available).
d), e), and f)
enter the dates of the scheduled completion, expected
completion, and actual completion respectively.
Expected completion date may change during the
development if delays are encountered or if work
is completed faster than scheduled.
A.5 U̲D̲F̲ ̲V̲O̲L̲U̲M̲E̲S̲ ̲L̲I̲S̲T̲
If a UDF consists of several volumes one shall be considered
the main volume and contain the control info. The rest
of the volumes shall be described on this form.
a) enter the identification number of the volume
b) describe on which medium the volume exists e.g.
source file, document, listing, card deck.
c) give a brief description of the volume
d) and e)
enter the issue and change numbers of the volume
if applicable. Those columns will mostly be used
if officially issued documents are used as part
of a UDF.
A.6 R̲E̲L̲A̲T̲E̲D̲ ̲U̲N̲I̲T̲S̲ ̲L̲I̲S̲T̲
This form shall be used to track the relations between
current unit and any other units within the system
which is dependent on this unit or on which this unit
is dependent.
a) enter the name of the related unit
b) state the relative level of the unit within the
system hiararchy e.g. "parent", "child" "same level".
c) give a brief description of the relation (a reference
to an interface description may be included).
d) enter the initials of the person to be contacted
in questions about the relation between units.
A.7 R̲E̲F̲E̲R̲E̲N̲C̲E̲D̲ ̲D̲O̲C̲U̲M̲E̲N̲T̲ ̲L̲I̲S̲T̲
All documents referenced during the development shall
be tracked on this form.
a) enter the doucment identification no.
b) enter the title of the document.
c) state the relation of the document to the current
unit e.g. "requirement", "applicable doc", "reference",
"ICD".
d) and f)
enter the issue and change number of the document
f) enter the issue date of the document
A.8 A̲C̲T̲I̲O̲N̲S̲/̲P̲R̲O̲B̲L̲E̲M̲S̲ ̲T̲R̲A̲C̲K̲I̲N̲G̲ ̲L̲I̲S̲T̲
Keep track of all officially assigned actions and problems
on this form.
a) enter the type: "A" for action, "P" for problem.
b) enter the identification number of the action/problem
c) enter the initials of the person assigned the responsibility
for the action/problem
d) enter the scheduled completion date for the action
or the expected date for a solution of the problem.
e) enter the date the action was completed or a solution
to the problem was available
f) enter a reference to the document et. al. by which
the action/problem was closed.
g) enter a reference to a document (if applicable)
which is directly affected by an action/problem.
h) give any additional information available
A.9 W̲O̲R̲K̲ ̲S̲T̲A̲T̲U̲S̲ ̲L̲I̲S̲T̲
This Form is Optional. It is meant as a help for the
developer to keep track of the individual work items
he may identify as necessary:
a) enter an identification number for the work item
b) give a brief description of the item
c), d), and e)
enter the dates the work must be completed to meet
schedule, the expected completion date, and the
actual completion date.
f) enter the initial of a person who must be notified
when work is completed (if applicable).
