CPL - Chalmers Publication Library
| Utbildning | Forskning | Styrkeområden | Om Chalmers | In English In English Ej inloggad.

Towards Prioritizing Architecture Technical Debt: Information Needs of Architects and Product Owners

Antonio Martini (Institutionen för data- och informationsteknik, Software Engineering (Chalmers)) ; Jan Bosch (Institutionen för data- och informationsteknik, Software Engineering (Chalmers))
41st Euromicro Conference on Software Engineering and Advanced Applications (SEAA), 26-28 August, 2015 p. 422-429. (2015)
[Konferensbidrag, refereegranskat]

Architectural Technical Debt is a metaphor for representing sub-optimal architectural solutions that might cause an interest, in terms of effort or quality, to be paid by the organization in the long run. Such metaphor has been regarded as useful for communicating risks of suboptimal solutions between technical and non-technical stakeholders. However, it's fundamental to understand the information needs of the involved stakeholders in order to produce technical debt measurements that would allow proper communication and informed prioritization. We have investigated, through a combination of interviews, observations and a survey, what key information is needed by agile product owners and software architects in order to prioritize the refactoring of risky architectural technical debt items with respect to feature development.

Nyckelord: Architecture Technical Debt; Prioritization Aspects; Feature Prioritization; Refactoring Prioritization; Information Need

Denna post skapades 2015-11-27. Senast ändrad 2016-09-14.
CPL Pubid: 226474


Läs direkt!

Länk till annan sajt (kan kräva inloggning)