Books Guide: Requirements

Scalability Rules is the easy-to-use scalability primer and reference for every architect, developer, web professional, and manager. Authors Martin L. Abbott and Michael T. Fisher have helped scale more than 200 hypergrowth Internet sites through their consulting practice. Now, drawing on their unsurpassed experience, they present 50 clear, proven scalability rules–and practical guidance for applying them.

This is the first comprehensive, practical guide for Scrum practitioners working in large-scale distributed environments. Written by three of IBM’s leading Scrum practitioners—in close collaboration with the IBM QSE Scrum Community of more than 1000 members worldwide—this book offers specific, actionable guidance for everyone who wants to succeed with Scrum in the enterprise.

Requirements engineering is the process of eliciting individual stakeholder requirements and needs and developing them into detailed, agreed requirements documented and specified in such a way that they can serve as the basis for all other system development activities. In this textbook, Klaus Pohl provides a comprehensive and well-structured introduction to the fundamentals, principles, and techniques of requirements engineering.

This book integrates key tools and processes into a comprehensive program for developing more robust and reliable technology-based products. Drawing on their extensive product development expertise, the authors present a complete process for ensuring product performance throughout the entire lifecycle, from understanding customers’ needs through manufacturing and post launch support.

Designed to meet the hands-on needs of those working in the field, especially those concerned with testing, Modeling Software Behavior: A Craftsman’s Approach provides engineers, developers, and technicians with a detailed treatment of various models of software behavior that will support early analysis, comprehension, and model-based testing.

This book provides a systematic and practical approach to the engineering of high-quality requirements. It covers the entire requirements lifecycle and integrates state-of-the-art techniques for requirements elicitation, evaluation, specification, analysis, and evolution. Modeling plays a central role. A method is presented for building and analyzing a multi-view model of the target system, where each step is supported by heuristic rules, tactics, modeling patterns, and bad smells to avoid.

One of the least discussed and most challenging roles in the Scrum Agile Methodology is that of Product Owner. Quite often Product Owners are selected from the ranks of Product Managers or Business Analysts and simply "thrown" into the role. While these backgrounds can lead to successful product ownership, often there are fundamental understanding and large skills gaps that need to be crossed in order to be truly successful.

Whether you're leading an organization, a team, or a project, Stand Back and Deliver gives you the agile leadership tools you'll need to achieve breakthrough levels of performance. This book brings together immediately usable frameworks and step-by-step processes that help you focus all your efforts where they matter most: delivering business value and building competitive advantage.

Requirements Management has proven itself to be an enormous potential for the optimization of development projects throughout the last few years. Especially in the climate of an increasingly competitive market Requirements Management helps in carrying out developments faster, cheaper and with a higher quality.

Much as we hate to admit it, most prototyping practice lacks a sophisticated understanding of the broad concepts of prototypingand its strategic position within the development process. Often we overwhelm with a high fidelity prototype that designs us into a corner. Or, we can underwhelm with a prototype with too much ambiguity and flexibility to be of much use in the software development process.

Written in an engaging style and relevant for any software analyst or designer, Mastering the Requirements Process provides a powerful and useful guide to defining more complete software requirements that lead to better software overall. It's also filled with innovative advice.

Not connecting software project management to actual, real-world development processes can lead to cost overruns, bad tasking decisions, and unrealistic schedules that can hinder any software project. This volume describes clearly and simply how to make the project management-process management connection to control software engineering tasking, quality, metrics, and repeatability.

Software Specification and Design: An Engineering Approach proposes a strategy for software development that emphasizes measurement. It promotes the measurement of every aspect of the software environment - from initial testing through test activity and deployment/operation. This book details the path to effective software and design. It recognizes that each project is different, with its own set of problems, so it does not propose a specific model.

The Reverse Detective is an easy-to-read, breakthrough book that shows you how to prevent software failure by using the same disciplined, step-by-step process used by professional detectives to solve crimes.

There's just one difference: You put the traditional Sherlock Holmes approach in reverse.

The result? Instead of solving the crime of software failure, you prevent it by precisely determining and modeling the right requirements before you begin writing code.

While a number of books on the market deal with software requirements, this is the first resource to offer you a methodology for discovering and testing the real business requirements that software products must meet in order to provide value. The book provides you with practical techniques that help prevent the main causes of requirements creep, which in turn enhances software development success and satisfaction among the organizations that apply these approaches.

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.

"Software Reliability Engineering" is the classic guide to this time-saving practice for the software professional. ACM Software Engineering Notes praised it as: ". . .

Discover ECSAM, a method for requirements engineering and the modeling of computer-based systems (CBS). Practiced since 1980 in evolving versions by systems and software engineers, ECSAM was developed in part at Israel Aircraft Industries for the analysis and design of complex reactive embedded systems and software and has been presented in numerous undergraduate, graduate, and industrial courses.

If you're responsible for protecting Windows systems, firewalls and anti-virus aren't enough. You also need to master incident response, recovery, and auditing. Leading Windows security expert and instructor Harlan Carvey offers a start-to-finish guide to everything administrators must know to recognize and respond to virtually any attack.

Offers a comprehensive treatment of the techniques and practices of systems reliability and failure prevention, without the use of advanced mathematics. Features real-world examples from communication networks, aircraft and missile systems, the process industry, and satellite missions.

You code. And code. And code. You build only to rebuild. You focus on making your site compatible with almost every browser or wireless device ever put out there. Then along comes a new device or a new browser, and you start all over again.

You can get off the merry-go-round.

"Requirements" are essential for creating successful software because they let users and developers agree on what features will be delivered in new systems. Karl Wiegers's Software Requirements shows you how to define and get more out of software requirements with dozens of "best practices" and tips that make this book a valuable resource for both software project managers and developers.

Building Web Applications with UML is a guide to building robust, scalable, and feature-rich web applications using proven object-oriented techniques. Written for the project manager, architect, analyst, designer, and programmer of web applications, this book examines the unique aspects of modeling web applications with the Web Application Extension (WAE) for the Unified Modeling Language (UML).

The book's collected articles offer important perspectives on the role of metrics in the development process, and show how metrics directly enhance software quality and output efficiency. The book explores several vital areas, including Function Point Analysis, project estimation and management, outsourcing, statistical process control, and more. These articles range from basic theory to the sophisticated application of metrics.

"I spend much time helping organizations capture requirements and even more time helping them recover from not capturing requirements. Many of them have gone through some motions regarding requirements, as if they were sleepworking. It's time to wake up, and do it right—and this book is going to be their alarm clock." (Jerry Weinberg, author of numerous books on productivity enhancement)

Most IT systems fail to meet expectations. They don't meet business goals and don't support users efficiently. Why? Because the requirements didn't address the right issues. Writing a good requirements specification doesn't take more time. This book shows how it's done -- many times faster and many times smarter.

Experience has shown us that investment in the requirements process saves time, money, and effort. Yet, development efforts consistently charge ahead without investing sufficiently in the requirements process. We are so intent to develop the technical solutions that we are unwilling to take the time and effort to understand and meet the real customer needs.

Use case analysis is a methodology for defining the outward features of a software system from the user's point of view. Applying Use Cases, Second Edition, offers a clear and practical introduction to this cutting-edge software development technique. Using numerous realistic examples and a detailed case study, you are guided through the application of use case analysis in the development of software systems.

(From the Back Cover)

Why do so many software projects fail? The reality is that many of these projects are led by programmers or developers thrown into the role of project manager without the necessary skills or training to see a project through successfully. Patricia Ensworth has written a hands-on survival guide designed to rescue the "accidental project manager" and help them to quickly ramp up on all key areas involved in software project management.

When your product development process fails, do you blame scarce resources or unforeseen technical challenges? Those may be factors, of course, but most product failures and development rework can be traced to a poor understanding of customer-centered needs and requirements. This book will show you, as a manager, how to prevent failure by guiding and empowering your people to define and understand the right requirements early in the product development cycle.

The hallmarks of Extreme Programming--constant integration and automated testing, frequent small releases that incorporate continual customer feedback, and a teamwork approach--make it an exceptionally flexible and effective approach to software development.

Derek Hatley and Imtiaz Pirbhai -- authors of Strategies for Real-Time System Specification -- join with influential consultant Peter Hruschka to present a much anticipated update to their widely implemented Hatley/Pirbhai methods.

Introduces a model for a mature software development process that accommodates flexibility, focusing on policies and procedures that define how software development is performed, and technologies available. Tells how to sell the business case for software process improvement, how to establish dialogue between developers and customers, and how to manage multiple constituencies, personalities, and issues.

This book presents an integrated framework for testing object-oriented software throughout the software engineering lifecycle. It discusses recipes for testing of requirements, designs, base classes, derived classes, and integrated systems. For each phase the authors describe objectives of testing, approaches used, testing techniques, ordered sets of activities, planned efforts, and acceptance criteria for transition to the next phase.

(From the Back Cover) * Reduce the incidence of duplicate and inconsistent requirements;
* Communicate requirements that are understandable to both users and developers;
* Communicate a vision of what the application needs to do without the distractions inherent in a coded prototype;
* Document the entire requirements process clearly and efficiently.

Does your company Web site convey your message effectively? Are your customers finding what they need easily? Determining these factors is a difficult task that has challenged Usability professionals since the first Web page was posted.

(Book Description)
The message of this book is simple. Software development should be done quickly and effectively. Systems that take years to develop can often end up out of synch. with their users evolving requirements and business objectives by the time they are delivered. Requirements Engineering and Rapid Development shows how to solve the problem by using a systematic approach to requirements gathering and business modelling.

A world-renowned technology expert reveals the true cost to business and society created by little-known problems rife within the software industry. Software kills? Yes. Industry insider Mark Minasi argues that it routinely destroys millions of work hours, files, deals, and ideas. Most of us are familiar with conputer problems, but how many realize that software victims also include people: a 7 year-old killed by bad fuel-injection software in a Chevrolet in Alabama, 28 U.S.

Cleanroom software engineering is a process for developing high-reliability software. The cleanroom process answers today's call for more reliable software and provides methods for more cost-effective software development. It accomplishes this by combining theory-based engineering technologies in project management, incremental development, software specification and design, correctness verification, and statistical quality certification.

This book is a comprehensive guide for the programmer or manager writing requirements for the first time, as well as the experienced system analyst.

The author takes a unique approach to the subject: that a useful requirements document derives from the design patterns employed by programmers and interface designers. His in-depth treatment includes non-hierarchical ways to break down complex problems, elements of the problem domain, and different problem types.

Web Site Usability: A Designer's Guide is a report that every person involved in Web design, commerce, or online marketing will want to have. This book is, undoubtedly, the most comprehensive data demonstrating how Web sites actually work when users need specific answers. Researched and compiled by User Interface Engineering, the results are written in an easy to understand style, illustrating the need to make Web sites useful, not complicated.

Requirements engineering is one facet of large project development that is often overlooked. If more effort is put into the definition and documentation of what the system is to do, the end result will be more reliable and easier to improve. Requirements need formal analysis and review before the work begins. This book provides a guide to do this in a rigid, structured manner that will produce documentation and test plans needed to design a successful system.

This book is the first professional-level guide in the important new field of software reuse. With the latest data on reuse, it explains the fundamental methods and metrics for successful reuse. Reuse has been called the central technical concept of the 1990s programming breakthrough: object technology. The book discusses object-oriented technologies, but goes well beyond them.

Although not a book focused on testing or Quality Assurance, this book provides and excellent introduction to the concept of "Electronic Commerce" (e-commerce). By understanding how e-commerce is supposed to function, a tester can gain critical insight into how to focus the testing efforts for a Web-based, e-commerce site.

This is the first book to offer a practical way to identify systems requirements and manage them when budgets and schedules are tight. It describes a process that leads from fuzzy, ill-defined requirements to requirements that can be modeled and prototyped.

This book is a collection of approximately seventy-five short pieces dealing with topics in the field of software requirements analysis, specification, and design.

This book is recommended reading for anyone in software development who has to honor a commitment. It examines the characteristics of risk in general and emphasizes the creative nature of such analysis. The coverage then turns to the establishment of an "optimum risk environment" and shows the reader how to manage this at every stage through successful project conclusion.

The author (from Telecom Australia) describes particular tools, usability testing, and evaluation procedures. Most of these have been derived from behavioral and social science, but have been updated specifically to the human-computer interaction environment. Numerous examples show how and when the tools can be used most effectively.

This book focuses on the early phases of the software development lifecycle. The author discusses the latest research results from the requirements arena and examines techniques that will lend themselves to your particular problem. Each technique is followed by a case study illustrating how that technique can be applied to three real problems. The book is recommended for the practicing systems engineer, software analyst, or requirements writer.

The creation of an effective design that satisfies the requirements is often the greatest obstacle to overcome during project development. This book discusses both specification and design, including software and systems engineering interface. It provides a consistent set of notations, guidelines, and a step-by-step process to explain the methodology.

This book is an expanded version and new edition of what used to be called Effective Methods of EDP Quality Assurance. New chapters include coverage verification, validation, testing techniques, maintenance, QA for the personal computer, and measuring reliability. With its appendices the book now extends over 800 pages and is hard to digest. The book contains a sample QA manual as an appendix. The book is worthwhile for the dedicated QA specialist or organization.

The fledgling problem solver invariably rushes in with solutions before taking time to define the problem being solved. Even experienced solvers, when subjected to social pressure, yield to this demand for haste. When they do, many solutions are found, but not necessarily to the problem at hand.

This is a superb book aimed at helping developers design products and systems that people really need and want. Nontheoretical and lots of fun, this is destined to become another Weinberg classic. Likening the requirements process to a process of exploration, the principles described apply wherever people design and build products for other people.

This book takes a lighthearted look at the very serious business of designing simple (and not so simple) everyday objects. The principles necessary to design ergonomically acceptable phone systems and swinging doors are the same principles needed to effectively design automated computer systems. Software engineers, designers, and requirements analysts will find this a rewarding and useful book.

More system development efforts fail due to poorly defined user requirements than any other cause. This book examines each facet of this critical activity and delineates a plan to systematically specify user-centered requirements. The book includes detailed discussion on three basic types of analysis: objective analysis, functional analysis, and data analysis.