A Rational Design Process: How and Why to Fake It

IEEE Transactions on Software Engineering

Volumn SE-12, Issue 2, 1986, Pages 251-257

  Parnas, David Lorge ^a   Clements, Paul C ^a  

^a NAVAL RESEARCH LABORATORY   (United States)

Author keywords

Programming methods; software design; software documentation; software engineering

Indexed keywords

COMPUTER SYSTEMS PROGRAMMING - DOCUMENTATION;

MODULE INTERFACES; MODULE STRUCTURES;

COMPUTER SOFTWARE;

EID: 0022667615     PISSN: 00985589     EISSN: None     Source Type: Journal    
DOI: 10.1109/TSE.1986.6312940     Document Type: Article

References (17)

1. D. L. Parnas, D. M. Weiss, P. C. Clements, and K. H. Britton, “Interface specifications for the SCR (A-7E) extended computer module,” NRL Memor. Rep. 5502, Dec. 31, 1984 (major revisions to NRL Rep. 4843).
2. K. H. Britton, R. A. Parker, and D. L. Parnas, “A procedure for designing abstract interfaces for device-interface modules,” in Proc. 5th Int. Conf. Software Eng., 1981.
3. K. H. Britton and D. L. Parnas, “A-7E software module guide,” NRL Memo. Rep. 4702, Dec. 1981.
4. F. P. Brooks, Jr., The Mythical Man-Month: Essays on Software Engineering. Reading, MA: Addison-Wesley, 1975.
5. P. Clements, A. Parker, D. L. Parnas, J. Shore, and K. Britton, “A standard organization for specifying abstract interfaces,” NRL Rep. 8815, June 14, 1984.
6. P. Clements, D. Parnas, and D. Weiss, “Enhancing reusability with information hiding,” in Proc. Workshop Reusability in Program., Sept. 1983, pp. 240–247.
7. H. S. Elovitz, “An experiment in software engineering: The architecture research facility as a case study,” in Proc. 4th Int. Conf. Software Eng., Sept. 1979.
8. K. L. Heninger, “Specifying software requirements for complex systems: New techniques and their application,” IEEE Trans. Software Eng., vol. SE-6, pp. 2–13, Jan. 1980.
9. K. Heninger, J. Kallander, D. L Parnas, and J. Shore, “Software requirements for the A-7E aircraft”, NRL Memo. Rep. 3876, Nov. 27, 1978.
10. R. C. Linger, H. D. Mills, B. I. Witt, Structure Programming: Theory and Practice. Reading, MA: Addison-Wesley, 1979.
11. A. Parker, K. Heninger, D. Parnas, and J. Shore, “Abstract interface specifications for the A-7E device interface module,” NRL Memo. Rep. 4385, Nov. 20, 1980.
12. D. L. Parnas, “On the design and development of program families,” IEEE Trans. Software Eng., vol. SE-2, Mar. 1976.
13. D. L. Parnas, “Designing software for ease of extension and contraction,” in Proc. 3rd Int. Conf. Software Eng., May 10–12, 1978, pp. 264–277.
14. D. L. Parnas, “A generalized control structure and its formal definition,” Commun. ACM, vol. 26, no. 8, pp. 572–581, Aug. 1983.
15. D. L. Parnas, P. Clements and D. Weiss, “The modular structure of complex systems,” in Proc. 7th Int. Conf. Software Eng., Mar. 1984, pp. 408–417.
16. S. Faulk, B. Labaw, and D. Parnas, “SCR module implementation document guidelines,” NRL Tech. Memor. 7590-072:SF:BL:DP, Apr. 1, 1983.
17. D. L. Parnas and D. M. Weiss, “Active design reviews: Principles and practices,” in Proc. 8th Int. Conf. Software Eng., London, Aug. 1985.