Publications

Export 58 results:
Sort by: Author [ Title (Desc)] Type Year
[A] B C D E F G H I J K L M N O P Q R S T U V W X Y Z   [Show ALL]
C
e Abreu, F. B., and M. Goulão, "Coupling and Cohesion as Modularization Drivers: Are we being over-persuaded?", 5th European Conference on Software Maintenance and Reengineering (CSMR'2001), Lisboa, Portugal, IEEE Computer Society Press, pp. 47-57, 2001. Abstract

n/a

n/a
Monteiro, A. S., M. Goulão, F. B. Abreu, A. B. Almeida, and P. Sousa, "Controlling the Evolution of Legacy Systems Using Internet Technology: A Defect Report and Tracking System", 6th European Conference on Software Quality, Vienna, Austria, European Organization for Quality, pp. 473-483, 1999. Abstract

n/a

n/a
Goulão, M., and F. B. Abreu, "Composition assessment metrics for CBSE", Euromicro-SEAA 2005: 31st Euromicro Conference on Software Engineering and Advanced Applications, Porto, Portugal, IEEE Computer Society, pp. 96-103, 2005. Abstract

n/a

n/a
Fernandes, A. I., M. Goulão, and Armanda Rodrigues, "A Comparison of Maps Application Programming Interfaces", 16th AGILE Conference on Geographic Information Science, AGILE 2013, Leuven, Belgium, May 14-17, 2013. Abstractagile2013fernandesetalcameraready.pdf

The development of web applications that manipulate geo-referenced information is often supported by Application Programming Interfaces (APIs), allowing a fast development cycle for high quality applications. APIs can be used by programmers with different expertise levels and choosing an adequate API may
have a dramatic impact on the productivity achieved by those programmers. Our goal is to compare maps APIs with respect to their usability. We compare three different APIs: the Google Maps JavaScript API, the ArcGIS API for JavaScript, and the OpenLayers JavaScript Mapping Library. Our comparison is supported by
a set of software metrics and is performed in two orthogonal ways: the comparison of three implementations of the same system prototype, each using one of the APIs under scrutiny; the comparison of the APIs specifications. The main results of the study are related to the size of the APIs, with the Google API being significantly smaller than the others.

B
Goulão, M., and F. B. Abreu, "Bridging the gap between Acme and UML 2.0 for CBD", Specification and Verification of Component-Based Systems (SAVCBS'2003), at the ESEC/FSE'2003, Helsinki, Finland, 2003. Abstract

n/a

n/a
A
Baroni, A. L., M. Goulão, and F. B. Abreu, "Avoiding the Ambiguity of Quantitative Data Extraction: An Approach to Improve the Quality of Metrics Results", Work in Progress Session at the 28th EUROMICRO Conference, Dortmund, Germany, 2002. Abstract

n/a

n/a
Araújo, J., M. Goulão, A. Moreira, I. Simão, V. Amaral, and E. Baniassad, "Advanced Modularity for Building SPL Feature Models: a Model-Driven Approach", 28th ACM Symposium on Applied Computing, Requirements Engineering Track, ACM-SAC 2013, Coimbra, Portugal, ACM, 18-22 Mar., 2013. Abstractaraujo2013sac.pdf

Feature Models are commonly used to specify commonalities and variabilities in Software Product Lines (SPL). Our goal is to enhance feature modeling with traceability and improved support for crosscutting concerns. While traceability will show the features’ requirement-origins, providing means to reason about
their existence, crosscutting concerns will be handled through advanced modularity mechanisms (e.g. aspects), making the impact of changes to SPL models less difficult to understand and analyze. The result is Theme/SPL, a novel SPL requirements technique based on a concern-driven approach (Theme/Doc). Theme/SPL includes the proposal of a domain-specific language for specifying Theme/Doc models and uses model-driven development to generate automatically feature models from them. We show the applicability of the technique through a case study using a within-group design to evaluate the final results and tools developed.

Monteiro, R., J. Araújo, V. Amaral, M. Goulão, and P. Patrício, "Adding Interoperability to Requirements Models", Software Quality Professional Journal, vol. 15, issue 4, pp. 16-27, 2013. Abstract

(c) American Society for Quality

sqpv15i4monteiro.pdfWebsite

Complex software systems inherently require a variety of models used in all of the development stages. A general concern is to guarantee consistency and traceability among these models. Model-driven development (MDD) can help tackle this concern. Although MDD has been mainly used in later development stages, it is relatively unexplored in requirements engineering. In this article, the authors discuss how to
leverage MDD to support consistency and traceability in requirements modeling. To illustrate this, they apply MDD to goaloriented requirements engineering (GORE) by making bidirectional mappings between two well-known GORE approaches (i* and KAOS). The result is an interoperable framework that can be used to migrate from one goal model to another through automatic model transformations, keeping consistency and traceability, so requirements engineers can make the best use of each approach.