The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. ex. Some numerals are expressed as "XNUMX".
Copyrights notice
The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. Copyrights notice
Os processos de software e os modelos correspondentes são entidades dinâmicas que são frequentemente alteradas e evoluídas por trabalhadores qualificados, como os membros de uma equipe de desenvolvimento de software. Consequentemente, a flexibilidade do processo foi identificada como uma das características mais importantes que deve ser suportada tanto pelas Linguagens de Modelagem de Processos (PMLs) como pelas ferramentas de software que gerem os processos. Contudo, na prática diária, a maioria dos membros da equipe de software não deseja flexibilidade total. Preferem ter flexibilidade controlada, ou seja, aprender e seguir conselhos previamente modelados por um engenheiro de processo sobre quais e como podem alterar os elementos que compõem um processo de software. Como os modelos de processos constituem um veículo preferencial para compartilhar e comunicar conhecimento sobre processos de software, o engenheiro de processos precisa de uma PML que possa expressar essa flexibilidade controlada, juntamente com outras perspectivas de processos. Para alcançar esse PML aprimorado, primeiro precisamos de um conjunto sólido de conceitos e relacionamentos que defina o domínio de conhecimento associado à modelagem de flexibilidade controlada. Neste artigo capturamos e representamos este domínio usando Mapas Conceituais (Cmaps). Estes incluem diagramas e descrições que revelam as relações entre os conceitos envolvidos. Os Cmaps propostos podem então ser usados como entrada para estender uma PML com construções de modelagem para expressar flexibilidade controlada dentro de processos de software. Os engenheiros de processo podem usar essas construções para definir, em um modelo de processo, conselhos sobre mudanças que podem ser feitas no próprio modelo ou em instâncias relacionadas. Os membros da equipe de software podem então consultar essas informações de flexibilidade controlada nos modelos de processo e realizar as alterações necessárias.
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Copiar
Ricardo MARTINHO, Dulce DOMINGOS, João VARAJÃO, "Concept Maps for the Modelling of Controlled Flexibility in Software Processes" in IEICE TRANSACTIONS on Information,
vol. E93-D, no. 8, pp. 2190-2197, August 2010, doi: 10.1587/transinf.E93.D.2190.
Abstract: Software processes and corresponding models are dynamic entities that are often changed and evolved by skillful knowledge workers such as the members of a software development team. Consequently, process flexibility has been identified as one of the most important features that should be supported by both Process Modelling Languages (PMLs) and software tools that manage the processes. However, in the everyday practice, most software team members do not want total flexibility. They rather prefer to have controlled flexibility, i.e., to learn and follow advices previously modelled by a process engineer on which and how they can change the elements that compose a software process. Since process models constitute a preferred vehicle for sharing and communicating knowledge on software processes, the process engineer needs a PML that can express this controlled flexibility, along with other process perspectives. To achieve this enhanced PML, we first need a sound core set of concepts and relationships that defines the knowledge domain associated with the modelling of controlled flexibility. In this paper we capture and represent this domain by using Concept Maps (Cmaps). These include diagrams and descriptions that elicit the relationships between the concepts involved. The proposed Cmaps can then be used as input to extend a PML with modelling constructs to express controlled flexibility within software processes. Process engineers can use these constructs to define, in a process model, advices on changes that can be made to the model itself or to related instances. Software team members can then consult this controlled flexibility information within the process models and perform changes accordingly.
URL: https://global.ieice.org/en_transactions/information/10.1587/transinf.E93.D.2190/_p
Copiar
@ARTICLE{e93-d_8_2190,
author={Ricardo MARTINHO, Dulce DOMINGOS, João VARAJÃO, },
journal={IEICE TRANSACTIONS on Information},
title={Concept Maps for the Modelling of Controlled Flexibility in Software Processes},
year={2010},
volume={E93-D},
number={8},
pages={2190-2197},
abstract={Software processes and corresponding models are dynamic entities that are often changed and evolved by skillful knowledge workers such as the members of a software development team. Consequently, process flexibility has been identified as one of the most important features that should be supported by both Process Modelling Languages (PMLs) and software tools that manage the processes. However, in the everyday practice, most software team members do not want total flexibility. They rather prefer to have controlled flexibility, i.e., to learn and follow advices previously modelled by a process engineer on which and how they can change the elements that compose a software process. Since process models constitute a preferred vehicle for sharing and communicating knowledge on software processes, the process engineer needs a PML that can express this controlled flexibility, along with other process perspectives. To achieve this enhanced PML, we first need a sound core set of concepts and relationships that defines the knowledge domain associated with the modelling of controlled flexibility. In this paper we capture and represent this domain by using Concept Maps (Cmaps). These include diagrams and descriptions that elicit the relationships between the concepts involved. The proposed Cmaps can then be used as input to extend a PML with modelling constructs to express controlled flexibility within software processes. Process engineers can use these constructs to define, in a process model, advices on changes that can be made to the model itself or to related instances. Software team members can then consult this controlled flexibility information within the process models and perform changes accordingly.},
keywords={},
doi={10.1587/transinf.E93.D.2190},
ISSN={1745-1361},
month={August},}
Copiar
TY - JOUR
TI - Concept Maps for the Modelling of Controlled Flexibility in Software Processes
T2 - IEICE TRANSACTIONS on Information
SP - 2190
EP - 2197
AU - Ricardo MARTINHO
AU - Dulce DOMINGOS
AU - João VARAJÃO
PY - 2010
DO - 10.1587/transinf.E93.D.2190
JO - IEICE TRANSACTIONS on Information
SN - 1745-1361
VL - E93-D
IS - 8
JA - IEICE TRANSACTIONS on Information
Y1 - August 2010
AB - Software processes and corresponding models are dynamic entities that are often changed and evolved by skillful knowledge workers such as the members of a software development team. Consequently, process flexibility has been identified as one of the most important features that should be supported by both Process Modelling Languages (PMLs) and software tools that manage the processes. However, in the everyday practice, most software team members do not want total flexibility. They rather prefer to have controlled flexibility, i.e., to learn and follow advices previously modelled by a process engineer on which and how they can change the elements that compose a software process. Since process models constitute a preferred vehicle for sharing and communicating knowledge on software processes, the process engineer needs a PML that can express this controlled flexibility, along with other process perspectives. To achieve this enhanced PML, we first need a sound core set of concepts and relationships that defines the knowledge domain associated with the modelling of controlled flexibility. In this paper we capture and represent this domain by using Concept Maps (Cmaps). These include diagrams and descriptions that elicit the relationships between the concepts involved. The proposed Cmaps can then be used as input to extend a PML with modelling constructs to express controlled flexibility within software processes. Process engineers can use these constructs to define, in a process model, advices on changes that can be made to the model itself or to related instances. Software team members can then consult this controlled flexibility information within the process models and perform changes accordingly.
ER -