| 2012 | ||
|---|---|---|
| j20 | ||
| 2010 | ||
| c6 | ||
| 2006 | ||
| j19 | James A. Whittaker, Richard Ford: How to Think about Security. IEEE Security & Privacy 4(2): 68-71 (2006) | |
| 2004 | ||
| j18 | ||
| j17 | Herbert H. Thompson, Chia-Chu Chiang, Ibrahim K. El-Far, Stefan Gruner, Markus Montigel, James A. Whittaker: Special Issue on Software Engineering: Applications, Practices and Tools from the ACM Symposium on Applied Computing 2003. Information & Software Technology 46(5): 279-280 (2004) | |
| j16 | Ahmed M. Salem, Kamel Rekab, James A. Whittaker: Prediction of software failures through logistic regression. Information & Software Technology 46(12): 781-789 (2004) | |
| 2003 | ||
| j15 | Martin R. Stytz, James A. Whittaker: Software Protection: Security's Last Stand? IEEE Security & Privacy 1(1): 95-98 (2003) | |
| j14 | James A. Whittaker: Why Secure Applications are Difficult to Write. IEEE Security & Privacy 1(2): 81-83 (2003) | |
| j13 | Martin R. Stytz, James A. Whittaker: Caution: This Product Contains Security Code. IEEE Security & Privacy 1(5): 86-88 (2003) | |
| j12 | Daniel E. Geer Jr., David Aucsmith, James A. Whittaker: Monoculture. IEEE Security & Privacy 1(6): 14-19 (2003) | |
| j11 | ||
| c5 | Herbert H. Thompson, Chia-Chu Chiang, Ibrahim K. El-Far, Stefan Gruner, Markus Montigel, James A. Whittaker: Software Engineering Track Editorial. SAC 2003: 1076-1077 | |
| 2002 | ||
| j10 | Anup K. Ghosh, Chuck Howell, James A. Whittaker: Building Software Securely from the Ground Up. IEEE Software 19(1): 14-16 (2002) | |
| j9 | James A. Whittaker, Steven Atkin: Software Engineering is Not Enough. IEEE Software 19(4): 108-115 (2002) | |
| c4 | Giampaolo Bella, Ronaldo Menezes, James A. Whittaker: Editorial Message: special track on computer security. SAC 2002: 194-195 | |
| c3 | James A. Whittaker, Andres De Vivanco: Neutralizing windows-based malicious mobile code. SAC 2002: 242-246 | |
| c2 | Herbert H. Thompson, James A. Whittaker, Florence E. Mottay: Software security vulnerability testing in hostile environments. SAC 2002: 260-264 | |
| 2001 | ||
| j8 | ||
| c1 | Matt Bishop, Anup K. Ghosh, James A. Whittaker: How Useful is Software Fault Injection for Evaluating the Security of COTS Products? ACSAC 2001: 339-340 | |
| 2000 | ||
| j7 | James A. Whittaker, Jeffrey M. Voas: Toward a More Reliable Theory of Software Reliability. IEEE Computer 33(12): 36-42 (2000) | |
| j6 | Jesse H. Poore, Gwendolyn H. Walton, James A. Whittaker: A constraint-based approach to the representation of software usage models. Information & Software Technology 42(12): 825-833 (2000) | |
| j5 | James A. Whittaker, Kamel Rekab, Michael G. Thomason: A Markov chain model for predicting the reliability of multi-build software. Information & Software Technology 42(12): 889-894 (2000) | |
| j4 | James A. Whittaker: What Is Software Testing? Why Is It So Hard? Practice Tutorial. IEEE Software 17(1): 70-79 (2000) | |
| 1997 | ||
| j3 | ||
| 1994 | ||
| j2 | James A. Whittaker, Michael G. Thomason: A Markov Chain Model for Statistical Software Testing. IEEE Trans. Software Eng. 20(10): 812-824 (1994) | |
| 1993 | ||
| j1 | James A. Whittaker, Jesse H. Poore: Markow Analysis of Software Specifications. ACM Trans. Softw. Eng. Methodol. 2(1): 93-106 (1993) | |
Colors in the list of coauthors
Last update Sun May 26 01:24:31 2013 CET by the DBLP Team —
Data released under the ODC-BY 1.0 license — See also our legal information page