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
Proses perisian dan model yang sepadan ialah entiti dinamik yang sering diubah dan berkembang oleh pekerja berpengetahuan mahir seperti ahli pasukan pembangunan perisian. Akibatnya, fleksibiliti proses telah dikenal pasti sebagai salah satu ciri terpenting yang harus disokong oleh kedua-dua Bahasa Pemodelan Proses (PML) dan alat perisian yang menguruskan proses. Walau bagaimanapun, dalam amalan harian, kebanyakan ahli pasukan perisian tidak mahukan fleksibiliti sepenuhnya. Mereka lebih suka mempunyai fleksibiliti yang terkawal, iaitu, untuk mempelajari dan mengikuti nasihat yang dimodelkan sebelum ini oleh jurutera proses yang mana dan bagaimana mereka boleh mengubah elemen yang menyusun proses perisian. Memandangkan model proses membentuk kenderaan pilihan untuk berkongsi dan menyampaikan pengetahuan tentang proses perisian, jurutera proses memerlukan PML yang boleh menyatakan fleksibiliti terkawal ini, bersama-sama dengan perspektif proses yang lain. Untuk mencapai PML yang dipertingkatkan ini, pertama sekali kita memerlukan set konsep dan perhubungan teras yang kukuh yang mentakrifkan domain pengetahuan yang dikaitkan dengan pemodelan fleksibiliti terkawal. Dalam makalah ini kami menangkap dan mewakili domain ini dengan menggunakan Peta Konsep (Cmaps). Ini termasuk gambar rajah dan huraian yang menimbulkan hubungan antara konsep yang terlibat. Cmaps yang dicadangkan kemudiannya boleh digunakan sebagai input untuk melanjutkan PML dengan binaan pemodelan untuk menyatakan fleksibiliti terkawal dalam proses perisian. Jurutera proses boleh menggunakan binaan ini untuk mentakrifkan, dalam model proses, nasihat tentang perubahan yang boleh dibuat pada model itu sendiri atau kepada kejadian yang berkaitan. Ahli pasukan perisian kemudiannya boleh merujuk maklumat fleksibiliti terkawal ini dalam model proses dan melakukan perubahan dengan sewajarnya.
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.
Salinan
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
Salinan
@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},}
Salinan
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 -