James A. Whittaker

	2006
24		James A. Whittaker, Richard Ford: How to Think about Security. IEEE Security & Privacy 4(2): 68-71 (2006)
	2004
23		Mike Andrews, James A. Whittaker: Computer Security. IEEE Security & Privacy 2(5): 68-71 (2004)
22		Ahmed M. Salem, Kamel Rekab, James A. Whittaker: Prediction of software failures through logistic regression. Information & Software Technology 46(12): 781-789 (2004)
21		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)
	2003
20		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
19		James A. Whittaker, Herbert H. Thompson: Black Box Debugging. ACM Queue 1(9): 68-74 (2003)
18		Martin R. Stytz, James A. Whittaker: Software Protection: Security's Last Stand? IEEE Security & Privacy 1(1): 95-98 (2003)
17		James A. Whittaker: Why Secure Applications are Difficult to Write. IEEE Security & Privacy 1(2): 81-83 (2003)
16		Martin R. Stytz, James A. Whittaker: Caution: This Product Contains Security Code. IEEE Security & Privacy 1(5): 86-88 (2003)
15		Daniel E. Geer Jr., David Aucsmith, James A. Whittaker: Monoculture. IEEE Security & Privacy 1(6): 14-19 (2003)
	2002
14		Giampaolo Bella, Ronaldo Menezes, James A. Whittaker: Editorial Message: special track on computer security. SAC 2002: 194-195
13		James A. Whittaker, Andres De Vivanco: Neutralizing windows-based malicious mobile code. SAC 2002: 242-246
12		Herbert H. Thompson, James A. Whittaker, Florence E. Mottay: Software security vulnerability testing in hostile environments. SAC 2002: 260-264
11		Anup K. Ghosh, Chuck Howell, James A. Whittaker: Building Software Securely from the Ground Up. IEEE Software 19(1): 14-16 (2002)
10		James A. Whittaker, Steven Atkin: Software Engineering is Not Enough. IEEE Software 19(4): 108-115 (2002)
	2001
9		Matt Bishop, Anup K. Ghosh, James A. Whittaker: How Useful is Software Fault Injection for Evaluating the Security of COTS Products? ACSAC 2001: 339-342
8		James A. Whittaker: Software's Invisible Users. IEEE Software 18(3): (2001)
	2000
7		James A. Whittaker, Jeffrey M. Voas: Toward a More Reliable Theory of Software Reliability. IEEE Computer 33(12): 36-42 (2000)
6		James A. Whittaker: What Is Software Testing? Why Is It So Hard? Practice Tutorial. IEEE Software 17(1): (2000)
5		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)
4		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)
	1997
3		James A. Whittaker: Stochastic Software Testing. Ann. Software Eng. 4: 115-131 (1997)
	1994
2		James A. Whittaker, Michael G. Thomason: A Markov Chain Model for Statistical Software Testing. IEEE Trans. Software Eng. 20(10): 812-824 (1994)
	1993
1		James A. Whittaker, Jesse H. Poore: Markow Analysis of Software Specifications. ACM Trans. Softw. Eng. Methodol. 2(1): 93-106 (1993)

Coauthor Index

1	Mike Andrews	[23]
2	Steven Atkin	[10]
3	David Aucsmith	[15]
4	Giampaolo Bella	[14]
5	Matt Bishop	[9]
6	Chia-Chu Chiang	[20] [21]
7	Ibrahim K. El-Far	[20] [21]
8	Richard Ford	[24]
9	Daniel E. Geer Jr.	[15]
10	Anup K. Ghosh	[9] [11]
11	Stefan Gruner	[20] [21]
12	Charles Howell (Chuck Howell)	[11]
13	Ronaldo Menezes	[14]
14	Markus Montigel	[20] [21]
15	Florence E. Mottay	[12]
16	Jesse H. Poore	[1] [5]
17	Kamel Rekab	[4] [22]
18	Ahmed M. Salem	[22]
19	Martin R. Stytz	[16] [18]
20	Michael G. Thomason	[2] [4]
21	Herbert H. Thompson	[12] [19] [20] [21]
22	Andres De Vivanco	[13]
23	Jeffrey M. Voas	[7]
24	Gwendolyn H. Walton	[5]

Colors in the list of coauthors