Skip to main content

Model Top-Down Analysis in software products.

In this paper will discuss an approach from the environmental variability of presentation software solutions. Focusing on the concept of software product family.

If we play the role of architects:

  •          How many times we try analyzing common feature in different forms of presentation?
  •          How many times have we requested a mobile solution attached to our traditional solution?
  •          Are simply the decisions to implement new presentations of the software solution?

Here is an introduction to the concept….

Software organizations are building a product vision characterized by the development and evolution of product families instead of creating a specific software product for a given client.
This trend is driven by several factors such as, business strategy, diversity computing devices and reuse of software components in complex software systems. However, the commercial dynamics of software development companies in Latin America have led them to have multiple software products developed in an ad hoc for each specific customers (system view).

These products evolve in order to meet the new requirements imposed by the clients, generating a set of software products with specific features of interaction in various settings, such as mobile environments, web, wap, or traditional management (e.g., Windows environment, Windows Form Application project). The architectural documentation of these devices, if available, does not reflect the implemented architecture, the main asset owned by the company is a set of assemblies and components that have different dependencies between them. A company that uses a system view and want to evolve into a product view must pass through a complex process. This process requires tools and techniques for processing of artifacts of the development process to allow extracting, abstracting, and refactory them and thus help in building a family of products.
I propose a method for automatic analyzing the various assemblies resulting from the development process, their relationships and their nature.

The method focuses on the analysis of the different environment of interaction of a set of software artifacts and their possible variants linked to a variation point.

For the moment I leave the model representation. This is Exavar..

I built a tool that uses the model and method for automated detection. This framework is one of my activities PhD.


Until the next time!
Labels:

Comments

Post a Comment

Popular posts from this blog

Google Assistant, simpleness of interaction to call a webhook

The creation of an application using Google Assistant is very simple and represent a big impact to interact with users in diverse environments and particularly in home Hey Google ...Where is my dog? If we plan to connect a security camera system, the challenge of finding my pet in an automated way is more feasible, then I will give more details of how I intend to do it. Now we are going to prepare the functionality of the assistant’s requests. To create an agent and interact with Google Assistant , we will use DialogFlow . Let's see the main elements to create an agent, and using this agent call a webhook with some functionality. * Part of the objective will be to try to prepare the logic of interaction with a home security system * Arlo System From the DialogFlow console, we will create a new agent: We can customize different support languages, for this case I will use English to facilitate the testing of the agent. [You can include Spanish and also go in
Post a Comment
Read more

Architectural reviews of software engineering, a simple approach

I wanted to share an analysis of a very interesting work where they develop concepts related to software architecture solutions. We know that the architecture of a software solution is very important to the success of a development. In my experience as a software architect in previous works dedicated to the software industry, very often expressed an effect of "do not have time to complete thearchitectural review. " What is the justification? if we can justify it. It is very expensive,time consuming, depending on the architectural documentation of the solution, a scenario that could never discuss "is a small project with a limited life cycle, with minimum documentation" So what options do we have when the project has these characteristics, and we'resure that we execute architectural reviews? “However, in spite of the demonstrated benefits of architecture reviews, many projects are unable or unwilling to use them. These projects tend to have the following cha
Post a Comment
Read more

SMI Developer Day - Session 2 was pure developers adrenaline

A new session of SMI Developer Day program has been conducted at the Cultural Center Borges in Buenos Aires. The event was pure adrenaline to the ecosystem of technology development in Google. A great attendance and I could feel pure adrenaline at the conference on May 8 at the Cultural Center Borges in the context of SMI Developer Day event . In this opportunity we present an approach to development Web solutions , innovative technologies such as HTML5 and present an option for persistence in disconnected scenarios. A great conversation environments with a lot of questions, showed the state of motivation of the developer community in the region. A region full of talent. A region that every day becomes more involved in technology , mobility , computing in the cloud. Furthermore, this region strengthens a vision of entrepreneurship, and drive an amazing ecosystem. An excellent shared moment with the community
1 comment
Read more