Modeling the software process using coordination rules

Ciancarini, Paolo

doi:10.1109/enabl.1995.484547

Cited by 3 publications

(1 citation statement)

References 37 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Process definition usually lies on Process Modeling Languages (PML) based on some linguistic paradigms such as (Cass et al, 2000), Petri nets or logical languages; several of them are discussed in (Fuggetta, 2000). Others are componentbased software process support (Gary et al, 1998), role-based approaches (Kopka and Wellen, 2002), coordination rules (Ciancarini, 1995); some interesting reflections can be found in (Barnes and Gray, 2000). Even process support could based on tools integration mechanisms, like in (Pohl et al, 1999).…”

Section: Related Workmentioning

confidence: 99%

Defining and Using a Metamodel for Document-Centric Development Methodologies

Bollaín¹,

Garbajosa²

2007

Proceedings of the Second International Conference on Evaluation of Novel Approaches to Software Engineering

View full text Add to dashboard Cite

The concept of software product is often associated to software code; process documents are, therefore, considered as by-products. Also very frequently, customers primarily demand "results" and, in a second place, documentation. Development efforts are then focused on code production at the expense of documents quality and corresponding verification activities. As discussed within this paper, one of the root problems for this is that documentation in the context of methodologies is often described with not enough level of detail. This paper presents a metamodel that faces this problem. It is an extension of ISO/IEC 24744, the metamodel for methodologies development. Under this extension, documents can become the drivers of the methodology activities. Documents will be the artifact in which method engineers should focus for methodology development, by defining its structure and constraints. Developers will put their effort in filling sections of the documents as the way to progress in the process execution. This process execution will be guided by those documents defined by the method engineers. This approach can be, as well, the basis for a new approach to a Document-Centric Software Engineering Environment.

show abstract