Software Requirements • Boise, ID

Attend a Software Requirements course in the BOISE area:

Course Guide

Attendee Reviews

Course Overview

Benefits

• Learn to identify requirement sources
• Learn to overcome common requirements errors
• Learn various ways to write requirements
• Learn elicitation goals and techniques
• Learn Use Case diagramming using free UML tools
• Learn to construct data-flow diagrams
• Learn to prioritize project requirements
• Learn to identify and qualify project risks
• Learn to create a Work Breakdown Structure (WBS)
• Learn how a project progresses through the PRD to HLA to SRS
• Learn to create a High Level Analysis (HLA) document
• Learn to create a Software Requirements Specification (SRS) document
• Learn to build a product roadmap
• Learn the five types of software estimates
• Learn to align project requirements with business goals
• Learn about upstream and downstream traceability
• Learn to manage scope creep via change control
• Learn to conduct proper requirement approvals, and effectively
  manage approval noise
• Learn effective interviewing techniques for in-house and off-site
  stakeholders and subject matter experts
• Learn the value of a requirements showcase

Software Requirements Course Overview

Our course contains the following program:

Part I - A Business Case for Improving Requirement Skills

• How critical are requirements development skills to the overall success of a software project?
• Software project success rate trends.
• Common challenges facing requirements management.
• What you should know about requirements errors.
• Ten unavoidable truths about software requirements.

Part II - Understanding Software Requirements

• Who gathers requirements?
• What is the role of the requirements gatherer?
• Sources of requirements.
• What is a requirement?
  a. PMI� definition
  b. iEEE� definition
• Domain, Problem Space, Solution Space
• What a requirement isn't!
• Types of requirements:
  a. Governing requirements
  b. Emergent requirements
  c. Component requirements
• Business Rules:
  a. Sources of Business Rules
• Parts of a requirement:
  a. The Identifier
  b. The Classifier
  c. The Description
  d. The Constraint
• Example Requirement
• Test-driven requirements
• Requirement Traceability
• Some common ways to write requirements:
  a. Natural form
  b. Formal form
  c. Use cases
  d. User stories
• What to do with unknown requirements.

Part III - How to structure software requirements documents

• Survey of software project types.
• Documentation Audiences.
• Documentation and Trust.
• How much time is typically spent on Requirements?
• How to speed up the requirements process.
• How to structure requirement documents.

Part IV - A requirements baseline development framework

• A Process for gathering requirements:
  a. Elicitation
  b. Analysis
  c. Specification
  d. Validation
• Requirements elicitation.
• Requirements analysis.
  a. Prioritizing requirements:
      i. Risk driven prioritization
      ii. Critical path prioritization
      iii. Strategic prioritization
• Requirements specification.
  a. HLA, SRS, SDD, COO
• Requirements validation.
• Requirement �baseline� approval.
• The approval process.

PART V - After the baseline

• Triple constraint project dynamic
• Managing change: Change Control
• Keeping a change history log
• Managing schedule impact

Part VI - Collaboration

• Interviewing etiquette
• Questioning techniques
• Active listening
• Group dynamics
• Five dysfunctions of a team
• Meeting etiquette
• Facilitation and facilitative workshops
• Negotiation
• Handling special situations

Part VII - Improving your skills going forward

• Four strategies to improve your requirements management performance going forward.

Software Requirements Activities

Improve Productivity