2014 IEEE 22nd International Requirements Engineering Conference (RE) 2014
DOI: 10.1109/re.2014.6912255
|View full text |Cite
|
Sign up to set email alerts
|

Traceability-enabled refactoring for managing just-in-time requirements

Abstract: Abstract-Just-in-time requirements management, characterized by lightweight representation and continuous refinement of requirements, fits many iterative and incremental development projects. Being lightweight and flexible, however, can cause wasteful and procrastinated implementation, leaving certain stakeholder goals not satisfied. This paper proposes traceabilityenabled refactoring aimed at fulfilling more requirements fully. We make a novel use of requirements traceability to accurately locate where the so… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
6
0
1

Year Published

2015
2015
2024
2024

Publication Types

Select...
6
1
1

Relationship

2
6

Authors

Journals

citations
Cited by 31 publications
(8 citation statements)
references
References 40 publications
1
6
0
1
Order By: Relevance
“…In their seminal work on just-in-time RE, Ernst and Murphy [51] emphasize on the extensive use of issue tracking systems in requirements elicitation and elaboration for OSS systems. Such a use of issue trackers has also been corroborated by other studies involving OSS systems [52][53][54][55]. However, our approach is general enough, and other sources of information, such as e-mail and IRC, could also be used in our framework.…”
Section: Our Creativity Frameworksupporting
confidence: 68%
“…In their seminal work on just-in-time RE, Ernst and Murphy [51] emphasize on the extensive use of issue tracking systems in requirements elicitation and elaboration for OSS systems. Such a use of issue trackers has also been corroborated by other studies involving OSS systems [52][53][54][55]. However, our approach is general enough, and other sources of information, such as e-mail and IRC, could also be used in our framework.…”
Section: Our Creativity Frameworksupporting
confidence: 68%
“…It is recommended the researchers pay more attention to an industry-based investigation on the refactoring. Niu, Bhowmik, Liu, and Niu [30] suggested an approach to trace the requirements to identify accurately the locations in a system that need to be refactored and the refactoring that should to be applied. To assess the approach, an industrial case study was used.…”
Section: Resultsmentioning
confidence: 99%
“…Statistically, thirteen out of twenty studies (i.e. 65%) did not identify any type of refactoring techniques proposed by Fowler ([12], [13][23], [24], [25], [28], [29], [30], [31], [34], [32], [36], [38]). Moreover, two out of these thirteen studies ( [23], [34]) did not use the refactoring techniques from Fowler's catalog.…”
Section: • Applied Refactoring Techniquesmentioning
confidence: 99%
“…Terdapat beberapa metode yang digunakan untuk refactoring. Metode clustering digunakan pada tiga penelitian, yaitu refactoring level package untuk menyeimbangkan antara cohesion dan coupling dengan algoritma Adaptif K-Nearest Neighbour (A-KNN) [5], refactoring pada requirement dalam format eXtensible Markup Language (XML) [6], dan refactoring pada komponen arsitektur untuk mencari komponen apa saja yang mirip dengan clustering dan selanjutnya dilakukan proses restrukturisasi [7]. Penelitian [8] menggunakan metode pendeteksian refactoring pada Refined Process Tree dari repositori process model dengan mencari kemiripan string label dan kemiripan fragmen.…”
Section: Rq1 : Teknik Atau Algoritma Metode -Metode Non-heuristicunclassified