MDRE: New System Vs. Existing System, Extension or Upgrade

  • Chapter
  • First Online:
Requirements Engineering: Laying a Firm Foundation

Abstract

Most engineers would rather work on new systems rather than refurbish, refactor, or extend legacy systems, but these systems exist because they work. They may have out of data hardware, software, and construction, but if they are still in the field, they still operate. One of the major tasks for the MDRE team with a legacy system to be updated or upgraded (we’ll explore the difference in this chapter) is to understand which requirements stay and which requirements must be replaced with updated versions that drive the new capabilities, new facilities, or new equipment (e.g., new computer systems) to be infused into the existing legacy system.

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

Access this chapter

Subscribe and save

Springer+ Basic
EUR 32.99 /Month
  • Get 10 units per month
  • Download Article/Chapter or Ebook
  • 1 Unit = 1 Article or 1 Chapter
  • Cancel anytime
Subscribe now

Buy Now

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 99.00
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 129.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free ship** worldwide - see info
Hardcover Book
USD 179.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free ship** worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Abbreviations

AC:

Alternating current

C:

Centigrade

CONOPS:

Concept of Operations

DC:

Direct current (or 0 Hz)

F:

Fahrenheit

HVAC:

Heating, ventilation, and air conditioning

MDRE:

Multidisciplinary requirements engineering

OSHA:

Occupational Safety and Health Administration

UCAV:

Unmanned combat air vehicle

V:

Volts

Vac:

Volts AC

References

  1. Matsumoto, Y. (1989). Some experiences in promoting reusable software: Presentation in higher abstract levels. In T. J. Biggerstaff & A. J. Perlis (Eds.), Software reusability: Concepts and models (Vol. 2, pp. 157–185). ACM Addison Wesley Publishing Company.

    Chapter  Google Scholar 

  2. Meyer, B. (1985). On formalism in specifications. IEEE Software, 6–26.

    Google Scholar 

  3. Morel, J.-M. and Faget, J. (1993), “The REBOOT environment,” presented at Advances in Software Reuse: Selected Papers from the Second International Workshop on Software Reusability, Lucca, Italy.

    Google Scholar 

  4. Morris, S. J. and Finkelstein, A. C. W. (1994). “Development of multiple media documents,” Imperial College, Department of Computing.

    Google Scholar 

  5. Myer, B. A. (1990). Visual programming, programming by example, and program visualization: A taxonomy. In E. P. Glinert (Ed.), Visual programming environments: Paradigms and systems (pp. 33–40). IEEE Computer Society Press.

    Google Scholar 

  6. Poulin, J. (1993). Integrated support for software reuse in computer-aided software engineering (CASE). ACM SIGSOFT Software Engineering Notes, 18, 75–82.

    Article  Google Scholar 

  7. Prieto-Diaz, R., & Arango, G. (1991). Domain analysis and software systems modeling. IEEE Computer Society Press.

    Google Scholar 

  8. Reubenstein, H. B. and Waters, R. C. (1989). “The requirements apprentice: An initial scenario,” presented at 5th International Workshop on Software Specifications and Design.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2022 The Author(s), under exclusive license to Springer Nature Switzerland AG

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Crowder, J.A., Hoff, C.W. (2022). MDRE: New System Vs. Existing System, Extension or Upgrade. In: Requirements Engineering: Laying a Firm Foundation. Springer, Cham. https://doi.org/10.1007/978-3-030-91077-8_8

Download citation

  • DOI: https://doi.org/10.1007/978-3-030-91077-8_8

  • Published:

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-030-91076-1

  • Online ISBN: 978-3-030-91077-8

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics

Navigation