dblp.uni-trier.dewww.uni-trier.de

Jeffrey M. Voas

List of publications from the DBLP Bibliography Server - FAQ
Coauthor Index - Ask others: ACM DL/Guide - CiteSeer - CSB - Google - MSN - Yahoo

2008
82EEJeffrey M. Voas: Software Product Certification. Wiley Encyclopedia of Computer Science and Engineering 2008
81EEJeffrey M. Voas, Phillip A. Laplante: Standards Confusion and Harmonization. IEEE Computer 40(7): 94-96 (2008)
2007
80EEJeffrey M. Voas, Keith W. Miller: One in a Baker's Dozen: Debugging Debugging. HASE 2007: 75-81
2006
79EEAnn Miller, John McLean, O. Sami Saydjari, Jeffrey M. Voas: COMPSAC Panel Session on Trustworthy Computing. COMPSAC (1) 2006: 31
78EEJeffrey M. Voas: Reliability and Fault Tolerance in Trust. COMPSAC (1) 2006: 35-36
77EEBrian A. Malloy, Nicholas A. Kraft, Jason O. Hallstrom, Jeffrey M. Voas: Improving the Predictable Assembly of Service-Oriented Architectures. IEEE Software 23(2): 12-15 (2006)
2004
76EEJia Zhang, Carl K. Chang, Jeffrey M. Voas: A Uniform Meta-Model for Mediating Formal Electronic Conferences. COMPSAC 2004: 376-383
75EEJeffrey M. Voas: Software Engineering's Role in Business. IEEE Software 21(5): 26-27 (2004)
74EEJeffrey M. Voas: Software's Secret Sauce: The "-ilities". IEEE Software 21(6): 14-15 (2004)
73EETerry Bollinger, Jeffrey M. Voas, Maarten Boasson: Persistent Software Attributes. IEEE Software 21(6): 16-18 (2004)
2003
72EEStephen S. Yau, Carl E. Landwehr, Jeffrey M. Voas, Thomas J. Weigert: Challenges and Recent Advances in Developing Trustworthy Software-Based Systems. COMPSAC 2003: 208-
71EEJeffrey M. Voas: Trusted Software's Holy Grail. HICSS 2003: 338
70 Jeffrey M. Voas: Adaptive Software Quality. ICEIS (1) 2003: 586-589
69EEJeffrey M. Voas: Guest Editor's Introduction: Assuring Software Quality Assurance. IEEE Software 20(3): 48-49 (2003)
68EEJeffrey M. Voas: Trusted Software's Holy Grail. Software Quality Journal 11(1): 9-17 (2003)
2001
67 Jeffrey M. Voas: Why Testing under Expected Operational Scenarios is Not Sufficient. HASE 2001: 5-
66 Allen P. Nikora, Raphael R. Some, Jeffrey M. Voas, Victor L. Winter, Jie Xu: Software Dependability in Distributed and Mobile Computing Environments. HASE 2001: 7-10
65EEJeffrey M. Voas: Discovering Unanticipated Software Output Modes. RE 2001: 277
64EEJeffrey M. Voas: Why Is It So Hard to Predict Software System Trustworthiness from Software Component Trustworthiness?. SRDS 2001: 179-
63 Jeffrey M. Voas: Discovering Unanticipated Software Output Modes. Ann. Software Eng. 11(1): 79-88 (2001)
62EEJeffrey M. Voas: Quality Time - Faster, Better, and Cheaper. IEEE Software 18(3): (2001)
61EEJeffrey M. Voas: Composing Software Component "ilities". IEEE Software 18(4): 16-17 (2001)
60EEJeffrey M. Voas: Guest Editor's Introduction: Software Fault Tolerance-Making Software Behave. IEEE Software 18(4): 18-19 (2001)
59EEJeffrey M. Voas: Fault Tolerance. IEEE Software 18(4): 54-57 (2001)
58 Jeffrey M. Voas: Why testing software under expected operational profiles is not sufficient. Software Focus 2(1): 13-14 (2001)
2000
57EEJeffrey M. Voas: Disposable COTS-Intensive Software Systems (A Position Statement). CSMR 2000: 239-241
56EEJeffrey M. Voas: Limited Software Warranties. ECBS 2000: 56-63
55 Colleen K. Vossler, Jeffrey M. Voas: Defective software: An overview of legal remedies and technical measures available to consumers. Advances in Computers 53: 452-498 (2000)
54EEJames A. Whittaker, Jeffrey M. Voas: Toward a More Reliable Theory of Software Reliability. IEEE Computer 33(12): 36-42 (2000)
53EEJeffrey M. Voas: Developing a Usage-Based Software Certification Process. IEEE Computer 33(8): 32-37 (2000)
52EEJeffrey M. Voas: Quality Time - A New Generation of Software Quality Conferences. IEEE Software 17(1): (2000)
51EEJeffrey M. Voas: Quality Time - Will the Real Operational Profile Please Stand Up? IEEE Software 17(2): (2000)
50EEJeffrey M. Voas, Nancy R. Mead: Malicious IT - Guest Editors' Introduction. IEEE Software 17(5): (2000)
49EEJeffrey M. Voas: Quality Time - Can Chaotic Methods Improve Software Quality Predictions? IEEE Software 17(5): (2000)
48EEJohn Viega, Jeffrey M. Voas: Quality Time - Can Aspect-Oriented Programming Lead to More Reliable Software? IEEE Software 17(6): (2000)
47EEJeffrey M. Voas, Jeffery E. Payne: Dependability certification of software components. Journal of Systems and Software 52(2-3): 165-172 (2000)
1999
46EEJeffrey M. Voas: Can Generic Software Be Assured? COMPSAC 1999: 94-95
45 Jeffrey M. Voas: User Participation-based Software Certification. EUROVAV 1999: 267-276
44EEJeffrey M. Voas: COTS and High Assurance: An Oxymoron? HASE 1999: 119-
43EEJeffrey M. Voas: A World Without Risks: Let Me Out! HASE 1999: 274-274
42EEAnup K. Ghosh, Jeffrey M. Voas: Inoculating Software for Survivability. Commun. ACM 42(7): 38-44 (1999)
41 Jeffrey M. Voas: The Future of Computer Assurance. IEEE Computer 32(1): 76-77 (1999)
40EEJeffrey M. Voas: Quality Time - Protecting Against What? The Achilles Heel of Information Assurance. IEEE Software 16(1): (1999)
39EEJeffrey M. Voas: Quality Time - Does Untested Software Threaten Infrastructures? IEEE Software 16(2): (1999)
38EEJeffrey M. Voas: Quality Time - A US Government-Regulated Software Industry. IEEE Software 16(3): (1999)
37EEJeffrey M. Voas: Guest Editor's Introduction: Certification-Reducing the Hidden Costs of Poor Quality. IEEE Software 16(4): 22-25 (1999)
36EEJeffrey M. Voas: Certifying Software for High-Assurance Environments. IEEE Software 16(4): 48-54 (1999)
35EEJeffrey M. Voas: Software Quality's Eight Greatest Myths. IEEE Software 16(5): 118-120 (1999)
34EEJeffrey M. Voas: Disposable information systems: the future of software maintenance? Journal of Software Maintenance 11(2): 143-150 (1999)
1998
33EEJeffrey M. Voas: Certifying High Assurance Software. COMPSAC 1998: 99-105
32EELora Kassab, Jeffrey M. Voas: Agent Trustworthiness. ECOOP Workshops 1998: 300
31EEJeffrey M. Voas: Are COTS Products and Component Packaging Killing Software Malleability? ICSM 1998: 156-
30EEJeffrey M. Voas, M. M. Lehman, Lionel C. Briand, Norman F. Schneidewind: Maintaining COTS-Based Systems: Is it Possible? (Panel). ICSM 1998: 220-221
29 Jeffrey M. Voas: The Challenges of Using COTS Software in Component-Based Development (Guest Editor's Introduction). IEEE Computer 31(6): 44-45 (1998)
28 Jeffrey M. Voas: Certifying Off-the-Shelf Software Components. IEEE Computer 31(6): 53-59 (1998)
27EEJeffrey M. Voas: COTS Software: The Economical Choice? IEEE Software 15(2): 16-19 (1998)
26EEJeffrey M. Voas: Maintaining Component-Based Systems. IEEE Software 15(4): 22-27 (1998)
1997
25EEJeffrey M. Voas: Building Software Recovery Assertions from a Fault Injection-based Propagation Analysis. COMPSAC 1997: 505-510
24 Christoph C. Michael, Jeffrey M. Voas: The Ability of Directed Tests to Predict Software Quality. Ann. Software Eng. 4: 31-64 (1997)
23 Jeffrey M. Voas: Fault Injection for the Masses. IEEE Computer 30(12): 129-130 (1997)
22 Jeffrey M. Voas, Gary McGraw, Lora Kassab, Larry Voas: A 'Crystal Ball' for Software Liability. IEEE Computer 30(6): 29-36 (1997)
21 Jeffrey M. Voas: Quality Time: How Assertions Can Increase Test Effectiveness. IEEE Software 14(2): 118-122 (1997)
20 Jeffrey M. Voas, Frank Charron, Gary McGraw, Keith W. Miller, Michael Friedman: Predicting How Badly ``Good'' Software Can Behave. IEEE Software 14(4): 73-83 (1997)
19 Jeffrey M. Voas: Quality Time: Can Clean Pipes Produce Dirty Water? IEEE Software 14(4): 93-95 (1997)
18EEJeffrey M. Voas: Software testability measurement for intelligent assertion placement. Software Quality Journal 6(4): 327-336 (1997)
1996
17EEJeffrey M. Voas, Keith W. Miller: The Avalanche Paradigm: An Experimental Software Programming Technique for Improving Fault-tolerance. ECBS 1996: 142-147
16EEJeffrey M. Voas, Frank Charron, Keith W. Miller: Investigating rare-event failure tolerance: reductions in future uncertainty. HASE 1996: 78-85
1995
15 Jeffrey M. Voas: Software Testability Measurement for Assertion Placement and Fault Localization. AADEBUG 1995: 133-144
14EETaghi M. Khoshgoftaar, Robert M. Szabo, Jeffrey M. Voas: Detecting program modules with low testability. ICSM 1995: 242-250
13EEJeffrey M. Voas, Jeffery E. Payne, R. Mills, John McManus: Software Testability: An Experiment in Measuring Simulation Reusability. SSR 1995: 247-255
12EEJeffrey M. Voas, Keith W. Miller: Software Testability: The New Verification. IEEE Software 12(3): 17-28 (1995)
1994
11EETimothy J. Shimeall, Michael Friedman, John Chilenski, Jeffrey M. Voas: Views on Software Testability (Panel Abstract). ISSTA 1994: 240
1993
10EERichard G. Hamlet, Jeffrey M. Voas: Faults on Its Sleeve: Amplifying Software Reliability Testing. ISSTA 1993: 89-98
9EEJeffrey M. Voas, Jeffery E. Payne, Frederick B. Cohen: A model for detecting the existence of software corruption in real time. Computers & Security 12(3): 275-283 (1993)
8EEJeffrey M. Voas, Jeffery E. Payne, Keith W. Miller: Designing programs that are less likely to hide faults. Journal of Systems and Software 20(1): 93-100 (1993)
7EEJeffrey M. Voas, Keith W. Miller: Semantic metrics for software testability. Journal of Systems and Software 20(3): 207-216 (1993)
6EELarry J. Morell, Jeffrey M. Voas: A framework for defining semantic metrics. Journal of Systems and Software 20(3): 245-251 (1993)
1992
5EEKeith W. Miller, Larry J. Morell, Robert E. Noonan, Stephen K. Park, David M. Nicol, Branson W. Murrill, Jeffrey M. Voas: Estimating the Probability of Failure When Testing Reveals No Failures. IEEE Trans. Software Eng. 18(1): 33-43 (1992)
4EEJeffrey M. Voas: PIE: A Dynamic Failure-Based Technique. IEEE Trans. Software Eng. 18(8): 717-727 (1992)
3 Jeffrey M. Voas, Keith W. Miller: The Revealing Power of a Test Case. Softw. Test., Verif. Reliab. 2(1): 25-42 (1992)
1991
2 Jeffrey M. Voas: A Dynamic Failure Model for Predicting the Impact that a Program Location has on the Program. ESEC 1991: 308-331
1 Jeffrey M. Voas, Larry J. Morell, Keith W. Miller: Predicting Where Faults Can Hide from Testing. IEEE Software 8(2): 41-48 (1991)

Coauthor Index

1Maarten Boasson [73]
2Terry Bollinger [73]
3Lionel C. Briand [30]
4Carl K. Chang [76]
5Frank Charron [16] [20]
6John Chilenski [11]
7Frederick B. Cohen [9]
8Michael Friedman [11] [20]
9Anup K. Ghosh [42]
10Jason O. Hallstrom [77]
11Richard G. Hamlet [10]
12Lora Kassab [22] [32]
13Taghi M. Khoshgoftaar [14]
14Nicholas A. Kraft [77]
15Carl E. Landwehr [72]
16Phillip A. Laplante [81]
17Meir M. Lehman (M. M. Lehman) [30]
18Brian A. Malloy [77]
19Gary McGraw [20] [22]
20John McLean [79]
21John McManus [13]
22Nancy R. Mead [50]
23Christoph C. Michael [24]
24Ann Miller [79]
25Keith W. Miller [1] [3] [5] [7] [8] [12] [16] [17] [20] [80]
26R. Mills [13]
27Larry J. Morell [1] [5] [6]
28Branson W. Murrill [5]
29David M. Nicol [5]
30Allen P. Nikora [66]
31Robert E. Noonan [5]
32Stephen K. Park [5]
33Jeffery E. Payne [8] [9] [13] [47]
34O. Sami Saydjari [79]
35Norman F. Schneidewind [30]
36Timothy J. Shimeall [11]
37Raphael R. Some [66]
38Robert M. Szabo [14]
39John Viega [48]
40Larry Voas [22]
41Colleen K. Vossler [55]
42Thomas J. Weigert [72]
43James A. Whittaker [54]
44Victor L. Winter [66]
45Jie Xu [66]
46Stephen S. Yau [72]
47Jia Zhang [76]

Colors in the list of coauthors

Copyright © Sun May 17 03:24:02 2009 by Michael Ley (ley@uni-trier.de)