Written by Joy Beatty, co-author of Visual Models for Software Requirements (ISBN: 9780735667723) As business analysts, if we hand developers nothing more than a list of thousands of “system shall” requirements statements, the project is doomed to fail before even a line of code is written. Such a list, as in Figure 1, is impossible to consume for analysis, development, or testing. Any large volume of requirements should be modeled visually to ensure they are complete and all necessary. Figure 1 Unorganized list of “system shall” statements   Because there are many models you can use to better describe the requirements visually (in fact you’ll find 22 Requirements Modeling Language (RML) models in Visual Models for Software Requirements ), it can be a daunting task to try to figure out ...read more