Developer Tester Proxy Pattern - OSLC/lifecycle-integration-patterns GitHub Wiki

PatternID: 100.001

Name: Developer-Tester Proxy Pattern

Category: Business Scenario

Creation Date: 2017-06-12

Creators: Rainer Ersch, Wesley Coelho

Description: If an expert tool needs to include artifacts from other repositories to connect them with local information, it is not always possible to do this only through external LinkedData references. In such cases, it is a good practice to create a local proxy object with the minimum information required for the local function and an reference link to the original object. Such a proxy object could be automatically created or updated in an earlier process step through OSLC CRUD services (e.g. when a consolidated set of this object type is available in the original repository).

Stakeholder Roles: Software Developer, Software Tester (QA)

Systems of Record: Agile Project Management System, Quality Management System

Key Artifacts: Story, Requirement, Test Case, Defect

Link to related patterns: N/A

Example: When a Requirements Baseline is released (has reached a certain majority) in the Requirements Repository, a set of proxy objects for this baseline with just ID, short description and link back to the requirement could be created in the Quality Management Repository to allow a tester to relate the test cases to. This enables the use the build in functions of the QM tool (e.g. coverage report) as well as a trace across the repository for other tool spanning reports and collaborations.

Related Information: See blog post of Wesley Coelho and Rainer Ersch See blog post of Wesley Coelho and Rainer Ersch “Debunking the OSLC link-only myth”

Diagram: