Search For:

Displaying 1-15 out of 15 total
Message from the MTD 2013 Workshop Chairs
Found in: 2013 ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)
By Philippe Kruchten,Robert L. Nord,Ipek Ozkaya,Davide Falessi
Issue Date:October 2013
pp. 396
The goal of this fifth workshop on managing technical debt is to engage leading empiricists and practitioners in exploring practical problems to provide opportunities for research that can provide evidence for or against the emerging definition of technica...
Variations on Using Propagation Cost to Measure Architecture Modifiability Properties
Found in: 2013 IEEE International Conference on Software Maintenance (ICSM)
By Robert L. Nord,Ipek Ozkaya,Raghvinder S. Sangwan,Julien Delange,Marco Gonzalez,Philippe Kruchten
Issue Date:September 2013
pp. 400-403
Tools available for measuring the modifiability or impact of change of a system through its architecture typically use structural metrics. These metrics take into account dependencies among the different elements of a system. However, they fail to capture ...
Technical Debt: From Metaphor to Theory and Practice
Found in: IEEE Software
By Philippe Kruchten,Robert L. Nord,Ipek Ozkaya
Issue Date:November 2012
pp. 18-21
The metaphor of technical debt in software development was introduced two decades ago to explain to nontechnical stakeholders the need for what we call now "refactoring." As the term is being used to describe a wide range of phenomena, this paper...
Analysis and Management of Architectural Dependencies in Iterative Release Planning
Found in: Software Architecture, Working IEEE/IFIP Conference on
By Nanette Brown, Robert L. Nord, Ipek Ozkaya, Manuel Pais
Issue Date:June 2011
pp. 103-112
Within any incremental development paradigm, there exists a tension between the desire to deliver value to the customer early and the desire to reduce cost by avoiding architectural refactoring in subsequent releases. What is lacking, however, is quantifia...
Hard choice: A game for balancing strategy for agility
Found in: Software Engineering Education and Training, Conference on
By Nanette Brown,Robert Nord,Ipek Ozkaya,Philippe Kruchten,Erin Lim
Issue Date:May 2011
pp. 553
This poster presents the educational Hard Choices board game that simulates design decision process to communicate the concepts of design strategies in the face of uncertainty. At the end of the game, players experience the implications of investing effort...
A cost-benefit framework for making architectural decisions in a business context
Found in: Software Engineering, International Conference on
By Jeromy Carriere,Rick Kazman,Ipek Ozkaya
Issue Date:May 2010
pp. 149-157
In any IT-intensive organization, it is useful to have a model to associate a value with software and system architecture decisions. More generally, any effort---a project undertaken by a team---needs to have an associated value to offset its labor and cap...
Using Architecturally Significant Requirements for Guiding System Evolution
Found in: Software Maintenance and Reengineering, European Conference on
By Ipek Ozkaya, Andres Diaz-Pace, Arie Gurfinkel, Sagar Chaki
Issue Date:March 2010
pp. 127-136
Rapidly changing technology is one of the key triggers of system evolution. Some examples are: physically relocating a data center, replacement of infrastructure such as migrating from an in-house broker to CORBA, moving to a new architectural approach suc...
Towards engineered architecture evolution
Found in: Modeling in Software Engineering, International Workshop on
By Sagar Chaki, Andres Diaz-Pace, David Garlan, Arie Gurfinkel, Ipek Ozkaya
Issue Date:May 2009
pp. 1-6
Architecture 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 paper, we argue that archite...
Representing Requirement Relationships
Found in: Requirements Engineering Visualization, First International Workshop on
By Ipek Ozkaya
Issue Date:September 2006
pp. 3
Capturing structural relationships between requirements is essential for effective visualization. Existing techniques such as UML, SysML, and goaloriented requirement engineering present a relationship focused approach in visualization; however, a commonly...
Technical debt: from source to mitigation
Found in: Proceedings of the 2013 companion publication for conference on Systems, programming, & applications: software for humanity (SPLASH '13)
By Bill Opdyke, Alexandra Szynkarski, Dennis Mancl, Ipek Ozkaya, Judith Bishop, Junilu Lacar, Pradeep Kathail, Steven Fraser
Issue Date:October 2013
pp. 67-70
The term "Technical Debt" was coined over 20 years ago by Ward Cunningham in a 1992 OOPSLA experience report. Ward used "Technical debt" to describe the trade-offs be-tween delivering the most appropriate - albeit likely immature - product, in the shortest...
Architecting with just enough information
Found in: Proceeding of the 6th international workshop on SHAring and Reusing architectural Knowledge (SHARK '11)
By Ipek Ozkaya, Nanette Brown, Robert L. Nord
Issue Date:May 2011
pp. 9-12
We learned an important lesson recently about breaking down barriers among architects, developers, and other stakeholders when we were engaged on a project and were challenged to deliver the architecture in smaller increments and shorter iterations. We lea...
Second international workshop on managing technical debt: (MTD 2011)
Found in: Proceeding of the 33rd international conference on Software engineering (ICSE '11)
By Ipek Ozkaya, Nanette Brown, Philippe Kruchten, Robert Nord
Issue Date:May 2011
pp. 1212-1213
The technical debt metaphor is gaining significant traction in the software development community as a way to understand and communicate issues of intrinsic quality, value, and cost. The idea is that developers sometimes accept compromises in a system in o...
Managing technical debt in software-reliant systems
Found in: Proceedings of the FSE/SDP workshop on Future of software engineering research (FoSER '10)
By Alan MacCormack, Carolyn Seaman, Erin Lim, Ipek Ozkaya, Kevin Sullivan, Miryung Kim, Nanette Brown, Nico Zazworka, Philippe Kruchten, Raghvinder Sangwan, Rick Kazman, Robert Nord, Yuanfang Cai, Yuepu Guo
Issue Date:November 2010
pp. 47-52
Delivering increasingly complex software-reliant systems demands better ways to manage the long-term effects of short-term expedients. The technical debt metaphor is gaining significant traction in the agile development community as a way to understand and...
Architecture knowledge management during system evolution: observations from practitioners
Found in: Proceedings of the 2010 ICSE Workshop on Sharing and Reusing Architectural Knowledge (SHARK '10)
By Ipek Ozkaya, Jakob Axelsson, Peter Wallin
Issue Date:May 2010
pp. 52-59
It is widely accepted that awareness of architectural decisions enables better management and planning of system evolution, refactoring, and modernization efforts. In this paper we report data from interviews with software architects about how practitioner...
Deciding what to design: closing a gap in software engineering education
Found in: Proceedings of the 27th international conference on Software engineering (ICSE '05)
By Ipek Ozkaya, Jim Herbsleb, Mary Shaw
Issue Date:May 2005
pp. 607-608
Software has jumped "out of the box" - it controls critical systems; it pervades business and commerce; it is embedded in myriad mechanisms; it infuses entertainment, communication, and other activities of everyday life. Designs for these applications are ...