 | 2009 |
|---|
| 58 |       | Norman F. Schneidewind,
Mike Hinchey:
A consumer/producer approach to risk-driven software reliability and testing.
SAC 2009: 537-538 |
| 57 | | Norman F. Schneidewind:
Integrating testing with reliability.
Softw. Test., Verif. Reliab. 19(3): 175-198 (2009) |
| 2008 |
|---|
| 56 | | Norman F. Schneidewind,
Mike Hinchey:
Why Predicting Outliers in Software is a Good Thing to Do!
ICECCS 2008: 91-97 |
| 55 | | Michael G. Hinchey,
Karama Kanoun,
Mikael Lindvall,
Michael R. Lyu,
Tiziana Margaria,
Veena B. Mendiratta,
Paul Pettersson,
Norman F. Schneidewind,
W. Eric Wong:
Anything You Want to Ask about Software Reliability Engineering.
ISSRE 2008: 6 |
| 2007 |
|---|
| 54 | | Norman F. Schneidewind:
A New Way to Predict Software Reliability with Parameter Evaluation: Shuttle Applications.
SEW 2007: 167-178 |
| 53 | | Norman F. Schneidewind:
A Quantitative Approach to Software Development Using IEEE 982.1.
IEEE Software 24(1): 65-72 (2007) |
| 52 | | Norman F. Schneidewind:
Predicting shuttle software reliability with parameter evaluation.
ISSE 3(3): 181-191 (2007) |
| 51 | | Norman F. Schneidewind:
Finding the optimal parameters for a software reliability model.
ISSE 3(4): 319-332 (2007) |
| 50 | | Norman F. Schneidewind:
Experience report on using object-oriented design for software maintenance.
Journal of Software Maintenance 19(3): 183-201 (2007) |
| 2006 |
|---|
| 49 | | Norman F. Schneidewind:
Reliability - Security Model.
ICECCS 2006: 279-288 |
| 48 | | Norman F. Schneidewind:
Allocation and analysis of reliability: multiple levels: system, subsystem, and module.
ISSE 2(3-4): 121-136 (2006) |
| 47 | | Norman F. Schneidewind:
Software reliability engineering process.
ISSE 2(3-4): 179-190 (2006) |
| 2005 |
|---|
| 46 | | Norman F. Schneidewind:
Predicting Risk as a Function of Risk Factors.
SEW 2005: 131-141 |
| 45 |  | Norman F. Schneidewind:
Software Requirements Risk and Maintainability.
Encyclopedia of Information Science and Technology (V) 2005: 2562-2566 |
| 44 | | Norman F. Schneidewind:
Predicting risk as a function of risk factors.
ISSE 1(1): 63-70 (2005) |
| 2004 |
|---|
| 43 | | Norman F. Schneidewind:
Assessing Reliability Risk Using Fault Correction Profiles.
HASE 2004: 139-148 |
| 2003 |
|---|
| 42 | | Norman F. Schneidewind:
Fault Correction Profiles.
ISSRE 2003: 257-270 |
| 41 | | Norman F. Schneidewind:
Applying Fault Correction Profiles.
SEW 2003: 185 |
| 2002 |
|---|
| 40 | | Norman F. Schneidewind:
An Integrated Failure Detection and Fault Correction Model.
ICSM 2002: 238-241 |
| 39 | | Norman F. Schneidewind:
Panel Introduction.
ICSM 2002: 470 |
| 38 | | Norman F. Schneidewind:
Body of Knowledge for Software Quality Measurement.
IEEE Computer 35(2): 77-83 (2002) |
| 2001 |
|---|
| 37 | | Norman F. Schneidewind:
Investigation of the Risk to Software Reliability and Maintainability of Requirements Changes.
ICSM 2001: 127- |
| 36 | | Norman F. Schneidewind:
Investigation of Logistic Regression as a Discriminant of Software Quality.
IEEE METRICS 2001: 328-337 |
| 35 | | Norman F. Schneidewind:
Modelling the Fault Correction Process.
ISSRE 2001: 185-191 |
| 34 | | Norman F. Schneidewind:
Maintenance Process and Product Evaluation Using Reliability, Risk, and Test Metrics.
Advances in Computers 54: 154-183 (2001) |
| 33 | | Norman F. Schneidewind:
Knowledge Requirements for Software Quality Measurement.
Empirical Software Engineering 6(3): 201-205 (2001) |
| 2000 |
|---|
| 32 | | Norman F. Schneidewind:
On the Repeatability of Metric Models and Metrics across Software Builds.
ISSRE 2000: 234-245 |
| 31 | | Norman F. Schneidewind:
Software quality control and prediction model for maintenance.
Ann. Software Eng. 9: 79-101 (2000) |
| 1999 |
|---|
| 30 | | Norman F. Schneidewind:
Cost Framework for COTS Evaluation.
COMPSAC 1999: 100- |
| 29 | | Norman F. Schneidewind:
Software Quality Maintenance Model.
ICSM 1999: 277-286 |
| 28 | | Norman F. Schneidewind,
Wendell D. Jones,
Taghi M. Khoshgoftaar,
Paul W. Oman,
George E. Stark:
Can Metrics and Models be Applied Across Multiple Releases or Projects?
IEEE METRICS 1999: 324- |
| 27 | | Norman F. Schneidewind:
Measuring and Evaluating Maintenance Process Using Reliability, Risk, and Test Metrics.
IEEE Trans. Software Eng. 25(6): 769-781 (1999) |
| 26 | | Barbara A. Kitchenham,
Guilherme Horta Travassos,
Anneliese von Mayrhauser,
Frank Niessink,
Norman F. Schneidewind,
Janice Singer,
Shingo Takada,
Risto Vehvilainen,
Hongji Yang:
Towards an ontology of software maintenance.
Journal of Software Maintenance 11(6): 365-389 (1999) |
| 1998 |
|---|
| 25 | | Jeffrey M. Voas,
M. M. Lehman,
Lionel C. Briand,
Norman F. Schneidewind:
Maintaining COTS-Based Systems: Is it Possible? (Panel).
ICSM 1998: 220-221 |
| 24 | | Norman F. Schneidewind:
Methods for Assessing COTS Reliability, Maintainability, and Availability.
ICSM 1998: 224- |
| 23 | | Norman F. Schneidewind:
An Integrated Process and Product Model.
IEEE METRICS 1998: 224-234 |
| 22 | | Lionel C. Briand,
Filippo Lanubile,
Shari Lawrence Pfleeger,
Gregg Rothermel,
Norman F. Schneidewind:
Empirical Studies of Software Maintenance: A Report from WESS `97.
Empirical Software Engineering 3(3): 299-307 (1998) |
| 21 | | Norman F. Schneidewind,
Christof Ebert:
Guest Editors' Introduction: Preserve or Redesign Legacy Systems?
IEEE Software 15(4): 14-17 (1998) |
| 20 | | Norman F. Schneidewind:
How To Evaluate Legacy System Maintenance.
IEEE Software 15(4): 34-42 (1998) |
| 1997 |
|---|
| 19 | | Norman F. Schneidewind:
Measuring and evaluating maintenance process using reliability, risk, and test metrics.
ICSM 1997: 232- |
| 18 | | Norman F. Schneidewind:
Software Metrics Model For Quality Control.
IEEE METRICS 1997: 127-136 |
| 17 | | Norman F. Schneidewind:
Nasa Shuttle Software Maintenance Evolution.
Empirical Software Engineering 2(2): 192-196 (1997) |
| 1996 |
|---|
| 16 | | Norman F. Schneidewind:
Reliability Modeling for Safety Critical Software.
Ada-Europe 1996: 17-37 |
| 15 | | Norman F. Schneidewind:
Reliability and Risk Analysis for Software that Must be Safe.
IEEE METRICS 1996: 142- |
| 14 | | Norman F. Schneidewind,
Norman E. Fenton:
Point-Counterpoint: Do Standards Improve Quality?
IEEE Software 13(1): 22, 24 (1996) |
| 1995 |
|---|
| 13 | | Norman F. Schneidewind:
Predictions for increasing confidence in the reliability of safety critical software.
ICECCS 1995: 104-107 |
| 12 | | Norman F. Schneidewind:
Software Metrics Validation: Space Shuttle flight Software Example.
Ann. Software Eng. 1: 287-309 (1995) |
| 1994 |
|---|
| 11 | | Norman F. Schneidewind:
Validating Metrics for Ensuring Space Shuttle Flight Software Quality.
IEEE Computer 27(8): 50-57 (1994) |
| 1993 |
|---|
| 10 | | Norman F. Schneidewind:
Report on the IEEE Standard for a Software Quality Memcs Methodology.
ICSM 1993: 104-106 |
| 9 | | Norman F. Schneidewind:
Software Reliability Model with Optimal Selection of Failure Data.
IEEE Trans. Software Eng. 19(11): 1095-1104 (1993) |
| 1992 |
|---|
| 8 | | Norman F. Schneidewind:
Experimental Designs for Validating Metrics and Applying them across Multiple Projects.
Experimental Software Engineering Issues 1992: 216-220 |
| 7 | | Norman F. Schneidewind,
Ted W. Keller:
Applying Reliability Models to the Space Shuttle.
IEEE Software 9(4): 28-33 (1992) |
| 6 | | Norman F. Schneidewind:
Methodology For Validating Software Metrics.
IEEE Trans. Software Eng. 18(5): 410-422 (1992) |
| 1989 |
|---|
| 5 | | Norman F. Schneidewind:
Distributed System Software Design Paradigm with Application to Computer Networks.
IEEE Trans. Software Eng. 15(4): 402-412 (1989) |
| 1987 |
|---|
| 4 | | Norman F. Schneidewind:
The State of Software Maintenance.
IEEE Trans. Software Eng. 13(3): 303-310 (1987) |
| 1986 |
|---|
| 3 | | Raghu Singh,
Norman F. Schneidewind:
Concept of a Software Quality Metrics Standard.
COMPCON 1986: 362-369 |
| 1984 |
|---|
| 2 | | Robert S. Arnold,
Norman F. Schneidewind,
Nicholas Zvegintzov:
A Software Maintenance Workshop.
Commun. ACM 27(11): 1120-1121 (1984) |
| 1979 |
|---|
| 1 | | Norman F. Schneidewind,
Heinz-Michael Hoffmann:
An Experiment in Software Error Data Collection and Analysis.
IEEE Trans. Software Eng. 5(3): 276-286 (1979) |
