Author of the publication

Can Knowledge of Technical Debt Help Identify Software Vulnerabilities?

, , , , and . CSET @ USENIX Security Symposium, USENIX Association, (2016)

Please choose a person to relate this publication to

To differ between persons with the same name, the academic degree and the title of an important publication will be displayed. You can also use the button next to the name to display some publications already assigned to the person.

 

Other publications of authors with the same name

Planning realistic schedules using software architecture (tutorial session)., , and . ICSE, page 824. ACM, (2000)Understanding the Context of Architecture Evaluation Methods., and . WICSA/ECSA, page 277-281. IEEE, (2012)System and software architecture track third IEEE International Conference on Engineering of Complex Computer Systems (ICECCS'97).. ACM SIGSOFT Softw. Eng. Notes, 22 (2): 5 (1997)The Ergo Attribute System., and . Software Development Environments (SDE), page 110-120. ACM, (1988)Managing technical debt in software-reliant systems., , , , , , , , , and 4 other author(s). FoSER, page 47-52. ACM, (2010)Industry's Cry for Tools that Support Large-Scale Refactoring., , , , , and . ICSE (SEIP), page 163-164. IEEE, (2022)Elaboration on an integrated architecture and requirement practice: Prototyping with quality attribute focus., , and . TwinPeaks@ICSE, page 8-13. IEEE Computer Society, (2013)Architecting with just enough information., , and . SHARK@ICSE, page 9-12. ACM, (2011)Architectural dependency analysis to understand rework costs for safety-critical systems., , , and . ICSE Companion, page 185-194. ACM, (2014)Missed Architectural Dependencies: The Elephant in the Room., , , , , and . WICSA, page 41-50. IEEE Computer Society, (2016)