A rational design process: How and why to fake it

Many have sought a software design process that allows a program to be derived systematically from a precise statement of requirements. It is proposed that, although designing a real product in that way will not be successful, it is possible to produce documentation that makes it appear that the sof...

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on software engineering 1986-02, Vol.SE-12 (2), p.251-257
Main Authors: Parnas, D. L., Clements, P. C.
Format: Article
Language:English
Subjects:
Applied sciences
Computer programming
Computer science
control theory
systems
Computers
Data structures
Design
Documentation
Engineering
Exact sciences and technology
Maintenance engineering
Mathematical model
Methods
Programming methods
Software
Software design
software documentation
Software engineering
Citations: Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Many have sought a software design process that allows a program to be derived systematically from a precise statement of requirements. It is proposed that, although designing a real product in that way will not be successful, it is possible to produce documentation that makes it appear that the software was designed by such a process. The ideal process and the documentation that it requires are described. The authors explain why one should attempt to design according to the ideal process and why one should produce the documentation that would have been produced by that process. The contents of each of the required documents are outlined.
ISSN:0098-5589
1939-3520
DOI:10.1109/TSE.1986.6312940