Log in

Relevant bibliographies by topics / Software failures

Contents

Journal articles
Dissertations / Theses
Books
Book chapters
Conference papers
Reports

Academic literature on the topic 'Software failures'

Author: Grafiati

Published: 4 June 2021

Last updated: 3 March 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software failures.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Software failures"

1

Yakovyna, V. S. "Software failures prediction using RBF neural network." Odes’kyi Politechnichnyi Universytet. Pratsi, no. 2 (June 15, 2015): 111–18. http://dx.doi.org/10.15276/opu.2.46.2015.20.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Munson, John C. "Software faults, software failures and software reliability modeling." Information and Software Technology 38, no. 11 (November 1996): 687–99. http://dx.doi.org/10.1016/0950-5849(96)01117-2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Peaker, B. "Review: Software Development Failures." Computer Bulletin 46, no. 4 (July 1, 2004): 30–31. http://dx.doi.org/10.1093/combul/46.4.30-c.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Neil, Martin. "Are software failures deterministic?" Information and Software Technology 39, no. 3 (March 1997): 217–19. http://dx.doi.org/10.1016/s0950-5849(96)01146-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Hatton, L. "Software failures: follies and fallacies." IEE Review 43, no. 2 (March 1, 1997): 49–52. http://dx.doi.org/10.1049/ir:19970201.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

SIMPSON, ROY L. "Learning from Software Development Failures." Nursing Management (Springhouse) 23, no. 9 (September 1992): 30???32. http://dx.doi.org/10.1097/00006247-199209000-00017.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Perrow, Charles. "Software Failures, Security, and Cyberattacks." TATuP - Zeitschrift für Technikfolgenabschätzung in Theorie und Praxis 20, no. 3 (November 1, 2011): 41–46. http://dx.doi.org/10.14512/tatup.20.3.41.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Zhu, Mengmeng, and Hoang Pham. "A Novel System Reliability Modeling of Hardware, Software, and Interactions of Hardware and Software." Mathematics 7, no. 11 (November 4, 2019): 1049. http://dx.doi.org/10.3390/math7111049.

Full text

Abstract:

In the past few decades, a great number of hardware and software reliability models have been proposed to address hardware failures in hardware subsystems and software failures in software subsystems, respectively. The interactions between hardware and software subsystems are often neglected in order to simplify reliability modeling, and hence, most existing reliability models assumed hardware subsystems and software subsystem are independent of each other. However, this may not be true in reality. In this study, system failures are classified into three categories, which are hardware failures, software failures, and hardware-software interaction failures. The main contribution of our research is that we further classify hardware-software interaction failures into two groups: software-induced hardware failures and hardware-induced software failures. A Markov-based unified system reliability modeling incorporating all three categories of system failures is developed in this research, which provides a novel and practical perspective to define system failures and further improve reliability prediction accuracy. Comparison of system reliability estimation between the reliability models with and without considering hardware-software interactions is elucidated in the numerical example. The impacts on system reliability prediction as the changes of transition parameters are also illustrated by the numerical examples.

APA, Harvard, Vancouver, ISO, and other styles

9

Li, Yifan, Hong-Zhong Huang, and Tingyu Zhang. "Reliability Analysis of C4ISR Systems Based on Goal-Oriented Methodology." Applied Sciences 11, no. 14 (July 8, 2021): 6335. http://dx.doi.org/10.3390/app11146335.

Full text

Abstract:

Hard-and-software integrated systems such as command and control systems (C4ISR systems) are typical systems that are comprised of both software and hardware, the failures of such devices result from complicated common cause failures and common (or shared) signals that make classical reliability analysis methods will be not applicable. To this end, this paper applies the Goal-Oriented (GO) methodology to detailed analyze the reliability of a C4ISR system. The reliability as well as the failure probability of the C4ISR system, are reached based on the GO model constructed. At the component level, the reliability of units of the C4ISR system is computed. Importance analysis of failures of such a system is completed by the qualitative analysis capability of the GO model, by which critical failures of hardware failures like communication module failures and motherboard module failures as well as software failures like network module application software failures and decompression module software failures are ascertained. This method of this paper contributes to the reliability analysis of all hard-and-software integrated systems.

APA, Harvard, Vancouver, ISO, and other styles

10

SCHNEIDEWIND, NORMAN. "APPLYING NEURAL NETWORKS TO SOFTWARE RELIABILITY ASSESSMENT." International Journal of Reliability, Quality and Safety Engineering 17, no. 04 (August 2010): 313–29. http://dx.doi.org/10.1142/s0218539310003834.

Full text

Abstract:

We adapt concepts from the field of neural networks to assess the reliability of software, employing cumulative failures, reliability, remaining failures, and time to failure metrics. In addition, the risk of not achieving reliability, remaining failure, and time to failure goals are assessed. The purpose of the assessment is to compare a criterion, derived from a neural network model, for estimating the parameters of software reliability metrics, with the method of maximum likelihood estimation. To our surprise the neural network method proved superior for all the reliability metrics that were assessed by virtue of yielding lower prediction error and risk. We also found that considerable adaptation of the neural network model was necessary to be meaningful for our application – only inputs, functions, neurons, weights, activation units, and outputs were required to characterize our application.

APA, Harvard, Vancouver, ISO, and other styles

More sources

Dissertations / Theses on the topic "Software failures"

1

Hou, Wei. "Integrated reliability and availability analysis of networks with software failures and hardware failures." [Tampa, Fla.] : University of South Florida, 2003. http://purl.fcla.edu/fcla/etd/SFE0000173.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Hou, Wei. "Integrated Reliability and Availability Aanalysis of Networks With Software Failures and Hardware Failures." Scholar Commons, 2003. https://scholarcommons.usf.edu/etd/1393.

Full text

Abstract:

This dissertation research attempts to explore efficient algorithms and engineering methodologies of analyzing the overall reliability and availability of networks integrated with software failures and hardware failures. Node failures, link failures, and software failures are concurrently and dynamically considered in networks with complex topologies. MORIN (MOdeling Reliability for Integrated Networks) method is proposed and discussed as an approach for analyzing reliability of integrated networks. A Simplified Availability Modeling Tool (SAMOT) is developed and introduced to evaluate and analyze the availability of networks consisting of software and hardware component systems with architectural redundancy. In this dissertation, relevant research efforts in analyzing network reliability and availability are reviewed and discussed, experimental data results of proposed MORIN methodology and SAMOT application are provided, and recommendations for future researches in the network reliability study are summarized as well.

APA, Harvard, Vancouver, ISO, and other styles

3

Georgiadis, Ioannis. "Self-organising distributed component software architectures." Thesis, Imperial College London, 2001. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.396255.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Clause, James Alexander. "Enabling and supporting the debugging of software failures." Diss., Georgia Institute of Technology, 2011. http://hdl.handle.net/1853/39514.

Full text

Abstract:

This dissertation evaluates the following thesis statement: Program analysis techniques can enable and support the debugging of failures in widely-used applications by (1) capturing, replaying, and, as much as possible, anonymizing failing executions and (2) highlighting subsets of failure-inducing inputs that are likely to be helpful for debugging such failures. To investigate this thesis, I developed techniques for recording, minimizing, and replaying executions captured from users' machines, anonymizing execution recordings, and automatically identifying failure-relevant inputs. I then performed experiments to evaluate the techniques in realistic scenarios using real applications and real failures. The results of these experiments demonstrate that the techniques can reduce the cost and difficulty of debugging.

APA, Harvard, Vancouver, ISO, and other styles

5

Savor, Tony. "Automatic detection of software failures with hierarchical supervisors." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1997. http://www.collectionscanada.ca/obj/s4/f2/dsk3/ftp04/nq22233.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Taing, Nguonly, Thomas Springer, Nicolás Cardozo, and Alexander Schill. "A Rollback Mechanism to Recover from Software Failures in Role-based Adaptive Software Systems." ACM, 2017. https://tud.qucosa.de/id/qucosa%3A75214.

Full text

Abstract:

Context-dependent applications are relatively complex due to their multiple variations caused by context activation, especially in the presence of unanticipated adaptation. Testing these systems is challenging, as it is hard to reproduce the same execution environments. Therefore, a software failure caused by bugs is no exception. This paper presents a rollback mechanism to recover from software failures as part of a role-based runtime with support for unanticipated adaptation. The mechanism performs checkpoints before each adaptation and employs specialized sensors to detect bugs resulting from recent configuration changes. When the runtime detects a bug, it assumes that the bug belongs to the latest configuration. The runtime rolls back to the recent checkpoint to recover and subsequently notifes the developer to fix the bug and re-applying the adaptation through unanticipated adaptation. We prototype the concept as part of our role-based runtime engine LyRT and demonstrate the applicability of the rollback recovery mechanism for unanticipated adaptation in erroneous situations.

APA, Harvard, Vancouver, ISO, and other styles

7

Huang, Bing. "Study of the impact of hardware failures on software reliability." College Park, Md. : University of Maryland, 2006. http://hdl.handle.net/1903/3853.

Full text

Abstract:

Thesis (Ph. D.) -- University of Maryland, College Park, 2006.
Thesis research directed by: Mechanical Engineering. Title from t.p. of PDF. Includes bibliographical references. Published by UMI Dissertation Services, Ann Arbor, Mich. Also available in paper.

APA, Harvard, Vancouver, ISO, and other styles

8

Zhang, Xiaoni. "An Analysis of the Effect of Environmental and Systems Complexity on Information Systems Failures." Thesis, University of North Texas, 2001. https://digital.library.unt.edu/ark:/67531/metadc2857/.

Full text

Abstract:

Companies have invested large amounts of money on information systems development. Unfortunately, not all information systems developments are successful. Software project failure is frequent and lamentable. Surveys and statistical analysis results underscore the severity and scope of software project failure. Limited research relates software structure to information systems failures. Systematic study of failure provides insights into the causes of IS failure. More importantly, it contributes to better monitoring and control of projects and enhancing the likelihood of the success of management information systems. The underlining theories and literature that contribute to the construction of theoretical framework come from general systems theory, complexity theory, and failure studies. One hundred COBOL programs from a single company are used in the analysis. The program log clearly documents the date, time, and the reasons for changes to the programs. In this study the relationships among the variables of business requirements change, software complexity, program size and the error rate in each phase of software development life cycle are tested. Interpretations of the hypotheses testing are provided as well. The data shows that analysis error and design error occur more often than programming error. Measurement criteria need to be developed at each stage of the software development cycle, especially in the early stage. The quality and reliability of software can be improved continuously. The findings from this study suggest that it is imperative to develop an adaptive system that can cope with the changes to the business environment. Further, management needs to focus on processes that improve the quality of the system design stage.

APA, Harvard, Vancouver, ISO, and other styles

9

Aggarwal, Sonia. "State Intervention in the Indian Software Industry." Scholarship @ Claremont, 2012. http://scholarship.claremont.edu/cmc_theses/438.

Full text

Abstract:

India's meteoric economic growth rate has been a subject of much discussion since the country began its economic liberalization in the early 1990s. The software segment, in particular, is growing at a rate of 48.5 percent. The conventional wisdom argues that market forces have driven India's software's success, and more broadly, information technology. This thesis marshals evidence for the role of the state in interaction with the software sector. More specifically, by discussing India's broad-scale import substitution industrialization efforts from the 1950s to 1991 and its transition to a more open economic structure, as well as more industry specific policies within a theoretical context, this work attempts to identify the key driving forces and impact of government policy. Most works that have attempted to assess such state efforts have done so in a casual fashion, without linking the actions to carefully specified rationales for state intervention. This thesis specifies four plausible rationales for government intervention: market failures, government goals in promoting a domestic industry for national security and the state role in international negotiations that might affect specific sectors, intervention driven by rent seeking behavior on the part of private-sector actors, and state intervention to address previous government policies in a particular market that may be seen as being inadequate or failures. It then empirically assesses the support for each of these claims in light of the evolution of the Indian software industry since its inception. In so doing, this work allows one to gauge the significant contributions of the state within a clear context of possible state roles. It also helps in understanding the software industry’s current challenges, and possible future role of the state in the industry.

APA, Harvard, Vancouver, ISO, and other styles

10

Sycofyllos, Nikolaos. "An Empirical Exploration in the Study of Software-Related Fatal Failures." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-31939.

Full text

Abstract:

This thesis investigates and explores the subject of software-related fatal failures. In our technology oriented society, deadly disasters due to software failures are not that uncommon as we might think. During recent years there has been a large amount of software-related fatal failures documented, although there have not been as far as we are aware of, any research studies trying to put those failures in the context of a wider evidence. That fact motivated us to answer two research questions: how many lives have been lost through failures of software and what is the nature of the main cause of software-related fatal failures. The aim of this thesis is to explore these questions and provide some empirical answers and also contribute to the knowledge of these failures.Our goal is to provide an empirical and conceptual basis for investigating fatal software failures that will attempt to place these failure examples in a wider record. A similar study has been conducted by Donald MacKenzie in the area of computer related failures but it is not directly answering our questions of interest and it is somehow outdated. Computer scientist Peter Neumann has done a lot of research in computer safety and is also the author of a wide collection of computer failure cases named “Risks to the public in computer and related systems” also called “RISKS” Reports. Those reports were the main source of our investigation and answers were given out of data collected from those reports. The methodology used in this research was an exploratory systematic review study. Starting off by defining Software-Related Fatal Failures (SRFF) and the inclusion criteria for the cases to be investigated, allowed us to avoid misinterpretations and collect the data in a better way. We searched through the “RISKS” reports and collected cases according to our criteria. The final collected data was reviewed and analyzed. Finally the results were illustrated and presented in terms of tables, plots, charts and descriptive statistics. We found out that in the “RISKS” reports, over 2600 people have lost their lives due to software-related failures and the majority of those failures had been caused by problematic user-software interaction. While answering our research questions we observed based on the information related to fatal software failures that the topic of SRFF is poorly investigated. Our research provides agood basis for future investigation and aims to trigger further research in the subject ofsoftware-related fatal failures.

APA, Harvard, Vancouver, ISO, and other styles

More sources

Books on the topic "Software failures"

1

1962-, Pels David, ed. Bad software: What to do when software fails. New York: Wiley, 1998.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

2

American Bar Association. Section of Litigation., ed. Litigating failed software actions. [New York, N.Y.?: American Bar Association], Section of Litigation, 1993.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

3

Software runaways. Upper Saddle River, NJ: Prentice Hall PTR, 1998.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

4

Software development failures: Anatomy of abandoned projects. Cambridge, Mass: MIT Press, 2003.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

5

Sherer, Susan A. Software failure risk: Measurement and management. New York: Plenum Press, 1992.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

6

Software failure, management failure: Amazing stories and cautionary tales. Chichester: Wiley, 1996.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

7

Wallace, Dolores R. The EFFective Manager Tool for software developers. Gaithersburg, MD: U.S. Dept. of Commerce, Technology Administration, National Institute of Standards and Technology, 1998.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

8

Pierre, Ladet, Vernadat F, and International Federation for Information Processing., eds. Integrated manufacturing systems engineering. London: Chapman & Hall, 1995.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

9

Richard, Kuhn D., and National Institute of Standards and Technology (U.S.), eds. Software quality lessons from medical device failure data. Gaithersburg, MD: U.S. Dept. of Commerce, Technology Administration, National Institute of Standards and Technology, 1999.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

10

United States. National Aeronautics and Space Administration., ed. Experimental study of software dependability. Urbana, Ill: Coordinated Science Laboratory, College of Engineering, University of Illinois at Urbana-Champaign, 1994.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

More sources

Book chapters on the topic "Software failures"

1

Eloff, Jan, and Madeleine Bihina Bella. "Software Failures: An Overview." In Software Failure Investigation, 7–24. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-61334-5_2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Helvik, Bjarne E., Petra Vizarreta, Poul E. Heegaard, Kishor Trivedi, and Carmen Mas-Machuca. "Modelling of Software Failures." In Computer Communications and Networks, 141–72. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-44685-7_6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Jahanian, Hamid, and Annabelle McIver. "Reasoning with Failures." In Formal Methods and Software Engineering, 36–52. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-63406-3_3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Smith, David J., and Kenneth B. Wood. "Software Failures—Causes and Hazards." In Engineering Quality Software, 12–21. Dordrecht: Springer Netherlands, 1989. http://dx.doi.org/10.1007/978-94-009-1121-5_2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Smith, David J. "Software failures and the life cycle." In Achieving Quality Software, 9–18. Dordrecht: Springer Netherlands, 1995. http://dx.doi.org/10.1007/978-94-011-0549-1_2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Kantipudi, Manmahesh, James S. Collofello, Ken W. Collier, and Scott Medeiros. "Software engineering course projects: Failures and recommendations." In Software Engineering Education, 324–38. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/3-540-55963-9_60.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Boldyreva, Alexandra, Jean Paul Degabriele, Kenneth G. Paterson, and Martijn Stam. "On Symmetric Encryption with Distinguishable Decryption Failures." In Fast Software Encryption, 367–90. Berlin, Heidelberg: Springer Berlin Heidelberg, 2014. http://dx.doi.org/10.1007/978-3-662-43933-3_19.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Eloff, Jan, and Madeleine Bihina Bella. "Practical Demonstration of Conducting a Near-Miss Analysis Investigation for Software Failures." In Software Failure Investigation, 75–100. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-61334-5_7.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Eloff, Jan, and Madeleine Bihina Bella. "A Methodology for Investigating Software Failures Using Digital Forensics and Near-Miss Analysis." In Software Failure Investigation, 39–56. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-61334-5_4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Gomes, Leandro, Alexandre Madeira, and Mario Benevides. "Logics for Petri Nets with Propagating Failures." In Fundamentals of Software Engineering, 145–57. Cham: Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-31517-7_10.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software failures"

1

Burger, Martin, and Andreas Zeller. "Minimizing reproduction of software failures." In the 2011 International Symposium. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/2001420.2001447.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Lan, Wenhui, Kuanjiu Zhou, Jinjin Feng, and Zongzheng Chi. "Research on Software Cascading Failures." In 2010 International Conference on Multimedia Information Networking and Security. IEEE, 2010. http://dx.doi.org/10.1109/mines.2010.214.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Dorin, Michael, and Sergio Montenegro. "Eliminating Software Caused Mission Failures." In 2019 IEEE Aerospace Conference. IEEE, 2019. http://dx.doi.org/10.1109/aero.2019.8741837.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Kadav, Asim, Matthew J. Renzelmann, and Michael M. Swift. "Tolerating hardware device failures in software." In the ACM SIGOPS 22nd symposium. New York, New York, USA: ACM Press, 2009. http://dx.doi.org/10.1145/1629575.1629582.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Khatter, K., and A. Kalia. "Modeling Software Failures using Neural Network." In Fourth International Conference on Advances in Recent Technologies in Communication and Computing (ARTCom2012). Institution of Engineering and Technology, 2012. http://dx.doi.org/10.1049/cp.2012.2505.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Boon, Ang, Chan Kit, Chua Keng, and Oh Khiam. "TetraMax Diagnosis and Laker Software on Failure Analysis For ATPG/Scan Failures." In 13th International Symposium on the Physical and Failure Analysis of Integrated Circuits. IEEE, 2006. http://dx.doi.org/10.1109/ipfa.2006.251034.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Stehle, Edward, Kevin Lynch, Maxim Shevertalov, Chris Rorres, and Spiros Mancoridis. "Diagnosis of software failures using computational geometry." In 2011 26th IEEE/ACM International Conference on Automated Software Engineering (ASE). IEEE, 2011. http://dx.doi.org/10.1109/ase.2011.6100108.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Solanki, Sudarshan D., and Bala P. Subramanya. "Software frame work for ESD soft failures." In 2016 International Conference on ElectroMagnetic Interference & Compatibility (INCEMIC). IEEE, 2016. http://dx.doi.org/10.1109/incemic.2016.7921491.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Abedi, Vajiheh, Mehrdad H. Zadeh, Javad Dargahi, and Pedram Fekri. "Software Failures Prediction in Self-Driving Vehicles." In 2020 IEEE 92nd Vehicular Technology Conference (VTC2020-Fall). IEEE, 2020. http://dx.doi.org/10.1109/vtc2020-fall49728.2020.9348849.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Zhao, Jing, Yuliang Jin, Kishor S. Trivedi, and Rivalino Matias Jr. "Injecting Memory Leaks to Accelerate Software Failures." In 2011 IEEE 22nd International Symposium on Software Reliability Engineering (ISSRE). IEEE, 2011. http://dx.doi.org/10.1109/issre.2011.24.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software failures"

1

Kaufman, Gordon M. Stochastic Software Reliability: Modeling of Software Failures. Fort Belvoir, VA: Defense Technical Information Center, November 1996. http://dx.doi.org/10.21236/ada329608.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Muhlheim, Michael David, and Richard Wood. Technical Basis for Evaluating Software-Related Common-Cause Failures. Office of Scientific and Technical Information (OSTI), April 2016. http://dx.doi.org/10.2172/1279406.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Lehner, J. Workshop on Philosophical Basis for Incorporating Software Failures in a Probabilistic Risk Assessment. Office of Scientific and Technical Information (OSTI), October 2009. http://dx.doi.org/10.2172/1439792.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Hemphill, Jeff. Unsettled Issues in Drive-by-Wire and Automated Driving System Availability. SAE International, January 2022. http://dx.doi.org/10.4271/epr2022002.

Full text

Abstract:

While many observers think that autonomy is right around the corner, there many unsettled issues. One such issue is availability, or how the vehicle behaves in the event of a failure of one of its systems such as those with the latest “by-wire” technologies. Handling of failures at a technical actuation level could involve many aspects, including time of operation after first fault, function/performance after first fault, and exposure after first fault. All of these and other issues are affected by software and electronic and mechanical hardware. Drive-by-wire and Automated Driving System Availability discusses the necessary systems approach required to address these issues. Establishing an industry path forward for these topics will simplify system development and provide a framework for consistent regulation and liability, which is an enabler for the launch of autonomous vehicles.

APA, Harvard, Vancouver, ISO, and other styles

5

Shileall, Timothy J., John M. Bolchoz, and Rachel Griffin. Analytical Derivation of Software Failure Regions. Fort Belvoir, VA: Defense Technical Information Center, September 1991. http://dx.doi.org/10.21236/ada244021.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Actis, Ricardo L. Stress/Failure Analysis Software for Multi-Material Interfaces. Fort Belvoir, VA: Defense Technical Information Center, December 1996. http://dx.doi.org/10.21236/ada360535.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Actis, Richardo. Stress/Failure Analysis Software for Multi-Material Interfaces. Fort Belvoir, VA: Defense Technical Information Center, November 1999. http://dx.doi.org/10.21236/ada371837.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Wallace, Dolores R., and D. Richard Kuhn. Software quality lessons from medical device failure data. Gaithersburg, MD: National Institute of Standards and Technology, 1999. http://dx.doi.org/10.6028/nist.ir.6407.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Brownsword, Lisa, Cecilia Albert, Patrick Place, and David Carney. Software Acquisition Patterns of Failure and How to Recognize Them. Fort Belvoir, VA: Defense Technical Information Center, April 2013. http://dx.doi.org/10.21236/ada584766.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Guo, Xingzhou, Chi Tian, Jinwu Xiao, Yunfeng Chen, and Jiansong Zhang. Life Cycle Integration of Building Information Modeling in Infrastructure Projects. Purdue University, 2022. http://dx.doi.org/10.5703/1288284317356.

Full text

Abstract:

Building Information Modeling (BIM) can provide solutions to many challenges of asset management, such as missing data, incompatible software, and an unclear business process. However, current implementation of BIM in infrastructure projects has only considers limited factors, such as technology application and digital information delivery, while issues of system compatibility and information needs are still missing. Different aspects of a business are interdependent and an incompatible development of various factors might result in different levels of BIM implementation or even project failure. Comprehensive research is needed to explore the key factors and challenges of BIM implementation in infrastructure projects. This study conducted interviews and surveys with key stakeholders of infrastructure projects to explore the challenges and potential solutions of BIM implementation. Interviews were conducted with 37 professionals and surveys were conducted with 102 professional stakeholders, including owners, designers, contractors, and software vendors. Four main factors, challenges, and potential solutions were identified from content analysis of the interviews and further validated by the surveys. These factors include process factor (when), technology factor (how), people factor (who), and information factor (what). Corresponding solutions are proposed to refine the current workflow and practices.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!