Stability for component integration assessment

Component-Based Software Development is focused on assembling previously existing components (COTS and other non-developmental items) into larger systems, and migrating existing systems toward component approaches. Ideally, most of the application developer’s time is spent integrating components. We present an approach that can be used in the process of establishing component integration’s quality as an important field to resolving CBS quality problems – problems ranging from CBS quality definition, measurement, analysis, and improvement to tools, methods and processes. In this paper, we introduce an important property we called system’s stability as part of a cycle for assessing and improving component-based systems. This property is the basis for determining the impact of incorporating COTS components into a stable system.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

Issues for assessing component-based systems

The use of component-based software has become more and more important in state-of-the-art and state-of-the-practice of software and system development. Using COTS software promises faster time-to-market, which can yield substantial advantages over competitors with regards to earlier placement of a new product on a market. At the same time, component-based software introduces risks such as unknown quality properties of the components in use that can inject harmful side effects into the final product. This paper proposes a multidimensional classification scheme for assessing component-based systems. The classification scheme provides insight into what quality characteristics, managerial features, or assessment methods and techniques might be used for evaluating different component artefacts.Eje: Ingeniería de softwareRed de Universidades con Carreras en Informática (RedUNCI

Issues for assessing component-based systems

The use of component-based software has become more and more important in state-of-the-art and state-of-the-practice of software and system development. Using COTS software promises faster time-to-market, which can yield substantial advantages over competitors with regards to earlier placement of a new product on a market. At the same time, component-based software introduces risks such as unknown quality properties of the components in use that can inject harmful side effects into the final product. This paper proposes a multidimensional classification scheme for assessing component-based systems. The classification scheme provides insight into what quality characteristics, managerial features, or assessment methods and techniques might be used for evaluating different component artefacts.Eje: Ingeniería de softwareRed de Universidades con Carreras en Informática (RedUNCI

Stability for component integration assessment

Component-Based Software Development is focused on assembling previously existing components (COTS and other non-developmental items) into larger systems, and migrating existing systems toward component approaches. Ideally, most of the application developer’s time is spent integrating components. We present an approach that can be used in the process of establishing component integration’s quality as an important field to resolving CBS quality problems – problems ranging from CBS quality definition, measurement, analysis, and improvement to tools, methods and processes. In this paper, we introduce an important property we called system’s stability as part of a cycle for assessing and improving component-based systems. This property is the basis for determining the impact of incorporating COTS components into a stable system.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

Supply Chain Management Software Systems Integration and Version Upgrades: Vendor and Customer Based Framework

Integration and upgrade phases of an information systems project are as critical to an organization as the first time the system is implemented. In order to make the ex-post implementation of an IT project completely successful and sustain the adopted information systems, the basic definition of success needs to be extended to include customer satisfaction factors as well as vendor capabilities. This study focuses on identifying the key elements that managers consider when making the decision to upgrade and integrate supply chain management systems that are already in use. We present a framework on both vendor and customer perspectives in the evaluation of supply chain management software systems integration and version upgrades

Issues for assessing component-based systems

The use of component-based software has become more and more important in state-of-the-art and state-of-the-practice of software and system development. Using COTS software promises faster time-to-market, which can yield substantial advantages over competitors with regards to earlier placement of a new product on a market. At the same time, component-based software introduces risks such as unknown quality properties of the components in use that can inject harmful side effects into the final product. This paper proposes a multidimensional classification scheme for assessing component-based systems. The classification scheme provides insight into what quality characteristics, managerial features, or assessment methods and techniques might be used for evaluating different component artefacts.Eje: Ingeniería de softwareRed de Universidades con Carreras en Informática (RedUNCI

Quantifying software architecture attributes

Software architecture holds the promise of advancing the state of the art in software engineering. The architecture is emerging as the focal point of many modem reuse/evolutionary paradigms, such as Product Line Engineering, Component Based Software Engineering, and COTS-based software development. The author focuses his research work on characterizing some properties of a software architecture. He tries to use software metrics to represent the error propagation probabilities, change propagation probabilities, and requirements change propagation probabilities of a software architecture. Error propagation probability reflects the probability that an error that arises in one component of the architecture will propagate to other components of the architecture at run-time. Change propagation probability reflects, for a given pair of components A and B, the probability that if A is changed in a corrective/perfective maintenance operation, B has to be changed to maintain the overall function the system. Requirements change propagation probability reflects the likelihood that a requirement change that arises in one component of the architecture propagates to other components. For each case, the author presents the analytical formulas which mainly based on statistical theory and empirical studies. Then the author studies the correlations between analytical results and empirical results. The author also uses several metrics to quantify the properties of a Product Line Architecture, such as scoping, variability, commonality, and applicability. He presents his proposed means to measure the properties and the results of the case studies

State of the art for the systematic construction and analysis of i* models for assessing COTS-based systems development

This document presents the state of the art related with the systematic construction and analysis of i* models for assessing COTS-based systems development. The fist section presents an overview of the Component-Based Systems (CBS) development processes. As components are part of the architecture of the system, the second section introduces the evaluation of software architectures. The i* framework has been proved useful on the representation and evaluation of software architectures, including those containing COTS, the third section presents the i* framework and some other requirements engineering techniques. As the i* framework is agent-oriented, and so, the fourth section presents an overview of agent-oriented paradigm. Finally, as CBS development is an activity that seldom takes place from the scratch, we can tackle it as a process reengineering activity, because of that, section 5 outline the main issues in business process reengineering.Postprint (published version

Model-Driven Development of Aspect-Oriented Software Architectures

The work presented in this thesis of master is an approach that takes advantage of the Model-Driven Development approach for developing aspect-oriented software architectures. A complete MDD support for the PRISMA approach is defined by providing code generation, verification and reusability properties.Pérez Benedí, J. (2007). Model-Driven Development of Aspect-Oriented Software Architectures. http://hdl.handle.net/10251/12451Archivo delegad