Knowledge Management using Business Process Modelling and Workflow Techniques. M.Sc Thesis (original) (raw)
Related papers
Knowledge management using business process modeling and workflow techniques
18th International Joint …, 2003
Enterprise Modeling (EM) methods are recognised for their value in providing a more organised way to describe a complex, informal domain. A problem with EM is that it does not always provide direct input for software system development. There is a gap between EM and software ...
Lectures on Concurrency and Petri Nets, 2004
Over the last decade there has been a shift from "data-aware" information systems to "process-aware" information systems. To support business processes an enterprise information system needs to be aware of these processes and their organizational context. Business Process Management (BPM) includes methods, techniques, and tools to support the design, enactment, management, and analysis of such operational business processes. BPM can be considered as an extension of classical Workflow Management (WFM) systems and approaches. This tutorial introduces models, systems, and standards for the design, analysis, and enactment of workflow processes. Petri nets are used for the modeling and analysis of workflows. Using Petri nets as a formal basis, contemporary systems, languages, and standards for BPM and WFM are discussed. Although it is clear that Petri nets can serve as a solid foundation for BPM/WFM technology, in reality systems, languages, and standards are developed in an ad-hoc fashion. To illustrate this XPDL, the "Lingua Franca" proposed by the Workflow Management Coalition (WfMC), is analyzed using a set of 20 basic workflow patterns. This analysis exposes some of the typical semantic problems restricting the application of BPM/WFM technology.
A hybrid approach to workflow modelling
Journal of Enterprise Information Management, 2010
PurposeThe increase in business process management projects in the past decade has seen an increase in demand for business process modelling (BPM) techniques. A rapidly growing aspect of BPM is the use of workflow management systems to automate routine and sequential processes. Workflows tend to move away from traditional definitions of business processes that can often be forced to fit a model that does not suit its nature. Existing process modelling tools tend to be biased to either the informational, behavioural or object‐oriented aspect of the workflow. Because of this, models can often miss important aspects of a workflow. As well as managing the relationship between the types of model it is important to consider who will be using it, as process models are useful in various ways. The paper aims to address these issues.Design/methodology/approachThis paper reports on a case study in a manufacturing company, where users were surveyed to see which are the notations that are most c...
Considerations on the particular features for process and workflow modeling
2008
Modeling processes and workflow for complex systems constitutes a challenge for designers. The resources that are used in systems are in limited amounts and these must be shared between the processes and workflow instances activities. Our considerations refer to the need of a data base in that the workflow constituents: instances and activities must be represented in a data base and also their time evolution. Concerning the resources that are used in the processes and in the workflow instances execution must be adequately represented. Two important classes of information systems, Workflow Management Systems (WfMSs) and Enterprise Resource Planning (ERP) systems, have been used to support e-business process redesign, integration, and management. We intend to propose a model for resource representation and allocation and as conclusion propose considerations concerning the design of processes, workflows and workflow management systems. This paper is partially supported by the project P...
BRIDGING THE GAP BETWEEN BUSINESS MODELS AND WORKFLOW SPECIFICATIONS
This paper presents a methodology to bridge the gap between business process modeling and workflow specification. While the first is concerned with intuitive descriptions that are mainly used for communication, the second is concerned with configuring a process-aware information system, thus requiring a more rigorous language less suitable for communication. Unlike existing approaches the gap is not bridged by providing formal semantics for an informal language. Instead it is assumed that the desired behavior is just a subset of the full behavior obtained using a liberal interpretation of the informal business process modeling language. Using a new correctness criterion (relaxed soundness), it is verified whether a selection of suitable behavior is possible. The methodology consists of five steps and is illustrated using event-driven process chains as a business process modeling language and Petri nets as the workflow specification language.
Business process management with unified modeling language
WSEAS Transactions on …, 2007
The evolution of Enterprise Information Systems(EIS) has been shift from data-centric information systems to process-centric information systems in last decade. Business Process Management(BPM), extension of Workflow Management(WFM) contains methods, techniques and tools to support the design, enactment, management and analysis of business process. Petri Nets(PN) are used like standard for BPM and WFM technology. Our approach is to define a methodology for analyze, design, implement, maintain EIS only with Computer Aided Software Engineering(CASE) tools, according to Model Driven Architecture(MDA) from Platform Independent Models(PIMs) to Platform Specific Models(PSMs). In our approaches we proposed an extension of Object Constraint Language(OCL), Complete Constraint Language(CCL) in idea to use the Activity Diagram(AD) from Unified Modeling Language(UML) as formal basis for BPM and WFM technology, respectively Entity Relationship-Stored Procedures(ER-SP), an extension of ER(Entity Relationship) model for conceptual, syntactic and semantic modeling of relational databases in idea to create a link between external to physical models.
1999
Abstract Meta-Languages for the definition of processes serve several purposes. They can be employed as an integration platform for the exchange of process models that are specified in proprietary languages, their expressiveness can serve as a benchmark for the selection of a application specific modeling language and they can be used for the application-independent specification of process models that can then be transformed into the language relevant for the domain-specific context.
Business process modeling languages
ACM Computing Surveys, 2010
Requirements capture is arguably the most important step of software engineering and yet the most difficult and the least formalized one [Phalp & Shepperd,2000]. Enterprises build information systems to support their business processes. Software engineering research has typically focused on the development process, starting with user requirements-if that-with business modeling often confused with software system modeling [Isoda, 2001]. Researchers and practitioners in management information systems have long recognized that understanding the business processes that an information system must support is key to eliciting the needs of its users (see e.g. [reference]), but lacked the tools to model such business processes or to relate such models to software requirements. Researchers and practitioners in business administration have long been interested in modeling the processes of organizations for the purposes of understanding, analyzing, and improving such processes [reference], but their models were often too coarse to be of use to software engineers. The advent of eCommerce and workflow management systems, among other things, have led to a convergence of interests and tools, within the broad IT community, for modeling and enabling business processes. In this paper, we present an overview of business process modeling languages. We first propose a categorization of the various languages. Then, we describe representative languages from each family.
Business Process Modeling for developing Process Oriented IT Systems
2004
Information system developers are challenged to develop systems that should meet the requirements of modern organizations. By promoting the enterprise-wide integration, the paradigm of Business Process Management contrasts with traditional information system development. The latter was suffered, but also crystallized, the vertical division of the enterprise activities. In addition, the paradigms of Business Process Reengineering and Improvement contrast with traditional information system development that focused on automating and supporting existing business processes. Now, enterprises should create new ways of working to survive in a competitive environment. In this context, enterprise modeling can help understanding the current business situation and establishing a vision of what the future should be like. Therefore, business process modeling becomes a prerequisite for system requirements elicitation and system development.