Your browser does not support JavaScript!
  • LinkedIn
  • YouTube
  • RSS

XM Patterns

Just as software design patterns have dramatically accelerated the speed of quality software development, we are seeing hardware design patterns provide repeatable solutions to common challenges faced by hardware scrum team. The “Gang of Four” format is being used to describe patterns:

  • Pattern Name and Classification: A descriptive and unique name that helps in identifying and referring to the pattern.
  • Intent: A description of the goal behind the pattern and the reason for using it.
  • Also Known As: Other names for the pattern.
  • Motivation (Forces): A scenario consisting of a problem and a context in which this pattern can be used.
  • Applicability: Situations in which this pattern is usable; the context for the pattern.
  • Structure: A graphical representation of the pattern. Class diagrams and Interaction diagrams may be used for this purpose.
  • Participants: A listing of the classes and objects used in the pattern and their roles in the design.
  • Collaboration: A description of how classes and objects used in the pattern interact with each other.
  • Consequences: A description of the results, side effects, and trade offs caused by using the pattern.
  • Implementation: A description of an implementation of the pattern; the solution part of the pattern.
  • Sample Code: An illustration of how the pattern can be used in a programming language.
  • Known Uses: Examples of real usages of the pattern.
  • Related Patterns: Other patterns that have some relationship with the pattern; discussion of the differences between the pattern and similar patterns.

This page was adapted from Hubert Smit's work on XM patterns.

Abstract Factory
Pattern: Provide an interface for creating families of related or dependent objects without specifying their concrete classes.

 

Builder
Pattern: Separate the construction of a complex object from its representation, allowing the same construction process to create various representations.

 

Factory Method
Pattern: Define an interface for creating a single object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.

 

Lazy Initialization
Pattern: Tactic of delaying the creation of an object, the calculation of a value, or some other expensive process until the first time it is needed. This pattern appears in the GoF catalog as “virtual proxy," an implementation strategy for the Proxy pattern.

Also see: Proxy Pattern 

 

Multiton
Pattern: Ensure a class has only named instances, and provide a global point of access to them.

 

Object Pool
Pattern: Avoid expensive acquisition and release of resources by recycling objects that are no longer in use. Can be considered a generalization of connection pool and thread pool patterns.

Also see: Connection pool and Thread pool

 

Prototype
Pattern: Specify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototype.
Resource Acquisition is Initialization
Pattern: Ensure that resources are properly released by tying them to the lifespan of suitable objects.

 

Singleton
Pattern: Ensure a class has only one instance, and provide a global point of access to it.

 

Object Library
Pattern: Encapsulate object management including factory interface with live and dead lists.

 

Related Open Topics:

Scrum for Hardware: eXtreme Manufacturing

Scrum for Hardware: Full Scale Manufacturing

Back to all Open Topics

6 Agile Ways To Increase Employee Engagement

employee support

Organizations who utilize Agile ways of working experience a 20-30% improvement in employee engagement. Engage, Equip & Empower your employees.

learn more button click here

Categories:

en_USEnglish
fr_FRFrench es_ARSpanish en_USEnglish
Shares