Software Engineering Institute | Carnegie Mellon University
Software Engineering Institute | Carnegie Mellon University

Digital Library

Javascript is currently disabled for your browser. For an optimal search experience, please enable javascript.

Advanced Search

Basic Search

Content Type

Topics

Publication Date

Presentation

Architecture Governance and Rules Enforcement Using AOP and SonarJ—A Case Study (SATURN 2009)

  • May 2009
  • By Srini Penchikala
  • In this SATURN 2009 presentation, Srini Penchikala talks about the significance of enforcing architecture standards and how to implement policy enforcement in software development projects.
  • Publisher: Software Engineering Institute
  • This presentation was created for a conference series or symposium and does not necessarily reflect the positions and views of the Software Engineering Institute.
  • Abstract

    Although many companies have some kind of application architecture standards, they don’t usually have a mechanism to enforce those standards. As a result of this lack of architecture governance, the implementation (code) often doesn't match the requirements (reference architecture). Enforcing reference architecture guidelines promotes consistency and modularity in the system. In this presentation, I will talk about the significance of enforcing architecture rules and how to implement policy enforcement in software development projects. I will also discuss an architecture enforcement framework created to “inject” architecture rules and design policies into the continuous integration (CI) process using aspects to enforce quality of the code. The framework also uses tools like Eclipse, AJDT and Maven to integrate policy enforcement into the agile development process to detect architecture deviations early and often and validates that the design and code are in compliance with the reference architecture (RA).

  • Download