Leesa Murray, Alena Griffths, Peter Lindsay, Paul Strooper  Home/Search
Context
Related
| uq.edu.au/techreports/tr0041.ps.gz Cached: PS.gz PS PDF This document uses CoBlitz to cache paper downloads. If your firewall is blocking outgoing connections to port 3125, you can use these links to download local copies.
Image Update HelpPS.gz PS PDF From: uq.edu.au/techreports/ (more) (Enter author homepages) |
Rate this article:      (best)Comment on this article |
Abstract: Requirements traceability is an enabling capability for verification and validation of software-based systems. This paper reports on the outcomes of an industrial pilot project investigating the costs and potential bene ts of adding requirements traceability to the development lifecycle of embedded software. The project forms part of an industry research collaboration which aims to increase integrity assurance for products containing embedded software. (Update)
Active bibliography (related documents): More All
0.8: A Pilot Project on Module Testing for Embedded Software - McDonald, Murray.. (2000) (Correct)
0.5: Improving Safety Management in Defence Acquisition - Atchison, Cant (1999) (Correct)
0.5: Trustworthy Refinement Through Intrusion-Aware Design - Ellison, Moore (2002) (Correct)
Similar documents based on text: More All
0.5: Factors Influencing Requirements Traceability Practice - Ramesh (1998) (Correct)
0.4: Supporting Fine-grained Traceability in Software Development.. - Lindsay, al. (1995) (Correct)
0.4: Inheritance and Specification-based Object-oriented.. - Murray, Carrington.. (1997) (Correct)
BibTeX entry: (Update)
@misc{ murray-requirements,
author = "Leesa Murray and Alena Griffths and Peter Lindsay and Paul Strooper",
title = "Requirements Traceability for Embedded Software --- an Industry Experience
Report",
url = "citeseer.ist.psu.edu/murray00requirements.html" }
Citations (may not include all citations):176 The TAME project: towards improvement-oriented software envi.. (context) - Basili, Rombach - 1988
71 Software Considerations in Airborne Systems and Equipment Ce.. (context) - Inc - 1992
22 Requirements Engineering - Processes and Techniques (context) - Kotonya, Sommerville - 1998
14 Requirements tracing (context) - Jarke - 1998
6 Functional Safety: Safety-Related Systems (context) - Commission - 1999
3 IEEE Standard for Software Test Documentation (context) - Society - 1983
2 Annals of Software Engineering (context) - Ramesh, Stubbs et al. - 1997
2 Document number: P00901G (context) - Group, Subset - 1995
2 of Defence. Def Stan 00-55: Requirements for Safety Related .. (context) - Ministry - 1997
1 Factors in uencing requirements traceability practice (context) - Ramesh - 1998
1 Application Layer (context) - Group - 1997
1 RequisitePro Installation Guide and User Manual (context) - Corporation - 1997
1 Certication Procedure Subset Level (context) - Group, Intelligent et al. - 1999
1 and metrics (context) - Rosenberg, Hammer et al. - 1998
1 Doing requirements right the rst time (context) - Hammer, Hu et al. - 1998
1 Requirements management using tables (context) - Petty - 1998
1 IEEE Guide to Software Requirements Specication (context) - Society - 1984
Documents on the same site (ftp://svrc.it.uq.edu.au/techreports/): More
An Empirical Study of Formal User-Interface Design - Hussey, al. (1997) (Correct)
The PRT User Manual - Version 1.03 - Carrington, Hayes, al. (1995) (Correct)
Software Visualisation in a Language Based Editor - Jones, Welsh (1997) (Correct)
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC