GDPA  
Process Embedding  

A-B-C-D-E-F-G-H-I-J-K-L-M-N-O-P-Q-R-S-T-U-V-W-X-Y-Z

Identification

Process Embedding

Definitions/Uses

1994
Reference /Garg, 1994/ The SMART Approach for Software Process Engineering
Definition/ Uses Once a process has been successfully analyzed for various properties, it can be embedded and executed within a software engineering environment. This involves assigning and scheduling specified users, tools, and data objects to the process.

A shift in process representations needs to occur at this stage. While the process model in the modelling and analysis stages of the life-cycle is mainly used for communication, understanding, and analysis, the process model at the embedding stage is mainly used to derive an executable PSEE. Therefore, specific software tools, such as Emacs, needs to be associated with the process model, whereas in the earlier stages it would have been sufficient to say that a toll of class "text-editor" is required. Similarly, in the earlier stages we could have modeled a "Requirements Document" in the abstract, while at this stage that will be bound to some data object identifier, which eventually resolves to a path specification or named file in the local network file system.

Related terms in the glossary

Process Life-cycle

This page online  •  GDPA Online  •  Last Updated 10.June.2002 by C. Freericks