Publications

Export 65 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 
D
Alanen, M., J. Cabot, M. Goulão, and J. Sáez, "Doctoral symposium", UML Modeling Languages and Applications, vol. 3297: Springer Berlin / Heidelberg, pp. 85-93, 2005. Abstract

n/a

n/a
Gabriel, P., M. Goulão, and V. Amaral, "Do Software Languages Engineers Evaluate their Languages?", XIII Congreso Iberoamericano en "Software Engineering" (CIbSE'2010), ISBN: 978-9978-325-10-0, Cuenca, Ecuador, Universidad del Azuay, pp. 149-162, 2010. Abstractgabrielgoulaoamaralcibse2010.pdf

Domain Speci c Languages (DSLs) can contribute to increment productivity, while reducing the required maintenance and programming expertise. We hypothesize that Software Languages Engineering (SLE) developers consistently skip, or relax, Language Evaluation. Based on the experience of engineering other types of software products, we assume that this may potentially lead to the deployment of inadequate languages. The fact that the languages already deal with concepts from the problem domain, and not the solution domain, is not enough to validate several issues at stake, such as its expressiveness, usability,
eff ectiveness, maintainability, or even the domain expert's productivity while using them. We present a systematic review on articles published in top ranked venues, from 2001 to 2008, which report DSLs' construction, to characterize the common practice. This work con rms our initial hypothesis and lays the ground for the discussion on how to include a systematic approach to DSL evaluation in the SLE process.

Abreu, F. B., and M. Goulão, "Designing and Coding Object-Oriented Systems: An Introductory Course Experience Report", Workshop on Introducing OO Design and Programming with Special Emphasis on Concrete Examples (ECOOP'99), vol. 1743, Lisboa, Portugal, Springer Verlag, pp. 351-353, 1999. Abstract

n/a

n/a
Abreu, F. B., R. Esteves, and M. Goulão, "The Design of Eiffel Programs: Quantitative Evaluation Using the MOOD Metrics", TOOLS'96 (Technology of Object Oriented Languages and Systems), Santa Barbara, CA, EUA, 1996. Abstract

n/a

n/a
C
Goulão, M., and F. B. Abreu, "Cross-Validation of a Component Metrics Suite", IX Jornadas de Ingeniería del Software y Bases de Datos (JISBD'2004), Malaga, Spain, 2004. Abstract

n/a

n/a
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
Goulão, M., "Component-Based Software Engineering: a Quantitative Approach", Faculdade de Ciências e Tecnologia, Universidade Nova de Lisboa, Caparica, Universidade Nova de Lisboa, 2008. Abstract

http://run.unl.pt/handle/10362/1883

tese.pdf

Background: Often, claims in Component-Based Development (CBD) are only sup-
ported by qualitative expert opinion, rather than by quantitative data. This contrasts
with the normal practice in other sciences, where a sound experimental validation of
claims is standard practice. Experimental Software Engineering (ESE) aims to bridge
this gap. Unfortunately, it is common to find experimental validation efforts that are
hard to replicate and compare, to build up the body of knowledge in CBD.


Objectives:
In this dissertation our goals are (i) to contribute to evolution of ESE, in
what concerns the replicability and comparability of experimental work, and (ii) to ap-
ply our proposals to CBD, thus contributing to its deeper and sounder understanding.


Techniques:
We propose a process model for ESE, aligned with current experimen-
tal best practices, and combine this model with a measurement technique called
Ontology-Driven Measurement (ODM). ODM is aimed at improving the state of prac-
tice in metrics definition and collection, by making metrics definitions formal and ex-
ecutable, without sacrificing their usability. ODM uses standard technologies that can
be well adapted to current integrated development environments.


Results:
Our contributions include the definition and preliminary validation of a pro-
cess model for ESE and the proposal of ODM for supporting metrics definition and
collection in the context of CBD. We use both the process model and ODM to perform
a series experimental works in CBD, including the cross-validation of a component
metrics set for JavaBeans, a case study on the influence of practitioners expertise in
a sub-process of component development (component code inspections), and an ob-
servational study on reusability patterns of pluggable components (Eclipse plug-ins).
These experimental works implied proposing, adapting, or selecting adequate ontolo-
gies, as well as the formal definition of metrics upon each of those ontologies.


Limitations:
Although our experimental work covers a variety of component models
and, orthogonally, both process and product, the plethora of opportunities for using
our quantitative approach to CBD is far from exhausted.


Conclusions:
The main contribution of this dissertation is the illustration, through
practical examples, of how we can combine our experimental process model with
ODM to support the experimental validation of claims in the context of CBD, in a re-
peatable and comparableway. In addition, the techniques proposed in this dissertation
are generic and can be applied to other software development paradigms.

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.

Goulão, M., "CBSE: a Quantitative Approach", ECOOP Doctoral Symposium, Darmstadt, Germany, 2003. Abstract

n/a

n/a
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.