Role-based views to approach suitable software process models for the development of multimedia systems

Kopka, Corina; Wellen, Ursula

doi:10.1109/mmse.2002.1181606

Cited by 4 publications

(2 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Compared with these works, this article motivated process views from the perspective of role-based perception control, and analyzed the view derivation and composition according to the role hierarchy and interactions between roles. Kopka and Wellen [2002] have studied role-based process views in the domain of multimedia system development process. In preliminary work on this topic, they proposed the idea of creating different logical views of the same business process for different involved roles, without further exploring the support to automatic view generation or formal process perception description.…”

Section: Related Work and Discussionmentioning

confidence: 99%

Role-Based Process View Derivation and Composition

Zhao

Liu

Yongchareon

et al. 2015

ACM Trans. Manage. Inf. Syst.

View full text Add to dashboard Cite

The process view concept deploys a partial and temporal representation to adjust the visible view of a business process according to various perception constraints of users. Process view technology is of practical use for privacy protection and authorization control in process-oriented business management. Owing to complex organizational structure, it is challenging for large companies to accurately specify the diverse perception of different users over business processes. Aiming to tackle this issue, this article presents a rolebased process view model to incorporate role dependencies into process view derivation. Compared to existing process view approaches, ours particularly supports runtime updates to the process view perceivable to a user with specific view merging operations, thereby enabling the dynamic tracing of process perception. A series of rules and theorems are established to guarantee the structural consistency and validity of process view transformation. A hypothetical case is conducted to illustrate the feasibility of our approach, and a prototype is developed for the proof-of-concept purpose.

show abstract

Section: Related Work and Discussionmentioning

confidence: 99%

Role-Based Process View Derivation and Composition

Zhao

Liu

Yongchareon

et al. 2015

ACM Trans. Manage. Inf. Syst.

View full text Add to dashboard Cite

show abstract

“…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

Preliminary Results from a Survey of Multimedia Development Practices in Australia

Hannington

Reed

2006

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Role-based views to approach suitable software process models for the development of multimedia systems

Cited by 4 publications

References 13 publications

Role-Based Process View Derivation and Composition

Role-Based Process View Derivation and Composition

Defining and Using a Metamodel for Document-Centric Development Methodologies

Preliminary Results from a Survey of Multimedia Development Practices in Australia

Contact Info

Product

Resources

About