Skip to main navigation Skip to search Skip to main content

An evolutionary model of requirements correctness with early aspects

João Araujo, Didar Zowghi, Ana Moreira

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

The achievement of building evolvable systems depends on how efficiently the changeable requirements are elicited and structured by software engineers. In current requirements approaches changing requirements are not dealt with satisfactorily. Partially, this is due to the crosscutting nature of some of these requirements. Aspect-Oriented Requirements Engineering tackles the problem of crosscutting requirements, and its concepts can be used to address this problem. This work describes how early aspects, i.e. aspects identified at early stages of software development, could be integrated to an evolutionary requirements model.

Original languageEnglish
Title of host publicationIWPSE'07
Subtitle of host publicationNinth International Workshop on Principles of Software Evolution - In conjunction with the 6th ESEC/FSE Joint Meeting
EditorsMassimiliano Di Penta, Michele Lanza
Place of PublicationNew York
PublisherACM - Association for Computing Machinery
Pages67-70
Number of pages4
ISBN (Print)978-1-59593-722-3
DOIs
Publication statusPublished - 2007
EventIWPSE'07: Ninth International Workshop on Principles of Software Evolution - In conjunction with the 6th ESEC(European Software Engineering Conference)/FSE(Foundations of Software Engineering) Joint Meeting - Dubrovnik, Croatia
Duration: 3 Sept 20074 Sept 2007

Conference

ConferenceIWPSE'07: Ninth International Workshop on Principles of Software Evolution - In conjunction with the 6th ESEC(European Software Engineering Conference)/FSE(Foundations of Software Engineering) Joint Meeting
Country/TerritoryCroatia
CityDubrovnik
Period3/09/074/09/07

Keywords

  • Early aspects
  • Requirements correctness
  • Aspect-oriented software development

Fingerprint

Dive into the research topics of 'An evolutionary model of requirements correctness with early aspects'. Together they form a unique fingerprint.

Cite this