[TOC]

Meetings schedule, agendas and minutes

Preliminary Pattern Catalog

These are all examples of the Lifecycle Integration Patterns User Group to discuss the pattern principles. If the User Group is successful, the pattern catalog should get a prominent place on open-services.net.

Use the Pattern Template below as a guide to contribute your own patterns. All types of Lifecycle Integration Patterns are welcome including very high level business scenarios and highly detailed technical implementations. We will use the category field in the pattern template to organize and group patterns that are at a similar level of detail. If a lifecycle integration pattern is helpful for your organization, contribute it to the list of patterns so that others can benefit from it and to drive further discussion and evolution of the specifications.

Pattern template:

• template [ [[template]] ]

First Pattern examples:

• Proxy Pattern [ [[prox]] ]
• other Proxy Pattern [ [[prox1]] ]

Pattern Categories:

• Category 1
• Category 2
• Category 100 (preliminary for test)
• …
• low level patterns
• business patterns

<pattern name>

• PatternID: <category#>.<sequ#>
• Name: <pattern name>
• Category: <category name. Categories are yet to be defined. Currently we anticipate “Business Scenario” patterns and lower level “Implementation” patterns that are can be combined to address integration needs.>
• Creation Date: <date>
• Creators: <creator1 name>, <creator2 name>
• Description: <description of the pattern (500 chars max). For Business Scenarios, include the business problem and business outcome of applying this pattern.>
• Stakeholder Roles: <What are the roles and responsibilities of the people who are experiencing the business challenge? Stakeholder roles might include business analysts, developers, testers, project managers, senior executives, or mechanical engineers, for example. >
• Systems of Record: <What are the systems of record used by the stakeholders that are require integration? Systems of Record might include an Agile software project management system, a test management tool, or a system for tracking the bill of materials for a physical product. >
• Key Artifacts: <What are the artifacts in each system of record that are used by the stakeholders and relevant for the collaboration across tools? E.g. Defect, Story, Test, Part, etc. >
• Link to related patterns: Proxy1 Pattern
• Example:<description of an example>
• Related Information: <title of related information> <http link to related information 2>
• Diagram: <Include sketches to illustrate the pattern (picture image)>

• PatternID: 100.001
• Name: Proxy Pattern
• Category: Category 1
• 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).
• Link to related patterns: Proxy1 Pattern
• 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 “Debunking the OSLC link-only myth”
• Diagram: … to be included : sketches to illustrate the pattern (picture image)

[TOC]

Meetings schedule, agendas and minutes

Preliminary Pattern Catalog

These are all examples of the Lifecycle Integration Patterns User Group to discuss the pattern principles. If the User Group is successful, the pattern catalog should get a prominent place on open-services.net.

Pattern template:

• template [ [[template]] ]

First Pattern examples:

• Proxy Pattern [ [[prox]] ]
• other Proxy Pattern [ [[prox1]] ]

Pattern Categories:

• Category 1
• Category 2
• Category 100 (preliminary for test)
• …
• low level patterns
• business patterns

• PatternID: <category#>.<sequ#>
• Name: <pattern name>
• Category: <category name>
• Creation Date: <date>
• Creators: <creator1 name>, <creator2 name>
• Description: <description of the pattern (500 chars max)>
• Link to related patterns: Proxy1 Pattern
• Example:<description of an example>
• Related Information: <title of related information> <http link to related information 2>
• Diagram: … to be included : sketches to illustrate the pattern (picture image)

• PatternID: 100.001
• Name: Proxy Pattern
• Category: Category 1
• 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).
• Link to related patterns: Proxy1 Pattern
• 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 “Debunking the OSLC link-only myth”
• Diagram: … to be included : sketches to illustrate the pattern (picture image)

[TOC]

Meetings schedule, agendas and minutes

Preliminary Pattern Catalog

These are all examples of the Lifecycle Integration Patterns User Group to discuss the pattern principles. If the User Group is successful, the pattern catalog should get a prominent place on open-services.net.

Pattern template:

• template [ [[template]] ]

First Pattern examples:

• Proxy Pattern [ [[prox]] ]
• other Proxy Pattern [ [[prox1]] ]

Pattern Categories:

• Category 1
• Category 2
• Category 3
• …
• low level patterns
• business patterns

[TOC]

Meetings schedule, agendas and minutes

Pattern Catalog

First Pattern examples:

• Proxy Pattern [[prox]]
• other Proxy Pattern [[prox1]]

Pattern Categories:

• Category 1
• Category 2
• Category 3
• …

[TOC]

Meetings schedule, agendas and minutes

Pattern Catalog

First Pattern examples:

• Proxy Pattern [[prox]]
• other Proxy Pattern [[prox1]]

Pattern Categories:

• Category 1
• Category 2
• Category 3
• …

• PatternID: 100.001
• Name: Proxy Pattern
• Category: Category 1
• 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).
• Link to related patterns: Proxy1 Pattern
• 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 “Debunking the OSLC link-only myth”

• PatternID: 100.001
• Name: Proxy Pattern
• Category: Category 1
• 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).
• Link to related patterns: Proxy1 Pattern
• 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.

[TOC]

Meetings schedule, agendas and minutes

First Pattern examples:

• Proxy Pattern [[prox]]
• other Proxy Pattern [[prox1]]

Pattern Categories:

• Category 1
• Category 2
• Category 3
• …

• PatternID: 100.002
• Name: the other Proxy Pattern
• Category:
• Creation Date:
• Creators:
• Description: the other proxy …
• Link to related patterns: Proxy Pattern
• Example: example for the prox1

• PatternID: 100.001
• Name: Proxy Pattern
• Category:
• Creation Date:
• Creators:
• 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).
• Link to related patterns: Proxy1 Pattern
• 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.

• PatternID: 100.001
  • Name: Proxy Pattern
  • Category:
  • Creation Date:
  • Creators:
  • 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).
  • Link to related patterns:
  • 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.

[TOC]

Meetings schedule, agendas and minutes

First Pattern examples: - Proxy Pattern [[prox]]

[TOC]

Meetings schedule, agendas and minutes

Meeting Schedule: