Proceedings of the 24th International Conference on Software Engineering - ICSE '02 2002
DOI: 10.1145/581352.581355
|View full text |Cite
|
Sign up to set email alerts
|

Detection of conflicting functional requirements in a use case-driven approach

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
18
0

Year Published

2005
2005
2016
2016

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 71 publications
(18 citation statements)
references
References 13 publications
0
18
0
Order By: Relevance
“…User's requirements may generate conflicts among themselves. A conflict occurs when requirements generate incompatibilities between common software attributes [26] or when performing an activity that prevents the execution of another one [27]. It can be due to inconsistency in the specifications in case of multiple stakeholders [28].…”
Section: Requirement Elicitation Phasementioning
confidence: 99%
“…User's requirements may generate conflicts among themselves. A conflict occurs when requirements generate incompatibilities between common software attributes [26] or when performing an activity that prevents the execution of another one [27]. It can be due to inconsistency in the specifications in case of multiple stakeholders [28].…”
Section: Requirement Elicitation Phasementioning
confidence: 99%
“…To restrict the choice of matches for rules, we introduce the concept of partial rule dependencies which may relate output parameter nodes of one rule to input parameter nodes of a (not necessarily direct) subsequent rule in a given rule sequence 2 . We say that rule sequences are dependency-compatible, if the transitive closure of all dependencies between each two rules is well-defined.…”
Section: Partial Rule Dependenciesmentioning
confidence: 99%
“…This refinement serves as a basis for consistency analysis. The refinement of activities by pre-and post-conditions was first introduced in [2] to analyze inconsistencies between individual activities refining use cases. Pre-and post conditions are formalized as graph transformation rules.…”
Section: Introductionmentioning
confidence: 99%
“…The set of critical pairs represents precisely all potential conflicts: Given two rules pi and p2, there exists a critical pair if and only if pi may disable p2, or p2 may disable pi. If no conflicts exist between any pair of rules the graph transformation system has a functional behavior [Hausmann et al, 2002].…”
Section: Validationmentioning
confidence: 99%