If you are a non-technical person with a stake in the success of a software project, this book is for you. Business managers often find it impossible to communicate business objectives and specify their software requirements to technical members of staff. This beginner’s guide teaches readers to communicate with software developers in a more focused, effective way. It describes the basic diagrams of the UML modeling notation and shows how they are used to specify requirements in an unambiguous way. When used on project, the risk of failure through unclear requirements is removed.
• First book of its kind, focuses only on software requirements • Empowers non-technical members of staff to communicate their needs to and check the work of software developers • Slim volume, practical approach makes book ideal for business travel reading
Contents
1. Introduction: Software - yet another knowledge industry; 2. Aligning to the business; 3. Adding rigor to the requirements; 4. Sketching the inside structure; 5. Sketching the inside dynamics; 6. Moving towards components; 7. Mapping to data structures; 8. Concluding remarks.
Printer friendly version
Email a colleague