Una propuesta de marco de trabajo orientado al dominio del procesamiento transaccional

La ingeniería de software establece que la construcción de programas debe ser encarado de la misma forma que los ingenieros construyen otros sistemas complejos. Los sistemas de procesamiento transaccional no son la excepción. Para lidiar con algunos de los desafíos de construir estas soluciones, se desarrolló una propuesta de marco de trabajo, que propone la construcción de una base de conceptos comunes, obtenidos del análisis de soluciones preexistentes, y de experiencias del equipo que desarrolla esta propuesta. Esta recolección de factores comunes se hace de forma iterativa, y se capitaliza en elementos del framework que aquí se introduce. Ese marco de trabajo tendrá como objetivos aumentar la reusabilidad, disminuir los costos de mantenimiento, y fomentar la comunicación entre los desarrolladores. Para tal fin, se pretende implementar una metodología MDD (DSM) que permita facilitar el uso del marco de trabajo a otros usuarios ajenos al desarrollo de esta propuesta. La implementación específica DSM será a través de un lenguaje de dominio específico que concentre en elementos de dominio, la experiencia concentrada en el framework.Eje: Ingeniería de Softwar

Toward Quality Attribute Driven Approach to Software Architectural Design

It has been well-documented that the software architecture of any system plays a critical role in success or failure of software intensive systems. In this paper, a method has been proposed to evaluate the software architecture’s fitness with respect to key quality attributes for a web-based system. To the end, a comparative analysis based on quality attributes scenarios and tactics is carried out to select an optimal software architecture that meets the system level requirements of a web-based system, namely, Student and Course Evaluation System (SCES). The comparative study was driven by study of quality attributes and tactics with the selected architectures to select the optimal one

Una propuesta de marco de trabajo orientado al dominio del procesamiento transaccional

La ingeniería de software establece que la construcción de programas debe ser encarado de la misma forma que los ingenieros construyen otros sistemas complejos. Los sistemas de procesamiento transaccional no son la excepción. Para lidiar con algunos de los desafíos de construir estas soluciones, se desarrolló una propuesta de marco de trabajo, que propone la construcción de una base de conceptos comunes, obtenidos del análisis de soluciones preexistentes, y de experiencias del equipo que desarrolla esta propuesta. Esta recolección de factores comunes se hace de forma iterativa, y se capitaliza en elementos del framework que aquí se introduce. Ese marco de trabajo tendrá como objetivos aumentar la reusabilidad, disminuir los costos de mantenimiento, y fomentar la comunicación entre los desarrolladores. Para tal fin, se pretende implementar una metodología MDD (DSM) que permita facilitar el uso del marco de trabajo a otros usuarios ajenos al desarrollo de esta propuesta. La implementación específica DSM será a través de un lenguaje de dominio específico que concentre en elementos de dominio, la experiencia concentrada en el framework.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

Una propuesta de marco de trabajo orientado al dominio del procesamiento transaccional

La ingeniería de software establece que la construcción de programas debe ser encarado de la misma forma que los ingenieros construyen otros sistemas complejos. Los sistemas de procesamiento transaccional no son la excepción. Para lidiar con algunos de los desafíos de construir estas soluciones, se desarrolló una propuesta de marco de trabajo, que propone la construcción de una base de conceptos comunes, obtenidos del análisis de soluciones preexistentes, y de experiencias del equipo que desarrolla esta propuesta. Esta recolección de factores comunes se hace de forma iterativa, y se capitaliza en elementos del framework que aquí se introduce. Ese marco de trabajo tendrá como objetivos aumentar la reusabilidad, disminuir los costos de mantenimiento, y fomentar la comunicación entre los desarrolladores. Para tal fin, se pretende implementar una metodología MDD (DSM) que permita facilitar el uso del marco de trabajo a otros usuarios ajenos al desarrollo de esta propuesta. La implementación específica DSM será a través de un lenguaje de dominio específico que concentre en elementos de dominio, la experiencia concentrada en el framework.Eje: Ingeniería de SoftwareRed de Universidades con Carreras en Informática (RedUNCI

A novel model for improving the maintainability of web-based systems

Web applications incorporate important business assets and offer a convenient way for businesses to promote their services through the internet. Many of these web applica- tions have evolved from simple HTML pages to complex applications that have a high maintenance cost. This is due to the inherent characteristics of web applications, to the fast internet evolution and to the pressing market which imposes short development cycles and frequent modifications. In order to control the maintenance cost, quantita- tive metrics and models for predicting web applications’ maintainability must be used. Maintainability metrics and models can be useful for predicting maintenance cost, risky components and can help in assessing and choosing between different software artifacts. Since, web applications are different from traditional software systems, models and met- rics for traditional systems can not be applied with confidence to web applications. Web applications have special features such as hypertext structure, dynamic code generation and heterogenousity that can not be captured by traditional and object-oriented metrics. This research explores empirically the relationships between new UML design met- rics based on Conallen’s extension for web applications and maintainability. UML web design metrics are used to gauge whether the maintainability of a system can be im- proved by comparing and correlating the results with different measures of maintain- ability. We studied the relationship between our UML metrics and the following main- tainability measures: Understandability Time (the time spent on understanding the soft- ware artifact in order to complete the questionnaire), Modifiability Time(the time spent on identifying places for modification and making those modifications on the software artifact), LOC (absolute net value of the total number of lines added and deleted for com- ponents in a class diagram), and nRev (total number of revisions for components in a class diagram). Our results gave an indication that there is a possibility for a relationship to exist between our metrics and modifiability time. However, the results did not show statistical significance on the effect of the metrics on understandability time. Our results showed that there is a relationship between our metrics and LOC(Lines of Code). We found that the following metrics NAssoc, NClientScriptsComp, NServerScriptsComp, and CoupEntropy explained the effort measured by LOC(Lines of Code). We found that NC, and CoupEntropy metrics explained the effort measured by nRev(Number of Revi- sions). Our results give a first indication of the usefulness of the UML design metrics, they show that there is a reasonable chance that useful prediction models can be built from early UML design metrics

Foundations of systems and properties:methodological support for modeling properties of software-intensive systems

Engineering of software-intensive systems is concerned with the creation and evolution of systems that shall exhibit desired properties in their execution as well as development environment. In this context, the motivation of this thesis, derived from current development practice, was twofold. Firstly, software development methods are increasingly required to extend their scope of applicability towards systems engineering. As a consequence, their modeling approaches must be able to cope with a larger diversity of systems and consequently a larger diversity of properties. But these approaches still need to provide a smooth transition to software modeling. Secondly, non-functional properties, which are largely a result of this implicit systems scope, play a major role in the way we design our software-intensive systems. The conceptual aids of current development methods, however, are still less mature in their explicit support for non-functional properties compared with their ability to support functional ones. The principal objective of this thesis is to contribute toward an improved model-based treatment of non-functional properties in development methods. Because we cannot discuss properties independently of the objects they are ascribed to, this objective amounts to a progression from modeling of software and its properties to modeling of interrelated systems and their properties. To address this aim a philosophy of properties and systems is proposed. The philosophy is expressed as a holistic conceptual model of properties and/of systems. It is complemented with some basic rules, which we call tenets. Tenets formulate how we use the philosophical knowledge. The conceptual model offers the foundations for a more generalized understanding of those fundamentally different types of systems and different types of properties that are relevant in software-intensive systems engineering. The generality of our holistic model draws the benefits from our investigations in the areas of systems science, cognitive science, and basic philosophy. The model helps to scrutinize and make sense of the large amount of data in the literature about "non-functional" issues in software engineering. The model is applicable in the derivation of methodological building blocks that can be incorporated into development methods. The building blocks include (a) a general model to discover stakeholders and properties for a given system, (b) a principled manner to trace the fundamentally different types of properties through hierarchies of systems, and (c) a proposal for the representation of systems, their properties and property traces in the UML. The concrete application of the gained knowledge to software engineering results in a proposal for a context-sensitive, customizable quality attribute model. It also results in a proposal on how to structure quality descriptions of software components. In order for such descriptions to be standardized and possibly tool-automated, this thesis proposes to utilize the Reusable Asset Specification and suggests alternatives for its XML-based representation

Pervasive computing reference architecture from a software engineering perspective (PervCompRA-SE)

Pervasive computing (PervComp) is one of the most challenging research topics nowadays. Its complexity exceeds the outdated main frame and client-server computation models. Its systems are highly volatile, mobile, and resource-limited ones that stream a lot of data from different sensors. In spite of these challenges, it entails, by default, a lengthy list of desired quality features like context sensitivity, adaptable behavior, concurrency, service omnipresence, and invisibility. Fortunately, the device manufacturers improved the enabling technology, such as sensors, network bandwidth, and batteries to pave the road for pervasive systems with high capabilities. On the other hand, this domain area has gained an enormous amount of attention from researchers ever since it was first introduced in the early 90s of the last century. Yet, they are still classified as visionary systems that are expected to be woven into people’s daily lives. At present, PervComp systems still have no unified architecture, have limited scope of context-sensitivity and adaptability, and many essential quality features are insufficiently addressed in PervComp architectures. The reference architecture (RA) that we called (PervCompRA-SE) in this research, provides solutions for these problems by providing a comprehensive and innovative pair of business and technical architectural reference models. Both models were based on deep analytical activities and were evaluated using different qualitative and quantitative methods. In this thesis we surveyed a wide range of research projects in PervComp in various subdomain areas to specify our methodological approach and identify the quality features in the PervComp domain that are most commonly found in these areas. It presented a novice approach that utilizes theories from sociology, psychology, and process engineering. The thesis analyzed the business and architectural problems in two separate chapters covering the business reference architecture (BRA) and the technical reference architecture (TRA). The solutions for these problems were introduced also in the BRA and TRA chapters. We devised an associated comprehensive ontology with semantic meanings and measurement scales. Both the BRA and TRA were validated throughout the course of research work and evaluated as whole using traceability, benchmark, survey, and simulation methods. The thesis introduces a new reference architecture in the PervComp domain which was developed using a novel requirements engineering method. It also introduces a novel statistical method for tradeoff analysis and conflict resolution between the requirements. The adaptation of the activity theory, human perception theory and process re-engineering methods to develop the BRA and the TRA proved to be very successful. Our approach to reuse the ontological dictionary to monitor the system performance was also innovative. Finally, the thesis evaluation methods represent a role model for researchers on how to use both qualitative and quantitative methods to evaluate a reference architecture. Our results show that the requirements engineering process along with the trade-off analysis were very important to deliver the PervCompRA-SE. We discovered that the invisibility feature, which was one of the envisioned quality features for the PervComp, is demolished and that the qualitative evaluation methods were just as important as the quantitative evaluation methods in order to recognize the overall quality of the RA by machines as well as by human beings

Una propuesta de implementación MDD y TDD en el dominio de sistemas de procesamiento transaccional

La ingeniería de software establece que la construcción de programas debe ser encarada de la misma forma que los ingenieros construyen otros sistemas complejos. Los sistemas de procesamiento transaccional no son la excepción. Para lidiar con algunos de los desafíos de construir estas soluciones, se introduce una propuesta de implementación dual MDD y TDD.\nEsta propuesta define una base de conceptos comunes, obtenidos del análisis de soluciones preexistentes, y experiencias de los desarrolladores, con el objeto de definir elementos del dominio. En paralelo, se conjugarán estrategias de pruebas unitarias, como simulación de las transacciones entrantes en los sistemas bajo desarrollo. El conjunto de ambas metodologías intentará definir un framework orientado al dominio que fomente la reutilización de código, reduciendo los esfuerzos de mantenimiento. Así también, dada la naturaleza gráfica de los modelos, se intentará mejorar la visibilidad del sistema construido, tanto para los colegas de equipo, como para los stakeholders.XII Workshop Ingeniería de Software (WIS

Una propuesta de implementación MDD y TDD en el dominio de sistemas de procesamiento transaccional

La ingeniería de software establece que la construcción de programas debe ser encarada de la misma forma que los ingenieros construyen otros sistemas complejos. Los sistemas de procesamiento transaccional no son la excepción. Para lidiar con algunos de los desafíos de construir estas soluciones, se introduce una propuesta de implementación dual MDD y TDD. Esta propuesta define una base de conceptos comunes, obtenidos del análisis de soluciones preexistentes, y experiencias de los desarrolladores, con el objeto de definir elementos del dominio. En paralelo, se conjugarán estrategias de pruebas unitarias, como simulación de las transacciones entrantes en los sistemas bajo desarrollo. El conjunto de ambas metodologías intentará definir un framework orientado al dominio que fomente la reutilización de código, reduciendo los esfuerzos de mantenimiento. Así también, dada la naturaleza gráfica de los modelos, se intentará mejorar la visibilidad del sistema construido, tanto para los colegas de equipo, como para los stakeholders.XII Workshop Ingeniería de Software (WIS)Red de Universidades con Carreras en Informática (RedUNCI

Una propuesta de implementación MDD y TDD en el dominio de sistemas de procesamiento transaccional

La ingeniería de software establece que la construcción de programas debe ser encarada de la misma forma que los ingenieros construyen otros sistemas complejos. Los sistemas de procesamiento transaccional no son la excepción. Para lidiar con algunos de los desafíos de construir estas soluciones, se introduce una propuesta de implementación dual MDD y TDD. Esta propuesta define una base de conceptos comunes, obtenidos del análisis de soluciones preexistentes, y experiencias de los desarrolladores, con el objeto de definir elementos del dominio. En paralelo, se conjugarán estrategias de pruebas unitarias, como simulación de las transacciones entrantes en los sistemas bajo desarrollo. El conjunto de ambas metodologías intentará definir un framework orientado al dominio que fomente la reutilización de código, reduciendo los esfuerzos de mantenimiento. Así también, dada la naturaleza gráfica de los modelos, se intentará mejorar la visibilidad del sistema construido, tanto para los colegas de equipo, como para los stakeholders.XII Workshop Ingeniería de Software (WIS)Red de Universidades con Carreras en Informática (RedUNCI