NDLI: OPM: an object process modeling environment0

Please wait, while we are loading the content...

Review of the state-of-the-art (session summary)

Mechanisms (session summary)

Policies (session summary)

Data (session summary)

Control (session summary)

Emerging issues (session summary)

Tolerating inconsistency

Experiences with the spiral model as a process model generator

System dynamics models of software developments

Process programming and process models

Studying the process of software design teams

Process programming: a structured multi-paradigm approach could be achieved

Software process support through software configuration management

A structural framework for the formal representation of cooperation

The role of formalized domain-specific software frameworks

P4: a logic language for process programming

Software process instantiation and the planning paradigm

Modeling implications of the personal software process

Mechanisms for software process dynamics

Experience with Marvel

Experience with enactable software process models

Position paper for ISPW

The role of process models in software and systems development and evolution

A software process model based on unit workload network

Law-governed software processes

Product-based process models

A method for recording and analyzing design processes

Experiences with process programming

Acquiring experiences with executable process models

Software process dependability

Conceptual programming

Dynamics of process models in PML

Specification of software process measurement

Experiences with operational software process modeling in the system factory project

OPM: an object process modeling environment0

The software process as a goal-directed activity

Experiments with typing in process modeling

Domain understanding and the software process

An example of software development modelling

An example P4 process program for Rebus

GRAPPLE example: processes as plans

Marvel strategy language example

An example of process description in HFSP

Software process modeling example

An example of a software process model based on unit workload network

Example process program code, coded in Appl/A

Describing working environments in OPM

An overview of the ALF project

The Arcadia research project

ESF and software process modeling

Dynamics of process models in PML

Summary of software designer's associates project

OPM: an object process modeling environment0

Content Provider	ACM Digital Library
Author	Horowitz, Ellis Sugiyama, Yasuhiro
Abstract	This document as an attempt to give an overview of OPM, a process modeling environment . By an environment we mean a user interface through which process model templates are designed, instantiated, and tracked as they execute. The two novel features of OPM that we want to stress here are: (i) the way OPM uses conventional CASE tool graphical notations for describing process templates, and (ii) the way OPM supports model instantiation, resource management, and cooperative work among a team of developers.We begin with some basic definitions. A process is a collection of activities that will be carried out over time. An activity is a basic unit of work and it minimally contains a name, and some attributes such as a duration or some resources. Often the activities are ordered in some way, but not necessarily. If an ordering is available, then we can talk about an activity's predecessors and successors. When a process is being carried out (instantiated), typically more than one activity is going on at the same time. The result of an activity may be a product or simply a confirmation that it has concluded. An activity can invoke other processes. In fact, there is no logical reason to distinguish between an activity and a process, so in the future we will use these terms interchangeably.There are several basic features of processes that we assume. In particular:there are several ways a process may be started, e.g. by human intervention, by the arrival of a message, or by the completion of some product;an action by a computer may end a process and start a new one;a process may require access to resources before it can begin;sometimes the time for a process can be reliably estimated and sometimes it cannot;processes must have the ability to look at (access) directories, files, test file attributes, express conditions, and invoke programs.Figure 1 contains a description of how debugging takes place within some hypothetical organization. A database of bug reports is collected and there is an available pool of programmers to work on them. Each instantiation of debugging process will assign a bug report to a programmer for fixing. When the programmer is done, he submits his fix to the QA (quality assurance) group who confirm that his fix is correct. If not, it is returned for further work. If so, then a report is written and submitted to the manager.From this example we can draw conclusions that extend our earlier notions about processes and their descriptions. The use of dataflow diagram notation is suitable for describing this process. Rectangles are used to represent resources and ovals are used to represent processes. Arrows indicate process flow and they may carry data. Other examples we have done indicate that a wide variety of processes can be adequately described by this natural notation. To refine further the debugging example, we assume that when the programmer submits the corrected code to the quality assurance group, a new process is started. That process is shown in Figure 2. From this elaboration we conclude that processes may have lower levels which contain process descriptions. Therefore we see that a process description should be thought of as a hierarchical object.Another observation from this example is that there may be several people all following this process description at the same time. Therefore we see the need to view the process description as a template and talk about its instantiations. When the template of Figure 1 is instantiated we interpret this to mean that a new bug has been assigned to a programmer for repair. Observe that when a single programmer is selected to fix a single bug, that instantiation of the debugging process may give rise to multiple instantiations of the working on bug subprocess. Therefore we see that when a process is executing, subprocess templates may be instantiated multiple times.
Starting Page	134
Ending Page	136
Page Count	3
File Format	PDF
ISBN	0818621044
Language	English
Publisher	Association for Computing Machinery (ACM)
Publisher Date	1990-10-01
Access Restriction	Subscribed
Content Type	Text
Resource Type	Article

Central Library (ISO-9001:2015 Certified)
Indian Institute of Technology Kharagpur
Kharagpur, West Bengal, India | PIN - 721302

See location in the Map
03222 282435
Mail: support@ndl.gov.in

Sl.	Authority	Responsibilities	Communication Details
1	Ministry of Education (GoI), Department of Higher Education	Sanctioning Authority	https://www.education.gov.in/ict-initiatives
2	Indian Institute of Technology Kharagpur	Host Institute of the Project: The host institute of the project is responsible for providing infrastructure support and hosting the project	https://www.iitkgp.ac.in
3	National Digital Library of India Office, Indian Institute of Technology Kharagpur	The administrative and infrastructural headquarters of the project	Dr. B. Sutradhar bsutra@ndl.gov.in
4	Project PI / Joint PI	Principal Investigator and Joint Principal Investigators of the project	Dr. B. Sutradhar bsutra@ndl.gov.in Prof. Saswat Chakrabarti will be added soon
5	Website/Portal (Helpdesk)	Queries regarding NDLI and its services	support@ndl.gov.in
6	Contents and Copyright Issues	Queries related to content curation and copyright issues	content@ndl.gov.in
7	National Digital Library of India Club (NDLI Club)	Queries related to NDLI Club formation, support, user awareness program, seminar/symposium, collaboration, social media, promotion, and outreach	clubsupport@ndl.gov.in
8	Digital Preservation Centre (DPC)	Assistance with digitizing and archiving copyright-free printed books	dpc@ndl.gov.in
9	IDR Setup or Support	Queries related to establishment and support of Institutional Digital Repository (IDR) and IDR workshops	idr@ndl.gov.in