A tactic-centric approach for automating traceability of quality concerns

@article{Mirakhorli2012ATA,
  title={A tactic-centric approach for automating traceability of quality concerns},
  author={Mehdi Mirakhorli and Yonghee Shin and Jane Cleland-Huang and Murat Çinar},
  journal={2012 34th International Conference on Software Engineering (ICSE)},
  year={2012},
  pages={639-649}
}
The software architectures of business, mission, or safety critical systems must be carefully designed to balance an exacting set of quality concerns describing characteristics such as security, reliability, and performance. Unfortunately, software architectures tend to degrade over time as maintainers modify the system without understanding the underlying architectural decisions. Although this problem can be mitigated by manually tracing architectural decisions into the code, the cost and… 
Detecting, Tracing, and Monitoring Architectural Tactics in Code
TLDR
A machine learning approach for discovering and visualizing architectural tactics in code, mapping these code segments to tactic traceability patterns, and monitoring sensitive areas of the code for modification events in order to provide users with up-to-date information about underlying architectural concerns is presented.
BUDGET: A Tool for Supporting Software Architecture Traceability Research
TLDR
This tool demo presents a Web-based tool named BUDGET, as a solution to automate creation of training data for the problem of tracing architectural concerns, which uses Automated Web-Mining, and Big-Data Analysis techniques to generateTraining data for supervised architecture-traceability techniques.
Can Clustering Improve Requirements Traceability? A Tracelab-enabled Study
TLDR
The three key contributions are a machine learning component package for TraceLab featuring six classifier algorithms, five clustering algorithms, and a total of over 40 components for creating TraceLab experiments, built upon the WEKA machine learning package, as well as implementing methods outside of WEKA.
Preventing erosion of architectural tactics through their strategic implementation, preservation, and visualization
  • M. Mirakhorli
  • Computer Science
    2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE)
  • 2013
TLDR
This work presents a novel traceability approach for automating the construction of traceabilty links for architectural tactics and utilizing those links to implement a change impact analysis infrastructure to mitigate the problem of architecture degradation.
Towards Automated Evidence Generation for Rapid and Continuous Software Certification
TLDR
SHERLOCK is described, an integrated environment to facilitate the rapid and continuous certification of software systems using the novel concept of Traceability Certification Models (TCM) and a Catalog of Certification Assurance Case Patterns (CACP) which guides the efforts of establishing the required trace links for fulfilling the criteria for a given certification.
Archie: a tool for detecting, monitoring, and preserving architecturally significant code
TLDR
Eclipse plug-in named Archie is presented as a solution for maintaining architectural qualities in the design and code despite long-term maintenance and evolution activities and to keep developers informed of underlying design decisions and their associated rationales.
Towards a pattern language for construction and maintenance of software architecture traceability links
TLDR
The nature of the software architecture traceability phenomenon and its driving factors and impacts are studied, as well as the methods that provide the means to control software Architecture traceability, and a pattern language for construction and maintenance is presented.
Automated training-set creation for software architecture traceability problem
TLDR
The results indicate that automated techniques can create a reliable training set for the problem of tracing architectural tactics and investigate the impact of training set size on the accuracy of recovering trace links.
Trace links explained: An automated approach for generating rationales
TLDR
This RE:Next! paper proposes a novel approach for utilizing domain-specific knowledge bases to generate trace link rationales taken from the domain of Communication and Control of a Transportation system, and from a Medical Infusion pump domain.
Preserving the Quality of Architectural Tactics in Source Code
TLDR
A novel approach that utilizes machine learning techniques to recover and preserve the relationships between architecturally significant requirements, architectural decisions and their realizations in the implemented code to advance research and development of secure software systems is presented.
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 36 REFERENCES
Using tactic traceability information models to reduce the risk of architectural degradation during system maintenance
TLDR
The use of tTIMs significantly reduces the effort needed to create and maintain traceability links, provides support for visualizing the rationale behind various architectural components, and delivers timely information to maintainers so that they can preserve critical architectural qualities while implementing modifications.
A pattern system for tracing architectural concerns
TLDR
The patterns described in this paper emerged from the experiences and observations of tracing architectural concerns in safety critical systems and present six trace creation patterns describing techniques and supporting structures for creating architecturally significant traceability links.
Determining the cost-quality trade-off for automated software traceability
TLDR
The cost-quality trade-off of automated trace generation with the Trace Analyzer approach is reported and its expected impact onto several applications that consume its trace information is discussed and simple techniques to predict and manipulate the cost-benefit trade-offs with threshold-based filtering are explored.
Tracing architectural concerns in high assurance systems: (NIER track)
TLDR
The approach, which is informed through an extensive investigation of architectural decisions made in real-world safety-critical and performance-critical applications, provides enhanced support for advanced software engineering tasks.
Recovering and using use-case-diagram-to-source-code traceability links
TLDR
The results demonstrate that modest programmer effort to create TLs together with automated program mining and analysis is a promising approach than can increase program understanding while reducing programmer burden.
Object-oriented design patterns recovery
A heterogeneous solution for improving the return on investment of requirements traceability
This work describes a best-of-breed approach to traceability, in which the return-on-investment of the requirements traceability effort is maximized through the strategic deployment of a
A machine learning approach for tracing regulatory codes to product specific requirements
TLDR
This paper introduces and evaluates two machine-learning methods, designed to improve the quality of traces generated between regulatory codes and product level requirements, which were evaluated against security regulations from the USA government's Health Insurance Privacy and Portability Act.
Recovering Traceability Links between Code and Documentation
TLDR
A probabilistic and a vector space information retrieval model is applied in two case studies to trace C++ source code onto manual pages and Java code to functional requirements to recover traceability links between source code and free text documents.
Tool Support for Architectural Decisions
TLDR
An approach is outlined that systematically and semi-automatically documents architectural decisions and allows them to be effectively shared by the stakeholders and is demonstrated with an example demonstrating its usefulness with regards to some industrial use cases.
...
1
2
3
4
...