Process patterns: Difference between revisions

Revision as of 18:19, 8 August 2022

Latest revision as of 06:20, 27 August 2025

(4 intermediate revisions by 3 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}}

'''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]].

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 of 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.

Typical Examplesexamples are:

# Customer communication (a process activity).

# Analysis (an action).

Line 11 ⟶ 10:

# Design model (a work product).

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

# Communication.

# Planning.

Line 17 ⟶ 16:

# Development which involves code generation and testing.

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

==References==

{{reflist}}

==External links==