Skip to main content

Performance and Robustness Engineering and the Role of Automated Software Development

  • Chapter
  • First Online:
Performance Engineering (WOSP 2000, GWPESD 2000)

Abstract

Performance engineering aims to demonstrate that the software being developed will meet the performance needs. The goal of robustness engineering is to prove that the system will work correctly in the presence or after occurence of faults or stress conditions. From this point of view robustness engineering complements performance engineering to cover the full range of conditions to which a system1 may be exposed. Performance and robustness properties need to be continuously monitored during the development process to ensure that the system will meet the user’s needs at the end. This paper will discuss aspects and problems of performance and robustness engineering. Also, it presents an approach, called “ISG” (Instantaneous System and Software Generation)2 which allows to continuously derive performance and robustness properties from the system-under-development. In case of ISG figures are derived from the real system right from the beginning. Therefore deviations from the desired functional, performance and robustness envelope can be corrected at an early stage. The capability for getting an immediate3 feedback from the system is obtained by the automated generation of the software from system engineering inputs. ISG builds the software by construction rules. This reduces the manual effort and allows for an immediate and representative feedback right after provision of inputs by the user. Due to automation the system can easily be instrumented on a user’s demand without requiring any additional programming effort. ISG automatically stimulates the system and exposes it to stress tests and fault injection, and records coverage and performance figures. By incremental development a smooth transition from the first idea to the final version is possible at low risk. The ISG approach has been applied to the domain of realtime, distributed, fault-tolerant systems and shall be extended towards other application domains in future such as databases and graphical user interfaces.

A “system” as it is understood here comprises hardware and software. System development in the context of this paper addresses the software part, possibly hardware emulated by software and all aspects related to hardware-software integration. Performance and robustness engineering deal with the quality of service under nominal and non-nominal conditions of the software when executed on the system’s hardware.

© The ISG approach is property of Dr. Rainer Gerlich BSSE System and Software Engineering. All features of ISG are protected by international copyright, all rights are reserved (1999–2000)

“Immediate” means a range of about 20 minutes up to 2 hours depending on the complexity of the system on an UltraSparc I/143 or PC 200.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. BSSE internal communication, unpublished

    Google Scholar 

  2. CRISYS: Critical Instrumentation and Control System, ESPRIT project EP 25514 (1997-2001)

    Google Scholar 

  3. Ehrlich, W., Prasanna, B., Stampe, J., Wu, J.: Determining the Cost of a Stop-Test Decision, IEEE Software, March (1993) 33

    Google Scholar 

  4. Gerlich, R.: Tuning Development of Distributed Real-time Systems with SDL and MSC: Current Experience and Future Issues, In: Cavalli, A., Sarma, A. (eds.): SDL’97 Time for testing, SDL, MSC and Trends. Proceedings of the Eighth SDL Forum, Evry, France, 23–26 September (1997) 85–100

    Google Scholar 

  5. Harel, L.: Statemate/Rhapsody, i-Logix, Three Riverside Drive, Andover, MA 01810, http://info@ilogix.com

  6. HRDMS: Highly Reliable Data Management System and Simulation, ESA/ESTEC contract no. 9882/92/NL/JG(SC), Final Report, Noordwijk, The Netherlands (1994)

    Google Scholar 

  7. Gerlich, R.: ISG, Instantaneous System and Software Engineering, ISG User’s Manual and ISG Traning Manual, Auf dem Ruhbuehl 181, D-88090 Immenstaad (1999-2000) The ideas and implementation details related to ISG are property of Dr. Rainer Gerlich BSSE System and Software Engineering. They are protected by international copyright ©, 1999–2000. All rights reserved

    Google Scholar 

  8. MSC: ITU-T Recommendations Z.120, Message Sequence Charts (MSC), Helsinki (1993)

    Google Scholar 

  9. Gerlich, R., Birk, M., Brammer, U., Ziegler, M., Lattner, K.: Automated Generation of Real-Time Software from Datasheet-based Inputs-The Process Model, the Platform and the Feedback from the MSL Project Activities, Eurospace Symposium DASIA’00 “Data Systems in Aerospace”, May 22–26, 2000, Montreal, Canada, ESA (2000)

    Google Scholar 

  10. Birk, M., Brammer, U., Ziegler, M., Lattner, K., Gerlich, R.: Software Development for the Material Science Laboratory on ISS by Automated Generation of Real-Time Software from Datasheet-based Inputs, Eurospace Symposium DASIA’00 “Data Systems in Aerospace”, May 22–26, 2000, Montreal, Canada, ESA (2000)

    Google Scholar 

  11. Musa, J.D.: Operational Profiles in Software-Reliability Engineering, IEEE Software, March (1993) 14–32

    Google Scholar 

  12. OG: ObjectGEODE, Verilog, 52, Avenue Aristide Briand; Bagneux; 92220; France, http://verilog@verilog.fr, since 2000 part of Telelogic, see SDT (2000)

  13. OPNET: OPNET, MIL3 Inc., 3400 International Drive, NW-Washington, DC 20008, USA

    Google Scholar 

  14. SDL: ITU Z.100, Specification and Description Language, SDL, Geneve (1989)

    Google Scholar 

  15. SDT: SDT, Telelogic, Headquarters: Box 4128; S-203 12 Malmoe; Sweden. Vising address: Kungsgatan 6, info@telelogic.se

    Google Scholar 

  16. UML: Unified Modelling Language, http://www.rational.com/uml

  17. VWKS: TORNADO / VxWorks, WindRiver Systems, Inc. 1010 Atlantic Avenue, Alameda, CA 94501-1153, USA

    Google Scholar 

  18. WB: SES/workbench, 4301 Westbank Dr., Bldg. A, Austin, TX 78746 USA, mktg@ses.com

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2001 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Gerlich, R. (2001). Performance and Robustness Engineering and the Role of Automated Software Development. In: Dumke, R., Rautenstrauch, C., Scholz, A., Schmietendorf, A. (eds) Performance Engineering. WOSP GWPESD 2000 2000. Lecture Notes in Computer Science, vol 2047. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-45156-0_2

Download citation

  • DOI: https://doi.org/10.1007/3-540-45156-0_2

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-540-42145-0

  • Online ISBN: 978-3-540-45156-3

  • eBook Packages: Springer Book Archive

Publish with us

Policies and ethics