Use of the Unified Process for software requirements

Author: Wendell
Publisher:
Publish Date: 2003-10-01
Features: If you are an analyst responsible for describing the requirements analysis of software systems, we believe you will find a concise and effective method in this book that meets both user needs and the needs of developers and testers who require you to submit specifications. If you are a developer responsible for building software systems based on requirements specifications, we believe you will discover an effective method to communicate all software requirements in a consistent and user-friendly way. If you are a tester responsible for testing software systems based on requirements specifications, we believe you will find that the specifications introduced in this book provide a complete and clear control flow model of the entire system, enabling readers to systematically develop tests. We also believe you will find that the requirements work products introduced in this book allow you to quickly and thoroughly understand new systems. If you are a manager responsible for software development or testing, we believe you will find that establishing and maintaining requirements work products will ensure that new personnel can be integrated, accelerating system development. We also believe readers will find a practical method that can shorten the time spent describing software requirements while maintaining the intellectual resources of the organization. This book provides a systematic and easy-to-apply methodology for establishing effective requirements—using software requirements in the unified process—and introduces practical solutions for the entire requirements lifecycle, including acquisition, analysis, specification, verification, and maintenance. Through 18 chapters in five main sections, this book introduces the key characteristics of good software requirements, the requirements analysis process and work products, building user requirements, problem domains, participants, use cases, activity diagrams, and storyboards, constructing requirements architecture, entities and events, class diagrams, state transition diagrams, and sequence diagrams, building specifications, software requirements, interface requirements, and verification, using the constructed requirements architecture; and through an appendix (Part 6), it provides an actual software specification. Whether you are an analyst, architect, developer, tester, manager, or software customer, this book will help you formulate software requirements that accurately reflect your needs and can be converted into actual software more quickly and cost-effectively than ever before.