2004
DOI: 10.1631/jzus.2004.0587
|View full text |Cite
|
Sign up to set email alerts
|

Testing agile requirements models

Abstract: Abstract:This paper discusses a model-based approach to test software requirements in agile development processes. The use of models as central development artifact needs to be added to the portfolio of software engineering techniques, to further increase efficiency and flexibility of the development beginning already early in the requirements definition phase. Testing requirements is one of the most important techniques to give feedback and to increase the quality of the result. Therefore testing of artifacts… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2009
2009
2009
2009

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 12 publications
0
1
0
Order By: Relevance
“…The facilities provided by UML are ideally placed to capture functional requirements. However, as described in [2], although models can be used for an explicit description of a test case, the functional requirements expressed in UML using representations such as use case models and activity diagrams are often informal, have a weak semantics and are weakly integrated.…”
Section: Introductionmentioning
confidence: 99%
“…The facilities provided by UML are ideally placed to capture functional requirements. However, as described in [2], although models can be used for an explicit description of a test case, the functional requirements expressed in UML using representations such as use case models and activity diagrams are often informal, have a weak semantics and are weakly integrated.…”
Section: Introductionmentioning
confidence: 99%