| Number | Date | Title | Description | Bib Tex Entry |
| 15 | June, 2007 | Evaluating the Effectiveness of Java Static Analysis Tools | 2007 International Conference on Embedded Systems and Applications (ESA 2007), Las Vegas, NV. | @INPROCEEDINGS{Schilling2007c, author = {Walter W. Schilling, Jr.
and Dr. Mansoor Alam}, title = {Evaluating the Effectiveness of Java Static Analysis Tools}, booktitle = {Proc. of The 2007 International Conference on Embedded Systems and Applications (ESA 2007)}, year = {2007}, address = {Las Vegas, NV}, owner = {wws}, abstract={Static analysis tools have been successfully used to aid in improving the reliability of embedded systems developed in the C and C++ programming languages. As embedded systems begin to be developed in the Java Programming language, it is important that Static Analysis tools be assessed for their effectiveness in discovering faults in Java source code. This article provides results on a controlled experiment using nine static analysis tools and the Java Programming language. The effectiveness of the tools at detecting faults is discussed, as is the correlation between the tools. The experiment shows that there is some overlap in fault detection between tools, but there also is an overlap between false positive detections as well. Overall, for the most effective results, it is recommended that multiple static analysis tools be used when analyzing a given software module.}, keywords = {Static Analysis, Fault Detection, Java, Programming}, } |
| 14 | May, 2007 | Measuring the Reliability of Existing Web Servers | 2007 IEEE International Electro/Information Technology Conference, May 2007, Chicago, IL.. | @INPROCEEDINGS{Schilling2007b, author = {Walter W. Schilling, Jr.
and Dr. Mansoor Alam}, title = {Measuring the Reliability of Existing Web Servers}, booktitle = {Proceedings of the 2007 IEEE International Electro/Information Technology Conference}, year = {2007}, address = {Chicago, IL}, organization = {IEEE Region IV}, owner = {wws}, abstract={As the usage of the Internet increases and more critical functions rely on the World Wide Web for operation, it is important that network researchers have current and accurateinformation from a real-world standpoint of the achieved reliability of the Internet. Anecdotal evidence suggests that web outages are a serious issue from a cost standpoint. However, there have been few mainstream studies showing the reliability of the existing web infrastructure. As the internet has changed, so to has its capabilities and its reliability. Yet, there have been few independent studies which have provided quantitative measurement of actual web reliability. This article provides results from a controlled experiment intended to measure the reliability of the existing web infrastructure.}, keywords = {Software Reliability, Internet Reliability, Web Server, World WIde Web}, } |
| 13 | April, 2007 | Relating Software Reliability to Execution Rates Using Bayesian Belief Networks | NASA / Ohio Space Grant Consortium 2006-2007 Annual Student Research Symposium Proceedings XV | @INPROCEEDINGS{Schilling2007, author = {Walter W. Schilling,
Jr.}, title = {Relating Software Reliability to Execution Rates Using Bayesian Belief Networks}, booktitle = {NASA / Ohio Space Grant Consortium 2006-2007 Annual Student Research Symposium Proceedings XV}, year = {2007}, address = {Cleveland, Ohio}, organization = {Ohio Space Grant Consortium}, owner = {wws}, keywords = {Software Reliability, Bayesian Belief Networks, Markov Models}, } |
| 12 | November, 2006 | Integrate static analysis into a software development process | Embedded Systems Design | @ARTICLE{Schilling2006d, author = {Walter W. Schilling, Jr. and Mansoor Alam}, title = {Integrate static analysis into a software development process}, journal = {Embedded Systems Design}, year = {2006}, volume = {19}, pages = {57-66}, number = {11}, month = {November}, abstract = {Software reliability is an increasing risk to overall system reliability. As systems have grown larger and more complex, functionality in mission- and safety-critical systems is more often exclusively controlled through software. This change, coupled with improving reliability in hardware modules, has shifted the root cause of systems failure from hardware to software. Static analysis is a technique that can improve the quality and reliability of embedded systems software. Integrating static-analysis tools and techniques into the development process can yield significant reductions in development testing and field failures. However, integrating static analysis into a development process can be a daunting, especially if a large amount of legacy code is used in the development projects.}, url = {http://www.embedded.com/shared/printableArticle.jhtml?articleID=193500830}, } |
| 11 | November, 2006 | The Software Static Analysis Reliability Toolkit | The 17th International Symposium on Software Reliability Engineering, November 7 - 10, 2006, Raleigh, NC | @INPROCEEDINGS{Schilling2006c, author = {Walter W. Schilling, Jr. and Dr. Mansoor Alam}, title = {The Software Static Analysis Reliability Toolkit}, booktitle = {ISSRE 2006: The 17th International Symposium on Software Reliability Engineering}, year = {2006}, month={November}, address = {Raleigh, NC}, organization = {IEEE Computer Society and IEEE Reliability Society}, abstract = {A software reliability model combining static analysis, Bayesian Belief Networks, and code coverage measurement is proposed to estimate the reliability of existing software. Static analysis is used to detect faults within the source code which may lead to failure. Code coverage is used to determine which paths within the source code are executed as well as how often they execute. Finally, a Bayesian Belief Network is then used to combine these parameters and estimate the resulting software reliability. In order to facilitate the usage of this model, the Software Static Analysis Reliability Toolkit (SoSART) tool is proposed. This tool serves as both a reliability modeling tool and a bug finding meta tool suitable for comparing the results of different static analysis tools. This article discusses the purpose for this tool as well as the toolset capabilities. }, keywords = {Static Analysis, Software Development Process, Best practices}, } |
| 10 | July, 2006 | Estimating Software Reliability with Static Analysis Techniques | 15th International Conference on Software Engineering and Data Engineering (SEDE-2006), Los Angeles, California, July 6-8, 2006 | @INPROCEEDINGS{Schilling2006b, title = {Estimating Software
Reliability with Static Analysis Technique}, booktitle = {Proceedings of the 15th International Conference on Software Engineering and Data Engineering (SEDE-2006)}, year = {2006}, address = {Los Angeles, California}, organization = {International Society for Computers and their Applications (ISCA)}, owner = {wws}, abstract={Software unreliability represents an increasing risk to overall system reliability. Market forces, including decreased time to market, reduced development team sizes, and other factors, have encouraged projects to reuse existing software as well as to purchase COTS software solutions. This has made the usage of the more than 200 existing software reliability models increasingly dicult. It is imperative that practical reliability modeling techniques be developed to address these issues. It is on this premise that an appropriate software reliability model combining static analysis of existing source code modules, limited testing with path capture, and Bayesian Belief Networks is presented. Static analysis is used to detect faults within the source code which may lead to failure. Code coverage is used to determine which paths within the source code are executed as well as the execution rate. Finally, a Bayesian Belief Network is then used to combine these parameters and estimate the resulting software reliability.} |
| 9 | May, 2006 | Modeling the Reliability of Existing Software using Static Analysis (Presentation Slides) | 2006 IEEE International Electro/Information Technology Conference, May 7-10, 2006, East Lansing, MI. | @INPROCEEDINGS{Schilling2006a, author = {Walter W. Schilling, Jr.
and Dr. Mansoor Alam}, title = {Modeling the Reliability of Existing Software using Static Analysis}, booktitle = {Proceedings of the 2006 IEEE International Electro/Information Technology Conference}, year = {2006}, address = {East Lansing, MI}, organization = {IEEE Region IV}, owner = {wws}, abstract={Software reliability represents an increasing risk to overall system reliability. As systems become larger and more complex, mission critical and safety critical systems have had increasing functionality controlled exclusively through software. This change, coupled with generally increasing reliability in hardware modules, has resulted in a shift of the root cause of systems failure from hardware to software. Market forces, including increased time to market, reduced development team sizes, and other factors, have encouraged projects to reuse existing software as well as to purchase COTS software solutions. This has made the usage of the more than 200 existing software reliability models increasingly difficult. Traditional software reliability models require significant testing data to be collected during software development in order to estimate software reliability. If this data is not collected in a disciplined manner or is not made available to software engineers, these modeling techniques can not be applied. It is imperative that practical reliability modeling techniques be developed to address these issues. It is on this premise that an appropriate software reliability model combining static analysis of existing source code modules, limited testing with path capture, and Bayesian Belief Networks is presented. Static analysis is used to detect faults within the source code which may lead to failure. Code coverage is used to determine which paths within the source code are executed as well as how often they execute. Finally, Bayesian Belief Network is then used to combine these parameters and estimate the resulting software reliability.}, keywords = {Software Reliability, Static Analysis, BayesianNetworks, Code Coverage, Static Analysis}, } |
| 8 | April, 2006 | Modeling the Reliability of Existing Software Using Static Analysis | NASA / Ohio Space Grant Consortium 2005-2006 Annual Student Research Symposium Proceedings XIV | @INPROCEEDINGS{Schilling2006, author = {Walter W. Schilling,
Jr.}, title = {Modeling the Reliability of Existing Software using Static Analysis}, booktitle = {NASA / Ohio Space Grant Consortium 2005-2006 Annual Student Research Symposium Proceedings XIV}, year = {2006}, address = {Cleveland, Ohio}, organization = {Ohio Space Grant Consortium}, owner = {wws}, keywords = {Software Reliability, Static Analysis, BayesianNetworks, Code Coverage, Static Analysis}, } |
| 7 | November, 2005 | A Methodology for Estimating Software Reliability Using Limited
Testing (Presentation Slides) |
Fastabstract: The 16th International Symposium on Software Reliability Engineering, October 8 - 11, 2005, Chicago, IL | @INPROCEEDINGS{Schilling2005b, author = {Walter W. Schilling, Jr. and Dr. Mansoor Alam}, title = {A Methodology for Estimating Software Reliability Using Limited Testing}, booktitle = {ISSRE 2005: The 16th International Symposium on Software Reliability Engineering}, year = {2005}, month={November}, address = {Chicago, IL}, organization = {IEEE Computer Society and IEEE Reliability Society}, abstract = {As more advanced software systems have been developed incorporating reused source code and COTS components, the impact of software reliability has become increasingly important. Many mission critical and safety critical systems are now software controlled. As this transition has occurred, the root cause for systems failure has increasingly shifted from hardware to software. Traditional software reliability models require significant testing data to be collected during software development in order to estimate the reliability of the resultant software. However, if this data is not collected in a disciplined manner or is not made available to subsequent software engineers, these modeling techniques can not readily be applied. In this paper, we propose a different approach at estimating software reliability based upon limited testing, static analysis of the existing source code, and Bayesian belief networks. }, keywords = {Software Reliability, Static Analysis, BayesianNetworks, Code Coverage, Static Analysis}, } |
| 6 | October, 2005 | WORK
IN PROGRESS - MEASURING THE ROI TIME FOR STATIC ANALYSIS (Presentation Slides) |
2005 Frontiers in Education Conference: Pedagogies and Technologies for the Emerging Global Economy, October 19–22, 2005 | @INPROCEEDINGS{Schilling2005, author = {Walter W. Schilling, Jr. and Dr. Mansoor Alam}, title = {WORK IN PROGRESS - Measuring the ROItime for Static Analysis}, booktitle = {2005 Frontiers in Education}, year = {2005}, month={October}, address = {Indianapolis, IN}, organization = {IEEE Computer Society / ASEE}, abstract = {Static analysis is one method that offers potential for reducing errors in delivered software. Static analysis is currently used to discover buffer overflows and mathematical errors, as well as verifying compliance with documented programming standards. Static analysis is routinely used in safety critical software applications within the avionics and automotive industries. Outside of these applications, static analysis is not a routinely taught method for software development. This paper intends to provide a quantitative measure for evaluating the effectiveness of static analysis as well as presenting results from an academic environment.}, keywords = {Computer science education, Programming environments, Software economics, Software engineering, Software metrics, Software tools, Static Analysis software risk factors.}, } |
| 5 | April, 2005 |
Embedded Systems Software Reliability | NASA / Ohio Space Grant Consortium 2004-2005 Annual Student Research Symposium Proceedings XIII | @INPROCEEDINGS{Schilling2005, author = {Walter W. Schilling, Jr.}, title = {Embedded Systems Software Reliability}, booktitle = {NASA / Ohio Space Grant Consortium 2004-2005 Annual Student Research Symposium Proceedings XIII}, year = {2005}, address = {Cleveland, Ohio}, organization = {Ohio Space Grant Consortium}, abstract = {““The most significant problem facing the data processing business today is the software problem that is manifested in two major complaints: Software is too expensive and software is unreliable.”[Mye76, page 3] This paragraph, leading into Myers book Software Reliability: Principles and Practices was written in 1976. Yet, even today, this statement is equally valid. Software failure represents a continuing source for systems failure as we reach into the 21st century. A 2002 study by the National Institute of Standards found that software defects cost the American economy $59.5 billion annually. [Tas02] However, software failures of mission critical systems can have more than an economic impact, as is evidenced by the six deaths attributed to software failure in the Therac-25 system [LT93], the loss of life generally associated with the London Ambulance Failure [FD96], the Patriot Missile failure [Car92], or the crash of the Osprey Aircraft. Our research is intended to be capable of statistically measuring the reliability and risk level for embedded software based upon postmortem analysis of project data and assorted modeling techniques. However, in order to understand how to model risk for future programs, we believe it is important to study and understand past failures. Henry Petroski states that the lessons learned from failure “…can do more to advance engineering knowledge than all the successful machines and structures in the world.” [Pet92] This belief is further supported by Nancy Leveson in “High Pressure Steam Engines and Computer Software” [Lev94] and Michael Holloway “From Bridges and Rockets, Lessons for Software Systems” [Hol99]. In keeping with this direction, the first segment of our research has been an in-depth study of computer systems failures, specifically targeting embedded systems. This article presents an analysis of several software failures, including details about the system, the method or mode of failure, and contributing causes for the failure. From this point, our direct research will use postmortem analysis of project data to statistically measure the reliability and quality of completed software, including Commercial Off the Shelf (COTS) as well as custom developed software. Using this analysis, we intend to develop a statistical model for software quality, using Markov, Semi-Markov, Baysian, and other statistical methods to reflect on the resultant software reliability. This model can then be used in project planning and system analysis phases to predict the reliability of future software development projects. Once a cohesive model has been developed, we will develop a computer application to aid in predicting software quality and software risk factors. }, owner = {wws}, keywords = {Software Reliability, Software Failure, Case Studies}, } |
| 4 | May, 2004 | Issues
Effecting the Readiness of the Java Language for usage in Safety
Critical Real Time Systems |
Java Language Class Paper |
@UNPUBLISHED{Schilling2004, author = {Walter Schilling}, title = {Issues Effecting the Readiness of the Java Language for usage in Safety Critical Real Time Systems}, note = {Submitted to fulfill partial requirements for Special Topics: Java EECS8980-001, Dr. Gerald R Heuring, Instructor}, month = {May}, year = {2004}, abstract = {Since its introduction in 1996, the Java programming language has offered programmers an alternative to the dominant C and C++ programming languages. Initially intended for usage with embedded devices, Java has had significant success in the general purpose PC programming domain, especially in relation to web systems. However, the adoption of the Java programming language in the embedded computing field has been slower than many expected. In terms of microprocessor usage, 99% of all microprocessors and microcontrollers are used within embedded systems; less than 1% go into the traditional "desktop" computer. The majority of these microprocessors and microcontrollers are programmed using the C programming language, though C++ and Assembly language represent the second most commonly used languages.}, keywords = {Java, Real-Time Systems, Safety Critical Systems}, } |
| 3 | February, 2002 |
Randomized
playback of tracks in a multimedia player |
United States Patent #6,707,768 |
|
| 2 | August, 1999 | The Impact of Prefetching and Victim Caching on Computer Systems Performance | Proceedings of the 12 International Conference on Parallel and Distributed Computing Systems | @INPROCEEDINGS{Schilling1999, author = {walter Schilling}, title = {The Impact of Prefetching and Victim Caching on Computer Systems Performance}, booktitle = {Proceedings of the 12th International Conference on Parallel and Distributed Computing Systems (PDCS-99)}, year = {1999}, editor = {S. Olariu and J. Wu}, month = {August}, organization = {International Society for Computers and Their Applications (ISCA) }, publisher = {International Society for Computers and Their Applications (ISCA) }, note = {ISBN: 1-880843-29-3}, owner = {Walter Schilling}, } |
| 1 | December, 1998 | The Combination of Pre-fetching and Victim Caching to Improve Computer Performance | Master's Thesis | @MASTERSTHESIS{Schilling1998, author = {Walter Schilling}, title = {The Combination of Pre-fetching and Victin Caching to Improve Computer Systems Performance}, school = {University of Toledo}, year = {1998}, month = {December}, note = {Advisor: Dr. Mansoor Alam}, abstract = {The performance of computer systems is heavily dependent upon the caching system used. This thesis investigates the effect of two well known caching systems called Victim Caching and Prefetching. Three different Markov Models for Memory systems are presented for performance analysis of systems using Victim Caching, Prefetching, and the combination of the two techniques. Simulation models are also developed for these three schemes. Simulation results are presented and compared with standard caching mechanisms. The techniques are then shown to be effective at improving computer systems performance. }, keywords = {Prefetching, Victim Caching, Performance}, } |
Back
$Revision: 1.8 $
$Date: 2007/11/25 12:59:16 $
$Header: /cvs/webpage/Publications/publications.html,v 1.6 2006/11/16
20:13:56 wws Exp $
$Name: $
$Log: publications.html,v $
Revision 1.8 2007/11/25 12:59:16 wws
Updated web page with new information on publications, research, and education.
Revision 1.7 2007/04/01 02:14:42 wws Added ONU
Band recording of Rhapsody in Blue to Website.
Revision 1.6 2006/11/16 20:13:56 wws
Updated webpage with new material and new conference presentations.