CSC/ECE 517 Fall 2009/wiki2 12 PatternClassification - Revision history

Cybo: /* Links */

2009-10-15T01:56:45Z

Links

← Older revision		Revision as of 01:56, 15 October 2009
Line 99:		Line 99:


	= Links =		= Related Links =

	* [http://www.cs.helsinki.fi/u/salaakso/patterns/index.html User Interface]		* [http://www.cs.helsinki.fi/u/salaakso/patterns/index.html User Interface]

Cybo: /* Discipline */

2009-10-15T01:55:58Z

Discipline

← Older revision		Revision as of 01:55, 15 October 2009
Line 91:		Line 91:

	== Discipline ==		== Discipline ==
			It is perhaps the easiest and most natural way to classify patterns, i.e. categorize them according to a field or discipline where they are used, i.e. music, engineering, or economy. It is unlikely (but not impossible) that a pattern used in one discipline becomes relevant to another.

	= Article Definitions =		= Article Definitions =

Cybo: /* Problem */

2009-10-15T01:52:54Z

Problem

← Older revision		Revision as of 01:52, 15 October 2009
Line 20:		Line 20:
	The problem with patterns is classification and recognition or usage, i.e. what type of patterns to use for each given case. For example, a pattern that is not classified correctly will not be remembered and used. Several attempts to classify patterns has been made. The existing software classification of patterns uses the categories of:		The problem with patterns is classification and recognition or usage, i.e. what type of patterns to use for each given case. For example, a pattern that is not classified correctly will not be remembered and used. Several attempts to classify patterns has been made. The existing software classification of patterns uses the categories of:

	# Structural		* Structural
	# Behavioral		* Behavioral
	# Creational		* Creational

	While these are good starting points for patterns, it is very hard to make use of this information in different contexts.		While these are good starting points for patterns, it is very hard to make use of this information in different contexts.

Cybo: /* Scope */

2009-10-15T01:51:33Z

Scope

← Older revision		Revision as of 01:51, 15 October 2009
Line 88:		Line 88:

	== Scope ==		== Scope ==
			Scope classification is categorization of patterns according to features implemented in a given pattern. As an example in [http://en.wikipedia.org/wiki/Object-oriented_programming object-oriented design] patterns can be classified using either class inheritance or object composition

	== Discipline ==		== Discipline ==

Cybo: /* Purpose */

2009-10-15T01:46:02Z

Purpose

← Older revision		Revision as of 01:46, 15 October 2009
Line 80:		Line 80:

	'''Architectural support patterns''' - represent the strategic decisions for the organization of real-time applications.		'''Architectural support patterns''' - represent the strategic decisions for the organization of real-time applications.

	'''Collaboration and distribution''' - patterns provide solutions to common application domain problems in real-time systems.		'''Collaboration and distribution''' - patterns provide solutions to common application domain problems in real-time systems.

	'''Safety and reliability patterns''' - deal with common problems of safety and reliability.		'''Safety and reliability patterns''' - deal with common problems of safety and reliability.

	'''Behavioral patterns''' - provide different implementation solutions involving multiple objects.		'''Behavioral patterns''' - provide different implementation solutions involving multiple objects.

Cybo: /* Purpose */

2009-10-15T01:44:57Z

Purpose

← Older revision		Revision as of 01:44, 15 October 2009
Line 77:		Line 77:
	Purpose represents a specific type of a problem a pattern is trying to solve. It is the most useful criterion since it describes the exact situation where the pattern is used.		Purpose represents a specific type of a problem a pattern is trying to solve. It is the most useful criterion since it describes the exact situation where the pattern is used.

	~~Examples~~		Below are examples which were taken from [2] and [5]

			'''Architectural support patterns''' - represent the strategic decisions for the organization of real-time applications.
			'''Collaboration and distribution''' - patterns provide solutions to common application domain problems in real-time systems.
			'''Safety and reliability patterns''' - deal with common problems of safety and reliability.
			'''Behavioral patterns''' - provide different implementation solutions involving multiple objects.

	== Scope ==		== Scope ==

Cybo: /* References */

2009-10-15T01:43:01Z

References

← Older revision		Revision as of 01:43, 15 October 2009
Line 108:		Line 108:

	[4] F. Buschmann, R. Meunier, H. Rohnert, P. Sommerland and M. Stal. ”Pattern-Oriented Software Architecture: A System of Patterns”. Wiley , (1996).		[4] F. Buschmann, R. Meunier, H. Rohnert, P. Sommerland and M. Stal. ”Pattern-Oriented Software Architecture: A System of Patterns”. Wiley , (1996).

			[5] B. P. Douglass. “Doing Hard Time: Developing Real-Time Systems with UML, Objects, Frameworks, and Patterns”, Addison-Wesley, 19.

Cybo: /* Purpose */

2009-10-15T01:41:58Z

Purpose

← Older revision		Revision as of 01:41, 15 October 2009
Line 75:		Line 75:

	== Purpose ==		== Purpose ==
			Purpose represents a specific type of a problem a pattern is trying to solve. It is the most useful criterion since it describes the exact situation where the pattern is used.

			Examples

	== Scope ==		== Scope ==
	== Discipline ==		== Discipline ==

Cybo: /* Paradigm */

2009-10-14T23:14:15Z

Paradigm

← Older revision		Revision as of 23:14, 14 October 2009
Line 57:		Line 57:
	'''Opaque Type''' - Ensure that values of a datatype are hidden.		'''Opaque Type''' - Ensure that values of a datatype are hidden.

	'''Locally Defined''' ~~Global Identifier~~ - Ensure that a local name is globally unique.		'''Locally Defined Global Identifier''' - Ensure that a local name is globally unique.

	'''Incremental Solution''' - Compute solutions in an incremental manner.		'''Incremental Solution''' - Compute solutions in an incremental manner.

Cybo: /* Introduction */

2009-10-14T17:48:03Z

Introduction

← Older revision		Revision as of 17:48, 14 October 2009
Line 4:		Line 4:
	This article is intended for experienced programmers who are well in versatile patterns. It is not intended to familiarize the reader with the concept of a design pattern. If interested in learning what design patterns are please refer to [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29 Design Pattern]. The intent of the article is not to describe existing patterns and their usage but rather introduce a other ways of categorizing and cataloging of patterns.		This article is intended for experienced programmers who are well in versatile patterns. It is not intended to familiarize the reader with the concept of a design pattern. If interested in learning what design patterns are please refer to [http://en.wikipedia.org/wiki/Design_pattern_%28computer_science%29 Design Pattern]. The intent of the article is not to describe existing patterns and their usage but rather introduce a other ways of categorizing and cataloging of patterns.

	This article relies heavily on the [http://www.cs.tut.fi/~kk/webstuff/PatternClassificationKalvot.pdf presentation by Imed Hammouda & Jakub Rudzki]. We would like to thank them for their contribution to the field of design patterns and helping us to better understand pattern classification.		This article relies heavily on the [http://www.cs.tut.fi/~kk/webstuff/PatternClassificationKalvot.pdf presentation by Imed Hammouda and Jakub Rudzki]. We would like to thank them for their contribution to the field of design patterns and helping us to better understand pattern classification.

	= Definition =		= Definition =