Narrow Results

This paper is concerned with the design and manufacturing of 2D and 3D components in the context of process modeling and inspection. A methodology is proposed that models manufacturing processes and learns shape deformations that are the result of out-of-tolerance components. Then during inspection, a deformed shape is analyzed and the process parameter values determined. The key aspect of this approach is that the mapping between process parameters and shape is determined which is not possible using standard process modeling approaches such as finite element analysis. This is different to the traditional approach to tolerancing which is very much as additional procedure to design and doesn't consider process parameter variation, just shape variation. A review of tolerancing is presented as well as a description of techniques for process modeling.

Following the successful use of object-oriented metamodeling in the definition of the UML and other notation standards there is increasing interest in extending the approach to cover other concepts of software development, including processes. However, it turns out that the "obvious" approaches for using metamodels to describe processes and artifacts independently do not integrate well together in a natural and straightforward way. In this paper we discuss the problems and inconsistencies than can arise when trying to model a process and the products it creates within the same metamodeling framework, and present a solution that not only avoids many of these problems but also qualifies as a general metamodeling pattern. We then generalize the conceptual architecture to support the sound co-modeling of all independent areas of concern within the context of strict metamodeling.

Based on the requirements arising from process-centered organizations and because of the lack of process modeling mechanisms in traditional software development methods, this paper presents a Business Process-centered Software Analysis method (BPSA), which supports the modeling of business process control logic. As a method, BPSA is composed of two main parts: a model and the steps of how to model the requirements using this model. The model includes the functional, informational and organizational aspects as well as the behavioral aspect that provides the mechanism for modeling the process control logic. The event mechanism is employed in this method as a main technique for modeling the control aspect of business processes. This method is based on technologies such as Structured Analysis, OOA & OOD, Workflow, XML, and has been used in the development of several medium and large information systems, proving to be both useful and effective.

Knowledge is a key asset in software engineering. Facilitating access to the knowledge that software engineers require for the task at hand can therefore bring many benefits. To accomplish this, it is important to understand how knowledge flows through the organization, to identify problems that may hinder a suitable flow, and to define strategies with which to address them. Process modeling has proved to be a useful technique for analyzing knowledge flows. Traditional process modeling languages do not, however, provide primitives to explicitly represent the knowledge involved in the processes within the models. In this paper, we illustrate how the Software Process Engineering Metamodel (SPEM) can be adapted, to be used as a process modeling language for analyzing knowledge flows in software processes. We have extended SPEM to represent knowledge and its sources in process models in an explicit way. We also discuss the experiences obtained from using this extension in a software organization and the lesson we have learned from it.

This paper outlines a framework which supports the use of multiple perspectives in system development, and provides a means for developing and applying systems design methods. The framework uses "viewpoints" to partition the system specification, the development method and the formal representations used to express the system specifications. This VOSE (viewpoint-oriented systems engineering) framework can be used to support the design of heterogeneous and composite systems. We illustrate the use of the framework with a small example drawn from composite system development and give an account of prototype automated tools based on the framework.

The use of empirical data to understand and improve software products and software engineering processes is gaining ever increasing attention. Empirical data from products and processes is needed to help an organization understand and improve its way of doing business in the software domain. Additional motivation for collecting and using data is provided by the need to conform to guidelines and standards which mandate measurement, specifically the SEI’s Capability Maturity Model and ISO 9000–3. Some software engineering environments (SEEs) offer automated support for collecting and, in a few cases, using empirical data. Measurement will clearly play a significant role in future SEEs. The paper surveys the trend towards supporting measurement in SEEs and gives details about several existing research and commercial software systems.

This paper describes an approach to support software development process descriptions in the context of the Memphis Environment (a Reuse Based Software Development Environment), allowing the organization of a software development asset, i.e., the process knowledge. The approach uses software patterns to organize the information, and provides a tool that handles the process descriptions as a source of solutions to problems detected by project management. It enhances the environment features in terms of project management support, process modeling capability, and process evolution support.

The focus of traditional workflow management systems is on control flow within one process definition. The process definition describes how a single case (i.e. workflow instance) in isolation is handled. For many applications this paradigm is inadequate. Interaction between cases to support communication and collaboration is at least as important. This paper introduces and advocates the use of interacting proclets, i.e. lightweight workflow processes. By promoting interactions to first-class citizens it is possible to model complex workflows in a more natural manner. In addition, the expressive power and flexibility are improved compared to the more traditional workflow modeling languages.

Most of nowadays modeling tools for creating business processes in enterprises can be used by IT experts to semi-automatically create corresponding software artifacts of the given process. Unfortunately, these tools comprise a lot of complexity, and therefore, they are not usable by ordinary end users. In this paper, we propose a modeling tool for ad-hoc business processes with a comprehensible and simple user interface that is usable by end users to model their daily life workflows. Afterwards, a fully executable application can be created from the model automatically. Also, we introduce a notion of the so-called “micro-room concept”, which is used as a basis for the abstraction of the modeling tool. The created micro-room framework allows designing peer-to-peer applications based on configurable, shared data rooms. The evaluation and comparison analysis of the modeling tool itself and the underlying micro-room concept have been done by means of usability studies. The preliminary results show that the micro-room concept uses a more comprehensible abstraction compared to other modeling languages. It is well suited for modeling simple collaborative tasks whereas other approaches are better in case of very complex processes. Further, the developed modeling tool is more intuitive than the competing ones due to the simplifications allowed by using the micro-room concept.

Most of today’s approaches to business process engineering (also called business process management) start from an activity-centered perspective. They describe activities to be carried out within a business process and their relationships, but they usually pay little attention to the objects manipulated within processes. In this article, we discuss an approach to business process modeling, model analysis, and business process enaction (also called workflow management) which is based on data modeling, activity modeling, and organization modeling. In fact, the ℒeu approach to business process management considers data models (describing types of objects to be manipulated in a business process and their relationships), activity models (describing activities to be carried out in a business process), and organization models (describing organizational entities involved in a business process) as separate, but equally important, facets of business processes.

Scientific modeling provides mathematical abstractions of real-world systems and builds software as implementations of these mathematical abstractions. Ocean science is a multidisciplinary discipline developing scientific models and simulations as ocean system models that are an essential research asset. In software engineering and information systems research, modeling is also an essential activity. In particular, business process modeling for business process management and systems engineering is the activity of representing processes of an enterprise, so that the current process may be analyzed, improved and automated. In this paper, we employ process modeling for analyzing scientific software development in ocean science to advance the state in engineering of ocean system models and to better understand how ocean system models are developed and maintained in ocean science. We interviewed domain experts in semi-structured interviews, analyzed the results via thematic analysis, and modeled the results via the Business Process Modeling Notation (BPMN). The processes modeled as a result describe an aspired state of software development in the domain, which are often not (yet) implemented. This enables existing processes in simulation-based system engineering to be improved with the help of these process models.

The techniques of workflow mining can support the design of workflow. It is a challenge to exploit more information in a set of log. In practice, many business processes can vary with the change of time and environment. This paper presents a method to mine and describe the dynamic information in process log. A new conception named dynamic workflow net (DWF-net) was proposed, which evolves from workflow net (WF-net). DWF-net has new attributes to characterize the dynamic factors in workflow models. This paper also presents the idea and steps of the algorithm that can generate a DWF-net from a set of workflow log. The prototype and experiments have proved that the algorithm is effective.

This paper is concerned with the design and manufacturing of 2D and 3D components in the context of process modeling and inspection. A methodology is proposed that models manufacturing processes and learns shape deformations that are the result of out-of-tolerance components. Then during inspection, a deformed shape is analyzed and the process parameter values determined. The key aspect of this approach is that the mapping between process parameters and shape is determined which is not possible using standard process modeling approaches such as finite element analysis. This is different to the traditional approach to tolerancing which is very much as additional procedure to design and doesn't consider process parameter variation, just shape variation. A review of tolerancing is presented as well as a description of techniques for process modeling.

The use of empirical data to understand and improve software products and software engineering processes is gaining ever increasing attention. Empirical data from products and processes izs needed to help an organization understand and improve its way of doing business in the software domain. Additional motivation for collecting and using data is provided by the need to conform to guidelines and standards which mandate measurement, specifically the SEI's Capability Maturity Model and ISO 9000-3. Some software engineering environments (SEEs) offer automated support for collecting and, in a few cases, using empirical data. Measurement will clearly play a significant role in future SEEs. The paper surveys the trend towards supporting measurement in SEEs and gives details about several existing research and commercial software systems.

The purpose of this chapter is to present tools and techniques for modeling and managing business processes. For this, business process modeling is defined and classified according to two levels of detail. These categories are chained together with the help of a transformation technique, which is explained with the help of an example.

As soon as the number of processes increases, they cannot be managed manually. This motivates the need for a software system called a business process management system (BPMS). The properties of a BPMS are explained, and the components of a BPMS, which support the necessary requirements of managing processes, are also presented with their advantages. Also, the major principles of business process management (BPM) are presented in this chapter.

This paper aims at briefly overview the previous use of process modeling in denim manufacturing sectors, specifically, dyeing and finishing processes. A collection of relevant works is introduced, such as modeling the dyeing process for predicting the depth of shade, the effects of alkali reductive stripping process or cellulase washing process on color properties, and certain physical properties. A specific case in regard to modeling ozone fading denim by artificial neural networks (ANN) was studied as an example at the end, the results simply revealed that modeling process using soft computing techniques is capable to accurately predict the targeted outputs which is obviously promising and potential to make a difference in the future development of denim manufacturing.