Advertisement

e&i Elektrotechnik und Informationstechnik

, Volume 121, Issue 2, pp 43–47 | Cite as

Introducing object-oriented requirements engineering for automation systems

  • H. Kaindl
Originalarbeiten
  • 91 Downloads

Abstract

This article raises the question, if and how object-oriented requirements engineering can be applicable and useful for specifying automation systems. In order to ease the judgment of applicability, it introduces this author’s approach to object-oriented requirements engineering in the form of a mini-tutorial. Another such approach dedicated to specifying real-time industrial automation systems is sketched as well, and a combination of ideas appears feasible.

Keywords

requirements engineering systems engineering software engineering automation system 

Einführung in objektorientiertes Requirements Engineering im Hinblick auf die Spezifikation von Automationssystemen

Zusammenfassung

Dieser Artikel stellt die Frage, ob bzw. wie objektorientiertes Requirements Engineering für das Spezifizieren von Automationssystemen anwendbar und nützlich sein kann. Um die Beantwortung zu erleichtern, führt er in den Ansatz dieses Autors für objektorientiertes Requirements Engineering ein. Ein anderer solcher Ansatz speziell für das Spezifizieren von industriellen Automationssystemen mit Realzeit-Anforderungen wird ebenfalls skizziert. Eine Kombination der Ideen erscheint möglich.

Schlüsselwörter

Requirements Engineering Systems Engineering Software Engineering Automationssystem 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. Becker, L. B., Pereira, C. E. (2002): SIMOO-RT — An object-oriented framework for the development of real-time industrial automation systems. IEEE Trans. on Robotics and Automation 18(4): 421–430.CrossRefGoogle Scholar
  2. Davis, A. M. (1993): Software requirements: objects, functions, and states. Englewood Cliffs, NJ: Prentice Hall.MATHGoogle Scholar
  3. Ebner, G., Kaindl, H. (2002): Tracing all around in reengineering. IEEE Software, May/June 2002: 70–77.Google Scholar
  4. INCOSE (2000): Systems Engineering Handbook, Vers. 2.0. International Council on Systems Engineering, Seattle, WA, July 2000.Google Scholar
  5. Jacobson, I., Booch, G., Rumbaugh, J. (1999): The unified software development process. Reading, MA: Addison-Wesley.Google Scholar
  6. Kaffenberger, R. (2003): Will object-oriented systems-engineering reshape requirements engineering? In: Proc. of the 13th Annual Int. Symp. of the Int. Council on Systems Engineering, Arlington, VA, June/July 2003 INCOSE: 583–595.Google Scholar
  7. Kaindl, H. (1997): A practical approach to combining requirements definition and object-oriented analysis. Annals of Software Engineering 3: 319–343.CrossRefGoogle Scholar
  8. Kaindl, H. (1999): Difficulties in the transition from O-O analysis to design. IEEE Software: 94–102.Google Scholar
  9. Kaindl, H. (2001a): A design process based on a model combining scenarios with goals and functions. IEEE Trans. on Systems, Man, and Cybernetics (SMC), Part A 30(5): 537–551.CrossRefGoogle Scholar
  10. Kaindl, H. (2001b): Using hypermedia in requirements engineering practice. The New Review of Hypermedia and Multimedia 7: 185–205.CrossRefGoogle Scholar
  11. Kaindl, H., Brinkkemper, S., Bubenko, J. A., Jr. Farbey, B., Greenspan, S. J., Heitmeyer, C. L., Leite, J. C. S. do P., Mead, N. R., Mylopoulos, J., Siddiqi, J. (2002): Requirements engineering and technology transfer: obstacles, incentives and improvement agenda. Requirements Eng. 7(3): 113–123.CrossRefGoogle Scholar
  12. Kaindl, H., Carroll, J. M. (1999): Introduction: symbolic modeling in practice. Communications of the ACM. 42(1): 28–30.CrossRefGoogle Scholar
  13. Kaindl, H., Kramer, S., Kacsich, R. (1998): A case study of decomposing functional requirements. In: Proc. 3rd Int. Conf. on Requirements Engineering (ICRE ’98), Colorado Springs, CO, April 1998. IEEE: 156–163.Google Scholar
  14. Loucopoulos, P., Karakostas, V. (1995): System Requirements Engineering: London: McGraw-Hill.Google Scholar
  15. Mannion, M., Keepence, B., Kaindl, H., Wheadon, J. (1999): Reusing single system requirements from application family requirements: In: Proc. 21st Int. Conf. on Software Engineering (ICSE-99), Los Angeles, CA, May 1999. ACM: 453–462.Google Scholar
  16. Mannion, M., Lewis, O., Kaindl, H., Montroni, G., Wheadon, J. (2002): Representing requirements on generic software in an application family model. In: Proc. 6th Int. Conf. on Software Reuse (ICSR-6), Vienna, June 2000. Berlin: Springer: 153–169.Google Scholar
  17. Nuseibeh, B., Easterbrook, S. (2000): Requirements engineering: a roadmap. In: Future of Software Engineering, special volume of Proc. 22nd Int. Conf. on Software Engineering (ICSE-2000), Limerick, Ireland, June 2000. ACM.Google Scholar
  18. Oliver, D. W. (1997): Engineering of complex systems with models. IEEE Trans. on Aerospace and Electronic Systems 33(2): 667–685.CrossRefGoogle Scholar

Copyright information

© Springer 2004

Authors and Affiliations

  1. 1.Institute of Computer TechnologyVienna University of TechnologyVienna

Personalised recommendations