Author of the publication

Defining the Discipline of Secure Software Assurance: Initial Findings from the National Software Assurance Repository.

, , , and . HICSS, page 1-8. IEEE Computer Society, (2010)

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

Ensuring Cost Efficient and Secure Software through Student Case Studies in Risk and Requirements Prioritization., , and . HICSS, page 1-9. IEEE Computer Society, (2009)Threat Modeling the Cloud Computing, Mobile Device Toting, Consumerized Enterprise - an overview of considerations., , and . AMCIS, Association for Information Systems, (2011)Threat Modeling: Diving into the Deep End., , , and . IEEE Software, 25 (1): 28-34 (2008)Threat Modeling the Enterprise., , , and . AMCIS, page 133. Association for Information Systems, (2008)Teaching Security Requirements Engineering Using SQUARE., , and . REET, page 20-27. IEEE Computer Society, (2009)Supporting the Building and Analysis of an Infrastructure Portfolio Using UML Deployment Diagrams.. UML Satellite Activities, volume 3297 of Lecture Notes in Computer Science, page 105-117. Springer, (2004)A Study of the Impact on Students Understanding Cross Cultural Differences in Software Engineering Work., , , and . COMPSAC (1), page 644-645. IEEE Computer Society, (2009)Integrating Secure Software Assurance Content with SE2004 Recommendations., , , and . CSEE&T, page 59-66. IEEE Computer Society, (2008)A Comparison of the Software Assurance Common Body of Knowledge to Common Curricular Standards., , , and . CSEE&T, page 149-156. IEEE Computer Society, (2007)Defining the Discipline of Secure Software Assurance: Initial Findings from the National Software Assurance Repository., , , and . HICSS, page 1-8. IEEE Computer Society, (2010)