The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.02 - Feb. (1986 vol.12)
pp: 251-257
Paul C. Clements , Computer Science and Systems Branch, Naval Research Laboratory, Washington, DC 20375
ABSTRACT
Many have sought a software design process that allows a program to be derived systematically from a precise statement of requirements. This paper proposes that, although we will not succeed in designing a real product in that way, we can produce documentation that makes it appear that the software was designed by such a process. We first describe the ideal process, and the documentation that it requires. We then 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. We describe the contents of each of the required documents.
INDEX TERMS
Documentation, Software design, Computers, Maintenance engineering, Mathematical model, Data structures, software engineering, Programming methods, software design, software documentation
CITATION
Paul C. Clements, "A rational design process: How and why to fake it", IEEE Transactions on Software Engineering, vol.12, no. 2, pp. 251-257, Feb. 1986, doi:10.1109/TSE.1986.6312940
31 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool