The Experts below are selected from a list of 661812 Experts worldwide ranked by ideXlab platform
Maria Cecilia Bastarrica - One of the best experts on this subject based on the ideXlab platform.
-
MDE Software Process lines in small companies
Journal of Systems and Software, 2013Co-Authors: Julio Ariel Hurtado, Maria Cecilia Bastarrica, Sergio F. Ochoa, Jocelyn SimmondsAbstract:Software organizations specify their Software Processes so that Process knowledge can be systematically reused across projects. However, different projects may require different Processes. Defining a separate Process for each potential project context is expensive and error-prone, since these Processes must simultaneously evolve in a consistent manner. Moreover, an organization cannot envision all possible project contexts in advance because several variables may be involved, and these may also be combined in different ways. This problem is even worse in small companies since they usually cannot afford to define more than one Process. Software Process lines are a specific type of Software product lines, in the Software Process domain. A benefit of Software Process lines is that they allow Software Process customization with respect to a context. In this article we propose a model-driven approach for Software Process lines specification and configuration. The article also presents two industrial case studies carried out at two small Chilean Software development companies. Both companies have benefited from applying our approach to their Processes: new projects are now developed using custom Processes, Process knowledge is systematically reused, and the total time required to customize a Process is much shorter than before.
-
building Software Process lines with casper
International Conference on Software and System Process, 2012Co-Authors: Julio Ariel Hurtado Alegria, Maria Cecilia BastarricaAbstract:Software product quality and project productivity require defining suitable Software Process models. The best Process depends on the circumstances where it is applied. Typically, a Process engineer tailors a specific Process for each project or each project type from an organizational Software Process model. Frequently, tailoring is performed in an informal and reactive fashion, which is expensive, unrepeatable and error prone. Trying to deal with this challenge, we have built Casper, a meta-Process for defining adaptable Software Process models. This paper presents Casper illustrating it using the ISPW-6 Process. Casper meta-Process allows producing project specific Processes in a planned way using four Software Process principles and a set of Process practices that enable a feasible production strategy. According to its application to a canonical case, this paper concludes that Casper enables a practical technique for tailoring a Software Process model.
-
ICSSP - Building Software Process lines with CASPER
2012 International Conference on Software and System Process (ICSSP), 2012Co-Authors: Julio Ariel Hurtado Alegria, Maria Cecilia BastarricaAbstract:Software product quality and project productivity require defining suitable Software Process models. The best Process depends on the circumstances where it is applied. Typically, a Process engineer tailors a specific Process for each project or each project type from an organizational Software Process model. Frequently, tailoring is performed in an informal and reactive fashion, which is expensive, unrepeatable and error prone. Trying to deal with this challenge, we have built Casper, a meta-Process for defining adaptable Software Process models. This paper presents Casper illustrating it using the ISPW-6 Process. Casper meta-Process allows producing project specific Processes in a planned way using four Software Process principles and a set of Process practices that enable a feasible production strategy. According to its application to a canonical case, this paper concludes that Casper enables a practical technique for tailoring a Software Process model.
-
Software Process model blueprints
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process, 2010Co-Authors: Julio Ariel Hurtado Alegria, Alejandro Lagos, Alexandre Bergel, Maria Cecilia BastarricaAbstract:Explicitly defining a Software Process model is widely recognized as a good Software engineering practice. However, having a defined Process does not necessarily mean that this Process is good, sound and/or useful. There have been several approaches for Software Process evaluation including testing, simulation and metrics; the first one requires Software Process enactment, i.e., an expensive, risky and long Process, and the others require high expertise for correctly interpreting their meaning. In this paper we propose a visual approach for Software Process model evaluation based on three architectural view types, each one focusing on basic Process elements: ROLE BLUEPRINT, TASK BLUEPRINT and WORK PRODUCT BLUEPRINT. They enable visual evaluation of different perspectives of a Software Process, each being relevant for a particular stakeholder. We illustrate the proposed approach by applying it to the Software Process defined for a real world company that develops Software for retail. We show how design errors were identified.
-
Software Process model blueprints
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process, 2010Co-Authors: Julio Ariel Hurtado Alegria, Alejandro Lagos, Alexandre Bergel, Maria Cecilia BastarricaAbstract:Explicitly defining a Software Process model is widely recognized as a good Software engineering practice. However, having a defined Process does not necessarily mean that this Process is good, sound and/or useful. There have been several approaches for Software Process evaluation including testing, simulation and metrics; the first one requires Software Process enactment, i.e., an expensive, risky and long Process, and the others require high expertise for correctly interpreting their meaning. In this paper we propose a visual approach for Software Process model evaluation based on three architectural view types, each one focusing on basic Process elements: ROLE BLUEPRINT, TASK BLUEPRINT and WORK PRODUCT BLUEPRINT. They enable visual evaluation of different perspectives of a Software Process, each being relevant for a particular stakeholder. We illustrate the proposed approach by applying it to the Software Process defined for a real world company that develops Software for retail. We show how design errors were identified.
Fadila Aoussat - One of the best experts on this subject based on the ideXlab platform.
-
A DOMAIN ONTLOGY FOR Software Process REUSING
Computing and Informatics, 2014Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Mohamed Ahmed-nacerAbstract:Reuse the best practices and know-how capitalized from existing Software Process Models is a promising approach to model high quality Software Processes. This paper presents a part of an approach for Software Processes reuse based on Software architectures. This contribution is based on exploiting Software Process know-how and the solution proposed after the study of existing work on Software Process reuse field, our study focuses on approaches for reusing based on Software architectures and based on domain ontology. AoSP (Architecture oriented Software Process) approach, deals with the engineering "for" and "by" reusing Software Processes, it exploits the progress of two research fields that promote reusing for the Software Process reusing: domain ontologies and Software architectures. AoSP exploits an domain ontology to retrieve, describe and deploy Software Process architectures. This article details the engineering "for" reusing SPs step of AoSP, it explains how the Software Process architectures are described and discusses the Software Process ontology conceptualization and Software Process knowledge acquisition is done.
-
A Domain Ontology for Software Process Architecture Description
2012Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Mohamed Ahmed-nacerAbstract:This paper presents a part of an approach for Software Processes reuse based on Software architectures. This solution is proposed after the study of existing work on Software Process reuse field. Our study focuses on approaches for reusing based on Software architectures and domain ontology. AoSP (Architecture oriented Software Process) approach exploits the progress of two research fields that promote reusing for the Software Process reusing: Ontology and Software architectures. This article details how the Software Process architectures are described and discusses the Software Process ontology conceptualization and instantiation.
-
SPEM Extension with Software Process architectural concepts
2011Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Ahmed-nacer MohamedAbstract:SPEM is a metamodel adopted by the OMG for Software Processes engineering. For the Software Process architectures description, SPEM architectural concepts are very insufficient. Indeed, the existing concepts disallow describing configurations and explicit links specific to Software Process architectures and finally their deployment. The objective of this paper is to present an extension of SPEM (System and Software Process Engineering Metamodel) with lacking architectural concepts. This extension is an important step to implement a new approach for Software Process reusing based on Software architectures.
-
COMPSAC - SPEM Extension with Software Process Architectural Concepts
2011 IEEE 35th Annual Computer Software and Applications Conference, 2011Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Mohamed Ahmed NacerAbstract:SPEM is a metamodel adopted by the OMG for Software Processes engineering. For the Software Process architectures description, SPEM architectural concepts are very insufficient. Indeed, the existing concepts disallow describing configurations and explicit links specific to Software Process architectures and finally their deployment. The objective of this paper is to present an extension of SPEM (System and Software Process Engineering Metamodel) with lacking architectural concepts. This extension is an important step to implement a new approach for Software Process reusing based on Software architectures.
Mohamed Ahmed Nacer - One of the best experts on this subject based on the ideXlab platform.
-
COMPSAC - SPEM Extension with Software Process Architectural Concepts
2011 IEEE 35th Annual Computer Software and Applications Conference, 2011Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Mohamed Ahmed NacerAbstract:SPEM is a metamodel adopted by the OMG for Software Processes engineering. For the Software Process architectures description, SPEM architectural concepts are very insufficient. Indeed, the existing concepts disallow describing configurations and explicit links specific to Software Process architectures and finally their deployment. The objective of this paper is to present an extension of SPEM (System and Software Process Engineering Metamodel) with lacking architectural concepts. This extension is an important step to implement a new approach for Software Process reusing based on Software architectures.
Mourad Chabane Oussalah - One of the best experts on this subject based on the ideXlab platform.
-
A DOMAIN ONTLOGY FOR Software Process REUSING
Computing and Informatics, 2014Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Mohamed Ahmed-nacerAbstract:Reuse the best practices and know-how capitalized from existing Software Process Models is a promising approach to model high quality Software Processes. This paper presents a part of an approach for Software Processes reuse based on Software architectures. This contribution is based on exploiting Software Process know-how and the solution proposed after the study of existing work on Software Process reuse field, our study focuses on approaches for reusing based on Software architectures and based on domain ontology. AoSP (Architecture oriented Software Process) approach, deals with the engineering "for" and "by" reusing Software Processes, it exploits the progress of two research fields that promote reusing for the Software Process reusing: domain ontologies and Software architectures. AoSP exploits an domain ontology to retrieve, describe and deploy Software Process architectures. This article details the engineering "for" reusing SPs step of AoSP, it explains how the Software Process architectures are described and discusses the Software Process ontology conceptualization and Software Process knowledge acquisition is done.
-
A Domain Ontology for Software Process Architecture Description
2012Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Mohamed Ahmed-nacerAbstract:This paper presents a part of an approach for Software Processes reuse based on Software architectures. This solution is proposed after the study of existing work on Software Process reuse field. Our study focuses on approaches for reusing based on Software architectures and domain ontology. AoSP (Architecture oriented Software Process) approach exploits the progress of two research fields that promote reusing for the Software Process reusing: Ontology and Software architectures. This article details how the Software Process architectures are described and discusses the Software Process ontology conceptualization and instantiation.
-
SPEM Extension with Software Process architectural concepts
2011Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Ahmed-nacer MohamedAbstract:SPEM is a metamodel adopted by the OMG for Software Processes engineering. For the Software Process architectures description, SPEM architectural concepts are very insufficient. Indeed, the existing concepts disallow describing configurations and explicit links specific to Software Process architectures and finally their deployment. The objective of this paper is to present an extension of SPEM (System and Software Process Engineering Metamodel) with lacking architectural concepts. This extension is an important step to implement a new approach for Software Process reusing based on Software architectures.
-
COMPSAC - SPEM Extension with Software Process Architectural Concepts
2011 IEEE 35th Annual Computer Software and Applications Conference, 2011Co-Authors: Fadila Aoussat, Mourad Chabane Oussalah, Mohamed Ahmed NacerAbstract:SPEM is a metamodel adopted by the OMG for Software Processes engineering. For the Software Process architectures description, SPEM architectural concepts are very insufficient. Indeed, the existing concepts disallow describing configurations and explicit links specific to Software Process architectures and finally their deployment. The objective of this paper is to present an extension of SPEM (System and Software Process Engineering Metamodel) with lacking architectural concepts. This extension is an important step to implement a new approach for Software Process reusing based on Software architectures.
Julio Ariel Hurtado Alegria - One of the best experts on this subject based on the ideXlab platform.
-
building Software Process lines with casper
International Conference on Software and System Process, 2012Co-Authors: Julio Ariel Hurtado Alegria, Maria Cecilia BastarricaAbstract:Software product quality and project productivity require defining suitable Software Process models. The best Process depends on the circumstances where it is applied. Typically, a Process engineer tailors a specific Process for each project or each project type from an organizational Software Process model. Frequently, tailoring is performed in an informal and reactive fashion, which is expensive, unrepeatable and error prone. Trying to deal with this challenge, we have built Casper, a meta-Process for defining adaptable Software Process models. This paper presents Casper illustrating it using the ISPW-6 Process. Casper meta-Process allows producing project specific Processes in a planned way using four Software Process principles and a set of Process practices that enable a feasible production strategy. According to its application to a canonical case, this paper concludes that Casper enables a practical technique for tailoring a Software Process model.
-
ICSSP - Building Software Process lines with CASPER
2012 International Conference on Software and System Process (ICSSP), 2012Co-Authors: Julio Ariel Hurtado Alegria, Maria Cecilia BastarricaAbstract:Software product quality and project productivity require defining suitable Software Process models. The best Process depends on the circumstances where it is applied. Typically, a Process engineer tailors a specific Process for each project or each project type from an organizational Software Process model. Frequently, tailoring is performed in an informal and reactive fashion, which is expensive, unrepeatable and error prone. Trying to deal with this challenge, we have built Casper, a meta-Process for defining adaptable Software Process models. This paper presents Casper illustrating it using the ISPW-6 Process. Casper meta-Process allows producing project specific Processes in a planned way using four Software Process principles and a set of Process practices that enable a feasible production strategy. According to its application to a canonical case, this paper concludes that Casper enables a practical technique for tailoring a Software Process model.
-
Software Process model blueprints
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process, 2010Co-Authors: Julio Ariel Hurtado Alegria, Alejandro Lagos, Alexandre Bergel, Maria Cecilia BastarricaAbstract:Explicitly defining a Software Process model is widely recognized as a good Software engineering practice. However, having a defined Process does not necessarily mean that this Process is good, sound and/or useful. There have been several approaches for Software Process evaluation including testing, simulation and metrics; the first one requires Software Process enactment, i.e., an expensive, risky and long Process, and the others require high expertise for correctly interpreting their meaning. In this paper we propose a visual approach for Software Process model evaluation based on three architectural view types, each one focusing on basic Process elements: ROLE BLUEPRINT, TASK BLUEPRINT and WORK PRODUCT BLUEPRINT. They enable visual evaluation of different perspectives of a Software Process, each being relevant for a particular stakeholder. We illustrate the proposed approach by applying it to the Software Process defined for a real world company that develops Software for retail. We show how design errors were identified.
-
Software Process model blueprints
ICSP'10 Proceedings of the 2010 international conference on New modeling concepts for today's software processes: software process, 2010Co-Authors: Julio Ariel Hurtado Alegria, Alejandro Lagos, Alexandre Bergel, Maria Cecilia BastarricaAbstract:Explicitly defining a Software Process model is widely recognized as a good Software engineering practice. However, having a defined Process does not necessarily mean that this Process is good, sound and/or useful. There have been several approaches for Software Process evaluation including testing, simulation and metrics; the first one requires Software Process enactment, i.e., an expensive, risky and long Process, and the others require high expertise for correctly interpreting their meaning. In this paper we propose a visual approach for Software Process model evaluation based on three architectural view types, each one focusing on basic Process elements: ROLE BLUEPRINT, TASK BLUEPRINT and WORK PRODUCT BLUEPRINT. They enable visual evaluation of different perspectives of a Software Process, each being relevant for a particular stakeholder. We illustrate the proposed approach by applying it to the Software Process defined for a real world company that develops Software for retail. We show how design errors were identified.
-
ICSP - Software Process model blueprints
Lecture Notes in Computer Science, 2010Co-Authors: Julio Ariel Hurtado Alegria, Alejandro Lagos, Alexandre Bergel, Maria Cecilia BastarricaAbstract:Explicitly defining a Software Process model is widely recognized as a good Software engineering practice. However, having a defined Process does not necessarily mean that this Process is good, sound and/or useful. There have been several approaches for Software Process evaluation including testing, simulation and metrics; the first one requires Software Process enactment, i.e., an expensive, risky and long Process, and the others require high expertise for correctly interpreting their meaning. In this paper we propose a visual approach for Software Process model evaluation based on three architectural view types, each one focusing on basic Process elements: ROLE BLUEPRINT, TASK BLUEPRINT and WORK PRODUCT BLUEPRINT. They enable visual evaluation of different perspectives of a Software Process, each being relevant for a particular stakeholder. We illustrate the proposed approach by applying it to the Software Process defined for a real world company that develops Software for retail. We show how design errors were identified.
