Requirements Management

This book focuses on the interfaces of Requirements Management to the other disciplines of Systems Engineering. An introduction into Requirements Management and Requirements Development is given, along with a short sketch of Systems Engineering, and especially the necessary inputs and resulting outputs of Requirements Management are explained. Using these it is shown how Requirements Management can support and optimize the other project disciplines.

Organizations continue to experience project issues associated with poor performance on requirements-related activities. This guide will give you the tools you need to excel in requirements development and management — components of the larger field of business analysis and a critical competence for project, program and portfolio management. Requirements Management: A Practice Guide is a bridge between A Guide to the Project Management Body of Knowledge (PMBOK® Guide), which speaks to requirements development and management from a high-level perspective, and Business Analysis for Practitioners: A Practice Guide, which describes requirements development and management at a detailed and practical level. This practice guide is the middle ground, offering project managers, program managers, teams members and stakeholders the opportunity to learn more about the requirements process

Poor requirements management is one of the top five contributors to poor project performance. In extreme, safety critical or emergency-relief situations, failure to satisfy the real needs of the project stakeholders may well lead directly to loss of life or human suffering; other, more mundane, projects can also be severely compromised. Dr Mario Kossmann’s Requirements Management looks at the process from the perspectives of both Program and Project Management and Systems Engineering, showing the crucial role of RM in both contexts. The author puts great emphasis on the human aspects of any project, which is also significant given that over-emphasis on technical or technological aspects at the expense of the human side is another major source of project shortfalls. The book offers illustrated examples of systems of different levels of complexity (one simple system, one complex, and one highly complex system) to help you categorize your own system and enable you to select the right level of formality, a suitable organization and a set of techniques and tools to carry out your requirements work. It includes a series of comprehensive checklists which can be used immediately to improve urgent requirements aspects. This is a practical and realistic guide to requirements management that provides a flexible, hands-on and innovative approach to developing and managing program, project and system requirements at different levels of complexity; read it and use the advice offered to ensure your projects can actually deliver, first time, without the need for costly and time-consuming rework.

A classic treatise that defined the field of applied demand analysis, Consumer Demand in the United States: Prices, Income, and Consumption Behavior is now fully updated and expanded for a new generation. Consumption expenditures by households in the United States account for about 70% of Americaâ__s GDP. The primary focus in this book is on how households adjust these expenditures in response to changes in price and income. Econometric estimates of price and income elasticities are obtained for an exhaustive array of goods and services using data from surveys conducted by the Bureau of Labor Statistics, providing a better understanding of consumer demand. Practical models for forecasting future price and income elasticities are also demonstrated. Fully revised with over a dozen new chapters and appendices, the book revisits the original Taylor-Houthakker models while examining new material as well, such as the use of quantile regression and the stationarity of consumer preference. It also explores the emerging connection between neuroscience and consumer behavior, integrating the economic literature on demand theory with psychology literature. The most comprehensive treatment of the topic to date, this volume will be an essential resource for any researcher, student or professional economist working on consumer behavior or demand theory, as well as investors and policymakers concerned with the impact of economic fluctuations.

This is the digital version of the printed book (Copyright © 2005). If you develop software without understanding the requirements, you're wasting your time. On the other hand, if a project spends too much time trying to understand the requirements, it will end up late and/or over-budget. And products that are created by such projects can be just as unsuccessful as those that fail to meet the basic requirements. Instead, every company must make a reasonable trade-off between what's required and what time and resources are available. Finding the right balance for your project may depend on many factors, including the corporate culture, the time-to-market pressure, and the criticality of the application. That is why requirements management—gathering requirements, identifying the "right" ones to satisfy, and documenting them—is essential. Just Enough Requirements Management shows you how to discover, prune, and document requirements when you are subjected to tight schedule constraints. You'll apply just enough process to minimize risks while still achieving desired outcomes. You'll determine how many requirements are just enough to satisfy your customers while still meeting your goals for schedule, budget, and resources. If your project has insufficient resources to satisfy all the requirements of your customers, you must read Just Enough Requirements Management.

The new, Second Edition of the Practitioner's Guide to Requirements Management by Elizabeth Larson and Richard Larson is now available in both paperback and Kindle editions! Planning of requirements activities is essential for success, regardless of the project life cycle followed. The new, second edition of this realistic guide offers a step-by-step approach, and explains how to manage requirements without creating a mountain of paperwork. It has been expanded with more coverage of Agile life cycles and contains a 40-page realistic case study to help apply the concepts.

Optimize Your Entire Requirements Process-and Use Requirements to Build More Successful Software Using IBM� Rational� RequisitePro�, you can systematically improve the way you create and maintain requirements-and use those requirements to build more effective, higher-quality software. Now, for the first time, there''s a comprehensive, hands-on guide to optimally using RequisitePro in real-world development environments. Utilizing a start-to-finish sample project, requirements expert Peter Zielczynski introduces an organized, best-practice approach to managing requirements and shows how to implement every step with RequisitePro. You''ll walk through planning, eliciting, and clarifying stakeholder requirements; building use cases and other key project documents; managing changing requirements; transforming requirements into designs; and much more. Every stage of the process is illuminated with examples, realistic artifacts, and practical solutions. This book is an invaluable resource for everyone who creates requirements, and everyone who relies on them: business analysts, systems analysts, project managers, architects, designers, developers, and testers alike. Coverage includes Overcoming the three leading causes of project failure: lack of user input, incomplete requirements and specifications, and poorly managed change Understanding each type of software requirement-how they interrelate, and what makes a good requirement Establishing a Requirements Management Plan that describes how requirements are created and handled throughout the project lifecycle Developing a Vision document that can drive your project from beginning to end Creating high-quality use cases Using requirements as the basis for system design Leveraging RequisitePro features for improved project management Integrating requirements management with the IBM Rational Unified Process� Foreword xvii Preface xix Acknowledgments xxiii About the Author xxv Part I: Overview 1 Chapter 1: Requirements Management 3 Chapter 2: Overview of RequisitePro 23 Part II: Requirements Management Activities 33 Chapter 3: Establishing a Requirements Management Plan 35 Chapter 4: Setting up the Project 45 Chapter 5: Requirements Elicitation 63 Chapter 6: Developing a Vision Document 99 Chapter 7: Creating Use Cases 129 Chapter 8: Supplementary Specification 157 Chapter 9: Creating Test Cases from Use Cases 191 Chapter 10: Creating Test Cases from Supplementary Requirements 221 Chapter 11: Object-Oriented Design 243 Chapter 12: Documentation 273 Part III: Other Topics 285 Chapter 13: Managing Projects 287 Chapter 14: Requirements Management in the Rational Unified Process 295 Part IV: Review 311 Chapter 15: Summary 313 Appendix: Sample Requirements Management Plan 319 Index 327

Requirements engineering is the process by which the requirements for software systems are gathered, analyzed, documented, and managed throughout their complete lifecycle. Traditionally it has been concerned with technical goals for, functions of, and constraints on software systems. Aurum and Wohlin, however, argue that it is no longer appropriate for software systems professionals to focus only on functional and non-functional aspects of the intended system and to somehow assume that organizational context and needs are outside their remit. Instead, they call for a broader perspective in order to gain a better understanding of the interdependencies between enterprise stakeholders, processes, and software systems, which would in turn give rise to more appropriate techniques and higher-quality systems. Following an introductory chapter that provides an exploration of key issues in requirements engineering, the book is organized in three parts. Part 1 presents surveys of state-of-the art requirements engineering process research along with critical assessments of existing models, frameworks and techniques. Part 2 addresses key areas in requirements engineering, such as market-driven requirements engineering, goal modeling, requirements ambiguity, and others. Part 3 concludes the book with articles that present empirical evidence and experiences from practices in industrial projects. Its broader perspective gives this book its distinct appeal and makes it of interest to both researchers and practitioners, not only in software engineering but also in other disciplines such as business process engineering and management science.