Book Image

Systems Engineering Demystified, Second Edition - Second Edition

By : Jon Holt
4 (1)
Book Image

Systems Engineering Demystified, Second Edition - Second Edition

4 (1)
By: Jon Holt

Overview of this book

Systems engineering helps in developing and describing complex systems. Written by an internationally-recognized systems engineering expert, this updated edition provides insight into elements to consider when designing a complex system that is robust and successful. The latest edition covers the new approaches of Model-Based Systems Engineering (MBSE) and its deployment techniques using the Trinity approach. You will learn about the system engineering life cycle and processes to implement. Effective systems can be built only when the system is designed with close attention to detail, meaning each aspect of the system is recognized and understood before the system is built. The book explains in great detail, different system models and visualization techniques, with a focus on SysML, to help you visualize a system in the design phase. You will also learn various verification and validation techniques to ensure your system design is ready to be implemented. The book ends with key management processes, systems engineering best practices, and guidelines, with a new section on effective approaches based on the author’s impressive 30 years of experience in the field. By the end of this systems engineering book, you'll be able to apply modern model-based systems engineering techniques to your own systems and projects.
Table of Contents (20 chapters)
1
Part I: Introduction to Systems Engineering
4
Part II: Systems Engineering Concepts
8
Part III: Systems Engineering Techniques
14
Part IV: Next Steps
18
Other Books You May Enjoy
19
Index

The spoken language – the Systems Modeling Language (SysML)

SysML is a general-purpose visual modeling language. SysML is itself based on another general-purpose visual modeling language, known as UML. UML is a language that has its roots firmly in the software engineering world and was created for very pragmatic reasons. Prior to 1997, when the first version of UML was released, there was a whole plethora of modeling notations and methodologies that were being used for software engineering. In fact, there were over 150 different recognized approaches available.

Bearing in mind that one of the aims of a modeling notation is to provide a basic mechanism for communication, there were simply way too many available, which made the choice of Notation both bewildering and difficult. In the mid-1990s, therefore, the software industry collectively decided that there were too many languages and that there should be a single, standardized, common language that everybody could use. It was...