Requirements Driven Development (2G4)

Requirements Driven Development (2G4)

With Requirements Driven Development, you can link requirements and block definition diagrams to product lifecycle management objects such as document info records, materials, and configurable BOMs.

Usually, the Systems Engineer creates requirements models to link different products to block definition diagrams.

Key Process Steps Covered

  • Create requirements
  • Create block definition diagrams
  • Link the requirements to the block definition diagram
  • Link the design document, configuration profile, or material to the block definition diagram

Benefits

  • Use linked requirements to PLM objects to ensure consistency between defined requirements and changes during product development
  • Plan for intended changes with the support of impact analysis
  • Ensure the fulfillment of all requirements during the product-design process

Where is Requirements Driven Development(2G4) being used?

This Scope item is used in the following way:

  • As a core function of Product Lifecycle Management within R&D/Engineering Scope Item Group

Process flow of Requirements Driven Development (2G4)

Find below the process flow of the scope item Requirements Driven Development as it is defined for release s4hc-2111.


Download Process Flow of Best Practice scenario Requirements Driven Development (2G4) - S/4HANA Cloud
Ref: R&D/Engineering of SAP S4HC-2111
Best Practices related to S/4HANA*1) Yearly Updates are released per September of each year
*2) The Quarterly updates are released per Februari, May, August and November
Details of future releases can be found in the SAP Roadmap section of each product. Go to SAP Roadmap Product Finder.
Knowledge Center Scheer Nederland | The Process Experts Visit also the SAP Cloud ERP knowledge center of Scheer Netherlands. The following topics are covered:
Place comment