- Categories
- Acceptance Testing
- Agile Business Analysis
- Best Practices
- Business Analysis and Systems Analysis
- Business Analysis Planning and Monitoring
- Business Process Modeling (BPM)
- Business Rules
- Conducting Meetings
- Data Modeling, Data Analysis, Data Mining
- Enterprise Analysis
- Facilitation
- IIBA, BABOK, and CBAP certification
- JAD
- Making Teams and Virtual Teams Work
- Problem Analysis, Problem Solving
- Process Analysis
- Prototyping
- Request for Proposal (RFP)
- Requirements Analysis
- Requirements Documentation
- Requirements Elicitation
- Requirements Engineering
- Requirements Management
- Requirements Specifications
- Requirements Traceability
- Requirements Validation
- Software Testing and Test Cases
- System Development Life Cycles
- Test Data Engineering
- Test Planning
- Testing Tools
- Testing Web Applications and Web Services
- Unified Modeling Language (UML)
- Usability
- Use Cases and User Stories
- User Interfaces
- Workflow Analysis
Business Analysis for Information Technology
Books and Selected Products
More About Software Requirements: Thorny Issues and Practical Advice
Microsoft Press
January 2006
Paperback, 224 pages
ISBN: 0735622671
On-Site and On-Line Training Courses for Business Analysts All About Use Cases
How to Analyze Sets of Business Requirements
How to Elicit (Gather), Write, and Analyze Business Requirements
How to Elicit Business System Requirements
How to Estimate Early in a Project
How to Initiate Requirements Gathering with User Stories
How to Manage and Communicate Requirements
How to Manage Changing Requirements
How to Model, Analyze, and Improve Business Data
How to Model, Analyze, and Improve Business Processes
How to Plan and Monitor Business Analysis Activities
How to Write Effective Business Requirements
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 and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project.
Discover how to:
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 and bolts of documenting requirements, this essential companion gives developers, analysts, and managers the cosmic truths that apply to virtually every software development project.
Discover how to:
- Make the business case for investing in better requirements practices
- Generate estimates using three specific techniques
- Conduct inquiries to elicit meaningful business and user requirements
- Clearly document project scope
- Implement use cases, scenarios, and user stories effectively
- Improve inspections and peer reviews
- Write requirements that avoid ambiguity
About the Author:
Karl E. Wiegers, Ph.D., is Principal Consultant with Process Impact, a software process consulting and education company in Portland, Oregon. Previously, he spent 18 years at Eastman Kodak Company, where he held positions as a photographic research scientist, a software applications developer, a software manager, and a software process and quality improvement leader. He has led process–improvement activities for small teams, for a division of 500 software engineers building Kodak s digital imaging products, and for the Kodak Internet development group. His writing and teaching are based largely on his experience in improving development processes, technical practices, and quality practices in all these environments, as well as incorporating experiences drawn from his dozens of consulting clients. Karl is the author of three previous books, and he has written more than 160 articles on software engineering and management, chemistry, and military history during the past 30 years. He is a frequent speaker at software conferences, public seminars, and professional society meetings. As an independent consultant, Karl presents training seminars and consulting engagements at companies worldwide on requirements engineering, software peer reviews, process improvement, risk management, and related topics. He has worked with nearly 80 companies and government agencies in many different industry sectors since 1997.
Business Analysis for Information Technology deals
