scispace - formally typeset
Open Access

MVP-L Language Report Version 2

Reads0
Chats0
TLDR
The need for MVP-L is motivated, the prototype language is introduced, and further improvements to the language will be triggered by lessons learned from applications and experiments are assumed.
Abstract
Intellectual control over software development projects requires the existence of an integrated set of explicit models of the products to be developed, the processes used to develop them, the resources needed, and the productivity and quality aspects involved. In recent years the development of languages, methods and tools for modeling software processes, analyzing and enacting them has become a major emphasis of software engineering research. The majority of current process research concentrates on prescriptive modeling of small, completely formalizable processes and their execution entirely on computers. This research direction has produced process modeling languages suitable for machine rather than human consumption. The MVP project, launched at the University of Maryland and continued at Universitat Kaiserslautern, emphasizes building descriptive models of large, real-world processes and their use by humans and computers for the purpose of understanding, analyzing, guiding and improving software development projects. The language MVP-L has been developed with these purposes in mind. In this paper, we motivate the need for MVP-L, introduce the prototype language, and demonstrate its uses. We assume that further improvements to our language will be triggered by lessons learned from applications and experiments.

read more

Citations
More filters
Journal ArticleDOI

Knowledge-based techniques to increase the flexibility of workflow management

TL;DR: This paper describes how knowledge-based techniques can be used to overcome problems of workflow management in engineering applications using explicit process and product models as a basis for a workflow interpreter, resulting in increased flexibility of project coordination and enactment.
Proceedings ArticleDOI

Software process support over the Internet

TL;DR: The MILOS system as mentioned in this paper integrates process modeling with project planning and enactment, allowing refining and changing process models during project execution, and it supports change notifications and helps the project participants to ensure that the project plan as well as the state of the enactment engine reflect the "real world" development process.
Journal ArticleDOI

Managing process inconsistency using viewpoints

TL;DR: An approach to process analysis that helps discover different perceptions of a software process and that supports the discovery of process inconsistencies and process improvements stimulated by these inconsistencies is presented.
Proceedings ArticleDOI

The role of software process modeling in planning industrial measurement programs

TL;DR: This work provides guidelines that state how software processes should be modeled in order to support the introduction of measurement in a software project and presents the lessons learned from jointly applying software process modeling and measurement technologies in two industrial software projects.
Book ChapterDOI

The Ensemble Development Life Cycle and Best Practices for Collective Autonomic Systems

TL;DR: A software development life cycle that helps developers to engineer adaptive behavior and to address the issues posed by the diversity of self-* properties is proposed and a pattern catalog for the development of collective autonomic systems is presented to ease the engineering process.
Related Papers (5)