Populating Requirements into PLM Tools

Pattern name: Requirements Visibility in PLM

About this Pattern

PLM tools are central to organizations developing products that combine both hardware and software components. The complexity of these products often requires both PLM and ALM tool stacks, which are not commonly integrated. Both product management and the development teams can greatly benefit from an integration that creates powerful automated workflows that bridge the two stacks. 

This pattern represents one such workflow, whereby requirements created in a best-in-class Requirements Management tool (e.g., Jama, IBM DOORS NG, Sparx EA) automatically flow to a PLM tool (e.g., Aras or Windchill) where they can be consumed and referenced. Thus, the entire organization can use one purpose-built tool to manage both the hardware and software requirements, and any changes to requirements' basic and custom data fields will be reflected in PLM. 

Integration Pattern Populating Requirements into PLM Tools

Benefits

  • Reduce errors in product data and eliminate rework
  • Streamline the design-to-manufacturing workflow 
  • Create efficient traceability back to the originating requirement

Artifacts Typically Synchronized

Implementation Artifacts

PLM Artifacts

  • Requirements

  • Requirements