Validation of Component-Based Software with a Customer Centric Domain Level Approach

Skroch, Oliver

doi:10.1109/ecbs.2007.76

Cited by 2 publications

(2 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Fig. 2 (notation: activity diagram [24]) gives an overview on the ARIval (abstraction, reduction, inclusion, validation) method [32], where domain level scenarios are used to validate aspects of multi-layered component reuse specifications, if possible showing that the specified software works for the higher-order domain requirements.…”

Section: A Arival Overviewmentioning

confidence: 99%

“…[19] The distinction between technology based supplier testing and domain based customer testing is widely acknowledged, in particular with component-based software [12;40]. Recently, an approach was proposed specifically for component validation testing on the domain level of the demand side [32]. It is based on testable scenarios which are independently derived from an end user domain and become checked against reuse specifications from suppliers.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Reducing Domain Level Scenarios to Test Component-based Software

Skroch¹,

Turowski²

2007

JSW

Self Cite

View full text Add to dashboard Cite

Higher-order black box software tests against independent end user domain requirements has become an issue of increasing importance with compositional reuse of software artifacts. Recently, a general method was proposed that derives testable scenarios directly from a customer domain model by abstraction, reduction and inclusion for critical coverage [32]. The resulting linear (i.e. nonbranching) scenarios are used as references to test suppliers’ software specifications against. This paper presents the method in an overview and elaborates on the domain reduction step within the process for the generation of testable scenarios from a domain model. An example is provided which is non-fictitious on the domain side. Advantages of the method are an underlying clear business model, test oracles that are independent from the software development process, and validation results that are generated early in the development cycle, before the software itself is available.

show abstract

Section: A Arival Overviewmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%