A UML profile for goal-oriented and use case-driven representation of NFRs and FRs

Supakkul, Sam; Chung, Lawrence

doi:10.1109/sera.2005.19

Cited by 36 publications

(21 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some authors [42,82] use the UML profiling mechanism in a goal-oriented requirements engineering approach. Heaven et al [42] introduce a profile that allows the KAOS model [91] to be represented in UML.…”

Section: Requirements Metamodelingmentioning

confidence: 99%

“…They also provide an integration of requirements models with lower level design models. Supakkul et al [82] use the UML profiling mechanism to provide an integrated modeling language for functional and non-functional requirements that are mostly specified by using different notations. These two works aim at a metamodel for goal-oriented requirements engineering rather than reasoning over requirements and change impact analysis.…”

Section: Requirements Metamodelingmentioning

confidence: 99%

See 1 more Smart Citation

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

a b s t r a c tContext: Following the evolution of the business needs, the requirements of software systems change continuously and new requirements emerge frequently. Requirements documents are often textual artifacts with structure not explicitly given. When a change in a requirements document is introduced, the requirements engineer may have to manually analyze all the requirements for a single change. This may result in neglecting the actual impact of a change. Consequently, the cost of implementing a change may become several times higher than expected. Objective: In this paper, we aim at improving change impact analysis in requirements by using formal semantics of requirements relations and requirements change types. Method: In our previous work we present a requirements metamodel with commonly used requirements relation types and their semantics formalized in first-order logic. In this paper the classification of requirements changes based on structure of a textual requirement is provided with formal semantics. The formalization of requirements relations and changes is used for propagating proposed changes and consistency checking of proposed changes in requirements models. The tool support for change impact analysis in requirements models is an extension of our Tool for Requirements Inferencing and Consistency Checking (TRIC). Results: The described approach for change impact analysis helps in the elimination of some false positive impacts in change propagation, and enables consistency checking of changes. Conclusion: We illustrate our approach in an example which shows that the formal semantics of requirements relations and change classification enables change alternatives to be proposed semi-automatically, the reduction of some false positive impacts and contradicting changes in requirements to be determined.

show abstract

Section: Requirements Metamodelingmentioning

confidence: 99%

Section: Requirements Metamodelingmentioning

confidence: 99%

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…Some authors [21,45] use the UML profiling mechanism in a goal-oriented requirements engineering approach. Heaven et al [21] introduce a profile that allows the KAOS model [50] to be represented in UML.…”

Section: Requirements Metamodelingmentioning

confidence: 99%

“…They also provide an integration of requirements models with lower level design models. Supakkul et al [45] use the UML profiling mechanism to provide an integrated modeling language for functional and non-functional requirements that are mostly specified by using different notations. These two works aim at a metamodel for goal-oriented requirements engineering rather than reasoning over requirements.…”

Section: Requirements Metamodelingmentioning

confidence: 99%

Semantics of trace relations in requirements models for consistency checking and inferencing

et al. 2009

View full text Add to dashboard Cite

Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined.

show abstract

“…Many researchers have addressed the issue of change impact analysis in the context of requirements modeling. [6,17] use UML profiling mechanism for goal-oriented requirements engineering approach whereas KAOS model of [19] can be represented in UML by using the approach given in [6]. [17] use UML profiling mechanism to provide an integrated modeling language for functional and non-functional requirements that are mostly specified by using different notations.…”

Section: Related Workmentioning

confidence: 99%

Dependency based Process Model for Impact Analysis: A Requirement Engineering Perspective

Gupta¹,

Singh²,

Chauhan³

2010

IJCA

View full text Add to dashboard Cite

Changing requirements of customer needs establishes the need to analyze impact of requirement changes. For success of any software requirement analysis is very essential. In this paper, we propose a four stage method engineering process which aims at estimating impact of change. The process model described is a linear layered model. Impact sets are computed by analyzing dependency tractability relations with other connected method components. The results produced provide two type of information (a) added, deleted, modified methods (b) depth (extent) of impact on the system. General TermsChange impact analysis, software maintenance, software testing.

show abstract

A UML profile for goal-oriented and use case-driven representation of NFRs and FRs

Cited by 36 publications

References 16 publications

Change impact analysis for requirements: A metamodeling approach

Change impact analysis for requirements: A metamodeling approach

Semantics of trace relations in requirements models for consistency checking and inferencing

Dependency based Process Model for Impact Analysis: A Requirement Engineering Perspective

Contact Info

Product

Resources

About