A Software Development Environment Emphasizing Rapid Prototyping

  • David A. Nelson
Conference paper


A prototyping-oriented Software Development Environment (SDE) is described which is integrated, interactive and knowledge-based. It incorporates a model of software development which is based on the concepts of entities, processes, events and their relationships. In addition, a novel software product life-cycle is introduced which explicitly supports rapid prototyping. This SDE actively supports all stages of the software development process. The user services model for this SDE is based on the strategy of iterative refinement.

This SDE exploits the following technologies to achieve its capabilities:
  1. a)

    an object-oriented, interactive, user interface,

  2. b)

    an active, object dictionary/directory,

  3. c)

    a knowledge base specific to software prototyping,

  4. d)

    databases for representing software descriptions,

  5. e)

    a variety of software description transformation facilities,

  6. f)

    configuration management.



Software Development Rapid Prototype Configuration Management Iterative Refinement Software Development Environment 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Bibliography and References

  1. Bersoff, E. H. (et. al.): Software Configuration Management, Englewood Cliffs: Prentice-Hall 1980.Google Scholar
  2. Blum, B. I.: The Life Cvcle-A Debate Over Alternative Models. ACM, Software Engrg. Notes. 7(4), 18–27 (October 1982).CrossRefGoogle Scholar
  3. Boehm, B. W.: Software Engineering Economics. Englewood Cliffs: Prentice-Hall 1981.MATHGoogle Scholar
  4. Chen, P. P.-S.: The Entity Relationship Model: Toward A Unified View Of Data. ACM Trans. Database Sys. 1(1). 9–36 (March 1976).CrossRefGoogle Scholar
  5. Davis, A. M.: Rapid Prototyping Using Executable Reguireroents Specifications. ACM, Software Engrg. Notes. 7(5), 39–44 (December 1982).CrossRefGoogle Scholar
  6. Fischer, G., and H.-D. Becker: The Nature of Design Processes and how Computer Systems can support them. Proc. Eur. Conf. Interactive Computing Systems, Stresa 3 September 1982, 43–58 (1982).Google Scholar
  7. Floyd, C: A Process-Oriented Approach to Software Development. Proc. ICS’81, London March 1981, 285–294 (1981).Google Scholar
  8. Gilb, T.: Evolutionary Development. ACM, Software Engrg. Notes. 6(2). 17–17 (April 1981).CrossRefGoogle Scholar
  9. Howden, W. E.: Contemporary Software Development Environments. Comm. ACM. 25(5). 318–329 (May 1982).CrossRefGoogle Scholar
  10. Kant, E., and D. R. Barstow: The Refinement Paradigm: The Interaction of Coding and Efficiency Knowledge in Program Synthesis. IEEE Trans. Softw. Engrg. SE-7(5). 458–471 (September 1981).CrossRefGoogle Scholar
  11. Keus, H. E.: Prototyping: A More Reasonable Approach to System Development. ACM, Software Engrg. Notes. 7(5). 94–95 (December 1982).CrossRefGoogle Scholar
  12. Kilov, H.: An Approach to the User Interface and Semantic Integrity for a Relational DBMS. ACM, SIGMOD Record. 13(2). 64–71 (January 1983).MathSciNetCrossRefGoogle Scholar
  13. Kowalski, R. A.:Logic for Problem Solving. Amsterdam: North-Holland 1979.MATHGoogle Scholar
  14. McCracken, D. D., and M. A. Jackson: Life Cycle Concept Considered Harmful. ACM, Software Engrg. Notes. 7(2). 29–32 (April 1982).CrossRefGoogle Scholar
  15. Nau, D. S.: Expert Computer Systems. IEEE, Computer. 16(2), 63–85 (February 1983).CrossRefGoogle Scholar
  16. Nelson, D. A.: A Virtual Machine Approach to Object-Oriented Architecture. in: Stoyan, H., and H. Wedekind (EDS.) Objektorientierte Software-und Hardwarearchitekturen. Stuttgart: B. G. Teubner 1983.Google Scholar
  17. Nelsson, D. A.: For all x (x is a Programming Language Feature 3 x is Considered Harmful). (In preparation).Google Scholar
  18. Newman, P. S.: Towards an Integrated Development Environment. IBM Sys. J. 21(1). 81–107 (1982).CrossRefGoogle Scholar
  19. Pagan, F. G.: A Diagrammatic Notation for Abstract Syntax and Abstract Structured Objects. IEEE Trans. Softw. Engrg. SE-9(3), 280–289 (May 1983).CrossRefGoogle Scholar
  20. Parnas, D. L,: Designing Software for Ease of Extension and Contraction. IEEE Trans. Softw. Engrg. SE-5(2), 128–137 (March 1979).CrossRefGoogle Scholar
  21. Robinson, K. A.: An Entity/Event Data Modeling Method. BCS, Computer J. 22(3), 270–281 (August 1979).CrossRefGoogle Scholar
  22. ROLLAND, C.: Database Dynamics. ACM, SIGBDP DATABASE, 14(3), 32–42 (Spring 1983).CrossRefGoogle Scholar
  23. Rutkowski, C.: An Introduction to the Human Applications Standard Computer Interface, Part 1: Theory and Principles. Byte. 7(11). 291–310 (October 1982).Google Scholar
  24. Squires, S. L. (ed.): Working Papers from the ACM SIGSOFT Rapid Prototyping Workshop. ACM, Softw. Engrg. Notes. 7(5). 1–185 (December 1982).Google Scholar
  25. Stavely, A.M.: Models as Executable Designs. ACM, Softw. Engrg. Notes. 7(5). 167–168 (December 1982).CrossRefGoogle Scholar
  26. Thihbleby, H.: “What You See is What You Have Got”-a user engineering principle for manipulative display? in: Balzert, H. (ED.) Software-Ergonomie. Stuttgart: B. G. Teubner 1983.Google Scholar
  27. UTIDOC/CF (Anon.): UTIDOC: A Software Development and Project Management System. Concepts and Facilities Manual. Munich: SICL0S-EUR0S0FT GmbH February 1982.Google Scholar
  28. Zahran, F. S.: A Universal Data Model Holder for Data Dictionary Systems. BCS, Computer J. 24(3), 193–199 (August 1981).MathSciNetCrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1984

Authors and Affiliations

  • David A. Nelson
    • 1
  1. 1.Garmisch-PartenkirchenF.R. Germany

Personalised recommendations