Contributors can use the fields in this template to describe lifecycle integration patterns. All patterns should have a Pattern ID, name, and description. Use additional fields as needed to describe your pattern. Not all fields will be applicable for all categories of patterns. The template is extensible and contributors can freely add new fields as needed.
<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)>
