Application-specific language-oriented modularity: A case study of the ovirt project

Arik Hadas, David H. Lorenz

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

Abstract

Despite the availability of general purpose aspect languages (GPALs) and the availability of frameworks for creating domain specific aspect languages (DSALs), tangled and scattered code still prevails in modern software projects. Through the prism of a case study of the oVirt open source project we examine the conjecture that it may simply be too costly to implement crosscutting concerns in today's GPALs and DSALs. We introduce a subcategory of DSALs, called application specific aspect languages (ASALs), that along with a programming methodology, called language oriented modularity (LOM), allows such concerns to be modularized in a cost-effective, practical way. We illustrate this process concretely for the oVirt project.

Original languageEnglish
Title of host publicationMODULARITY Companion 2016 - Companion Proceedings of the 15th International Conference on Modularity
EditorsDon Batory, Lidia Fuentes, Krzysztof Czarnecki
PublisherAssociation for Computing Machinery
Pages178-183
Number of pages6
ISBN (Electronic)9781450340335
DOIs
StatePublished - 14 Mar 2016
Event15th International Conference on Modularity, MODULARITY 2016 - Malaga, Spain
Duration: 14 Mar 201617 Mar 2016

Publication series

NameMODULARITY Companion 2016 - Companion Proceedings of the 15th International Conference on Modularity

Conference

Conference15th International Conference on Modularity, MODULARITY 2016
Country/TerritorySpain
CityMalaga
Period14/03/1617/03/16

Keywords

  • Application specific aspect language (ASAL)
  • Aspect oriented programming (AOP)
  • Awesome
  • Domain specific aspect language (DSAL)
  • Domain specific language (DSL)
  • Language workbench

Fingerprint

Dive into the research topics of 'Application-specific language-oriented modularity: A case study of the ovirt project'. Together they form a unique fingerprint.

Cite this