research-article

Visualizing the effects of requirements evolution

Authors:

Hirokazu Tashiro,

Aaron K. Massey,

Annie I. AntónAuthors Info & Claims

ICSE '16: Proceedings of the 38th International Conference on Software Engineering Companion

Pages 152 - 161

https://doi.org/10.1145/2889160.2889237

Published: 14 May 2016 Publication History

Abstract

Changes to software requirements occur throughout the software life cycle. Requirements engineers who maintain software systems in regulated environments must identify the affected artifacts when requirements change. This identification is critical to: (a) ensure continued compliance with regulations, and (b) accurately estimate budget requests. Previously, we introduced Requirements Evolution Charts (REC) to provide a visual representation of requirements evolution history. An REC is generated from the issue tickets in which requirements engineers record changes to requirements artifacts. Herein, we examine whether a REC helps software engineers conduct an impact analysis. Thirty experienced NTT requirements engineers with no prior domain knowledge identified the impact of seven requirements changes in a large-scale system governed by Japanese laws and regulations. They were divided into two groups of fifteen engineers. The REC group employed the REC to aid their efforts; the Non-REC group conducted their impact analysis without the REC. Participants in both groups identified which of the 139 artifacts were affected based on a history of 108 issue tickets. Our study reveals that engineers in the REC group identified the affected artifacts more accurately and quickly than the Non-REC group, suggesting that the REC is a valuable tool for examining the impact of requirements evolution.

References

[1]

A. I. Anton and C. Potts. Functional paleontology: the evolution of user-visible system services. IEEE Transactions on Software Engineering, 29(2):151--166, Feb. 2003.

Digital Library

[2]

R. A. Carter, A. I. Anton, A. Dagnino, and L. Williams. Evolving beyond requirements creep: a risk-based evolutionary prototyping model. In Proceedings of the Fifth IEEE International Symposium on Requirements Engineering, pages 94--101, 2001.

Digital Library

[3]

J. Cleland-Huang, C. K. Chang, and M. Christensen. Event-based traceability for managing evolutionary change. IEEE Transactions on Software Engineering, 29(9):796--810, Sept. 2003.

Digital Library

[4]

J. Cohen. Statistical Power Analysis for Behavioral Sciences. New York: Academic Press, Revised Edition edition, 1977.

[5]

S. Easterbrook and B. Nuseibeh. Managing inconsistencies in an evolving specification. In Proceedings of the Second IEEE International Symposium on Requirements Engineering, pages 48--55, Mar. 1995.

Digital Library

[6]

M. E. Fagan. Advances in software inspections. IEEE Transactions on Software Engineering, SE-12(7):744--751, July 1986.

Digital Library

[7]

J. L. Fleiss and J. Cohen. The equivalence of weighted kappa and the intraclass correlation coefficient as measures of reliability. Educational and psychological measurement, 1973.

[8]

Graphviz. http://www.graphviz.org/, 2016.

[9]

S. D. P. Harker, K. D. Eason, and J. E. Dobson. The change and evolution of requirements as a challenge to the practice of software engineering. In Proceedings of IEEE International Symposium on Requirements Engineering, pages 266--272, Jan. 1993.

[10]

JIRA. http://www.atlassian.com/en/software/jira, 2016.

[11]

C. Jones. Strategies for managing requirements creep. Computer, 29(6):92--94, June 1996.

Digital Library

[12]

J. C. Maxwell, A. I. Anton, and P. Swire. Managing changing compliance requirements by predicting regulatory evolution. In Proceedings of the 20th IEEE International Requirements Engineering Conference, pages 101--110, Sept. 2012.

Digital Library

[13]

NTT. http://www.ntt.co.jp/index_e.html/, 2016.

[14]

Redmine. http://www.redmine.org/, 2016.

[15]

S. Saito, Y. Iimura, K. Takahashi, A. K. Massey, and A. I. Antón. Tracking Requirements Evolution by Using Issue Tickets: A Case Study of a Document Management and Approval System. In Companion Proceedings of the 36th International Conference on Software Engineering, ICSE Companion 2014, pages 245--254, New York, NY, USA, 2014. ACM.

Digital Library

[16]

The Trac Project. http://trac.edgewall.org/, 2016.

[17]

K. Wnuk, B. Regnell, and L. Karlsson. Feature Transition Charts for Visualization of Cross-Project Scope Evolution in Large-Scale Requirements Engineering for Product Lines. In Fourth International Workshop on Requirements Engineering Visualization (REV), pages 11--20, Sept. 2009.

Digital Library

[18]

R. Yin. Case Study Research: Design and Methods. Sage Publications, Third Edition edition, 2003.

[19]

D. Zowghi and R. Offen. A logical framework for modeling and reasoning about the evolution of requirements. In Proceedings of the Third IEEE International Symposium on Requirements Engineering, pages 247--257, Jan. 1997.

Digital Library

Cited By

Rocky SRahim LAhmad RSarlan A(2021)Hierarchical Permissioned Blockchain and Traceability Of Requirement Changes2021 International Conference on Intelligent Cybernetics Technology & Applications (ICICyTA)10.1109/ICICyTA53712.2021.9689117(144-148)Online publication date: 1-Dec-2021
https://doi.org/10.1109/ICICyTA53712.2021.9689117
Berry D(2021)Empirical evaluation of tools for hairy requirements engineering tasksEmpirical Software Engineering10.1007/s10664-021-09986-026:6Online publication date: 18-Aug-2021
https://doi.org/10.1007/s10664-021-09986-0
Ishizuka RWashizaki HFukazawa YSaito SOuji S(2019)Categorizing and Visualizing Issue Tickets to Better Understand the Features Implemented in Existing Software Systems2019 10th International Workshop on Empirical Software Engineering in Practice (IWESEP)10.1109/IWESEP49350.2019.00013(25-255)Online publication date: Dec-2019
https://doi.org/10.1109/IWESEP49350.2019.00013
Show More Cited By

Visualizing the effects of requirements evolution
1. Software and its engineering
  1. Software creation and management
    1. Designing software

Recommendations

Tracking requirements evolution by using issue tickets: a case study of a document management and approval system
ICSE Companion 2014: Companion Proceedings of the 36th International Conference on Software Engineering

Requirements evolve throughout the software life-cycle. When requirements change, requirements engineers must determine what software artifacts could be affected. The history of and rationale for requirements evolution provides engineers some ...
Supporting requirements update during software evolution

Updating the requirements specification when software systems evolve is a manual task that is expensive and time consuming. Therefore, maintainers usually apply the changes to the code directly and leave the requirements unchanged. This results in the ...
Requirements evolution drives software evolution
IWPSE-EVOL '11: Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th annual ERCIM Workshop on Software Evolution

Changes to software should be made with reference to the requirements of that software, as these requirements provide the reasons for a change. Requirements serve to tie the implementation world of the developers to the problem world of the ...

Comments

Information & Contributors

Information

Published In

cover image ACM Conferences

ICSE '16: Proceedings of the 38th International Conference on Software Engineering Companion

May 2016

946 pages

ISBN:9781450342056

DOI:10.1145/2889160

General Chair:
Laura Dillon
Michigan State University
,
Program Chairs:
Willem Visser
Stellenbosch University, South Africa
,
Laurie Williams
North Carolina State University

Copyright © 2016 ACM.

Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. Copyrights for components of this work owned by others than ACM must be honored. Abstracting with credit is permitted. To copy otherwise, or republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. Request permissions from [email protected]

Sponsors

ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
IEEE-CS\TCSE: TC on Software Engineering
IEEE-CS\DATC: IEEE Computer Society

Publisher

Association for Computing Machinery

New York, NY, United States

Publication History

Published: 14 May 2016

Permissions

Request permissions for this article.

Request Permissions

Check for updates

Author Tags

Qualifiers

Research-article

Conference

ICSE '16

Sponsor:

ACM
SIGSOFT
IEEE-CS\TCSE
IEEE-CS\DATC

ICSE '16: 38th International Conference on Software Engineering

May 14 - 22, 2016

Texas, Austin

Acceptance Rates

Overall Acceptance Rate 276 of 1,856 submissions, 15%

Upcoming Conference

ICSE 2025

2025 IEEE/ACM 46th International Conference on Software Engineering

April 26 - May 3, 2025

Ottawa , ON , Canada

Contributors

Other Metrics

View Article Metrics

Bibliometrics & Citations

Bibliometrics

Article Metrics

7
Total Citations
View Citations
277
Total Downloads

Downloads (Last 12 months)2
Downloads (Last 6 weeks)0

Reflects downloads up to 22 Jan 2025

Other Metrics

View Author Metrics

Citations

Cited By

Rocky SRahim LAhmad RSarlan A(2021)Hierarchical Permissioned Blockchain and Traceability Of Requirement Changes2021 International Conference on Intelligent Cybernetics Technology & Applications (ICICyTA)10.1109/ICICyTA53712.2021.9689117(144-148)Online publication date: 1-Dec-2021
https://doi.org/10.1109/ICICyTA53712.2021.9689117
Berry D(2021)Empirical evaluation of tools for hairy requirements engineering tasksEmpirical Software Engineering10.1007/s10664-021-09986-026:6Online publication date: 18-Aug-2021
https://doi.org/10.1007/s10664-021-09986-0
Ishizuka RWashizaki HFukazawa YSaito SOuji S(2019)Categorizing and Visualizing Issue Tickets to Better Understand the Features Implemented in Existing Software Systems2019 10th International Workshop on Empirical Software Engineering in Practice (IWESEP)10.1109/IWESEP49350.2019.00013(25-255)Online publication date: Dec-2019
https://doi.org/10.1109/IWESEP49350.2019.00013
Jeong SCho HLee SChaudron MCrnkovic IChechik MHarman M(2018)Agile requirement traceability matrixProceedings of the 40th International Conference on Software Engineering: Companion Proceeedings10.1145/3183440.3195089(187-188)Online publication date: 27-May-2018
https://dl.acm.org/doi/10.1145/3183440.3195089
Saito SIimura YMassey AAntón A(2018)Discovering undocumented knowledge through visualization of agile software development activitiesRequirements Engineering10.1007/s00766-018-0291-423:3(381-399)Online publication date: 1-Sep-2018
https://dl.acm.org/doi/10.1007/s00766-018-0291-4
Saito SIimura YMassey AAnton A(2017)How Much Undocumented Knowledge is there in Agile Software Development?: Case Study on Industrial Project Using Issue Tracking System and Version Control System2017 IEEE 25th International Requirements Engineering Conference (RE)10.1109/RE.2017.33(194-203)Online publication date: Sep-2017
https://doi.org/10.1109/RE.2017.33
Parwoto DOmori TItoga HOhnishi A(2017)Visualization of Quality of Software Requirements Specification Using Digital Elevation ModelRequirements Engineering: Foundation for Software Quality10.1007/978-3-319-54045-0_16(209-215)Online publication date: 21-Feb-2017
https://doi.org/10.1007/978-3-319-54045-0_16

View Options

Login options

Check if you have access through your login credentials or your institution to get full access on this article.

Full Access

Get this Publication

View options

PDF

View or Download as a PDF file.

eReader

View online with eReader.

Media

Figures

Other

Tables

View Table of Contents