2.110.1  Requirements Engineering Directive

Manual Transmittal

February 15, 2013


(1) This transmits new IRM 2.110.1, Requirements Engineering, Requirements Engineering Directive.

Material Changes

(1) This directive establishes Requirements and Demand Management authority and responsibility for the definition of Requirements Development and Requirements Management process areas; hereafter referred to as Requirements Engineering and defines the essential Requirements Engineering practices that all software development projects should employ.

  • This IT Directive supersedes the MITS Requirements Development Directive, V1.0, dated 04/2006

Effect on Other Documents



This Directive is applicable to all IRS managers, personnel, and executives who manage, directly support, or provide oversight to projects following the Information Technology Services Enterprise Life Cycle.

Effective Date


Terence V. Milholland
Chief Technology Officer  (02-15-2013)

  1. Requirements Engineering Directive  (02-15-2013)

  1. Requirements and Demand Management (RADM) is responsible for the development, implementation, and maintenance of this directive. All proposed changes to this directive must be submitted to Requirements and Demand Management.  (02-15-2013)
Purpose of Directive

  1. The purpose of this directive is to establish RADM's authority and responsibility for the definition of Requirements Development and Requirements Management process areas, hereafter referred to as Requirements Engineering (RE), on business change, software development, system integration, and legacy system upgrade projects, hereafter referred to as "projects", throughout IT. This directive clarifies expectations required for RADM to support the establishment and advancement of the RE discipline, and the expectations of all projects in execution and implementation of the RE discipline within the Internal Revenue Service (IRS).  (02-15-2013)

  1. All projects following the Enterprise Life Cycle (ELC) are required to perform requirements engineering processes and associated activities in accordance with this directive.  (02-15-2013)

  1. Organizational Directives: RADM also provides and facilitates: RE Definition, RE Education and Training; RE Mentoring and Coaching; RE Product Quality Assessments and Process Compliance; and RE Process Improvement.

    • Definition: RADM is responsible for defining, developing, updating, and institutionalizing the RE discipline to facilitate project implementation of quality requirements that accurately reflect the needs of the business and its customers. Definition also applies to establishing standards in appropriate tools that enable RE implementation consistent with the RE methodology.

    • Education and Training: RADM is responsible for making education and training available to personnel in overall RE methodology, supporting best practices, tailoring, RE methodology implementation against development life cycles, and use of supporting requirements tools.

    • Mentoring and Coaching: RADM assists and partners with program and project teams to promote implementation of the RE discipline towards the clear definition of project scope and the development of a solution that meets the business needs. RADM provides available support for the development and management of requirements through all phases of the ELC.

  2. The level of RADM service provided to a project team will be determined based on project characteristics such as organizational priority, strategic value to IRS, criticality, lifecycle phase, and the status of RE activities on the project. The level of service will be agreed upon by RADM, Business Executives, and the Project Manager; and can also depend upon RADM resource capacity, and the project funding constraints. The three levels of service are defined as:

    • Level 1. Coaching and Self-service - RADM provides guidance to projects in a mentoring capacity to direct projects in RE implementation, and includes work product/deliverable review and sign-off. RADM also provides access to RE-related standards, guidelines, templates, Data Item Descriptions (DIDs), and other tools via the RADM web site. This level of project interaction requires minimal involvement of RADM staff, and provides the foundation for more interactive levels of service.

    • Level 2. Consulting - RADM analysts provide the project team with support for requirements planning, requirements product tailoring, requirements development, requirements management, training, troubleshooting, and requirements verification services on an as requested basis. This level of direct support requires that project funding be transferred to RADM.

    • Level 3. Embedded Analysts - RADM analysts are an embedded part of the project team. They lead the development of requirement related work products and deliverables for the project. This level of support typically applies to a limited number of projects, and requires that project funding is transferred to RADM.

  3. Product Quality Assessments and Process Compliance: RADM will serve in a review and advisory capacity for process implementation on projects, providing approval authority of selected work products and artifacts developed by a project or program as prescribed within the ELC.

  4. Process Improvement: RADM will revise and extend the RE definition, training and coaching services execution, based on feedback from project implementation, training, and coaching activities.

  5. Project Directives: All project RE activities shall be planned, managed, implemented, and controlled in accordance with RADM guidance, applicable IRS policies, and IT directives, processes, and procedures.

    • Develop, maintain, and execute a project requirements plan that supports the implementation of RE standards defined by RADM.

    • Identify responsibilities for performing the RE activities, including stakeholders who may affect or be affected by RE activities.

    • Monitor project performance of the RE process against the plans that define and control development activities (e.g., Requirements Plan, Work Breakdown Structure) and take appropriate corrective action when necessary.

    • Ensure training is received by personnel on the objectives, processes, and procedures for performing RE activities according to RADM defined methodologies.

    • Place RE work products under appropriate Configuration Management (CM) levels of control in accordance with IRS CM policies, directives, processes, and procedures; and in support of the reporting standards established within the ELC DIDs.

    • Manage requirements and requirement components using standard tools and templates defined by RADM, and in a manner consistent with the defined RE guidance.

    • Identify and involve stakeholders who may affect or be affected by the project implementation or end product in the RE processes throughout the project lifecycle.

    • Tailor the RE process in a manner that does not conflict or comprise the RE discipline defined by RADM, and obtain appropriate tailoring approval from RADM.

    • Objectively evaluate project adherence to applicable RE methodologies on a periodic and event-driven basis.

    • Utilize the ELC reviews and deliverables for management review and insight into RE status and methodology execution of RE-related activities.

    • Submit ELC deliverables that require RADM approval or concurrence to RADM for review and approval.

    • Select appropriate requirements elicitation techniques and conduct elicitation to ensure stakeholder and user needs are captured.

    • Define system scope and develop solution concept diagrams and scenarios as necessary to identify system interfaces and to further refine scope.

    • Define system scope and develop solution concept diagrams and scenarios as necessary to identify system interfaces and to further refine scope.

    • Analyze requirements, develop models (e.g., business process, data, interface, system), and perform verification activities (e.g., peer reviews) in accordance with RADM methodology for establishing well-defined requirements.

    • Perform ongoing and final requirements validation activities to ensure user needs are satisfied.

    • Prioritize, allocate, and develop release strategies for requirements to balance user needs and objectives with other constraints of the project.

    • Identify and manage changes to requirements so that mutual agreement is established with stakeholders on appropriate adjustments to scope, resources, and/or schedule.

    • Create and maintain requirement traceability that results in an integrated set of requirements, work products, and components so that projects:

      • create requirements traceability between higher and lower level requirements,

      • create or ensure traceability to Enterprise Architecture Processes and/or Functional Requirements,

      • create traceability or directly allocate Reusable Program Level Requirements to the system,

      • document requirements traceability as necessary from a requirement to its allocation of functions, objects, people, processes, and work products (e.g., traceability between requirements and design components, testing artifacts, or organizations responsible for implementing the requirement),

      • document traceability as necessary from function to function and across interfaces (e.g., traceability from one project to a related project).  (02-15-2013)
Waivers and Deviations

  1. Any waivers or deviations of this directive require written approval from Requirements and Demand Management.  (02-15-2013)
Authority and Reference Documents

  1. The following lists the regulatory documents that validate the Requirements Engineering Directive:

    1. Treasury Directive 84-01, Information System Life Cycle.

    2. Requirements Management Office Concept of Operations, Version 1.0, March, 2005.

    3. Capability Maturity Model® Integration (CMMI) v1.31.

    4. GAO report number 06-310 IRS Need to Complete Recent Efforts to Develop Policies and Procedures to Guide Requirements Development and Management, March 2006

More Internal Revenue Manual