An active-architecture approach to COTS integration

Commercial off-the-shelf (COTS) software products are increasingly used as standard components within integrated information systems. This creates challenges since both their developers and source code are not usually available, and the ongoing development of COTS cannot be predicted. The ArchWare Framework approach recognises COTS products as part of the ambient environment of an information system and therefore an important part of development is incorporating COTS as effective system components. This integration of COTS components, and the composition of components, is captured by an active architecture model which changes as the system evolves. Indeed the architecture modelling language used enables it to express the monitoring and evolution of a system. This active architecture model is structured using control system principles. By modelling both integration and evolution it can guide the system’s response to both predicted and emergent changes that arise from the use of COTS products.Publisher PDFPeer reviewe

Developing Web Applications For Different Architectures: The MoWebA Approach

This study presents the Architecture Specific Model (ASM) defined by the MoWebA approach to improve the development of web applications for different architectures. MoWebA is a model-driven approach to web applications development. The article presents a general overview of MoWebA, including the methodological aspects related to its modeling and transformation processes, the process of defining the ASM, and an example of an ASM model.CONACYT – Consejo Nacional de Ciencia y TecnologíaPROCIENCI

From Analysis Model to Software Architecture: a PIM2PIM Mapping.

To our knowledge, no current software development methodology explicitly describes how to transit from the analysis model to the software architecture of the application. This paper presents a method to derive the software architecture of a system from its analysis model. To do this, we are going to use MDA. Both the analysis model and the architectural model are PIMs described with UML 2. The model type mapping designed consists of several rules (expressed using OCL and natural language) that, when applied to the analysis artifacts, generate the software architecture of the application. Specifically the rules act on elements of the UML 2 metamodel (metamodel mapping). We have developed a tool (using Smalltalk) that permits the automatic application of these rules to an analysis model defined in RoseTM to generate the application architecture expressed in the architectural style C2

The Impact of Ownership and Contribution Alignment on Code Technical Debt Accumulation

Software development organisations strive to maintain their effectiveness while the complexity of the systems they develop continues to grow. To tackle this challenge, organisations tend to be organised into small teams working with components that can be developed separately. Here, organisations must design their architecture and organisational structures in a way that enables communication and minimises dependencies, and helps teams reduce code and architectural degradation. Ensuring that each small independent team is responsible for components they primarily contribute is one approach to achieving this goal. This study aims at understanding the impact of ownership and contribution alignment on accumulation of code technical debt and how abrupt changes in team constellation affect teams' effectiveness in managing TD. We conducted an embedded case study in a company developing a very large software system, analysing ten components belonging to 1 team. During the studied period, the team was split into two, and the components owned by them were distributed between the two new teams. With high degrees of contribution alignment, we noticed a negative correlation between contribution alignment and TD Density before the team split. In 4 components, this correlation is statistically significant. This means a higher contribution alignment degree implies a lower TD Density. After the split, we observe a negative correlation in 3 components. The positive correlation observed in the other 5 components could be attributed to low contribution alignment, leading to difficulties in managing TD. Our findings suggest that contribution alignment can be important in controlling TD in software development organisations. Making teams responsible for the quality of components they have more expertise over and minimising dependencies between teams can help organisations mitigate the growth of TD.Comment: Submitted to Transactions on Software Engineering (TSE

An Architecture-Centric Approach for Information System Architecture Modeling, Enactement and Evolution

International audienc

DSL4SPM: Domain-specific language for software process modeling

This paper presents a novel formal approach to software process modeling based on the Software Process Engineering Metamodel (SPEM) for the syntactic aspect of a process model and a domain-specific language (DSL) for the semantic aspect of the model. This approach provides a conceptual framework for designing processes in a more abstract way and to enable process implementation on various platforms. A Process-Centered Software Environment (PCSE) called DSL4SPM (Domain-Specific Language for Software Process Modeling) is a plug-in tool which satisfies the meta-requirements for Process Modeling Languages (PMLs). The key concept of the DSL4SPM is the use of a toolbox, containing SPEM elements, to instantiate objects in a graphical scene. The process model designer links these elements with relations, and defines the values of the attributes required for both these and the objects, with the aim of arriving at a consolidated view of the problem. An overview of the advantages of the approach is presented. With it, the process manager is able to quickly and easily model a process from innovative perspectives, with the aim of better understanding the risks associated with software development

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

Daily Eastern News: April 22, 2004

https://thekeep.eiu.edu/den_2004_apr/1015/thumbnail.jp