Hatena::Groupprogram

桜、抹茶、白、日記(支店)

2010-05-02

[] MANAGING THE DEVELOPMENT OF LARGE SOFTWARE SYSTEMS(4/11) はてなブックマーク -  MANAGING THE DEVELOPMENT OF LARGE SOFTWARE SYSTEMS(4/11) - 桜、抹茶、白、日記(支店)

Dr. Winston W. Royceさんが1970年に発表した論文「MANAGING THE DEVELOPMENT OF LARGE SOFTWARE SYSTEMS」の原文そのまま。紙スキャンなPDFしか見当たらないので半手動OCR

PDFの4ページ目。

STEP 1: PROGRAM DESIGN COMES FIRST

The first step towards a fix is illustrated in Figure 5.

A preliminary program design phase has been inserted between the software requirements generation phase and the analysis phase.

This procedure can be criticized on the basis that the program designer is forced to design in the relative vacuum of initial software requirements without any existing analysis.

As a result, his preliminary design may be substantially in error as compared to his design if he were to wait until the analysis was complete.

This criticism is correct but it misses the point.

By this technique the program designer assures that the software will not fail because of storage, timing, and data flux reasons.

As the analysis proceeds in the succeeding phase the program designer must impose on the analyst the storage, timing, and operational constraints in such a way that he senses the consequences.

When he justifiably requires more of this kind of resource in order to implement his equations it must be simultaneously snatched from his analyst compatriots.

In this way all the analysts and all the program designers will contribute to a meaningful design process which will culminate in the proper allocation of execution time and storage resources.

If the total resources to be applied are insufficient or if the embryo operational design is wrong it will be recognized at this earlier stage and the iteration with requirements and preliminary design can be redone before final design, coding and test commences.


How is this procedure implemented? The following steps are required.

  1. Begin the design process with program designers, not analysts or programmers.
  2. Design, define and allocate the data processing modes even at the risk of being wrong. Allocate processing, functions, design the data base, define data base processing, allocate execution time, define interfaces and processing modes with the operating system, describe input and output processing, and define preliminary operating procedures.
  3. Write an overview document that is understandable, informative and current. Each and every worker must have an elemental understanding of the system. At least one person must have a deep understanding of the system which comes partially from having had to write an overview document.

Figure 5. Step 1 : Insure that a preliminary program design is complete before analysis begins.