Departamento de Engenharia Informática (IST)

Software Process Improvement is one of the main software development challenges. Unfortunately, process descriptions generally do not correspond to the processes actually performed during software development projects. They just represent high-level ...

Software requirements engineering is an essential activity for the successful development of information systems. The techniques used to specify software requirements range from those that use formal notations to those based upon the use of natural language. In this paper we describe the metamodel of a new controlled natural language for requirements specification, called ProjectIT-RSL, which was defined after the identification of the most common linguistic patterns used in requirements documents written in natural language. The initial version of the language was implemented in a prototype built using the Visual Studio .NET development environment, which enabled the development of a set of tools to validate the syntactic and semantic rules of requirements texts written in the ProjectIT-RSL language. 1

We collect ergonomic rules and normative rules considerations for automobile business and modeled these activities with a special UML language created for automobile business, VDML (Vehicle Development Modeling Language). From these high level process vision integrated in the product development activity a wide variety of improvements can be achieved related with time reduction, activity process quality as well as use of past experience. Also we intend to define ergonomic associated templates, which reflect standard ergonomic job routines to be incorporated in CAD application and improve the ergonomics process reference points and also the process optimization reached thorough UML high level vision. In these process we define also a ontology for ergonomics (EOL - Ergonomics Ontology Language) based on the OWL (Ontology Web Language) standards.

ABSTRACT Despite being the most suitable language to communicate requirements, the intrinsic ambiguity of natural language often undermines requirements quality criteria, specially clearness and consistency. Several proposals have been made to increase the rigor of requirements representations through conceptual models, which encompass different perspectives to completely describe the system. However, this multi-representation strategy warrants significant human effort to produce and reuse such models, as well as to enforce their consistency. This paper presents RSL-IL, a Requirements Specification Language that tackles the requirements formalization problem by providing a minimal set of constructs. To cope with the most typical Requirements Engineering concerns, RSL-IL constructs are internally organized into viewpoints. Since these constructs are tightly integrated, RSL-IL enables the representation of requirements in a way that makes them formal enough for being tractable by a computer. Given that RSL-IL provides a stable intermediate representation that can improve the quality and enables requirements reuse, it can be regarded as a requirements interlingua. Also, RSL-IL can be used as a source language within the context of model-to-model transformations to produce specific conceptual models. To illustrate how RSL-IL can be applied in a real project, this paper provides a running example based on a case study.

The great evolution of the mobile market during the last years caused some fragmentation of the mobile platforms namely through the existence of different programming languages and software development tools for each platform. This fact can be an obstacle and increases the development complexity and costs when we want to develop mobile applications for multiple platforms. The XIS-Mobile domain specific language (defined as a UML profile) and its MDD-based framework address this problem by proposing platform-independent models to describe mobile applications and from them automatically generate the application’s source code. Many issues arose during an iterative process of evaluation which originated changes and the evolution of XIS-Mobile. This paper presents the results of the evaluation of XIS-Mobile (both the language and the companion framework) obtained through the implementation of a case study and by conducting a user session, and discusses its benefits and challenges.