• Business process reengineering-the redesign of an organization's business processes to make them more efficient. • Coordination technology-an aid to managing dependencies among the agents within a business process, and provides automated support for the most routinized component processes. * Process-driven software development environments-an automated system for integrating the work of all software related management and staff; it provides embedded support for an orderly and defined software development process. These three applications share a growing requirement to represent the processes through which work is accomplished. To the extent that automation is involved, process representation becomes a vital issue in redesigning work and allocating responsibilities between humans and computers. This requirement reflects the growing use of distributed , networked systems to link the interacting agents responsible for executing a business process. To establish process modeling as a unique area, researchers must identify conceptual boundaries that distinguish their work from model-ing in other areas of information science. Process modeling is distinguished from other types of model-ing in computer science because many of the phenomena modeled must be enacted by a human rather than a machine. At least some mod-eling, however, in the area of human-machine system integration or information systems design has this 'human-executable' attribute. Rather than focusing solely on the user's behavior at the interface or the flow and transformation of data within the system, process model-ing also focuses on interacting behaviors among agents, regardless of whether a computer is involved in the transactions. Much of the research on process modeling has been conducted on software development organizations , since the software engineering community is already accustomed to formal modeling. Software process modeling, in particular , explicitly focuses on phenomena that occur during software creation and evolution, a domain different from that usually mod-eled in human-machine integration or information systems design. Software development is a challenging focus for process modeling because of the creative problem-solving involved in requirements analysis and design, and the coordination of team interactions during the development of a complex intellectual artifact. In this article, software process modeling will be used as an example application for describing the current status of process modeling, issues for practical use, and the research questions that remain ahead. Most software organizations possess several yards of software life cycle description, enough to wrap endlessly around the walls of project rooms. Often these descriptions do not correspond to the processes actually performed during software …

Process modeling

1. Place animal in induction chamber and anesthetize the mouse and ensure sedation. 2. Once the animal is sedated, move it to a nose cone for hair removal using cream. Only apply cream to the area of the chest that will be utilized for imaging. Once the hair is removed, wipe area with wet gauze to ensure all hair is removed. 3. Move the animal to the imaging platform and tape its paws to the ECG lead plates and insert rectal probe. Body temperature should be maintained at 36-37°C. During imaging, reduce anesthesia to maintain proper heart rate. If the animal shows signs of being awake, use a higher concentration of anesthetic.

人唾液天疱疮抗原的纯化

コンピュータ・サイエンス : ACM computing surveys

After more than 20 years of research and practice in software configuration management (SCM), constructing consistent configurations of versioned software products still remains a challenge. This article focuses on the version models underlying both commercial systems and research prototypes. It provides an overview and classification of different versioning paradigms and defines and relates fundamental concepts such as revisions, variants, configurations, and changes. In particular, we focus on intensional versioning, that is, construction of versions based on configuration rules. Finally, we provide an overview of systems that have had significant impact on the development of the SCM discipline and classify them according to a detailed taxonomy.

/pdf/version-models-for-software-configuration-management-1tcwwh2q9y.pdf

Version models for software configuration management

Specification matching is a way to compare two software components, based on descriptions of the component's behaviors. In the context of software reuse and library retrieval, it can help determine whether one component can be substituted for another or how one can be modified to fit the requirements of the other. In the context of object-oriented programming, it can help determine when one type is a behavioral subtype of another. We use formal specifications to describe the behavior of software components and, hence, to determine whether two components match. We give precise definitions of not just exact match, but, more relevantly, various flavors of relaxed match. These definitions capture the notions of generalization, specialization, and substitutability of software components. Since our formal specifications are pre- and postconditions written as predicates in first-order logic, we rely on theorem proving to determine match and mismatch. We give examples from our implementation of specification matching using the Larch Prover.

Specification matching of software components

An environment is described, called Professor Marvel, that provides early error checking and answers questions about the program under development. The environment has a certain understanding of the systems being developed and how to use tools to produce software. It aids individual programmers and helps coordinate programming teams. The key components of Marvel are a database that stores data represented as objects, as in object-oriented languages, and a model of the development process that imposes a structure on programming activities. Marvel's support of insight and of opportunistic processing is discussed at length, as is the handling of side effects. A sample session is described. >

/pdf/intelligent-assistance-for-software-development-and-4o00vynn18.pdf

Intelligent assistance for software development and maintenance

There are four fundamental aspects of use and reuse in building systems from components: conceptualization, retrieval, selection and correct use. The most important barrier to use and reuse is that of conceptualization. The Inscape environment is a specification-based software development environment integrated by the constructive use of formal interface specifications. The purpose of the formal interface specifications and the semantic interconnections is to make explicit the invisible semantic dependencies that result in conventionally-built systems. The important ingredient provided by Inquire in conceptualization, retrieval, selection and use is the set of predicates that describe the semantics of the elements in the interface. These predicates define the abstractions that are germane to the module interface and describe the properties of data objects and the assumptions and results of operations in a module. Use and reuse of components is based on a component's ability to provide needed semantics at a particular point in a system. It is the purpose of Inquire, the browser and predicate-based search mechanism, to aid both the environment and the user in the search for the components that will provide the desired predicates that are required to build and evolve an implementation correctly. >

Inquire: predicate-based use and reuse

The authors present a multi-user implementation of a bi-level process modeling language (PML). Most process modeling formalisms are well-suited to one of two levels of specification, but not both. Some concentrate on global control flow and synchronization. These languages make it easy to define the broad outline of a process, but harder to refine the process by expressing constraints and policies on individual tools and data. Other process formalisms are inherently local. It is easy to define constraints, but far from straightforward to express control flow. Combining global and local formalisms is proposed to produce bi-level formalisms suitable for expressing the enacting large scale processes. The new PML is called the activity structures language. The activity structures language integrates global constrained expressions with local rules. Its implementation on top of the Marvel rule-based environment is described. >

A bi-level language for software process modeling

We are developing an experimental programming language, MELD, that suppons a range of concurrent styles by supporting multiple programming paradigms at multiple levels of granularity. MELD integrates three granularities of parallelism: macro dataflow among statements within a method or among methods for flne grain concurrency, synchronous or asynchronous message passing among local or remote objects for medium grain concurrency, and transactions for large grain concurrency among users.

/pdf/melding-multiple-granularities-of-parallelism-3q7ol5vl97.pdf

MELDing Multiple Granularities of Parallelism

We present a model for developing rule based process servers with extensible syntax and semantics. New process enactment directives can be added to the syntax of the process modeling language, in which the process designer may specify specialized behavior for particular tasks or task segments. The process engine is peppered with callbacks to instance specific code in order to implement any new directives and to modify the default enactment behavior and the kind of assistance that the process centered environment provides to process participants. We realized our model in the Amber process server, and describe how we exploited Amber's extensibility to replace Oz's native process engine with Amber and to integrate the result with a mockup of TeamWare.

https://www.researchgate.net/profile/Gail_Kaiser2/publication/2774337_A_Metalinguistic_Approach_to_Process_Enactment_Extensibility/links/0deec520b9a8b3b36a000000.pdf

Steven S. Popovich

Papers

Intelligent assistance for software development and maintenance

Inquire: predicate-based use and reuse

A bi-level language for software process modeling

MELDing Multiple Granularities of Parallelism

A metalinguistic approach to process enactment extensibility