Nick Bortolotti

Before starting the development activity, we will define the concept for the use of "implicit Intents" on mobile solution (Android). The implicit Intents are used when a component is not specified exactly to use, instead, you specify the functionality required by an action (for example, 'view', 'make search', 'check') and data (For example, the URL of the page you want to see, the phone number you want to dial), and Android should determine the best component for use. This is one of the interesting features proposed by Android. This functionality allows an application to trigger an "Intent", without knowing exactly what the application or component that will receive it. The most commonly used filter is an action, and the most common action, has to do with how "ACTION_VIEW. " The basic steps to launch an activity using an "implied intent": Declaring the "intent" with the appropriate action, for example, &q

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 p

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