Writing Better Requirements

Author: Ian F. Alexander

Publisher: Pearson Education

ISBN:

Category: Computers

Page: 159

View: 827

Well-written requirements are crucial to systems of all kinds. This text explains and demonstrates exactly what requirements are for, and how to write them. It provides practical techniques and defines key terms, explaining and illustrating to develop the skills of good requirements writing.

The Requirements Engineering Handbook

Author: Ralph Rowland Young

Publisher: Artech House

ISBN:

Category: Computer software

Page: 254

View: 227

A concise and thorough handbook on requirements analysis, this invaluable book is the perfect desk guide for your systems or software development work. This first-of-its-kind handbook enables you to identify the real customer requirements for your projects and control changes and additions to these requirements. The books helps you understand the importance of requirements, leverage effective requirements practices, and better utilize resources. You also learn how to strengthen interpersonal relationships and communications which are major contributors to project effectiveness.

Requirements Engineering: Foundation for Software Quality

18th International Working Conference, REFSQ 2012, Essen, Germany, March 2012, Proceedings

Author: Björn Regnell

Publisher: Springer Science & Business Media

ISBN:

Category: Business & Economics

Page: 322

View: 985

This book constitutes the refereed proceedings of the 18th International Working Conference on Requirements Engineering: Foundation for Software Quality, REFSQ 2012, held in Essen, Germany, in March 2012. The papers are organized in 10 topical sections on contractual requirements, quality requirements, collaboration, complexity and creativity, requirements analysis, templates and heuristics, requirements traceability, tools and quality, services and clouds, self-adaptivity, and industrial case studies.

How to Save a Failing Project

Chaos to Control

Author: Ralph R. Young

Publisher: Berrett-Koehler Publishers

ISBN:

Category: Business & Economics

Page: 256

View: 438

You CAN Turn Around A Failing Project! Poor project results are all too common and result in dissatisfied customers, users, and project staff. With countless people, goals, objectives, expectations, budgets, schedules, deliverables, and deadlines to consider, it can be difficult to keep projects in focus and on track. How to Save a Failing Project: Chaos to Control arms project managers with the tools and techniques needed to address these project challenges. The authors provide guidance to develop a project plan, establish a schedule for execution, identify project tracking mechanisms, and implement turnaround methods to avoid failure and regain control. With this valuable resource you will be able to: • Identify key factors leading to failure • Learn how to recover a failing project and minimize future risk • Better analyze your project by defining proper business objectives and goals • Gain insight on industry best practices for planning

Software Requirement Patterns

Author: Stephen Withall

Publisher: Pearson Education

ISBN:

Category: Computers

Page: 384

View: 502

Learn proven, real-world techniques for specifying software requirements with this practical reference. It details 30 requirement “patterns” offering realistic examples for situation-specific guidance for building effective software requirements. Each pattern explains what a requirement needs to convey, offers potential questions to ask, points out potential pitfalls, suggests extra requirements, and other advice. This book also provides guidance on how to write other kinds of information that belong in a requirements specification, such as assumptions, a glossary, and document history and references, and how to structure a requirements specification. A disturbing proportion of computer systems are judged to be inadequate; many are not even delivered; more are late or over budget. Studies consistently show one of the single biggest causes is poorly defined requirements: not properly defining what a system is for and what it’s supposed to do. Even a modest contribution to improving requirements offers the prospect of saving businesses part of a large sum of wasted investment. This guide emphasizes this important requirement need—determining what a software system needs to do before spending time on development. Expertly written, this book details solutions that have worked in the past, with guidance for modifying patterns to fit individual needs—giving developers the valuable advice they need for building effective software requirements

Telling Stories

A Short Path to Writing Better Software Requirements

Author: Ben Rinzler

Publisher: John Wiley & Sons

ISBN:

Category: Computers

Page: 160

View: 986

From System Designers to Top Management, Everyone loves a good story Once upon a time, it was well understood that stories teach better than plain facts. Why then are most software requirements documents a baffling hodge-podge of diagrams, data dictionaries, and bullet points, held together by little more than a name and a staple? Telling Stories teaches you to combine proven standards of requirements analysis with the most ancient and effective tool for sharing information, the narrative. Telling Stories simplifies and refines the classic methods of Structured Analysis, providing organization, design, and old-fashioned writing advice. Whether you?re just getting started or an experienced requirements writer, Telling Stories can help you turn dull, detailed material into an engaging, logical, and readable story, a story that can make the difference for your project and your career. Learn why readers believe and remember what they learn from stories Work with team members to gather content, tell their stories, and win their support Use stories to find every requirement Create diagrams that almost tell the story on their own (while looking clear and professional) Explain everything important about a process Use precise language to remove the ambiguity from requirements Write a forceful executive summary that stands on its own and sells a project to senior management Summarize often to keep the reader focused on key issues Structure the document so every part has a clear place and purpose

Discovering Requirements

How to Specify Products and Services

Author: Ian F. Alexander

Publisher: John Wiley & Sons

ISBN:

Category: Computers

Page: 480

View: 717

"This book is not only of practical value. It's also a lot of fun to read." Michael Jackson, The Open University. Do you need to know how to create good requirements? Discovering Requirements offers a set of simple, robust, and effective cognitive tools for building requirements. Using worked examples throughout the text, it shows you how to develop an understanding of any problem, leading to questions such as: What are you trying to achieve? Who is involved, and how? What do those people want? Do they agree? How do you envisage this working? What could go wrong? Why are you making these decisions? What are you assuming? The established author team of Ian Alexander and Ljerka Beus-Dukic answer these and related questions, using a set of complementary techniques, including stakeholder analysis, goal modelling, context modelling, storytelling and scenario modelling, identifying risks and threats, describing rationales, defining terms in a project dictionary, and prioritizing. This easy to read guide is full of carefully-checked tips and tricks. Illustrated with worked examples, checklists, summaries, keywords and exercises, this book will encourage you to move closer to the real problems you're trying to solve. Guest boxes from other experts give you additional hints for your projects. Invaluable for anyone specifying requirements including IT practitioners, engineers, developers, business analysts, test engineers, configuration managers, quality engineers and project managers. A practical sourcebook for lecturers as well as students studying software engineering who want to learn about requirements work in industry. Once you've read this book you will be ready to create good requirements!

Requirements Management

How to Ensure You Achieve What You Need from Your Projects

Author: Dr Mario Kossmann

Publisher: Gower Publishing, Ltd.

ISBN:

Category: Business & Economics

Page: 212

View: 835

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.

Just Enough Requirements Management

Where Software Development Meets Marketing

Author: Alan Davis

Publisher: Addison-Wesley

ISBN:

Category: Computers

Page: 144

View: 271

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.

Scenarios, Stories, Use Cases

Through the Systems Development Life-Cycle

Author: Ian F. Alexander

Publisher: John Wiley & Sons

ISBN:

Category: Computers

Page: 544

View: 740

Extending the scenario method beyond interface design, this important book shows developers how to design more effective systems by soliciting, analyzing, and elaborating stories from end-users Contributions from leading industry consultants and opinion-makers present a range of scenario techniques, from the light, sketchy, and agile to the careful and systematic Includes real-world case studies from Philips, DaimlerChrysler, and Nokia, and covers systems ranging from custom software to embedded hardware-software systems