Process Modeling

• Process Basics
• AINSI
• Elicit

Process Basics

Framework Definitions

Levels of Software Process Models

Software Process Architecture

The three levels must be present in the process framework giving policies, procedures and standards (corresponding to the three levels). The architectural framework provides a definition for the basic elements, how they relate and how they are decomposed into greater detail.

The basic element of the process model is the Unit Cell. A unit cell is defined to accomplish a specific task and is uniquely identified. Each cell has required entry conditions with inputs, task standards, procedures, methods, responsibilities, and measures. Exit conditions define the results produced, their level of validation, and any post-task conditions. Feedback is allowed to and from other unit cells.

Table 1: Basic Unit Cell Specification
Specification
Entry	Conditions to be met before task initiation
Exit	Results produced
Feedback	IN: Feedback from other cells OUT: Feedback to other cells
Task	What is to be done (who, what, when)? Standards, procedures, and responsibilities.
Measurements	Task, output, and feedback measures

The Table 2 provides an example that should highlight the modeling activity. In particular, Table 2 offers a model for what we normally refer to as the development cycle for small projects.

Table 2: Unit Cell Definitions for Process Model
Cell	001	002	003
Entry	Approved requirements, changes and development plan	Inspected and approved design and changes	Inspected and approved code and changes
Exit	Inspected and approved design and changes	Inspected and approved code and changes	Inspected, tested and approved software
Feedback In	Design Issues	Implementation Issues
Feedback Out	Requirements Issues	Requirements and Design Issues	Requirements, Design Issues, and implementation issues
Task	Design	Implementation, Inspection and unit test	Testing: Integration, Function, System, and Acceptance
Measures	Resources, Product: Changes, Errors, Design, Document Pages	Resources, Product: Changes, Errors, Code, Document Pages	Resources, Product: Changes, Errors, Code, Document Pages, Test Suite

[Process Modeling Menu]
[AINSI] [Elicit]

Reference

Humphrey, W. (1989) Managing the Software Process. Reading, MA: Addison-Wesley. p. 247-286.

AINSI

Remarks on AINSI - An Inductive Software Process Improvement Method: Concrete Steps and Guidelines. (postscript)

1. What are the tasks in the process?

2. What are the dependencies between these tasks?

3. When do the tasks start and end?

4. Who are the actors that perform these tasks? What roles do these actors assume in the particular tasks?

5. What are the interdependencies between the actors?

The conceptual framework of Armitage and Kellner consists of three entity classes (agent, activity, artifact), and two aspects (relationships between and among entities, and behavior of enitities their relationships).

Elicit

The Elicit approach to process model elicitation is characterised by three dimensions: View (see Eliciting Formal Models of Software Engineering Processes, Method (see Elicit: A Method for Eliciting Process Models), and Tool.

The View dimension represents the different views from which one can visualise a process. In our projects, we generally use five perspectives:

1. Process Steps that are carried out in the software process,
2. Artifacts that are produced or consumed by the process steps,
3. Roles that are played by human and other agents in the process,
4. Resources that are necessary to carry out the process, and
5. Constraints that are acting on the process.

Another dimension to view is property. The property dimension attempts to capture attributes that describe the process. Elicit support three types of properties: descriptive, static, and dynamic.

To CIS Department at UMass Dartmouth
To UMass Dartmouth

Comments should be sent to

This document
Created: March 8, 1996
by RLU

Modified: August 6, 1996