TY - GEN
T1 - Trace Matrix analyzer (TMA)
AU - Li, Wenbin
AU - Hayes, Jane Huffman
AU - Yang, Fan
AU - Imai, Ken
AU - Yannelli, Jesse
AU - Cames, Chase
AU - Doyle, Maureen
PY - 2013
Y1 - 2013
N2 - A Trace Matrix (TM) represents the relationship between software engineering artifacts and is foundational for many software assurance techniques such as criticality analysis. In a large project, a TM might represent the relationships between thousands of elements of dozens of artifacts (for example, between design elements and code elements, between requirements and test cases). In mission- and safety-critical systems, a third party agent may be given the job to assess a TM prepared by the developer. Due to the size and complexity of the task, automated techniques are needed. We have developed a technique for analyzing a TM called Trace Matrix Analyzer (TMA), so that third party agents can perform their work faster and more effectively. To validate, we applied TMA to two TMs with known problems and golden answersets: MoonLander and MODIS. We also asked an experienced software engineer to manually review the TM We found that TMA properly identified TM issues and was much faster than manual review, but also falsely identified issues for one dataset. This work addresses the Trusted Grand Challenge, research projects 3, 5, and 6. Index Terms-Formal Specification, Temporal Requirements, Translation, Requirement Comprehension, Trusted Grand Challenge, Research Projects 3, 5, and 6.
AB - A Trace Matrix (TM) represents the relationship between software engineering artifacts and is foundational for many software assurance techniques such as criticality analysis. In a large project, a TM might represent the relationships between thousands of elements of dozens of artifacts (for example, between design elements and code elements, between requirements and test cases). In mission- and safety-critical systems, a third party agent may be given the job to assess a TM prepared by the developer. Due to the size and complexity of the task, automated techniques are needed. We have developed a technique for analyzing a TM called Trace Matrix Analyzer (TMA), so that third party agents can perform their work faster and more effectively. To validate, we applied TMA to two TMs with known problems and golden answersets: MoonLander and MODIS. We also asked an experienced software engineer to manually review the TM We found that TMA properly identified TM issues and was much faster than manual review, but also falsely identified issues for one dataset. This work addresses the Trusted Grand Challenge, research projects 3, 5, and 6. Index Terms-Formal Specification, Temporal Requirements, Translation, Requirement Comprehension, Trusted Grand Challenge, Research Projects 3, 5, and 6.
UR - https://www.scopus.com/pages/publications/84888632913
UR - https://www.scopus.com/pages/publications/84888632913#tab=citedBy
U2 - 10.1109/TEFSE.2013.6620153
DO - 10.1109/TEFSE.2013.6620153
M3 - Conference contribution
AN - SCOPUS:84888632913
SN - 9781479904952
T3 - 2013 7th International Workshop on Traceability in Emerging Forms of Software Engineering, TEFSE 2013 - Proceedings
SP - 44
EP - 50
BT - 2013 7th International Workshop on Traceability in Emerging Forms of Software Engineering, TEFSE 2013 - Proceedings
T2 - 2013 7th International Workshop on Traceability in Emerging Forms of Software Engineering, TEFSE 2013
Y2 - 19 May 2013 through 19 May 2013
ER -