Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Systems Engineering Demystified

You're reading from   Systems Engineering Demystified A practitioner's handbook for developing complex systems using a model-based approach

Arrow left icon
Product type Paperback
Published in Jan 2021
Publisher Packt
ISBN-13 9781838985806
Length 468 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Jon Holt Jon Holt
Author Profile Icon Jon Holt
Jon Holt
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Section 1: Introduction to Systems Engineering
2. Chapter 1: Introduction to Systems Engineering FREE CHAPTER 3. Chapter 2: Model-Based Systems Engineering 4. Section 2: Systems Engineering Concepts
5. Chapter 3: Systems and Interfaces 6. Chapter 4: Life Cycles 7. Chapter 5: Systems Engineering Processes 8. Section 3: Systems Engineering Techniques
9. Chapter 6: Needs and Requirements 10. Chapter 7: Modeling the Design 11. Chapter 8: Verification and Validation 12. Chapter 9: Methodologies 13. Chapter 10: Systems Engineering Management 14. Section 4: Next steps
15. Chapter 11: Best Practices 16. Other Books You May Enjoy

Summary

In this chapter, the concept of needs has been explored and modeling associated with the different concepts covered has been discussed.

Initially, the importance of the concept of needs and the different types of needs, such as requirements and capabilities, was discussed. This led to understanding how to analyze needs in two ways: by describing each need using text-based properties and descriptions, and by gaining a true understanding of the underlying need by exploring the contexts of each need.

Context was introduced as one of the single most important aspects of needs modeling and, in order to establish this understanding, how important it is to understand the stakeholders that have an interest in the system. Each of these stakeholders has the potential to interpret each need in a different way to all other stakeholders, which is known as a modeling use case.

Each use case, and therefore its related need descriptions, must be validated, and two ways of validation...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at R$50/month. Cancel anytime