PUMA

academical publication management
collect, organize, and share publications

( en | de )

 

Disambiguation of "Alspaugh, Thomas A."

Author of the publication

copydeleteadd this publication to your clipboard
Scenarios, state machines and purpose-driven testing.

, , and . ACM SIGSOFT Software Engineering Notes, 30 (4): 1-5 (2005)

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.

A. Laukemann

A. Laukemann

A. Laukemann

A. Vo{\ss}

A. Afkari

 

Other publications of authors with the same name

Intellectual Property Rights Requirements for Heterogeneously-Licensed Systems., , and . RE, page 24-33. IEEE Computer Society, (2009)The Role of Policy and Stakeholder Privacy Values in Requirements Engineering., , , and . RE, page 138-145. IEEE Computer Society, (2001)Getting the whole story: an experience report on analyzing data elicited using the war stories procedure., and . Empirical Software Engineering, 16 (4): 460-486 (2011)Governance and accountability in the new data ecology., and . RELAW, page 5-14. IEEE Computer Society, (2011)Architecture-based testing using goals and plans., , , and . ROSATEA, page 64-68. ACM, (2006)Using scenarios to support traceability., , , and . TEFSE@ASE, page 25-30. ACM, (2005)SMaRT - Scenario Management and Requirements Tool., , and . RE, page 351. IEEE Computer Society, (2003)Marginal Notes on Amethodical Requirements Engineering: What Experts Learned from Experience., , and . RE, page 105-114. IEEE Computer Society, (2008)An architectural pattern for non-functional dependability requirements., , , and . Journal of Systems and Software, 79 (10): 1370-1378 (2006)Securing Software Ecosystem Architectures: Challenges and Opportunities., and . IEEE Software, 36 (3): 33-38 (2019)