Requirement Management/Engineering for Effective Software Quality Management (CSQM #8) or (AKA #1) or (CTM Elective) or (CSTP Elective) or (CSTAS Elective)

This course covers the CSQM area #8 of the Certified Software Quality Manager requirements. This course also covers AKA area #1 of the International Software Process Improvement Certification (ISPIC) requirements. This course also covers the Elective area for the Certified Test Manager (CTM) certification and the Test Professional Body of Knowledge and the CSTAS certification.

For costs and cities where this course might be offered, please see the right border of this page or to bring this course to your test team at your location, contact our Education and Professionals Services Group.

Concepts

Understanding, articulating, and managing requirements is the most important and often weakest link in systems development.  Managing system quality therefore starts with managing the quality of the requirements and of the requirements process.  Too often, common characterizations as “requirements engineering” and “requirements management” create silos that actually compromise the quality of requirements and resulting development.  This interactive workshop describes the full requirements process, identifying common issues and what’s needed beyond requirements engineering and requirements management.  The course also explains how to promote, measure, and manage the quality of requirements process activities and their contributions to system quality throughout the requirements process.  Exercises enhance learning.

WHO SHOULD ATTEND:  This course has been designed for process and quality specialists, managers, analysts, designers, programmers, testers, auditors, and users who are concerned about the efficiency and effectiveness of software development and support.

Participants will learn:

• Role and importance of requirements in managing system quality.
• What the full requirements process should be.
• Commonly recognized and unrecognized issues with requirements and the requirements process.
• What requirements engineering and requirements management include and what they miss.
• Distinctions between REAL business requirements and product/system/software requirements.
• Suitable uses and limitations for common requirements documention formats, including use cases.
• Ways to check the clarity, testability, and correctness of requirements.
• Managing the quality of requirements and the requirements process.

Outline

• REQUIREMENTS AND SYSTEM QUALITY
  • Requirements relation to value
  • Role of requirements in the software process
  • Sources and economics of system errors
  • Quality management and requirements
  • Measuring requirements quality, effects
  • Requirements engineering, management
  • Traceability, issues and considerations, tools
  • Controlling changes, Change Control Board
  • Commonly-distinguished requirements types
  • Conventional creep explanations
  • Business vs. product/system requirements
  • Levels of detail/abstraction model flaws
  • Reducing real main cause of creep
  • Requirements relation to UAT, testing
• REQUIREMENTS PROCESS & QUALITY
  • Place in Proactive Testing™ Life Cycle
  • Business Analysis Body of Knowledge view
  • Business analysis planning
  • Enterprise analysis
  • Elicitation
  • Requirements analysis
  • Solution assessment and validation
  • Requirements management, communication
  • Requirements analysis projects to manage
• DEFINING REQUIREMENTS
  • Why conventional elicitation misses so much
  • Problem Pyramid™ tool to get on track
  • Data gathering techniques, why we do it
  • Generic vs. domain-specific analysis
  • Non-functional/quality requirements, traps
  • Evaluating, reviewing requirements
  • Format, clarity, and testability
  • Identifying overlooked requirements
  • Finding incorrect, incomplete requirements
  • Roles of the business analyst, QA/Tester
• DOCUMENTING REQUIREMENTS
  • Formats to aid understanding of the data
  • Business rules, decision trees and tables
  • E-R, data flow, flow, organization diagrams
  • Data models, process maps, forms, statistics
  • Formats for communicating requirements
  • IEEE standard for software requirements
  • Use cases, strengths and warnings
  • 7 guidelines for documenting requirements
  • Conceptual system design solutions
  • Functional specifications, the system shall...
  • Negotiating implementation scope, tradeoffs
  • Iterating to detail to avoid analysis paralysis