Abstract
Use case scenarios are known as powerful means for requirements specification. On the one hand, they join in the same modeling space the expectations of the stakeholders and the needs of the developers involved in the process. On the other hand, they describe the desired high level functionalities. By formalizing these descriptions we are able to extract relevant informations from them. Specifically, we are interested in identifying requirements patterns (common requirements with typical implementation solutions) in support for a requirements based software development approach. This paper addresses the transformation of use case descriptions expressed in a Controller Natural Language into an ontology expressed in the Web Ontology Language (OWL), as well as the query process for such information. It reports on a study aimed at validating our approach and our tool with real users. A preliminary set of results is discussed.

Abstract
Software development processes are known to produce a large set of artifacts such as models, code and documentation. Keeping track of these artifacts without supporting tools is not easy, and making them available to others can be even harder. Standard version control systems are not able to solve this issue. More than keeping track of versions, a system to help organize and make artifacts available in meaningful ways is needed. In this paper we review a number of alternative systems, and present the requirements and the implementation of a collaborative web repository which we developed to solve this issue.

Abstract
Purpose - This paper aims to present the Modelery, a platform for collaborative repository to support model-based software development. The Modelery is a Web platform, composed both by a Web page and Web services for interoperability. Design/methodology/approach - By performing a study in the existing platforms, it was possible to achieve a set of issues to tackle. The issues enabled the possibility to define a set of requirements that allowed the authors to design a new platform, and to perform a model-driven software development process, which started from the requirements until reaching the final software solution. Findings - With this work, it was possible to perform a survey on the currently available artifacts repositories, categorize them and identify their shortcomings. This was essential to define the set of requirements for a new platform to overcome the identified issues. This process leads to a platform able to improve the currently available solutions, and validated in the scientific community. In this paper, the authors also explore the applications of the repository. First, they use the Modelery to replace an older model's repository. Second, they have enabled the communication between other tools and the Modelery via Web services. Originality/value - This work presents a new Web repository for software artifacts aimed at supporting researchers and software developers. The presented platform is an improvement over other platforms on the integration of artifacts repository, social functionalities and scientific publications integration. The authors conclude this paper by comparing the achieved platform in terms of functionalities, against the other analyzed platforms.

Abstract
The spread of mobile devices in modern societies has forced the industry to create software paradigms to meet the new challenges it faces. Some of these challenges are the huge heterogeneity of devices or the quick changes of users' context. In this scenario, context becomes a key element, enabling mobile applications to be user centric and adapt to user requirements. The Mobile Context Framework, proposed in this paper, is a contribution to solve some of these challenges. Using Web servers running on the devices, context data can be provided to web applications. Besides the framework's architecture, a prototype is presented as proof of concept of the platform's potential. © 2013 Springer-Verlag Berlin Heidelberg.

Abstract
One of the problems of current software development lies on the existence of solutions to address properly the code portability for the increasing number of platforms. To build abstract models is one efficient and correct way to achieve this. The Model-Driven Software Engineering (MDSE) is a development methodology where models are the key for all project lifecycle, from requisites gathering, through modelling and to the development stage, as well as on testing. Pervasive computing demands the use of several technical specifications, such as wireless connections, advanced electronics, and the Internet, as well as it stresses the need to adjust the user interface layer to each one of the platforms. Using a model-driven approach it is possible to reuse software solutions between different targets, since models are not affected by the device diversity and its evolution. This paper reports on a tool, which is highly parameterizable and driven to support Model-2-Model and Model-2-Code transformations. Also, instead of using a predefined technology, the tool was built to be scalable and extensible for many different targets and also by addressing the user interface layer generation. © Springer International Publishing Switzerland 2016.

Abstract
A domain-specific language (DSL) aims to support software development by offering abstractions to a particular domain. It is expected that DSLs improve the maintainability of artifacts otherwise produced with general-purpose languages. However, the maintainability of the DSL artifacts and, hence, their adoption in mainstream development, is largely dependent on the usability of the language itself. Unfortunately, it is often hard to identify their usability strengths and weaknesses early, as there is no guidance on how to objectively reveal them. Usability is a multi-faceted quality characteristic, which is challenging to quantify beforehand by DSL stakeholders. There is even less support on how to quantitatively evaluate the usability of DSLs used in maintenance tasks. In this context, this paper reports a study to compare the usability of textual DSLs under the perspective of software maintenance. A usability measurement framework was developed based on the cognitive dimensions of notations. The framework was evaluated both qualitatively and quantitatively using two DSLs in the context of two evolving object-oriented systems. The results suggested that the proposed metrics were useful: (1) to early identify DSL usability limitations, (2) to reveal specific DSL features favoring maintenance tasks, and (3) to successfully analyze eight critical DSL usability dimensions.