Documentation Appropriate to Each Phase

A translation of Royce70 Diagram 6 into list format.

Questions are interspersed that are raised by the translation and not answered by the existing text (the text the diagram supplements).

**System Requirements**: None (?)

**Software Requirements:** A single document.

**Preliminary Program Design**: The *Preliminary Design (Spec)*. Is this produced at the end of the phase? (Which we'll see later involves a prototype?) Or is it the spec *for* the prototype?

**Analysis**: None (? I think this is a mistake. Given Royce's description of this phase, its output *must* be a document.)

**Program Design**: First produces an *Interface Design (Spec)* that divides the program into components and describes their interfaces. Then, for each component, there is a *Final Design (Spec)* that describes its "innards". Also produces a *Test Plan (Spec)*.

**Coding**: In the process of coding, the "Final Design" is updated to form the *Final Design (As Built)*.

**Testing**: Makes use of (what? The test plan, yes, but also the Final Design, I think.) This will produce changes to the *Final Design (As Built). (But not the *Test Plan*? Hmm.) Test results will also be appended to the *Test Plan (Spec)*. (Maybe? Or is it a separate document?)

**Operations**: Associated with the *Operating Instructions*. The arrow implies that the *Operating Instructions* come out of Operations the way the *Interface Design* comes out of the Program Design phase, but that can't be right. Surely at least version 1 is produced before the product is put into operation?