Skip to main content

The Overall Systems Engineering Design

  • Chapter
  • 1663 Accesses

Abstract

The mission/business analysis community typically attempted to keep analysis distinct from technical design. It is not inherently different or an incorrect term for development of a solution to a system design. In the end, the activities which we would call design are nothing different from the activities required to create the “To-be” requirements.

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

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   79.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   99.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   109.99
Price excludes VAT (USA)
  • Durable hardcover 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

Learn about institutional subscriptions

References

  1. Heidrick, J., Munch, J., Riddle, W., and Rombach, D. 2006. New Trends in Software Process Modelling. World Scientific, Volume 18, ISBN: 978-981-256-619-5.

    Google Scholar 

  2. Pohl, K. and Sikora, E. 2007. Structuring the Co-Design of Requirements and Architecture. International Conference on Requirements Engineering: Foundations for Software Quality. Springer Publishing, New York, NY.

    Google Scholar 

  3. Chung, L., Nixon, B., Yu, E., and Mylopoulos, J. 2000. Non-Functional Requirements in Software Engineering. Kluwer Academic Publishers.

    Google Scholar 

  4. Paech, B., et al. 2003. An Experience-Based Approach for Integrating Architecture and Requirements Engineering. International Software Requirements to Architecture Workshop, STRAW 2003, Portland Oregon.

    Google Scholar 

  5. Goteland, O. and Finkelstein, C. 1994. An Analysis of the Requirements Traceability Problem. International Conference on Requirements Engineering, Colorado Springs, CO.

    Google Scholar 

  6. Korel, G. 1990. Automated Software Test Data Generation. IEEE Transactions on Software Engineering, CiteSeerX: 10.1.1.121.8803.

    Google Scholar 

  7. Copeland, L. 2001. Extreme Programming. Computerworld.

    Google Scholar 

  8. Koskela, L. 2007. Test Driven: TDD and Acceptance TDD for Java Developers. Manning Publications, Shelter Island, NY.

    Google Scholar 

  9. Beck, K. 2003. Test-Driven Development by Example. Addison Wesley – Vaseem, Boston, MA.

    Google Scholar 

  10. Beck, K. 2002. Test Driven Development. Addison-Wesley Professional, Boston, MA.

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2016 Springer International Publishing Switzerland

About this chapter

Cite this chapter

Crowder, J.A., Carbone, J.N., Demijohn, R. (2016). The Overall Systems Engineering Design. In: Multidisciplinary Systems Engineering. Springer, Cham. https://doi.org/10.1007/978-3-319-22398-8_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-319-22398-8_5

  • Publisher Name: Springer, Cham

  • Print ISBN: 978-3-319-22397-1

  • Online ISBN: 978-3-319-22398-8

  • eBook Packages: EngineeringEngineering (R0)

Publish with us

Policies and ethics