logo
ABD
LiveZilla Live Chat Software



Training Presentation Systems Services & Consulting Cloud Services Purchase Client Center Computer Museum
Arrow Course Schedule | Classroom Rentals | Student Information | Free Seminars | Client Feedback | Partners | Survey
While System Source is working from home, we are still available for all of your calls and support needs.
Requirements Management
COST: $1295

10/26/20 | 12:00pm - 4:30pm Virtual-Instructor Led
10/27/20 | 12:00pm - 4:30pm Virtual-Instructor Led
10/28/20 | 12:00pm - 4:30pm Virtual-Instructor Led
Sign-In

Email

Password      Forgot your password?

PAYMENT by CREDIT CARD
First Name        Last Name
 
Company

Addr

City                    State      Zip
 
Card Number

Month   Year          Verification Code
     
     -or- Pay By PO

New to System Source?


(You will be brought back once your account is created)
Or Call (410)771-5544 x5

In this business analysis course, you will learn how to manage requirements and requirement designs throughout the whole solution development life cycle, using a structured and standardized approach based on latest "Business Analysis Body of Knowledge" (BABOKTM) from IIBATM and various sources from PMITM.

Requirements Life Cycle Management is one of the six knowledge areas identified in BABOKTM and describes the tasks required to manage and maintain requirements and design information from their inception to their retirement. These tasks include establishing and maintaining meaningful traceability between related requirements, designs, and other related elements/components, maintaining requirement attributes/properties, prioritizing requirements, assessing impacts of requirements and/or requirement changes, and gaining consensus and approval on which requirements/designs to implement.

The purpose of requirements life cycle management is to ensure that:

  • business, stakeholder, and solution requirements and designs are aligned to one another
  • requirements attributes/properties (e.g. status, priority, etc.) are well maintained/tracked, communicated, and understood by all stakeholders
  • solution implements requirements/designs that are in-scope and have been approved
  • project teams have the required means and information to assess impact of proposed requirements and requirement changes
  • targeted requirements/designs are developed and maintained for reuse (within or across projects)

Trace requirements' relationships to/from other requirements and to/from other elements upstream (e.g. enterprise goals/objectives, mission/vision, values) and/or downstream (e.g. design/architecture, implementation components, testing, etc.)

Capture/maintain requirements' attributes (e.g. type, status, functional area, release, complexity, etc.)
Assess and prioritize requirements (e.g. based on value to organization, value to customers, compliance, risks, etc.)
Manage changes to requirements (e.g. identify and assess requests to change, analyze/document changes, create a business case, evaluate and approve changes, monitor change implementation, track changes, etc.)
Manage project/product scope (e.g. define scope, agree/approve changes, avoid scope creep/gold plating)
Plan, monitor and control implementation of requirements/design
Manage requirements quality (e.g. identify missing/incomplete and/or bad requirements)
Analyze impact of proposed changes to requirements/design
Plan/optimize resource utilization
Reuse requirements within and across projects and solutions