The psychology of computer programming
The psychology of computer programming
The mythical man-month (anniversary ed.)
The mythical man-month (anniversary ed.)
Exploratory experimental studies comparing online and offline programming performance
Communications of the ACM
Letters to the editor: go to statement considered harmful
Communications of the ACM
Flow diagrams, turing machines and languages with only two formation rules
Communications of the ACM
Techniques of Program Structure and Design
Techniques of Program Structure and Design
Structured Analysis
A Simplified Guide to Structured COBOL Programming
A Simplified Guide to Structured COBOL Programming
Systematic Programming: An Introduction
Systematic Programming: An Introduction
Learning to Program in Structured COBOL
Learning to Program in Structured COBOL
Flowchart techniques for structured programming
ACM SIGPLAN Notices
Principles of Program Design
Reliable software through composite design
Reliable software through composite design
Structured programming
PDL: a tool for software design
AFIPS '75 Proceedings of the May 19-22, 1975, national computer conference and exposition
| Hi-index | 0.00 |
Data processing managers have a number of new "structured" methodologies to assist them in EDP software projects: structured programming, structured design, HIPO, top-down development, structured analysis, structured walkthroughs, and chief programmer teams. Since many of these methodologies are still considered new and "experimental", it is often difficult for the manager to determine which of the methodologies should be used on a software project. This paper briefly reviews each of the new structured methodologies. It then makes suggestions about the use of the methodologies for new projects, concluding that the use of informal walkthroughs is probably the best way for the manager to introduce the methodologies into an organization that has no previous experience with them. The point is also made that "research-and-development" projects have different trade-offs than "bread-and-butter" projects. For projects that have hard deadlines and budgets, a number of trade-offs are suggested in order to help the manager decide which of the structured methodologies should be employed.