Rapid prototyping is a promising approach for formulating accurate software requirements, particularly for complex systems with hard real-time constraints. Computer aid is needed for realizing the potential benefits of this approach in practice, because the problems associated with software evolution are greatly amplified in the context of iterative prototyping and exploratory design. This paper presents our newest models of software evolution products and processes, and explains the models and engineering automation capabilities they support via examples.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Badr, S.: Luqi: Automation Support for Concurrent Software Engineering. In: Proc. of the 6th International Conference Software Engineering and Knowledge Engineering, Jurmala, Latvia, June 20-23, pp. 46–53 (1994)Google Scholar
  2. 2.
    Bauer, F., et al.: The Munich Project CIP. LNCS, vol. 292. Springer, Heidelberg (1987)zbMATHGoogle Scholar
  3. 3.
    Berzins, V.: On Merging Software Enhancements. Acta Informatica 23(6), 607–619 (1986)zbMATHCrossRefMathSciNetGoogle Scholar
  4. 4.
    Berzins, V.: Luqi: An Introduction to the Specification Language Spec. IEEE Software 7(2), 74–84 (1990)CrossRefGoogle Scholar
  5. 5.
    Berzins, V.: Luqi: Software Engineering with Abstractions: An Integrated Approach to Software Development using Ada. Addison-Wesley Publishing Company, Reading (1991) ISBN 0-201-08004-4Google Scholar
  6. 6.
    Berzins, V.: Software Merge: Models and Methods. Journal of Systems Integration 1(2), 121–141 (1991)CrossRefGoogle Scholar
  7. 7.
    Berzins, V., Shing, M.: Luqi: Real-Time Scheduling for a Prototyping Language. Journal of Systems Integration 6(1-2), 41–72 (1996)CrossRefGoogle Scholar
  8. 8.
    Berzins, V., Ibrahim, O.: Luqi: A Requirements Evolution Model for Computer Aided Prototyping. In: Proceedings of the 9th International Conference on Software Engineering and Knowledge Engineering, Madrid, Spain, June 17-20, pp. 38–47 (1997)Google Scholar
  9. 9.
    Dampier, D., Berzins, V.: Luqi: Automated Merging of Software Prototypes. Journal of Systems Integration 4(1), 33–49 (1994)CrossRefGoogle Scholar
  10. 10.
    Berzins, V.: Software Merge: Semantics of Combining Changes to Programs. ACM TOPLAS 16(6), 1875–1903 (1994)CrossRefGoogle Scholar
  11. 11.
    Berzins, V.: Software Merging and Slicing. IEEE Computer Society Press Tutorial, Los Alamitos (1995) ISBN 0-8186-6792-3Google Scholar
  12. 12.
    Berzins, V., Dampier, D.: Software Merge: Combining Changes to Decompositions. Journal of Systems Integration, special issue on CAPS 6(1-2), 135–150 (1996)Google Scholar
  13. 13.
    Dowson, M.: The ARIANE 5 Software Failure. ACM Software Engineering Notes 22(2), 84 (1997)CrossRefGoogle Scholar
  14. 14.
    Evans, J.: Software Project Scheduling Tool, MS Thesis, Computer Science, Naval Postgraduate School (September 1997)Google Scholar
  15. 15.
    Feather, M.: A System for Assisting Program Change. ACM Transactions on Programming Languages and Systems 4(1), 1–20 (1982)zbMATHCrossRefGoogle Scholar
  16. 16.
    Feather, M.: A Survey and Classification of some Program Change Approaches and Techniques. In: Meertens, L.G.L.T. (ed.) Program Specification and Change (Proceedings of the IFIP TC2/WG 2.1 Working Conference), pp. 165–195. North-Holland, Amsterdam (1987)Google Scholar
  17. 17.
    Feather, M.: Constructing Specifications by Combining Parallel Elaborations. IEEE Transactions on Software Engineering 15(2), 198–208 (1989)CrossRefGoogle Scholar
  18. 18.
    Fickas, S.: Automating the Transformational Development of Software. IEEE Transactions on Software Engineering 11(11), 1268–1277 (1985)CrossRefGoogle Scholar
  19. 19.
    Gibbs, W.: Software’s Chronic Crisis. Scientific American, 86–94 (September 1994)Google Scholar
  20. 20.
    Johnson, W., Feather, M.: Building an Evolution Change Library. In: 12th International Conference on Software Engineering, pp. 238–248 (1990)Google Scholar
  21. 21.
    Kant, E.: On the Efficient Synthesis of Efficient Programs. Artificial Intelligence 20(3), 253–36 (1983); Also appears in [35], 157-183Google Scholar
  22. 22.
    Kraemer, B., Berzins, V.: Luqi: Compositional Semantics of a Real-Time Prototyping Language. IEEE Transactions on Software Engineering 19(5), 453–477 (1993)CrossRefGoogle Scholar
  23. 23.
    Lange, D.: Hypermedia Analysis and Navigation of Domains, MS Thesis, Computer Science, Naval Postgraduate School (Setember 1997)Google Scholar
  24. 24.
    Ketabchi, M.: Luqi: A Computer Aided Prototyping System. IEEE Software 5(2), 66–72 (1988)CrossRefGoogle Scholar
  25. 25.
    Berzins, V., Yeh, R.: Luqi: A Prototyping Language for Real-Time Software. IEEE Transactions on Software Engineering 14(10), 1409–1423 (1988)CrossRefGoogle Scholar
  26. 26.
    Luqi: Handling Timing Constraints in Rapid Prototyping. In: Proceedings of the 22nd Annual Hawaii International Conference on System Sciences, pp. 417–424. IEEE Computer Society, Los Alamitos (1989)Google Scholar
  27. 27.
    Luqi: Software Evolution via Rapid Prototyping. IEEE Computer 22(5), 13–25 (1989)Google Scholar
  28. 28.
    Luqi: A Graph Model for Software Evolution. IEEE Transactions on Software Engineering 16(8), 917–927 (1990)CrossRefGoogle Scholar
  29. 29.
    Luqi: Computer-Aided Prototyping for a Command-and-Control System Using CAPS. IEEE Software 9(1), 56–67 (1992)CrossRefGoogle Scholar
  30. 30.
    Luqi: Real-Time Constraints in a Rapid Prototyping Language. Journal of Computer Languages 18(2), 77–103 (1993)CrossRefGoogle Scholar
  31. 31.
    Luqi: Specifications in Software Prototyping. In: Proc. SEKE 1996, Lake Tahoe, NV, June 10-12, pp. 189–197 (1996)Google Scholar
  32. 32.
    Luqi: Scheduling Real-Time Software Prototypes. In: Proceedings of the 2nd International Symposium on Operations Research and its Applications, Guilin, China, December 11-13, pp. 614–623 (1996)Google Scholar
  33. 33.
    Luqi, Goguen, J.: Formal Methods: Promises and Problems. IEEE Software 14(1), 73–85 (1997)CrossRefGoogle Scholar
  34. 34.
    Lutz, R.: Analyzing Software Requirements: Errors in Safety-Critical Embedded Systems, TR 92-27, Iowa State University (August 1992)Google Scholar
  35. 35.
    Rich, C., Waters, R. (eds.): Readings in Artificial Intelligence and Software Engineering. Morgan Kaufmann, San Francisco (1986)Google Scholar
  36. 36.
    Rusin, D., Scanlon, M.: Luqi: SIDS Wireless Acoustic Monitor (SWAM). In: Proc. 21st Int. Conf. on Lung Sounds, Chester, England, September 4-6. International Lung Sounds Association (1996)Google Scholar
  37. 37.
    Smith, D., Kotik, G., Westfold, S.: Research on Knowledge-Based Software Environments at Kestrel Institute. IEEE Transactions on Software Engineering 11(11), 1278–1295 (1985)CrossRefGoogle Scholar
  38. 38.
    Chaos, Technical Report, The Standish Group, Dennis, MA (1995),
  39. 39.
    Swartout, W., Balzer, R.: On the Inevitable intertwining of Specification and implementation. Communication of the ACM 25(7), 438–440 (1982); Also appears in Gehani, N., McGettrick, A.D. (eds.): Software Specification techniques, pp. 41–45 (1986)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1998

Authors and Affiliations

  • Luqi
    • 1
  1. 1.Computer Science DepartmentNaval Postgraduate SchoolMontereyUSA

Personalised recommendations