Carlos Monsalve | ESPOL (Escuela Superior Politécnica del Litoral) (original) (raw)
Uploads
Papers by Carlos Monsalve
2015 Second International Conference on eDemocracy & eGovernment (ICEDEG), 2015
IECON Proceedings (Industrial Electronics Conference), 2012
Business process models have proved to be useful for requirements elicitation. Since software dev... more Business process models have proved to be useful for requirements elicitation. Since software development depends on the quality of the requirements specifications, generating highquality business process models is therefore critical. A key factor for achieving this is the expressiveness in terms of completeness and clarity of the modeling notation for the domain being modeled. The Bunge-Wand-Weber (BWW) representation model is frequently used for assessing the expressiveness of business process modeling notations. This article presents some propositions to adapt the BWW representation model to allow its application to the software requirements elicitation domain.
ABSTRACT En este documento se propone una metodología automatizada para la asignación de frecuenc... more ABSTRACT En este documento se propone una metodología automatizada para la asignación de frecuencias fijas en una red celular GSM, con el objetivo de mejorar la calidad del enlace de radio en las capas BCCH y Regular, reduciendo la interferencia entre celdas provocada por el reuso de frecuencias. La metodología propuesta consiste en la implementación del algoritmo de un árbol de búsqueda aproximadamente no determinístico (ANTS) para crear una macro en un libro de Microsoft Excel que realice la asignación de frecuencias fijas a cada transceptor de la red que así lo requiera. La herramienta toma como variables de entrada principales la configuración física de la red, e información acerca de los niveles de interferencia entre celdas, con las cuales puede generar planes óptimos de frecuencias fijas. Los planes que genere la herramienta implementada serán evaluados con la ayuda de un simulador de redes GSM/EDGE, el cual permitirá obtener los indicadores de desempeño de los mismos. Con fines comparativos, se elaborarán planes de frecuencias mediante un método tradicional de asignación de frecuencias. Al comparar el método tradicional con el método automatizado desarrollado en este trabajo, se demostrará que este último logra ganancias en términos de calidad y capacidad.
Business process models can be useful for requirements elicitation, among other things. Software ... more Business process models can be useful for requirements elicitation, among other things. Software development depends on the quality of the requirements elicitation activities, and so adequately modeling business processes (BPs) is critical. A key factor in achieving this is the active participation of all the stakeholders in the development of a shared vision of BPs. Unfortunately, organizations often find themselves left with inconsistent BPs that do not cover all the stakeholders' needs and constraints. However, consolidation of the various stakeholder requirements may be facilitated through the use of multiple levels of abstraction (MLA). This article contributes to the research into MLA use in business process modeling (BPM) for software requirements by reviewing the theoretical foundations of MLA and their use in various BP-oriented approaches.
Functional size measurement (FSM) is an important component of a software project, as it provides... more Functional size measurement (FSM) is an important component of a software project, as it provides information for estimating the effort required to develop the measured software. For planning purposes, FSM should be performed during the early stages of the project. Considering that a common use of business process models is to gather requirements from the early stages of the project, this raises the opportunity that a business process model could be a valuable source of information for FSM. This paper analyzes the feasibility of such an approach for the business application domain, including the derivation of the modeling rules for measurement purposes and the rules to map the modeling constructs of a business process modeling language into the COSMIC FSM method concepts. The results are compared with those of a previous FSM case study.
Business process models (BPM) can be useful for requirements elicitation, among other uses. Since... more Business process models (BPM) can be useful for requirements elicitation, among other uses. Since the active participation of all stakeholders is a key factor for successful requirements engineering, it is important that BPM be shared by all stakeholders. Unfortunately, organizations may end up with inconsistent BPM not covering all stakeholders' needs and constraints. The use of multiple levels of abstraction (MLA), such as at the strategic, tactical and operational levels, is often used in various process-oriented initiatives to facilitate the consolidation of various stakeholders' needs and constraints. This article surveys the use of MLA in recent BPM research publications and reports on a BPM action-research case study conducted in a Canadian organization, with the aim of exploring the usefulness of the strategic level.
Business process models (BPM) can be useful for requirements elicitation, among other uses. Since... more Business process models (BPM) can be useful for requirements elicitation, among other uses. Since the active participation of all stakeholders is a key factor for successful requirements engineering, it is important that BPM be shared by all stakeholders. Unfortunately, organizations may end up with inconsistent BPM not covering all stakeholders' needs and constraints. The use of multiple levels of abstraction (MLA), such as at the strategic, tactical and operational levels, is often used in various process-oriented initiatives to facilitate the consolidation of various stakeholders' needs and constraints. This article surveys the use of MLA in recent BPM research publications and reports on a BPM action-research case study conducted in a Canadian organization, with the aim of exploring the usefulness of the strategic level.
Business process models can be useful for requirements elicitation, among other things. Software ... more Business process models can be useful for requirements elicitation, among other things. Software development depends on the quality of the requirements elicitation activities, and so adequately modeling business processes (BPs) is critical. A key factor in achieving this is the active participation of all the stakeholders in the development of a shared vision of BPs. Unfortunately, organizations often find themselves left with inconsistent BPs that do not cover all the stakeholders' needs and constraints. However, consolidation of the various stakeholder requirements may be facilitated through the use of multiple levels of abstraction (MLA). This article contributes to the research into MLA use in business process modeling (BPM) for software requirements by reviewing the theoretical foundations of MLA and their use in various BP-oriented approaches.
Evidence shows that proposals for new modeling notations emerge and evolution of current ones are... more Evidence shows that proposals for new modeling notations emerge and evolution of current ones are becoming more complex, often in an attempt to satisfy the many different modeling perspectives required by each stakeholder. This paper presents a method to identify the specific notation construct requirements, at multiple levels of abstraction, which satisfy the needs of a stakeholder when performing a specific task. Initially the focus is on two different stakeholders: software engineers (SE) and business analysts (BA), and one specific software engineering activity: requirements eliciting and analysis. The specific body of knowledge of the two stakeholders (Software Engineering Book of Knowledge (SWEBOK) for the SE, and Business Analysis Body of Knowledge (BABOK) for the BA) are used to identify each stakeholder specific notation construct requirements, at multiple levels of abstraction, in order to propose a simplification of their notation and constructs set. This paper presents solution avenues to simplify business process modeling notations by identifying the specific constructs preferred by different stakeholders.
Functional size measurement (FSM) is an important component of a software project, as it provides... more Functional size measurement (FSM) is an important component of a software project, as it provides information for estimating the effort required to develop the measured software. For planning purposes, FSM should be performed during the early stages of the project. Considering that a common use of business process models is to gather requirements from the early stages of the project, this raises the opportunity that a business process model could be a valuable source of information for FSM. This paper analyzes the feasibility of such an approach for the business application domain, including the derivation of the modeling rules for measurement purposes and the rules to map the modeling constructs of a business process modeling language into the COSMIC FSM method concepts. The results are compared with those of a previous FSM case study.
1 specifies that a functional size measurement (FSM) method must provide 19 measurement procedure... more 1 specifies that a functional size measurement (FSM) method must provide 19 measurement procedures to quantify the functional user requirements (FURs) of soft-20 ware. Such quantitative information, functional size, is typically used, for instance, in 21 software estimation. One of the international standards for FSM is the COSMIC FSM 22 method -ISO 19761 -which was designed to be applied both to the business applica-23 tion (BA) software domain and to the real-time software domain. A recurrent problem 24
2015 Second International Conference on eDemocracy & eGovernment (ICEDEG), 2015
IECON Proceedings (Industrial Electronics Conference), 2012
Business process models have proved to be useful for requirements elicitation. Since software dev... more Business process models have proved to be useful for requirements elicitation. Since software development depends on the quality of the requirements specifications, generating highquality business process models is therefore critical. A key factor for achieving this is the expressiveness in terms of completeness and clarity of the modeling notation for the domain being modeled. The Bunge-Wand-Weber (BWW) representation model is frequently used for assessing the expressiveness of business process modeling notations. This article presents some propositions to adapt the BWW representation model to allow its application to the software requirements elicitation domain.
ABSTRACT En este documento se propone una metodología automatizada para la asignación de frecuenc... more ABSTRACT En este documento se propone una metodología automatizada para la asignación de frecuencias fijas en una red celular GSM, con el objetivo de mejorar la calidad del enlace de radio en las capas BCCH y Regular, reduciendo la interferencia entre celdas provocada por el reuso de frecuencias. La metodología propuesta consiste en la implementación del algoritmo de un árbol de búsqueda aproximadamente no determinístico (ANTS) para crear una macro en un libro de Microsoft Excel que realice la asignación de frecuencias fijas a cada transceptor de la red que así lo requiera. La herramienta toma como variables de entrada principales la configuración física de la red, e información acerca de los niveles de interferencia entre celdas, con las cuales puede generar planes óptimos de frecuencias fijas. Los planes que genere la herramienta implementada serán evaluados con la ayuda de un simulador de redes GSM/EDGE, el cual permitirá obtener los indicadores de desempeño de los mismos. Con fines comparativos, se elaborarán planes de frecuencias mediante un método tradicional de asignación de frecuencias. Al comparar el método tradicional con el método automatizado desarrollado en este trabajo, se demostrará que este último logra ganancias en términos de calidad y capacidad.
Business process models can be useful for requirements elicitation, among other things. Software ... more Business process models can be useful for requirements elicitation, among other things. Software development depends on the quality of the requirements elicitation activities, and so adequately modeling business processes (BPs) is critical. A key factor in achieving this is the active participation of all the stakeholders in the development of a shared vision of BPs. Unfortunately, organizations often find themselves left with inconsistent BPs that do not cover all the stakeholders' needs and constraints. However, consolidation of the various stakeholder requirements may be facilitated through the use of multiple levels of abstraction (MLA). This article contributes to the research into MLA use in business process modeling (BPM) for software requirements by reviewing the theoretical foundations of MLA and their use in various BP-oriented approaches.
Functional size measurement (FSM) is an important component of a software project, as it provides... more Functional size measurement (FSM) is an important component of a software project, as it provides information for estimating the effort required to develop the measured software. For planning purposes, FSM should be performed during the early stages of the project. Considering that a common use of business process models is to gather requirements from the early stages of the project, this raises the opportunity that a business process model could be a valuable source of information for FSM. This paper analyzes the feasibility of such an approach for the business application domain, including the derivation of the modeling rules for measurement purposes and the rules to map the modeling constructs of a business process modeling language into the COSMIC FSM method concepts. The results are compared with those of a previous FSM case study.
Business process models (BPM) can be useful for requirements elicitation, among other uses. Since... more Business process models (BPM) can be useful for requirements elicitation, among other uses. Since the active participation of all stakeholders is a key factor for successful requirements engineering, it is important that BPM be shared by all stakeholders. Unfortunately, organizations may end up with inconsistent BPM not covering all stakeholders' needs and constraints. The use of multiple levels of abstraction (MLA), such as at the strategic, tactical and operational levels, is often used in various process-oriented initiatives to facilitate the consolidation of various stakeholders' needs and constraints. This article surveys the use of MLA in recent BPM research publications and reports on a BPM action-research case study conducted in a Canadian organization, with the aim of exploring the usefulness of the strategic level.
Business process models (BPM) can be useful for requirements elicitation, among other uses. Since... more Business process models (BPM) can be useful for requirements elicitation, among other uses. Since the active participation of all stakeholders is a key factor for successful requirements engineering, it is important that BPM be shared by all stakeholders. Unfortunately, organizations may end up with inconsistent BPM not covering all stakeholders' needs and constraints. The use of multiple levels of abstraction (MLA), such as at the strategic, tactical and operational levels, is often used in various process-oriented initiatives to facilitate the consolidation of various stakeholders' needs and constraints. This article surveys the use of MLA in recent BPM research publications and reports on a BPM action-research case study conducted in a Canadian organization, with the aim of exploring the usefulness of the strategic level.
Business process models can be useful for requirements elicitation, among other things. Software ... more Business process models can be useful for requirements elicitation, among other things. Software development depends on the quality of the requirements elicitation activities, and so adequately modeling business processes (BPs) is critical. A key factor in achieving this is the active participation of all the stakeholders in the development of a shared vision of BPs. Unfortunately, organizations often find themselves left with inconsistent BPs that do not cover all the stakeholders' needs and constraints. However, consolidation of the various stakeholder requirements may be facilitated through the use of multiple levels of abstraction (MLA). This article contributes to the research into MLA use in business process modeling (BPM) for software requirements by reviewing the theoretical foundations of MLA and their use in various BP-oriented approaches.
Evidence shows that proposals for new modeling notations emerge and evolution of current ones are... more Evidence shows that proposals for new modeling notations emerge and evolution of current ones are becoming more complex, often in an attempt to satisfy the many different modeling perspectives required by each stakeholder. This paper presents a method to identify the specific notation construct requirements, at multiple levels of abstraction, which satisfy the needs of a stakeholder when performing a specific task. Initially the focus is on two different stakeholders: software engineers (SE) and business analysts (BA), and one specific software engineering activity: requirements eliciting and analysis. The specific body of knowledge of the two stakeholders (Software Engineering Book of Knowledge (SWEBOK) for the SE, and Business Analysis Body of Knowledge (BABOK) for the BA) are used to identify each stakeholder specific notation construct requirements, at multiple levels of abstraction, in order to propose a simplification of their notation and constructs set. This paper presents solution avenues to simplify business process modeling notations by identifying the specific constructs preferred by different stakeholders.
Functional size measurement (FSM) is an important component of a software project, as it provides... more Functional size measurement (FSM) is an important component of a software project, as it provides information for estimating the effort required to develop the measured software. For planning purposes, FSM should be performed during the early stages of the project. Considering that a common use of business process models is to gather requirements from the early stages of the project, this raises the opportunity that a business process model could be a valuable source of information for FSM. This paper analyzes the feasibility of such an approach for the business application domain, including the derivation of the modeling rules for measurement purposes and the rules to map the modeling constructs of a business process modeling language into the COSMIC FSM method concepts. The results are compared with those of a previous FSM case study.
1 specifies that a functional size measurement (FSM) method must provide 19 measurement procedure... more 1 specifies that a functional size measurement (FSM) method must provide 19 measurement procedures to quantify the functional user requirements (FURs) of soft-20 ware. Such quantitative information, functional size, is typically used, for instance, in 21 software estimation. One of the international standards for FSM is the COSMIC FSM 22 method -ISO 19761 -which was designed to be applied both to the business applica-23 tion (BA) software domain and to the real-time software domain. A recurrent problem 24