Overview of knowledge flow in a software development process <s> III. WORKFLOW <s> A significant number of companies are reengineering their business to be more effective and productive. Consequently, existing applications must be modified, and new applications must be written. The new applications typically run in a distributed and heterogeneous environment, performing single tasks in parallel, and demanding special transaction functionality for the supporting environments. Workflow-based applications offer this type of capability. In this paper, their principal advantages are derived and set in context to transaction, object, and CASE (computer-assisted software engineering) technology. In particular, a method is proposed to develop these workflow-based applications in a cohesive and consistent way. <s> BIB001 </s> Overview of knowledge flow in a software development process <s> III. WORKFLOW <s> Abstract Workflow management techniques have become an intensive area of research in information systems. In large scale workflow systems modularity and reusability of existing task structures with context dependent (parameterized) task execution are essential components of a successful application. In this paper we study the issues related to management of modular transactional workflows, i.e., workflows that reuse component tasks and thus avoid redundancy in design. The notion of parameterized transactional properties of workflow tasks is introduced and analyzed, and the underlying architectural issues are discussed. <s> BIB002 </s> Overview of knowledge flow in a software development process <s> III. WORKFLOW <s> The definition of exact semantics of workflows and involved processing entities is an open yet urgent problem for most systems. This paper considers the semantics and correctness of event-driven workflow execution by reactive components. The basis for the formalization in our approach is provided by an event his tory which records all the events generated during the execution of workflows by these components. Based on the formal notion of history, it is possible to determine the semantics of workflow systems as the set of event histories they can generate. It also allows to formalize the semantics of reactive components-and consequently, the semantics of workflows-as well as to check whether their observable behavior is correct. In addition to the precise understanding of event-driven workflow execution, the formalized notion of event history also serves as the specification of the workflow execution engine. Ultimately, the semantics of reactive components provides the basis for specifying transformation rules used to map these components to the execution level. <s> BIB003 </s> Overview of knowledge flow in a software development process <s> III. WORKFLOW <s> Abstract When designing a workflow schema, the workflow designer must often explicitly deal with exceptional situations, such as abnormal process termination or suspension of task execution. This paper shows how the designer can be supported by tools allowing him to capture exceptional behavior within a workflow schema, by reusing an available set of pre-configured exceptions skeletons. Exceptions are expressed by means of triggers, to be executed on the top of an active database environment. In particular, the paper deals with the handling of typical workflow exceptional situations which are modeled as generic exception skeletons to be included in a new workflow schema by simply specializing or instantiating them. Such skeletons, called patterns , are stored in a catalog; the paper describes the catalog structure and its management tools constituting an integrated environment for pattern-based exception design and reuse. <s> BIB004 </s> Overview of knowledge flow in a software development process <s> III. WORKFLOW <s> The dynamic nature of events, in particular business processes, is a natural and accepted feature of today’s business environment. Therefore, workflow systems, if they are to successfully model portions of the real world, need to acknowledge the temporal aspect of business processes. This is particularly true for processes where any deviation from the prescribed model is either very expensive, dangerous or even illegal. Such processes include legal processes, airline maintenance or hazardous material handling. However, time modeling in workflows is still an open research problem. This paper proposes a framework for time modeling in production workflows. Relevant temporal constraints are presented, and rules for their verification are defined. Furthermore, to enable visualization of some temporal constraints, a concept of “duration space” is introduced. The duration algorithm which calculates the shortest/longest workflow instance is presented. It is a generalization of two categories of algorithms: the shortest-path partitioning algorithm and the Critical Path Method (CPM). Based on the duration algorithm, the verification algorithm is designed to check the consistency of introduced temporal constraints. <s> BIB005
A workflow can be defined as a process that helps encourage Participation Around group parts as stated by definite procedure rationale. A workflow administration framework (WfMS). Fully determines, manages, and implements the workflow specification by implementing software. The order of this implementation is driven by a computer representation of the workflow logic [28, BIB001 30] . One of the important uses of workflows as a high-level tool is to combine the divided and different application processes into a process supported by lowlevel conveyed object part systems. Those qualities about occasion time modeling, reusability, special case handling, Also formal model of a workflow need been talked about BIB004 BIB003 BIB005 BIB002 45] . These qualities might make integrated into the WfMS to support a distributed team development setting. In fact, the current workflow model and the WfMS do not interact with the knowledge-level cooperation, and the execution of each task of a workflow is an inter-operation between humans and the support work environment. Human cognition plays a major role in effectively completing the development tasks. In  , a workflow is composed of the organized actions of the fixed routines in a business process as it represents the technology of the business process. Workflows are commonly be used at the level of process mechanization to which , information, document or task. are passed to the members according to predetermined rules and processes. Consequently, users become capable of performing a complete enterprise application or target. The success of a KM implementation system can be determined by integrating a KM and an enterprise. In the majority of KM projects, project managers tend to concentrate only on the knowledge itself and its collection, storage, and reuse. They disregard knowledge and business workflow integration. Aside from the collection of knowledge, the storage and the reuse of KM are also crucial elements of a project. However, recognizing the benefits of KM, knowledge creation, sharing, and use is important because only their relative interactions with a limited workflow consolidation can play an active role. Workflows are crucial innovation technology in business process modeling, restructuring, and implementing. They have the following roles: improve process control, simplify the performance of asynchronous and concurrent operations, enhance efficiency, diminish operational costs, and furthermore enhance services quality and others. The workflow technology innovation in all types of organization has been used broadly utilized within information, knowledge intensive business to improvement. It also plays a great role in technology development and competition. Aside from business process management, KM in knowledge-intensive organizations is An alternate essential act outside of the content. Through KM, enterprise associations could produces in the procedure Also in the transform significant business knowledge might make changed under knowledge assets should accomplish An enduring profit. Workflow is a common innovation technology that might be used to actualize all business in a cooperative system through defined process. it is defined as the automation mechanism of a set of business procedure in the whole or a part through what document , knowledge , information or task are passed from one team member to another for action depending on procedural rule. In practical applications, a workflow meta-model is required. It is a description model language in what workflow models. The workflow meta-model of WfMC is shown in Fig.  2 . The figure shows that the meta-model represents all components in a workflow, the relationship between these components, and the attribution of these elements, which are activity, role, transition conditions, and workflow relevant data, among others. However, this model only provides a basic process definition for a workflow instance because it does not present an organization and information (knowledge) model that need enough sufficient capacity in a cooperative system. It also does not focus on knowledge and KF in a business process. Consequently, it cannot tolerate complicated tasks in implementing a business process. For example, in a cooperative environment, many activities are grouped, and they must be completed through cooperation among the team members. In the application process activity, considerable knowledge is involved, but using that knowledge is a prerequisite in a cooperative system. 