This article may meet Wikipedia's criteria for speedy deletion as a page that is patent nonsense, consisting purely of incoherent text or gibberish with no meaningful content or history. This does not include poor writing, coherent vandalism and hoaxes (G3), coherent material not written in English, badly translated material, etc. This criterion also does not apply to pages in the user namespace. See CSD G1.
If this article does not meet the criteria for speedy deletion, or you intend to fix it, please remove this notice, but do not remove this notice from pages that you have created yourself. If you created this page and you disagree with the given reason for deletion, you can click the button below and leave a message explaining why you believe it should not be deleted. You can also visit the talk page to check if you have received a response to your message. Note that this article may be deleted at any time if it unquestionably meets the speedy deletion criteria, or if an explanation posted to the talk page is found to be insufficient.
Note to administrators: this article has content on its talk page which should be checked before deletion. Administrators: check links, talk, history (last), and logs before deletion. Consider checking Google.This page was last edited by Khalfani khaldun (contribs | logs) at 11:06, 20 March 2009 (UTC) (16 years ago) |
Process Patterns: 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.
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.
Typical Examples of Process Patterns are:
1. Customer communication (a process activity).
2. Analysis (an action).
3. Requirements gathering (a process task).
4. Reviewing a work product (a process task).
5. Design model (a work product).
Process Patterns can be best seen in software design cycle which involves the common stages of development. For example, a generic software design life cycles has following steps:
1. Communication.
2. Planning.
3. Modeling which involves requirement gathering, analysis and design from business perspective.
4. Development which involves code generation and testing.
5. Deployment includes the code deployment and testing in the production environment.
--Amit.kumarrawat (talk) 11:01, 20 March 2009 (UTC)