You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.

The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.

For the reports in this repository we specifically note that

  • the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
  • the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
    ss
  • technical reports and other articles issued by Mälardalen University is free for personal use. For other use, the explicit consent of the authors is required
  • in other cases, please contact the copyright owner for detailed information

By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.

If you are in doubt, feel free to contact webmaster@ide.mdh.se

Towards Engineered Architecture Evolution

Speakers:

Ipek Ozkaya , Ipek Ozkaya

Type:

Seminar

Start time:

2009-10-15 10:00

End time:

2009-10-15 11:00

Location:

Ypsilon

Contact person:



Description

Ipek Ozkaya from the Software Engineering Institute (Pittsburgh) is visiting us and vill give a seminar on Architecture EvolutionArchitecture evolution, a key aspect of software evolution, is typically done in an ad hoc manner, guided only by the competence of the architect performing it. This process lacks the rigor of an engineering discipline. In this presentation, I argue that architecture evolution must be engineered— based on rational decisions that are supported by formal models and objective analyses. Evolutions of a restricted form — close-ended evolution, where the starting and ending design points are known a priori — are amenable to being engineered. I discuss some of the key challenges in engineering close-ended evolution. I present a conceptual framework in which an architecture evolutionary trajectory is modeled as a sequence of steps, each captured by an operator. The goal of this framework is to support exploration and objective evaluation of different evolutionary trajectories. I present an example evaluation of such a trajectory and conclude with open research questions in developing such a framework.