Skip to main content

Introduction: Systems Engineering—Why?

  • Chapter
Multidisciplinary Systems Engineering

Abstract

The purpose of this text book is to arm the student with System Engineering principles, practices, and activities applicable to developing programs and systems within today’s complex, distributed multi-discipline converging enterprise environments. Specifically, the focus is to match the overwhelming design gaps and needs of the current Systems Engineering discipline with foundations of new and relevant procedures, products and implements. Therefore, this introductory text book provides the basis for a modern Multi-disciplinary Systems Engineering approach.

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 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

Institutional subscriptions

References

  1. Creswell, J. 2003. Research Design: Qualitative, Quantitative and Mixed Approached. Sage.

    Google Scholar 

  2. Camarinha-Matos, L. and Afsarmanesh, H. 2008. Collaborative Networks: Reference Modeling. Springer Publishing, New York NY.

    Book  Google Scholar 

  3. Clements, P. 1996. A survey of architecture description languages. Proceedings of the 8th international workshop on software specification and design. IEEE Computer Society.

    Google Scholar 

  4. Booch, G., Rumbaugh, J., and Jacobson, I. 1998. The Unified Modeling Language Users Guide. Addison Wesley Publishing, Boson, MA, ISBN: 0-201-57168-4.

    Google Scholar 

  5. Kruchten, P. 2000. The rational unified process: an introduction. Addison-Wesley Longman Publishing Co., Inc. Boston, MA.

    Google Scholar 

  6. Kossiakoff, A. and Sweet, W. 2003. Systems Engineering: Principles and Practice. John Wiley & Sons, Hoboken, NJ.

    Google Scholar 

  7. Luzeaux, D., and Rualt, J. 2010. Systems of Systems. ISTE Ltd and John Wiley & Sons Inc., New York, NY.

    Google Scholar 

  8. Ross, J., Weill, P., and Robertson, D. 2006. Enterprise Architecture as Strategy: Creating a Foundation for Business Execution. Harvard Business Review Press, Harvard University, Cambridge, MA.

    Google Scholar 

  9. Bass, L., Clements, P., and Kazman, R. 2003. Software Architecture in Practice, Second Edition. Addison Wesley Professional, Boston, MA.

    Google Scholar 

  10. Doerr, J., Kerlow, D., Koenig, T., Olson, T., and Suzuki, T. 2005. Non-Functional Requirements in Industry – Three Case Studies Adopting the ASPIRE NFR Method Technical Report 025.05/E, Fraunhofer IESE.

    Google Scholar 

  11. Parnas, D. 1979. Designing Software for ease of Extension and Contraction. IEEE Transactions of Software Engineering, 5(2):128-138.

    Article  MATH  Google Scholar 

  12. Parker, J. 2010. Applying a System of Systems Approach for improved transportation. S.A.P.I.EN.S. 3 (2).

    Google Scholar 

  13. Simon, D. 2000. Design and Rule Base Reduction of a Fuzzy Filter for the Estimation of Motor Currents. International Journal of Approximate Reasoning, 25(2).

    Google Scholar 

  14. Maier, M. 1998. Architecting Principles for System of Systems. Systems Engineering 1 (4): 267–284.

    Article  Google Scholar 

  15. Egyed, A., Grunbacher, P., and Medvidovic, N. 2001. Refinement and Evolution Issues in Bridging Requirements and Architecture-the CBSP Approach. In International Software Requirements to Architecture Workshop, Toronto, CAN.

    Google Scholar 

  16. Bahrami, A. 1999. Object-Oriented Systems Development: Using the Unified Modeling Language. McGraw Hill, New York, NY, ISBN 0-07-234966-2.

    Google Scholar 

  17. Crowder, J. and Carbone, J. 2012. Reasoning Frameworks for Autonomous Systems. Proceedings of the AIAA Infotech@Aerospace 2012 Conference, Garden Grove, CA.

    Google Scholar 

  18. Jamshidi, M. 2005. System-of-Systems Engineering - A Definition. IEEE SMC 2005, 10-12.

    Google Scholar 

  19. Conway, W. 1995. The Quality Secret: The Right Way to Manage. Conway Quality, Nashua, NH.

    Google Scholar 

  20. Books, F. 1975. The Mythical Man Month. Addison Wesley, Boston, MA.

    Google Scholar 

  21. Beck, K; et al. 2001. Manifesto for Agile Software Development. Agile Alliance.

    Google Scholar 

  22. Alpern, B. and Schneider, F. 1987. Recognizing Safety and Liveness. Distributed computing, 2(3):117–126.

    Article  MATH  Google Scholar 

  23. Abadi, M. and Lamport, L. 1991. The Existence of Refinement Mappings. Theoretical Computer Science, 82(2):253 – 284.

    Article  MathSciNet  MATH  Google Scholar 

  24. Cheng, B. and Atlee, J. 2009. Current and Future Research Directions in Requirements Engineering. In Design Requirements Engineering: A Ten-Year Perspective Workshop, Cleveland, OH.

    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). Introduction: Systems Engineering—Why?. In: Multidisciplinary Systems Engineering. Springer, Cham. https://doi.org/10.1007/978-3-319-22398-8_1

Download citation

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

  • 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