Using scenarios to support traceability

Naslavsky, Leila; Alspaugh, Thomas A.; Richardson, Debra J.; Ziv, Hadar

doi:10.1145/1107656.1107663

Cited by 24 publications

(11 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This is utilized by several recent research projects to store traces in XML files. (e.g., [116,123,127]). XML is also used in the GENESIS subproject [22] of the OSCAR project, which uses a common repository to integrate artifacts: The GENESIS platform defines a distributed repository based on XML in which so-called "active" artifacts can be stored.…”

Section: Integrative Approachesmentioning

confidence: 99%

A survey of traceability in requirements engineering and model-driven development

2009

View full text Add to dashboard Cite

Traceability-the ability to follow the life of software artifacts-is a topic of great interest to software developers in general, and to requirements engineers and model-driven developers in particular. This article aims to bring those stakeholders together by providing an overview of the current state of traceability research and practice in both areas. As part of an extensive literature survey, we identify commonalities and differences in these areas and uncover several unresolved challenges which affect both domains. A good common foundation for further advances regarding these challenges appears to be a combination of the formal basis and the automated recording opportunities of MDD on the one hand, and the more holistic view of traceability in the requirements engineering domain on the other hand.Keywords Requirements engineering · Model-driven engineering · Model-driven development · Traceability

show abstract

Section: Integrative Approachesmentioning

confidence: 99%

A survey of traceability in requirements engineering and model-driven development

2009

View full text Add to dashboard Cite

show abstract

“…Therefore, a use case can be considered to be a set of scenarios. Scenarios are popularly used for requirements specification and testing of the overall system implementation and have been recognized by UML as being part of the behavioural diagrams called Sequence Diagrams [60]. Scenarios are usually represented using formal graphical notations like the Message Sequence Charts (MSCs), Live Sequence Charts, etc.…”

Section: Current Approach To Test Distributed Software Functions At Smentioning

confidence: 99%

“…Majority of these studies have been found to be focusing on establishing traceability in formal model-based requirements specification and testing [91]. Other studies have addressed establishing traceability through semi-formal requirements specification and testing based on use cases and scenarios [60] [95].…”

Section: Traceabilitymentioning

confidence: 99%

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Chunduri

Feldt

Adenmark

2016

Product-Focused Software Process Improvement

View full text Add to dashboard Cite

Context. The share and importance of software within automotive vehicles is growing steadily. Most functionalities in modern vehicles, especially safety related functions like advanced emergency braking, are controlled by software. A complex and common phenomenon in today's automotive vehicles is the distribution of such software functions across several Electronic Control Units (ECUs) and consequently across several ECU system software modules. As a result, integration testing of these distributed software functions has been found to be a challenge. The automotive industry neither has infinite resources, nor has the time to carry out exhaustive testing of these functions. On the other hand, the traditional approach of implementing an ad-hoc selection of test scenarios based on the tester's experience, can lead to test gaps and test redundancies. Hence, there is a pressing need within the automotive industry for a feasible and effective verification strategy for testing distributed software functions. Objectives. Firstly, to identify the current approach used to test the distributed automotive embedded software functions in literature and in a case company. Secondly, propose and validate a feasible and effective verification strategy for testing the distributed software functions that would help improve test coverage while reducing test redundancies and test gaps. Methods. To accomplish the objectives, a case study was conducted at Scania CV AB, Södertälje, Sweden. One of the data collection methods was through conducting interviews of different employees involved in the software testing activities. Based on the research objectives, an interview questionnaire with open-ended and close-ended questions has been used. Apart from interviews, data from relevant artifacts in databases and archived documents has been used to achieve data triangulation. Moreover, to further strengthen the validity of the results obtained, adequate literature support has been presented throughout. Towards the end, a verification strategy has been proposed and validated using existing historical data at Scania. Conclusions. The proposed verification strategy to test distributed automotive embedded software functions has given promising results by providing means to identify test gaps and test redundancies. It helps establish an effective and feasible approach to capture function test coverage information that helps enhance the effectiveness of integration testing of the distributed software functions.

show abstract

“…If they were not found in the records they were then downloaded. Title [57] Recovering Traceability Links in Software Artifact Management Systems using Information Retrieval Methods [25] Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods [27] Design Traceability [31] Automating Requirements Traceability: Beyond the Record and Replay Paradigm [38] Extended Requirements Traceability: Results of an Industrial Case Study [39] Crafting the Requirements Record with the Informed use of Media [40] From Non-Functional Requirements to Design Through Patterns [42] TRAM: A Tool for Requirements and Architecture Management [44] Improving Requirements Tracing via Information Retrieval [45] Improving After-the-Fact Tracing and Mapping: Supporting Software Quality Predictions [46] REquirements TRacing On Target (RETRO): Improving Software Maintenance Through Traceability Recovery [47] A Case Study on Value-Based Requirements Tracing [51] Requirements Tracing [52] XTraQue: Traceability for Product Line Systems [53] Modeling Functional Requirements to Support Traceability Analysis [54] A Reusable Traceability Framework Using Patterns [56] Reconstructing Requirements Coverage Views from Design and Test Using Traceability Recovery via LSI [58] Recovery of Traceability Links Between Software Documentation and Source Code [59] Using Scenarios to Support Traceability [60] Enhancing Traceability Using Ontologies [61] Tool Support for Computer-Aided Requirements Traceability in Architectural Design: The Case of DesignTrack [62] Towards Method-Driven Trace Capture [28] Experiences Using Scenarios to Enhance Traceability [63] Factors In°uencing Requirements Traceability Practice [65] Requirements Traceability: Theory and Practice [64] Toward Reference Models for Requirements Traceability [66] Pre-Requirement Speci¯cation Traceability: Bridging the Complexity Gap Through Capabilities [68] An Evaluation of Traceability Approaches to Support Software Evolution [69] Im...…”

Section: Refmentioning

confidence: 99%

Requirements Traceability: A Systematic Review and Industry Case Study

Torkar

Gorschek

Feldt

et al. 2012

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

Requirements traceability enables software engineers to trace a requirement from its emergence to its ful¯llment. In this paper we examine requirements traceability de¯nitions, challenges, tools and techniques, by the use of a systematic review performing an exhaustive search through the years 1997À2007. We present a number of common de¯nitions, challenges, available tools and techniques (presenting empirical evidence when found), while complementing the results and analysis with a static validation in industry through a series of interviews.

show abstract

Using scenarios to support traceability

Cited by 24 publications

References 8 publications

A survey of traceability in requirements engineering and model-driven development

A survey of traceability in requirements engineering and model-driven development

An Effective Verification Strategy for Testing Distributed Automotive Embedded Software Functions: A Case Study

Requirements Traceability: A Systematic Review and Industry Case Study

Contact Info

Product

Resources

About