Process patterns: Difference between revisions

Revision as of 03:59, 10 December 2015

Revision as of 14:33, 25 November 2019

Line 8:

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 Examples are:<br />

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 Patterns 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:<br />

1.# Communication.<br />

2.# Planning.<br />

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

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

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

==External links==