Change impact analysis for Natural Language requirements: An NLP approach

Arora, Chetan; Sabetzadeh, Mehrdad; Göknil, Arda; Briand, Lionel C.; Zimmer, Frank

doi:10.1109/re.2015.7320403

Cited by 53 publications

(44 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To perform NLP in use case specifications, the Configurator and Artifact Consistency Checker components use a regular expression engine, called JAPE [43] [11,12] to tackle inconsistent naming conventions in the comparison. Data Layer.…”

Section: Tool Architecturementioning

confidence: 99%

Configuring use case models in product families

et al. 2016

Self Cite

View full text Add to dashboard Cite

In many domains such as automotive and avionics, the size and complexity of software systems is quickly increasing. At the same time, many stakeholders tend to be involved in the development of such systems, which typically must also be configured for multiple customers with varying needs. Product Line Engineering (PLE) is therefore an inevitable practice for such systems. Furthermore, because in many areas requirements must be explicit and traceability to them is required by standards, use cases and domain models are common practice for requirements elicitation and analysis. In this paper, based on the above observations, we aim at supporting PLE in the context of use casecentric development. Therefore, we propose, apply, and assess a use case-driven configuration approach which interactively receives configuration decisions from the analysts to generate Product Specific (PS) use case and domain models. Our approach provides the following: (1) a use case-centric product line modeling method (PUM), (2) automated, interactive configuration support based on PUM, and (3) an automatic generation of PS use case and domain models from Product Line (PL) models and configuration decisions. The approach is supported by a tool relying on Natural Language Processing (NLP), and integrated with an industrial requirements management tool, i.e., IBM Doors. We successfully applied and evaluated our approach to an industrial case study in the automotive domain, thus showing evidence that the approach is practical and beneficial to capture variability at the appropriate level of granularity and to configure PS use case and domain models in industrial settings.

show abstract

Section: Tool Architecturementioning

confidence: 99%

Configuring use case models in product families

et al. 2016

Self Cite

View full text Add to dashboard Cite

show abstract

“…The keyphrases are extracted automatically using a keyphrase extractor. We use a tailored extractor that we developed in our previous work [6] for supporting requirements tasks. For example, applying the extractor over the statement "Temperature lookup tables and voltage converters need to be adjusted."…”

Section: Ranking Potentially Impacted Elementsmentioning

confidence: 99%

“…In our previous work [6], we already used similarity measures as change impact predictors. Nevertheless, this earlier work was focused on inter-requirement change impact analysis, i.e., identifying the impact of requirements changes on other requirements, rather than on the design.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Automated change impact analysis between SysML models of requirements and design

Nejati

Sabetzadeh

Arora

et al. 2016

Proceedings of the 2016 24th ACM SIGSOFT International Symposium on Foundations of Software Engineering

Self Cite

View full text Add to dashboard Cite

An important activity in systems engineering is analyzing how a change in requirements will impact the design of a system. Performing this analysis manually is expensive, particularly for complex systems. In this paper, we propose an approach to automatically identify the impact of requirements changes on system design, when the requirements and design elements are expressed using models. We ground our approach on the Systems Modeling Language (SysML) due to SysML's increasing use in industrial applications.Our approach has two steps: For a given change, we first apply a static slicing algorithm to extract an estimated set of impacted model elements. Next, we rank the elements of the resulting set according to a quantitative measure designed to predict how likely it is for each element to be impacted. The measure is computed using Natural Language Processing (NLP) applied to the textual content of the elements. Engineers can then inspect the ranked list of elements and identify those that are actually impacted. We evaluate our approach on an industrial case study with 16 real-world requirements changes. Our results suggest that, using our approach, engineers need to inspect on average only 4.8% of the entire design in order to identify the actually-impacted elements. We further show that our results consistently improve when our analysis takes into account both structural and behavioral diagrams rather than only structural ones, and the natural-language content of the diagrams in addition to only their structural and behavioral content.

show abstract

“…Goknil defines the types of interdependence association between requirements and reasoning about the dependency association of requirements by using [5] formalization to review the consistency of association requirements and concludes the association of new requirements. In the other research about engineering requirements proposed an advanced methodology for requirements solution technical engineering [6].…”

Section: Introductionmentioning

confidence: 99%

Requirements Association Extraction based on Use Cases Diagram

Gelu

Sarno²,

Siahaan

2018

LKJITI

View full text Add to dashboard Cite

Requirements are the initial step in the software development process. It is very important to ensure the association (relationship) of requirements and high quality of specification as more than three-quarters failure of software derives from the software requirement process. Therefore, the analysis process is required to ensure the association between requirements and the requirements of other users. As a result, interdependency requirements association is essential. This research proposes an approach of software requirements association. These are based on the reference of interdependency in the user case, namely the result of collaboration of the association of the dependency of requirements based on Unified Modeling Language (UML) design in the Use cases diagram. In this research, the mapping between requirements and use cases and interdependencies between use cases are used to determine the interdependency between requirements. The analysis presented is the association of similar requirements, requires, or, temporal, elaborates dan generalises. The purpose of this research is to generate a requirements dependency graph that models the type of dependency between requirements within a software project.

show abstract

Change impact analysis for Natural Language requirements: An NLP approach

Cited by 53 publications

References 18 publications

Configuring use case models in product families

Configuring use case models in product families

Automated change impact analysis between SysML models of requirements and design

Requirements Association Extraction based on Use Cases Diagram

Contact Info

Product

Resources

About