For the most part, this book is about systems modeling with SysML, but doing it in an Agile way. Before we get into the detailed practices of systems modeling with that focus, however, we're going to spend some time discussing important project-related Agile practices that will serve as a backdrop of the modeling work.
Almost all of the Agile literature focuses on the "3 people in a garage developing a simple application" scope. The basic assumptions of such projects include the following:
- The end result is software that runs on a general-purpose computing platform (in other words, it is not embedded software).
- Software is the only truly important work product. Others may be developed but they are of secondary concern. Working software is the measure of success.
- The software isn't performance-, safety-, reliability-, or security-critical.
- It isn't necessary to meet regulatory standards...