Managing Requirements Knowledge


Book Description

Requirements engineering is one of the most complex and at the same time most crucial aspects of software engineering. It typically involves different stakeholders with different backgrounds. Constant changes in both the problem and the solution domain make the work of the stakeholders extremely dynamic. New problems are discovered, additional information is needed, alternative solutions are proposed, several options are evaluated, and new hands-on experience is gained on a daily basis. The knowledge needed to define and implement requirements is immense, often interdisciplinary and constantly expanding. It typically includes engineering, management and collaboration information, as well as psychological aspects and best practices. This book discusses systematic means for managing requirements knowledge and its owners as valuable assets. It focuses on potentials and benefits of “lightweight,” modern knowledge technologies such as semantic Wikis, machine learning, and recommender systems applied to requirements engineering. The 17 chapters are authored by some of the most renowned researchers in the field, distilling the discussions held over the last five years at the MARK workshop series. They present novel ideas, emerging methodologies, frameworks, tools and key industrial experience in capturing, representing, sharing, and reusing knowledge in requirements engineering. While the book primarily addresses researchers and graduate students, practitioners will also benefit from the reports and approaches presented in this comprehensive work.




Requirements Management


Book Description

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




Managing Software Requirements


Book Description

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.




Engineering and Managing Software Requirements


Book Description

Following an introductory chapter that provides an exploration of key issues in requirements engineering, this book is organized in three parts. It presents surveys of requirements engineering process research along with critical assessments of existing models, frameworks and techniques. It also addresses key areas in requirements engineering.




Mastering the Requirements Process


Book Description

“If the purpose is to create one of the best books on requirements yet written, the authors have succeeded.” —Capers Jones Software can solve almost any problem. The trick is knowing what the problem is. With about half of all software errors originating in the requirements activity, it is clear that a better understanding of the problem is needed. Getting the requirements right is crucial if we are to build systems that best meet our needs. We know, beyond doubt, that the right requirements produce an end result that is as innovative and beneficial as it can be, and that system development is both effective and efficient. Mastering the Requirements Process: Getting Requirements Right, Third Edition, sets out an industry-proven process for gathering and verifying requirements, regardless of whether you work in a traditional or agile development environment. In this sweeping update of the bestselling guide, the authors show how to discover precisely what the customer wants and needs, in the most efficient manner possible. Features include The Volere requirements process for discovering requirements, for use with both traditional and iterative environments A specification template that can be used as the basis for your own requirements specifications Formality guides that help you funnel your efforts into only the requirements work needed for your particular development environment and project How to make requirements testable using fit criteria Checklists to help identify stakeholders, users, non-functional requirements, and more Methods for reusing requirements and requirements patterns New features include Strategy guides for different environments, including outsourcing Strategies for gathering and implementing requirements for iterative releases “Thinking above the line” to find the real problem How to move from requirements to finding the right solution The Brown Cow model for clearer viewpoints of the system Using story cards as requirements Using the Volere Knowledge Model to help record and communicate requirements Fundamental truths about requirements and system development




Managing Software Requirements the Agile Way


Book Description

Learn how to deliver software that meets your clients’ needs with the help of a structured, end-to-end methodology for managing software requirements and building suitable systems Key FeaturesLearn how to communicate with a project’s stakeholders to elicit software requirementsDeal every phase of the requirement life cycle with pragmatic methods and techniquesManage the software development process and deliver verified requirements using Scrum and KanbanBook Description Difficulty in accurately capturing and managing requirements is the most common cause of software project failure. Learning how to analyze and model requirements and produce specifications that are connected to working code is the single most fundamental step that you can take toward project success. This book focuses on a delineated and structured methodology that will help you analyze requirements and write comprehensive, verifiable specifications. You'll start by learning about the different entities in the requirements domain and how to discover them based on customer input. You’ll then explore tried-and-tested methods such as impact mapping and behavior-driven development (BDD), along with new techniques such as D3 and feature-first development. This book takes you through the process of modeling customer requirements as impact maps and writing them as executable specifications. You’ll also understand how to organize and prioritize project tasks using Agile frameworks, such as Kanban and Scrum, and verify specifications against the delivered code. Finally, you'll see how to start implementing the requirements management methodology in a real-life scenario. By the end of this book, you'll be able to model and manage requirements to create executable specifications that will help you deliver successful software projects. What you will learnKick-start the requirements-gathering and analysis process in your first meeting with the clientAccurately define system behavior as featuresModel and describe requirement entities using Impact Mapping and BDDCreate a feature-based product backlog and use it to drive software developmentWrite verification code to turn features into executable specificationsDeliver the right software and respond to change using either Scrum or KanbanChoose appropriate software tools to provide transparency and traceability to your clientsWho this book is for This book is for software engineers, business analysts, product managers, project managers, and software project stakeholders looking to learn a variety of techniques and methodologies for collating accurate software requirements. A fundamental understanding of the software development life cycle (SDLC) is needed to get started with this book. Although not necessary, basic knowledge of the Agile philosophy and practices, such as Scrum, along with some programming experience will help you to get the most out of this book.




Knowledge Driven Development


Book Description

Provides detailed methodology for digitizing project knowledge by bridging the gap between Waterfall and Agile Methodologies.




Build Android-Based Smart Applications


Book Description

Build smart applications using cutting-edge technologies such as rules engines, code automation frameworks, and natural language processing (NLP). This book provides step-by-step instructions on how to port nine rules engines (CLIPS, JRuleEngine, DTRules, Zilonis, TermWare, Roolie, OpenRules, JxBRE, and JEOPS) to the Android platform. You’ll learn how to use each rules engine to build a smart application with sample code snippets so that you can get started with programming smart applications immediately. Build Android-Based Smart Applications also describes porting issues with other popular rules engines (Drools, JLisa, Take, and Jess). This book is a step-by-step guide on how to generate a working smart application from requirement specifications. It concludes by showing you how to generate a smart application from unstructured knowledge using the Stanford POS (Part of Speech) tagger NLP framework. What You Will Learn Evaluate the available rules engines to see which rules engine is best to use for building smart applications Build smart applications using rules engines Create a smart application using NLP Automatically generate smart application from requirement specifications Who This Book Is For Android and web developers with some experience.




Guide to the Software Engineering Body of Knowledge (Swebok(r))


Book Description

In the Guide to the Software Engineering Body of Knowledge (SWEBOK(R) Guide), the IEEE Computer Society establishes a baseline for the body of knowledge for the field of software engineering, and the work supports the Society's responsibility to promote the advancement of both theory and practice in this field. It should be noted that the Guide does not purport to define the body of knowledge but rather to serve as a compendium and guide to the knowledge that has been developing and evolving over the past four decades. Now in Version 3.0, the Guide's 15 knowledge areas summarize generally accepted topics and list references for detailed information. The editors for Version 3.0 of the SWEBOK(R) Guide are Pierre Bourque (Ecole de technologie superieure (ETS), Universite du Quebec) and Richard E. (Dick) Fairley (Software and Systems Engineering Associates (S2EA)).




Just Enough Requirements Management


Book Description

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.