Process patterns: Difference between revisions

Revision as of 23:58, 9 October 2010

Latest revision as of 06:20, 27 August 2025

(17 intermediate revisions by 13 users not shown)

Line 1:

'''Process patterns''' can be defined as the set of activities, actions, work tasks or work products and similar related behaviour followed in a [[software development life cycle]].<ref>{{cite book |last1=Tran |first1=Hanh |last2=Coulette |first2=Bernard |last3=Dong |first3=Bich Thuy |chapter=Modeling Process Patterns and Their Application |title=International Conference on Software Engineering Advances (ICSEA 2007) |date=September 2007 |page=15 |doi=10.1109/ICSEA.2007.52 |isbn=978-0-7695-2937-0 }}</ref>

{{Unreferenced|date=March 2008}}

{{wikify|date=October 2010}}

Process patterns can be more easily understood by dividing it into terms,: "Process", which means the steps followed to achieve a task and "patterns", which means the recurrence orof same basic features during the lifecycle of a process. Thus in a more universal term process patterns are common or general solution for a complexity.

'''Process patterns''' can be defined as the set of activities, actions, work tasks or work products and similar related behavior followed in a software process lifecycle.

Typical Examplesexamples are:<br />

Process patterns can be more easily understood by dividing it into terms, Process which means the steps followed to achieve a task and patterns which means the recurrence or same basic features during the lifecycle of a process. Thus in a more universal term process patterns are common or general solution for a complexity.

1.# Customer communication (a process activity).<br />

2.# Analysis (an action).<br />

3.# [[Requirements analysis|Requirements gathering]] (a process task).<br />

4.# Reviewing a work product (a process task).<br />

5.# Design model (a work product).

Process Patternspatterns can be best seen in [[Software engineering|software design]] cycle which involves the common [[DevelopmentalSoftware stagerelease life cycle|stages of development]]. For example, a generic software design life cycles has following steps:<br />

Typical Examples are:<br />

1.# Communication.<br />

1. Customer communication (a process activity).<br />

2.# Planning.<br />

2. Analysis (an action).<br />

3.# Modeling which involves requirement gathering, analysis and design from business perspective.<br />

3. [[Requirements analysis|Requirements gathering]] (a process task).<br />

4.# Development which involves [[code generation]] and testing.<br />

4. Reviewing a work product (a process task).<br />

5.# Deployment includes the code deployment and testing in the production environment.

5. Design model (a work product).

==References==

Process Patterns can be best seen in [[Software engineering|software design]] cycle which involves the common [[Developmental stage|stages of development]]. For example, a generic software design life cycles has following steps:<br />

{{reflist}}

1. Communication.<br />

2. Planning.<br />

==External links==

3. Modeling which involves requirement gathering, analysis and design from business perspective.<br />

* [http://www.ambysoft.com/processPatternsPage.html The Process Patterns Resource Page ]

4. Development which involves [[code generation]] and testing.<br />

* [http://c2.com/cgi/wiki?ProcessPatterns Process Patterns & Applications]

5. Deployment includes the code deployment and testing in the production environment.

* [http://c2.com/cgi/wiki?ProjectManagementPatterns Project Management Patterns]

* [http://orgpatterns.wikispaces.com/ Organizational Patterns]

[[Category:Software design patterns]]