Developing comprehensive acceptance tests from use cases and robustness diagrams.
Saved in:
| Title: | Developing comprehensive acceptance tests from use cases and robustness diagrams. |
|---|---|
| Authors: | El-Attar, Mohamed1 melattar@kfupm.edu.sa, Miller, James2 jm@ece.ualberta.ca |
| Source: | Requirements Engineering. Sep2010, Vol. 15 Issue 3, p285-306. 22p. 4 Color Photographs, 14 Diagrams, 21 Charts. |
| Subjects: | Use cases (Systems engineering), Agile software development, Robust control, Testing, System analysis |
| Abstract: | In agile development processes, the rewards from acceptance testing are maximized by using the practice to drive the development process. Traditionally, User Stories are used in agile projects to describe a system’s usage scenarios and are utilized as a basis for developing acceptance tests. This paper introduces a technique that aims to achieve the benefits of acceptance testing within large-scale development projects that deploy a V-model development process, specifically those that utilize use case models. The approach is based on utilizing a number of artifacts: use case models supported by robustness diagrams and domain models. The feasibility of the proposed approach is demonstrated by applying it to a real-world system—the RestoMapper system. The results show that a comprehensive set of acceptance tests can be developed based upon use case models. [ABSTRACT FROM AUTHOR] |
| Copyright of Requirements Engineering is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.) | |
| Database: | Engineering Source |
| FullText | Links: – Type: pdflink Text: Availability: 0 |
|---|---|
| Header | DbId: egs DbLabel: Engineering Source An: 52965353 AccessLevel: 6 PubType: Academic Journal PubTypeId: academicJournal PreciseRelevancyScore: 0 |
| IllustrationInfo | |
| Items | – Name: Title Label: Title Group: Ti Data: Developing comprehensive acceptance tests from use cases and robustness diagrams. – Name: Author Label: Authors Group: Au Data: <searchLink fieldCode="AR" term="%22El-Attar%2C+Mohamed%22">El-Attar, Mohamed</searchLink><relatesTo>1</relatesTo><i> melattar@kfupm.edu.sa</i><br /><searchLink fieldCode="AR" term="%22Miller%2C+James%22">Miller, James</searchLink><relatesTo>2</relatesTo><i> jm@ece.ualberta.ca</i> – Name: TitleSource Label: Source Group: Src Data: <searchLink fieldCode="JN" term="%22Requirements+Engineering%22">Requirements Engineering</searchLink>. Sep2010, Vol. 15 Issue 3, p285-306. 22p. 4 Color Photographs, 14 Diagrams, 21 Charts. – Name: Subject Label: Subjects Group: Su Data: <searchLink fieldCode="DE" term="%22Use+cases+%28Systems+engineering%29%22">Use cases (Systems engineering)</searchLink><br /><searchLink fieldCode="DE" term="%22Agile+software+development%22">Agile software development</searchLink><br /><searchLink fieldCode="DE" term="%22Robust+control%22">Robust control</searchLink><br /><searchLink fieldCode="DE" term="%22Testing%22">Testing</searchLink><br /><searchLink fieldCode="DE" term="%22System+analysis%22">System analysis</searchLink> – Name: Abstract Label: Abstract Group: Ab Data: In agile development processes, the rewards from acceptance testing are maximized by using the practice to drive the development process. Traditionally, User Stories are used in agile projects to describe a system’s usage scenarios and are utilized as a basis for developing acceptance tests. This paper introduces a technique that aims to achieve the benefits of acceptance testing within large-scale development projects that deploy a V-model development process, specifically those that utilize use case models. The approach is based on utilizing a number of artifacts: use case models supported by robustness diagrams and domain models. The feasibility of the proposed approach is demonstrated by applying it to a real-world system—the RestoMapper system. The results show that a comprehensive set of acceptance tests can be developed based upon use case models. [ABSTRACT FROM AUTHOR] – Name: AbstractSuppliedCopyright Label: Group: Ab Data: <i>Copyright of Requirements Engineering is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract.</i> (Copyright applies to all Abstracts.) |
| PLink | https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=52965353 |
| RecordInfo | BibRecord: BibEntity: Identifiers: – Type: doi Value: 10.1007/s00766-009-0088-6 Languages: – Code: eng Text: English PhysicalDescription: Pagination: PageCount: 22 StartPage: 285 Subjects: – SubjectFull: Use cases (Systems engineering) Type: general – SubjectFull: Agile software development Type: general – SubjectFull: Robust control Type: general – SubjectFull: Testing Type: general – SubjectFull: System analysis Type: general Titles: – TitleFull: Developing comprehensive acceptance tests from use cases and robustness diagrams. Type: main BibRelationships: HasContributorRelationships: – PersonEntity: Name: NameFull: El-Attar, Mohamed – PersonEntity: Name: NameFull: Miller, James IsPartOfRelationships: – BibEntity: Dates: – D: 01 M: 09 Text: Sep2010 Type: published Y: 2010 Identifiers: – Type: issn-print Value: 09473602 Numbering: – Type: volume Value: 15 – Type: issue Value: 3 Titles: – TitleFull: Requirements Engineering Type: main |
| ResultId | 1 |
