You may have to Search all our reviewed books and magazines, click the sign up button below to create a free account.
In Software Requirements, you'll discover practical, effective techniques for managing the requirements engineering process all the way through the development cycle--including tools to facilitate that all-important communication between users, developers, and management. Use them to: Book jacket.
No matter how much instruction you’ve had on managing software requirements, there’s no substitute for experience. Too often, lessons about requirements engineering processes lack the no-nonsense guidance that supports real-world solutions. Complementing the best practices presented in his book, Software Requirements, Second Edition, requirements engineering authority Karl Wiegers tackles even more of the real issues head-on in this book. With straightforward, professional advice and practical solutions based on actual project experiences, this book answers many of the tough questions raised by industry professionals. From strategies for estimating and working with customers to the nuts ...
Zero in on key project-initiation tasks—and build a solid foundation for successful software development. In this concise guide, critically-acclaimed author Karl E. Wiegers fills a void in project management literature by focusing on the activities that are essential—but often overlooked—for launching any project. Drawing on his extensive experience, Karl shares lessons learned, proven practices, and tools for getting your project off to the right start—and steering it to ultimate success. Lay a foundation for project success—discover how to: Effectively charter a project Define meaningful criteria for project success and product releases Negotiate achievable commitments for project teams and stakeholders Identify and document potential barriers to success—and manage project risks Apply the Wideband Delphi method for more accurate estimation Measure project performance and avoid common metrics traps Systematically apply lessons learned to future projects Companion Web site includes: Worksheets from inside the book Project document templates Resources for project initiation and process improvement
This is the digital version of the printed book (Copyright © 1996). Written in a remarkably clear style, Creating a Software Engineering Culture presents a comprehensive approach to improving the quality and effectiveness of the software development process. In twenty chapters spread over six parts, Wiegers promotes the tactical changes required to support process improvement and high-quality software development. Throughout the text, Wiegers identifies scores of culture builders and culture killers, and he offers a wealth of references to resources for the software engineer, including seminars, conferences, publications, videos, and on-line information. With case studies on process improve...
This volume in the Business Analysis Professional Development Series by renowned expert and best-selling author, Karl Wiegers, and a group of noteworthy contributors, provides experienced, advanced-level business analysis and project management practitioners with proven strategies and tips for making the successful transition from highly respected internal expert to a fulfilling and financially rewarding career in consulting. Key Features: Addresses how to effectively lay the foundation and structure of your consulting business; how to deal with or avoid the many pitfalls of working outside the corporate world and working remotely from home; and how to balance life, family, and work Presents...
This practical introduction to peer reviews covers different methods of peer review, from the formal method of inspection to other less formal methods, and addresses the cultural and practical aspects of both.
Learn effective, field-tested techniques to manage the requirements engineering process and get expert guidance from a leading requirements engineering authority. This updated edition features sample documents, a troubleshooting guide, and case examples.
This book describes how to gather and define software requirements using a process based on use cases. It shows systems analysts and designers how use cases can provide solutions to the most challenging requirements issues, resulting in effective, quality systems that meet the needs of users. Use Cases, Second Edition: Requirements in Context describes a three-step method for establishing requirements—an iterative process that produces increasingly refined requirements. Drawing on their extensive, real-world experience, the authors offer a wealth of advice on use-case driven lifecycles, planning for change, and keeping on track. In addition, they include numerous detailed examples to illus...
Have you ever noticed how many products appear to be designed by someone who has never used a product of that kind before? Nearly everyone has encountered websites, software apps, cars, appliances, and other products that made them wonder what the designers were thinking. The Thoughtless Design of Everyday Things presents more than 150 examples of products that violate nine fundamental design principles, along with suggestions for improving many of the flawed user interfaces and other design problems. These examples of thoughtless design reveal 70 specific lessons that designers ought to heed as they craft the user experience. This book describes numerous specific practices for enhancing product usability through usage-centered design strategies. You'll also see more than 40 products that exhibit particularly thoughtful designs, the kinds of products that surprise and delight users. Whether you're a designer, a product development manager, or a thoughtful and curious consumer, you'll find The Thoughtless Design of Everyday Things engaging, informative, and insightful.
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 ...