Opinion: This book is the end-all of SysML Encylopedia. Since the three authors are all equally giants they all split up the chapters and attacked the topics of what can you do with SysML. It's the most comprehensive book on the topic showing many examples to address their points. However, this book is not one project so it is best consumed by looking up what you want to do and read that section. Doesn't really address the interconnectivity of the data.
Read Style: Encyclopedia style. Look up topics as needed. Must have in your library.
Opinion: INCOSE (International Council On Systems Engineering). Is a great organization, at this point mostly industry organizations belong and run it. You can interact with other systems engineers share war stories and get help and possibly get employees or employed by other organizations. Unlike ieee which became an academic driven theory-based organization. This book is what you get when you get a book by committee. Many people contributed to the different chapters. Mostly this is used to get everyone on the same 'Language'. You may have been a system engineer for 20 years and everything is covered in this book it's just a matter of 'normalizing' the language we all use. PDF of this document is free with INCOSE membership.
Read Style: A must-read to pass the CSEP exam.
Opinion: Here's another example of acidemia going amuck. Let's just create another language exactly like SysML but fewer features and easier to diagram with less structure. MBSE Solutions has built a profile that allows SE's to create OPM like diagrams in SysML models so we can get the best of both worlds. OPM is great for the 50,000-foot view of what's going on. SysML gets into the nitty-gritty details necessary to document a complex system.
Read Style: Reads like an encyclopedia just look up the topic you care about and get out.
Opinion: This is the book for everyone starting out. It's a cube satellite project taken through the SysML diagrams. What you put on each diagram etc. It's basic and addresses what in general you can do with SysML. Ignore his chapter on use cases, it's antiquated and there is soo much more usage you can get from a use case. Use Cases can have Activities and diagrams, and Sequence diagrams to define the details of the use case. In his chapter, he gives the talking points of how we treated them in the 90's houses for a paragraph.
Read Style: Takes one project through all the different aspects of SysML. A good read.
Opinion: Tim Weilkiens is a leader in the world of SysML With great ideas and pushing the envelope. I recommend this book for people who already know UML Just eat a shaker of salt and understand this book was written a long time ago. More of his ideas have progressed since then. This book is detailed to the point that it's not for the beginning systems engineer. But the budding software engineer looking to get into Systems engineering.
Read Style: Easy read. Enjoyable with the understanding of what a profile is.
Opinion: A good way to change the way you think about problems. If you are not a systems thinker and are getting into systems engineering this is the book for you. If you don't know what a systems thinker is this book is for you.
Read Style: Meeh
Opinion: Having worked with Simon and Jon at Atego I would highly recommend this book as a good read. Jon talks of brontosaurs starting out small having a lot to consume in the middle and running thin on the backend of the project. I believe this is a reiteration of eating an elephant one bite at a time.
Read Style: This book can be consumed very easily, reads beautifully and understandable.
Opinion: The Engineering Design of Systems: Models and Methods. Covers topics like iDEF models, SysML modeling, some OPM modeling in theory. Slight discussions on stakeholder needs, Software design process waterfall, and spiral... Some analysis techniques for testing... Kind of catch-all but not great on any topic. I've never had the pleasure of meeting either of the authors as they have been involved at INOCSE. But typically with INOCSE if you aren't in the 'inner circle' you'll see many people but not directly have a discussion with them. Dennis a 40 year veteran in Systems Engineering has written many many books on the topic. William Miller a 50-year veteran which is probably the reason I haven't meet up with them. They both probably don't do happy hour at the events. Miller has some other topics that I see may be worth a look at like System Engineering Metrics.
Opinion: System Requirements Engineering. A SysML Supported Requirements Engineering Method. Anyone who knows me knows I advocate for the SyML model as being the Requirements of the system. Actually putting in the design the details necessary to build the system. There is always the need for textual requirements but those as well can be captured in SysML. But I would be remiss in not recommend Jean-Yves book on the topic. He's approach is close to what I would advocate but this book follows the process of creating your context then use scenarios followed by functional and non-functional requirements. Then Stakeholder needs finally Systems Requirements. This process is superior to those who say we start with requirements. I agree that Requirements aren't defined until we understand all the prior information. (Context, Functions, Stakeholder needs)... Read my topic on Stakeholder value networks to see even more information that should be captured and tracked.
Opinion: Systems Thinking made simple: New Hope for Solving Wicked Problems. Still need to get into this myself but was recommended to me by Matt Sease from Cummins. I've only glanced it but it looks like a good read.
Opinion: Architecting Spacecraft with SysML: A Model-based Systems Engineering Approach Another book by Sandy but this one reads end to end with one project in mind. INCOSE cube sat is the project and this and Delligotti's books write about it. I haven't gotten into this until just recently. It may become my new highest recommendation for beginners. I feel this was written to compete with Delligotti's book. But this was done with INCOSE's approval...
Opinion: Agile Systems Engineering - Bruce Powel Douglas here's a character. I've met him many times and every time he doesn't remember me. My old company Embedded Plus partner Salah Obeid and he use to work together at iLogic. And I've seen him many times at the OMG in my capacity as a contributor. I love that he subscribes himself as someone like Romulus and Ramius ... Raised by wolves. In my belief Bruce is a great theorist, I feel he is lacking some applied usage of his ideas. But that's not meant to be insulting in this I mean he can really dream up topics that others only just think of. His work with state mate was legendary which created ilogics now IBM's Rhapsody tool.
Opinion: Response Ability (The Language, Structure, and Culture of the Agile Enterprise) - Love the play on words but it makes it difficult to know this is an agile engineering book. Rick Dove a founder of the agile process. Not given enough credit for being one of the founders of the topic. I've had the great pleasure of spending hours with Rick over the past few years. If you want to get your organization agile and don't know what that means Rick provides seminars on a regular basis in Taos, New Mexico. Or on your company site if there are enough people to get signed up. I've only just started to read this but talking with Rick I feel I already know what it will read like. You can't go wrong as he makes everything enjoyable to read.
Opinion: Value Propositioning: Book One - Perception and Misperception in Decision Making. Rick loves the play on words. This covers the ideas that our out view of the world has to do with our perspective of what we are looking at. Kind of like the forest through the trees. If you are looking at an elephant but you are really close to it. You may only see something with grey wrinkly hard course surface, and not know the whole system is an elephant. Getting the 50,000-foot view would let us see the whole picture, but often we tend to focus on the details and not know how the part integrates into the whole.
Opinion: Design Structure Matrix. If you use MBSE Solutions plug-in for SysML you get a DSM generator for Ports specifically stereotyped interfaces (i.e. energy, matter, force,...). This profile generates a DSM for analysis. This book is a good read to understand the theory behind how and why to use DSM's what benefit it will make for your architecture you are designing.
Read Style: This reads like a math book. Just get in get what you need and get out.
Opinion: Along with this book. MIT xPro is offering an online training course that takes you through a similar topic covered in this book. It is a 4-5 week courses (Architecture of Complex Systems, Models in Engineering, Model-Based Systems Engineering, Quantitative Methods in Systems Engineering) At the end you get a certificate.
Model-Based Systems Engineering - covers OPM and some SysML. Just a spattering and is followed up with DSM's in the Quantitative section.
Read Style: Reads like a textbook. Couldn't do it fast. Took me many months to consume. Maybe easier to just take the MIT xPRO course.