Software Failure Air Traffic Control System
•Download as PPT, PDF•
4 likes•3,941 views
An air traffic control system in Los Angeles failed, losing contact with 400 airplanes. The main system failed and the backup system did not take over as expected. The failure was due to a software timing issue - the system had a countdown timer that would reset too high, causing the system to shut down after 50 days without being restarted. This known issue was an oversight by the manufacturer and exposed system to failure by not addressing the problem as instructed. The failure highlights the risks of technical deficiencies and lack of client participation in complex software projects.
Report
Share
Report
Share
![Overview ,[object Object],[object Object],[object Object],[object Object],[object Object],Air Control System, Software Failure Mehran University Institute of Science and Technology Development](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
Object Oriented Design Concept
This document summarizes Chapter 14 of Ian Sommerville's 1995 book "Software Engineering". The chapter covers object-oriented design, including identifying objects from requirements, defining object classes and inheritance, designing object interfaces, and implementing objects concurrently. Key aspects of object-oriented design are encapsulation, information hiding, and representing systems as interacting objects. Object identification is an important but challenging part of the design process.
01. 03.-introduction-to-infrastructure
This document provides an introduction to IT infrastructure architecture, defining key concepts and building blocks. It discusses how infrastructures have become more complex with new applications and the need for agility. The definition of infrastructure is examined, noting it depends on perspective. Infrastructure comprises processes/information, applications, application platforms, and underlying hardware/network blocks. Non-functional requirements like availability, performance and security are crucial to infrastructure and often conflicting to balance. Architecture is needed to manage infrastructure design, use and changes.
HCI 3e - Ch 15: Task analysis
Chapter 15: Task analysis
from
Dix, Finlay, Abowd and Beale (2004).
Human-Computer Interaction, third edition.
Prentice Hall. ISBN 0-13-239864-8.
http://www.hcibook.com/e3/
Mobile hci
The document discusses the mobile ecosystem and its various layers. It describes how the mobile ecosystem consists of operators who build cellular networks, mobile platforms that software runs on, application frameworks that apps are created with, and different types of mobile apps like games and web widgets. It also covers topics like mobile design, information architecture, and trends like Mobile 2.0.
06. security concept
This document outlines a security concept and risk management process. It discusses identifying risks and assets, assessing impact and probability, and determining appropriate risk responses such as acceptance, avoidance, mitigation, and transfer. It also describes common security controls around availability, confidentiality and integrity. Attack vectors like malware, denial of service attacks, social engineering and phishing are examined. Finally, it discusses security patterns for identity and access management, segregation of duties, layered security and cryptography.
HCI 3e - Ch 19: Groupware
Chapter 19: Groupware
from
Dix, Finlay, Abowd and Beale (2004).
Human-Computer Interaction, third edition.
Prentice Hall. ISBN 0-13-239864-8.
http://www.hcibook.com/e3/
Unit 5
The document discusses various object-oriented methodologies including Rumbaugh, Booch, and Jacobson methodologies. It provides details on Rumbaugh's Object Modeling Technique (OMT) which separates modeling into object, dynamic, and functional models. It describes Booch's methodology which uses class, object, state transition, and other diagrams. It also discusses Jacobson's methodologies including Object-Oriented Software Engineering (OOSE) which is use case driven, and Object-Oriented Business Engineering (OOBE) which uses use cases. The document then covers topics on software quality assurance including types of errors, testing strategies like black box and white box testing, and testing approaches like top-down
Software Engineering an Introduction
Program versus Software, Software Characteristics, S/W Failure rate, Evolution Pattern, Types of Software, Stakeholders in Software Engineering, Software Quality, Software Crisis, Software Engineering: A Layered Technology, Evolution of Design Techniques, Exploratory style of S/W Development
Recommended
Object Oriented Design Concept
This document summarizes Chapter 14 of Ian Sommerville's 1995 book "Software Engineering". The chapter covers object-oriented design, including identifying objects from requirements, defining object classes and inheritance, designing object interfaces, and implementing objects concurrently. Key aspects of object-oriented design are encapsulation, information hiding, and representing systems as interacting objects. Object identification is an important but challenging part of the design process.
01. 03.-introduction-to-infrastructure
This document provides an introduction to IT infrastructure architecture, defining key concepts and building blocks. It discusses how infrastructures have become more complex with new applications and the need for agility. The definition of infrastructure is examined, noting it depends on perspective. Infrastructure comprises processes/information, applications, application platforms, and underlying hardware/network blocks. Non-functional requirements like availability, performance and security are crucial to infrastructure and often conflicting to balance. Architecture is needed to manage infrastructure design, use and changes.
HCI 3e - Ch 15: Task analysis
Chapter 15: Task analysis
from
Dix, Finlay, Abowd and Beale (2004).
Human-Computer Interaction, third edition.
Prentice Hall. ISBN 0-13-239864-8.
http://www.hcibook.com/e3/
Mobile hci
The document discusses the mobile ecosystem and its various layers. It describes how the mobile ecosystem consists of operators who build cellular networks, mobile platforms that software runs on, application frameworks that apps are created with, and different types of mobile apps like games and web widgets. It also covers topics like mobile design, information architecture, and trends like Mobile 2.0.
06. security concept
This document outlines a security concept and risk management process. It discusses identifying risks and assets, assessing impact and probability, and determining appropriate risk responses such as acceptance, avoidance, mitigation, and transfer. It also describes common security controls around availability, confidentiality and integrity. Attack vectors like malware, denial of service attacks, social engineering and phishing are examined. Finally, it discusses security patterns for identity and access management, segregation of duties, layered security and cryptography.
HCI 3e - Ch 19: Groupware
Chapter 19: Groupware
from
Dix, Finlay, Abowd and Beale (2004).
Human-Computer Interaction, third edition.
Prentice Hall. ISBN 0-13-239864-8.
http://www.hcibook.com/e3/
Unit 5
The document discusses various object-oriented methodologies including Rumbaugh, Booch, and Jacobson methodologies. It provides details on Rumbaugh's Object Modeling Technique (OMT) which separates modeling into object, dynamic, and functional models. It describes Booch's methodology which uses class, object, state transition, and other diagrams. It also discusses Jacobson's methodologies including Object-Oriented Software Engineering (OOSE) which is use case driven, and Object-Oriented Business Engineering (OOBE) which uses use cases. The document then covers topics on software quality assurance including types of errors, testing strategies like black box and white box testing, and testing approaches like top-down
Software Engineering an Introduction
Program versus Software, Software Characteristics, S/W Failure rate, Evolution Pattern, Types of Software, Stakeholders in Software Engineering, Software Quality, Software Crisis, Software Engineering: A Layered Technology, Evolution of Design Techniques, Exploratory style of S/W Development
Operating system services 9
The operating system provides several key services to programs and users, including user interface, program execution, input/output operations, file system management, communications, error detection and handling, resource allocation, accounting, protection, command interpretation, and resource management. These services allow for running programs, performing input/output, creating and managing files, connecting between processes, detecting and handling errors, tracking usage for billing, protecting processes from each other, interpreting user commands, and optimizing resource usage.
HCI 3e - Ch 16: Dialogue notations and design
Chapter 16: Dialogue notations and design
from
Dix, Finlay, Abowd and Beale (2004).
Human-Computer Interaction, third edition.
Prentice Hall. ISBN 0-13-239864-8.
http://www.hcibook.com/e3/
Security models
To Support Digital India, We are trying to enforce the security on the web and digital Information. This Slides provide you basic as well as advance knowledge of security model. Model covered in this slides are Chinese Wall, Clark-Wilson, Biba, Harrison-Ruzzo-Ullman Model, Bell-LaPadula Model etc.
Types of Access Control.
Design Goals of Distributed System
The fundamental concept of Distributed System, Part -2. This is useful for CTEVT Diploma in Computer Engineering Students.
Fundamental software engineering activities
Describes the basic activities of software engineering - specification, design and implementation, validation and evolution.
Accompanies video:
https://www.youtube.com/watch?v=Z2no7DxDWRI
Function Oriented Design
This document discusses function-oriented software design. It explains that function-oriented design represents a system as a set of functions that transform inputs to outputs. The chapter objectives are to explain function-oriented design, introduce design notations, illustrate the design process with an example, and compare sequential, concurrent and object-oriented design strategies. Topics covered include data-flow design, structural decomposition, detailed design, and a comparison of design strategies.
Role of system analyst
A system analyst performs three main roles:
1. They research problems within an organization's existing systems and processes, plan solutions to improve efficiency and productivity, and recommend new hardware and software systems.
2. They act as an agent of change by introducing new IT systems and working to minimize resistance to changes.
3. They investigate issues with current systems, monitor new systems, and gather facts and opinions from users to define requirements and solve problems.
Distributed deadlock
Distributed deadlock occurs when processes are blocked while waiting for resources held by other processes in a distributed system without a central coordinator. There are four conditions for deadlock: mutual exclusion, hold and wait, non-preemption, and circular wait. Deadlock can be addressed by ignoring it, detecting and resolving occurrences, preventing conditions through constraints, or avoiding it through careful resource allocation. Detection methods include centralized coordination of resource graphs or distributed probe messages to identify resource waiting cycles. Prevention strategies impose timestamp or age-based priority to resource requests to eliminate cycles.
Human Computer Interaction Chapter 5 Universal Design and User Support - Dr....
Universal Design:
Introduction
Universal design principles
Multi-modal interaction
Designing for diversity
User Support:
Introduction
Requirements of user support
Approaches to user support
Adaptive help systems
Designing user support systems
SDLC Models
The document presents information on the Software Development Life Cycle (SDLC), including:
1) It describes the seven main phases of the SDLC - planning, analysis, design, development, testing, implementation, and maintenance.
2) It discusses several SDLC models like waterfall, iterative, prototyping, spiral and V-model and compares their strengths and weaknesses.
3) It emphasizes the important role of testing in the SDLC and describes different testing types done during the phases.
Software engineering
This document provides an introduction to software engineering. It discusses how software serves both as a product that delivers computing potential and as a vehicle for delivering other products. The document defines what constitutes software and discusses different types of software applications. It also covers software engineering practices, including communication, planning, analysis and design modeling, construction, and principles related to each practice. Overall, the document gives a high-level overview of key concepts in software engineering.
Software engineering
Define Software,software myth,Sofware components,Software crisis,Generic view of software engineering,characteristics
Processes and threads
This document discusses processes and threads in Perl programming. It defines a process as an instance of a running program, while a thread is a flow of control through a program with a single execution point. Multiple threads can run within a single process and share resources, while processes run independently. The document compares processes and threads, and covers creating and managing threads, sharing data between threads, synchronization, and inter-process communication techniques in Perl like fork, pipe, and open.
Spm project planning
This document outlines the 10 step process for software project planning. It begins with selecting the project and identifying its scope and objectives. It then covers identifying the project infrastructure, analyzing project characteristics, and identifying products and activities. Steps also include estimating effort for each activity, identifying risks, allocating resources, and reviewing/publicizing the plan. Execution then involves lower level planning. The document also discusses software effort estimation techniques such as algorithmic models, expert judgment, analogy, and top-down and bottom-up approaches.
Model Based Software Architectures
This document discusses software architecture from both a management and technical perspective. From a management perspective, it defines an architecture as the design concept, an architecture baseline as tangible artifacts that satisfy stakeholders, and an architecture description as a human-readable representation of the design. It also notes that mature processes, clear requirements, and a demonstrable architecture are important for predictable project planning. Technically, it describes Philippe Kruchten's model of software architecture, which includes use case, design, process, component, and deployment views that model different aspects of realizing a system's design.
Use Case Diagram
The document discusses use case diagrams and use case descriptions for modeling system requirements. It covers drawing use case diagrams to show functional requirements and actors, common mistakes, and writing use case descriptions including basic, alternate, and exception flows of events. The document provides examples and exercises to help understand use cases for requirements modeling.
Groupware/CSCW
1. Groupware aims to facilitate collaboration between individuals located remotely by eliminating distance.
2. It refers to software that supports cooperative work, including communication, coordination, and sharing of information.
3. Effective groupware addresses both technical and social aspects of human interaction and collaboration.
Network management
Network management involves controlling complex data networks to maximize efficiency and ensure data transmission. It aims to help with network complexity and transparency for users. The key aspects of network management include fault, configuration, security, performance, and accounting management. Network management standards and protocols like SNMP and CMIP allow for monitoring and configuration of network devices. Network management platforms provide the software and tools to integrate and manage different network components from a centralized location.
Anatomy of android application
An Android application is composed of activities, services, and content providers. Activities display user interfaces and are launched by intents. The context provides access to application-wide resources and functionality. Activities have a lifecycle of states like resumed, paused, and stopped that are called back through methods to manage resources. Intents are used to transition between activities within an app or launch other apps' components.
OPERATING SYSTEMS DESIGN AND IMPLEMENTATION
This document provides an overview of operating systems design and implementation. It discusses the basic functions of an operating system as an extended virtual machine and a resource manager. It describes the evolution of operating systems through four generations from the earliest batch systems using vacuum tubes and plugboards to today's personal computers. The document outlines key components of operating systems including processes, file systems, system calls, and virtual machines. It provides examples of early batch processing systems, multiprogramming, and the structure of system calls. Finally, it discusses different approaches to operating system structure such as layered systems, virtual machines, and the client-server model.
Software failure The knight's story
This Presentation focuses on describing what a software failure can do. And how big can the loss be with a simple error.
Exploratory Analysis of Pakistan Software Industry on Quality Improvement by ...
Exploratory Analysis of Pakistan Software Industry on Quality Improvement by ...International Journal of Computer and Communication System Engineering
Nowadays the need of risk management has been truly augmented but its industrial perspective is very less explored. The product quality can improve by having proper risk management in any process methodology. In this paper, the domain of risk management practice within 20 software organizations in Pakistan Software Industry has been explored. The research begins with the study of practice of risk management in the industry and highlights some particular criteria. After that it investigates how the companies have integrated their risk management with software development. The main focus of study is handling of requirement related risks. Regarding the state of industrial risk management practice, our results show that there are some discrepancies between the industrial practice and the standard models studied. The industrial organizations have not implemented all the important activities as prescribed by the standard models. Hence, this paper suggests a list of issues that need to be addressed particularly of requirement related risk management. Keywords: process model, software development process, agile methods, requirement risk management.More Related Content
What's hot
Operating system services 9
The operating system provides several key services to programs and users, including user interface, program execution, input/output operations, file system management, communications, error detection and handling, resource allocation, accounting, protection, command interpretation, and resource management. These services allow for running programs, performing input/output, creating and managing files, connecting between processes, detecting and handling errors, tracking usage for billing, protecting processes from each other, interpreting user commands, and optimizing resource usage.
HCI 3e - Ch 16: Dialogue notations and design
Chapter 16: Dialogue notations and design
from
Dix, Finlay, Abowd and Beale (2004).
Human-Computer Interaction, third edition.
Prentice Hall. ISBN 0-13-239864-8.
http://www.hcibook.com/e3/
Security models
To Support Digital India, We are trying to enforce the security on the web and digital Information. This Slides provide you basic as well as advance knowledge of security model. Model covered in this slides are Chinese Wall, Clark-Wilson, Biba, Harrison-Ruzzo-Ullman Model, Bell-LaPadula Model etc.
Types of Access Control.
Design Goals of Distributed System
The fundamental concept of Distributed System, Part -2. This is useful for CTEVT Diploma in Computer Engineering Students.
Fundamental software engineering activities
Describes the basic activities of software engineering - specification, design and implementation, validation and evolution.
Accompanies video:
https://www.youtube.com/watch?v=Z2no7DxDWRI
Function Oriented Design
This document discusses function-oriented software design. It explains that function-oriented design represents a system as a set of functions that transform inputs to outputs. The chapter objectives are to explain function-oriented design, introduce design notations, illustrate the design process with an example, and compare sequential, concurrent and object-oriented design strategies. Topics covered include data-flow design, structural decomposition, detailed design, and a comparison of design strategies.
Role of system analyst
A system analyst performs three main roles:
1. They research problems within an organization's existing systems and processes, plan solutions to improve efficiency and productivity, and recommend new hardware and software systems.
2. They act as an agent of change by introducing new IT systems and working to minimize resistance to changes.
3. They investigate issues with current systems, monitor new systems, and gather facts and opinions from users to define requirements and solve problems.
Distributed deadlock
Distributed deadlock occurs when processes are blocked while waiting for resources held by other processes in a distributed system without a central coordinator. There are four conditions for deadlock: mutual exclusion, hold and wait, non-preemption, and circular wait. Deadlock can be addressed by ignoring it, detecting and resolving occurrences, preventing conditions through constraints, or avoiding it through careful resource allocation. Detection methods include centralized coordination of resource graphs or distributed probe messages to identify resource waiting cycles. Prevention strategies impose timestamp or age-based priority to resource requests to eliminate cycles.
Human Computer Interaction Chapter 5 Universal Design and User Support - Dr....
Universal Design:
Introduction
Universal design principles
Multi-modal interaction
Designing for diversity
User Support:
Introduction
Requirements of user support
Approaches to user support
Adaptive help systems
Designing user support systems
SDLC Models
The document presents information on the Software Development Life Cycle (SDLC), including:
1) It describes the seven main phases of the SDLC - planning, analysis, design, development, testing, implementation, and maintenance.
2) It discusses several SDLC models like waterfall, iterative, prototyping, spiral and V-model and compares their strengths and weaknesses.
3) It emphasizes the important role of testing in the SDLC and describes different testing types done during the phases.
Software engineering
This document provides an introduction to software engineering. It discusses how software serves both as a product that delivers computing potential and as a vehicle for delivering other products. The document defines what constitutes software and discusses different types of software applications. It also covers software engineering practices, including communication, planning, analysis and design modeling, construction, and principles related to each practice. Overall, the document gives a high-level overview of key concepts in software engineering.
Software engineering
Define Software,software myth,Sofware components,Software crisis,Generic view of software engineering,characteristics
Processes and threads
This document discusses processes and threads in Perl programming. It defines a process as an instance of a running program, while a thread is a flow of control through a program with a single execution point. Multiple threads can run within a single process and share resources, while processes run independently. The document compares processes and threads, and covers creating and managing threads, sharing data between threads, synchronization, and inter-process communication techniques in Perl like fork, pipe, and open.
Spm project planning
This document outlines the 10 step process for software project planning. It begins with selecting the project and identifying its scope and objectives. It then covers identifying the project infrastructure, analyzing project characteristics, and identifying products and activities. Steps also include estimating effort for each activity, identifying risks, allocating resources, and reviewing/publicizing the plan. Execution then involves lower level planning. The document also discusses software effort estimation techniques such as algorithmic models, expert judgment, analogy, and top-down and bottom-up approaches.
Model Based Software Architectures
This document discusses software architecture from both a management and technical perspective. From a management perspective, it defines an architecture as the design concept, an architecture baseline as tangible artifacts that satisfy stakeholders, and an architecture description as a human-readable representation of the design. It also notes that mature processes, clear requirements, and a demonstrable architecture are important for predictable project planning. Technically, it describes Philippe Kruchten's model of software architecture, which includes use case, design, process, component, and deployment views that model different aspects of realizing a system's design.
Use Case Diagram
The document discusses use case diagrams and use case descriptions for modeling system requirements. It covers drawing use case diagrams to show functional requirements and actors, common mistakes, and writing use case descriptions including basic, alternate, and exception flows of events. The document provides examples and exercises to help understand use cases for requirements modeling.
Groupware/CSCW
1. Groupware aims to facilitate collaboration between individuals located remotely by eliminating distance.
2. It refers to software that supports cooperative work, including communication, coordination, and sharing of information.
3. Effective groupware addresses both technical and social aspects of human interaction and collaboration.
Network management
Network management involves controlling complex data networks to maximize efficiency and ensure data transmission. It aims to help with network complexity and transparency for users. The key aspects of network management include fault, configuration, security, performance, and accounting management. Network management standards and protocols like SNMP and CMIP allow for monitoring and configuration of network devices. Network management platforms provide the software and tools to integrate and manage different network components from a centralized location.
Anatomy of android application
An Android application is composed of activities, services, and content providers. Activities display user interfaces and are launched by intents. The context provides access to application-wide resources and functionality. Activities have a lifecycle of states like resumed, paused, and stopped that are called back through methods to manage resources. Intents are used to transition between activities within an app or launch other apps' components.
OPERATING SYSTEMS DESIGN AND IMPLEMENTATION
This document provides an overview of operating systems design and implementation. It discusses the basic functions of an operating system as an extended virtual machine and a resource manager. It describes the evolution of operating systems through four generations from the earliest batch systems using vacuum tubes and plugboards to today's personal computers. The document outlines key components of operating systems including processes, file systems, system calls, and virtual machines. It provides examples of early batch processing systems, multiprogramming, and the structure of system calls. Finally, it discusses different approaches to operating system structure such as layered systems, virtual machines, and the client-server model.
What's hot (20)
Human Computer Interaction Chapter 5 Universal Design and User Support - Dr....
Human Computer Interaction Chapter 5 Universal Design and User Support - Dr....
Viewers also liked
Software failure The knight's story
This Presentation focuses on describing what a software failure can do. And how big can the loss be with a simple error.
Exploratory Analysis of Pakistan Software Industry on Quality Improvement by ...
Exploratory Analysis of Pakistan Software Industry on Quality Improvement by ...International Journal of Computer and Communication System Engineering
Nowadays the need of risk management has been truly augmented but its industrial perspective is very less explored. The product quality can improve by having proper risk management in any process methodology. In this paper, the domain of risk management practice within 20 software organizations in Pakistan Software Industry has been explored. The research begins with the study of practice of risk management in the industry and highlights some particular criteria. After that it investigates how the companies have integrated their risk management with software development. The main focus of study is handling of requirement related risks. Regarding the state of industrial risk management practice, our results show that there are some discrepancies between the industrial practice and the standard models studied. The industrial organizations have not implemented all the important activities as prescribed by the standard models. Hence, this paper suggests a list of issues that need to be addressed particularly of requirement related risk management. Keywords: process model, software development process, agile methods, requirement risk management.Mars climate obiter failure
The Mars Climate Orbiter failed due to a metric-imperial unit conversion error. The spacecraft's software used metric units while ground teams entered data using imperial units, resulting in incorrect calculations that sent the orbiter too low into Mars' atmosphere, where it disintegrated. The failure was caused by human error in not ensuring consistent use of units across software and teams. It underscores the importance of strict protocols and training to prevent mistakes when using different measurement systems.
Software project failure in new zealand – what’s killing us and what we can d...
The document summarizes the findings of a study on software project failure in New Zealand. It found that 54% of projects studied failed, and failed projects cost twice as much and took 110% longer than planned. Custom software development projects had a much higher failure rate than those integrating existing software. Key factors contributing to failure included unmanaged scope changes, a lack of clarity about the software's purpose, and weak leadership. Successful projects tended to have clearer scopes, business cases, and processes for learning lessons. The study identified several areas of concern for different roles in projects.
Software Disasters
The document discusses several major software project failures and disasters including OS/2, Netscape, Ariane 5, the FBI Virtual Case File system, the 2003 Northeast Blackout, the WoW Corrupted Blood glitch, Knight Capital's $440 million trading loss, and common reasons why software projects fail according to the IEEE. Some key points are that OS/2 lost out to Windows due to marketing and ecosystem factors, Netscape's code rewrite took too long allowing Windows to dominate, type conversion errors destroyed the Ariane 5 rocket, and the FBI system was unusable after $170 million due to poor planning and requirements changes.
Failure of Mars Climate Orbiter
The Mars Climate Orbiter failed due to a mismatch between the units used by Lockheed Martin to calculate thruster firings and the units expected by NASA for navigation. Lockheed Martin used English units (pounds, feet, inches) while NASA expected metric units. As a result, trajectory correction maneuvers put the orbiter in a lower orbit than intended, and it burned up in the Martian atmosphere upon arrival. An investigation found the root cause was a failure in NASA's engineering systems and processes to detect the mismatch in units between the teams.
Software Faults, Failures and Their Mitigations | Turing100@Persistent
Prof Kishor Trivedi, Duke University, USA talks about Software Faults, Failures and Their Mitigations at the 6th Session of Turing100@Persistent
Major blackout in the world
This document summarizes several major blackouts that have occurred worldwide. It provides details on the number of people affected, location, duration and key causes and lessons learned from each event. Some of the major blackouts discussed include the Northeast Blackout of 1965 affecting 30 million people in the US and Canada for 12 hours due to human error. The Southern Brazil Blackout of 1999 left 97 million without power for 30 hours after a lightning strike caused protective systems to fail. The Northeast Blackout of 2003 was caused by inadequate grid monitoring and affected 55 million for 16 hours, highlighting the need for mandatory reliability standards.
7 historical software bugs
This document summarizes 7 historical software bugs that had critical impacts: 1) The Y2K bug, 2) A 1980 bug that caused false reports of incoming US missiles from Russia, 3) An undetected hole in the ozone layer from 1978-1985, 4) Radiation therapy overdoses in 1985-1987 and 2000, 5) A 1996 bug that caused the European Ariane 5 rocket to veer off course, 6) Flight crashes of a Swedish fighter jet in 1993 and Scottish helicopter in 1994, and 7) A 1999 Mars orbiter crash caused by a bug during testing.
Warsaw airbus accident
A Lufthansa Airbus landing in Warsaw in 1993 encountered bad weather conditions. Upon landing, the aircraft's braking system did not activate for 9 seconds, leaving insufficient runway to stop. This caused the plane to run into an embankment, killing 2 people and injuring 54. The accident was caused by outdated wind information provided to the pilots, their failure to notice inconsistent wind data, and the braking software's inability to handle a landing where only one wheel initially touched down due to weather. The software functioned as specified but did not anticipate this condition.
Intro to requirements eng.
Requirements engineering covers all activities involved in discovering, documenting, and maintaining system requirements. Requirements specify what a system should do and its qualities. There are three main types - functional, non-functional, and domain. Requirements engineering uses systematic techniques to ensure requirements are complete and consistent. Difficulties in requirements engineering are a leading cause of project failures and system problems, as stakeholders often have unclear needs and requirements change over time with multiple priorities involved.
Ariane 5 launcher failure
Explains the causes of the Ariane 5 launcher failure in 1996. Due to a failure in the software controlling the inertial navigation system
Video: http://www.youtube.com/watch?v=W3YJeoYgozw
Airbus Flight Control System
Explains how redundancy and diversity are used in the flight control systems of the Airbus 330/340 to achieve safety and reliability
Mars orbiter mission (Mangalyaan)The govt. of INDIA
All details of the Mars orbiter mission of India. Also the details about ISRO who is carrying out this mission. Also Mp4 video of launch of PSLV-XL which was the launch vehicle for the spacecraft. I hope this presentation is useful for you.The video will work.
Unit 5, GRE401
Here is a potential 10-minute presentation to the Chinese Environment Minister on solutions to China's ecological challenges from rapid economic growth:
"Mr. Minister, thank you for the opportunity to present some solutions. China's economic growth has lifted hundreds of millions out of poverty but put immense pressure on natural systems. If left unaddressed, continued degradation risks undermining long-term prosperity. We propose a three-pronged approach:
1. Implement an ecological tax reform. Shift taxes off business and labor and onto resource use and pollution. This creates incentives for efficiency and innovation while raising funds for environmental protection.
2. Establish an accurate national ecological footprint accounting system and set targets to reduce China's footprint to within global bioc
Hoe uw website aantrekkelijker maken ?
Wilt u graag weten hoe uw uw webshop nog meer conversies kan laten opleveren ? We zetten enkele tips voor je op een rij!
Viewers also liked (20)
Exploratory Analysis of Pakistan Software Industry on Quality Improvement by ...
Exploratory Analysis of Pakistan Software Industry on Quality Improvement by ...
Software project failure in new zealand – what’s killing us and what we can d...
Software project failure in new zealand – what’s killing us and what we can d...
Software Faults, Failures and Their Mitigations | Turing100@Persistent
Software Faults, Failures and Their Mitigations | Turing100@Persistent
Mars orbiter mission (Mangalyaan)The govt. of INDIA
Mars orbiter mission (Mangalyaan)The govt. of INDIA
Similar to Software Failure Air Traffic Control System
Rocky Mtn Safety090917
The document discusses several incidents involving software errors that led to accidents, including a dropped cable that killed a dockworker due to inconsistent speed readings by sensors, injuries caused by erratic behavior of elevators and bales from an outdated software patch, and a generator trip caused by an unofficial software change made by a vendor. It emphasizes the importance of software configuration management, requirements gathering, failure mode analysis, and change control to prevent such incidents.
Cyber security in_next_gen_air_transportation_system_wo_video
Federal Aviation Administration (FAA) is responsible for overseeing the US National Airspace System, which comprises ATC systems, procedures, facilities, and aircraft, and the people who operate them. FAA is implementing Next Generation Air Transportation System (NextGen) to move the current radar-based air-traffic control (ATC) system to one that is based on satellite navigation and automation. It is essential that FAA ensures effective information-security controls are incorporated in the design of NextGen programs to protect them from threats. This talk discusses the threats FAA faces and the cyber security controls adopted by FAA in implementation of these NextGen Air Transportation System.
Human Factors
The document introduces human factors and discusses the interaction between humans, tasks, equipment, and the environment. It covers the four key elements of human factors as liveware (the person), hardware (physical equipment), software (non-physical aspects like procedures), and environment. The document discusses how errors can occur at the interfaces between these elements when there is a mismatch. Specifically, it examines safety incidents from failures in liveware-liveware and liveware-hardware interactions.
SE2018_Lec 19_ Software Testing
1. The document discusses various types of software testing including unit testing, integration testing, system testing, and acceptance testing. It explains that unit testing focuses on individual program units in isolation while integration testing tests modules assembled into subsystems.
2. The document then provides examples of different integration testing strategies like incremental, bottom-up, top-down, and discusses regression testing. It also defines smoke testing and explains its purpose in integration, system and acceptance testing levels.
3. Finally, the document emphasizes the importance of system and acceptance testing to verify functional and non-functional requirements and ensure the system can operate as intended in a real environment.
Avionics System Standards
This presentation is about the Avionics System Standards in terms of hardware and software briefly discussing the DO-254( ) and DO-178( ) as required for basic understanding.
Avionics system Standard
This presentation is about the Avionics System Standards in terms of hardware and software briefly discussing the DO-254( ) and DO-178( ) as required for basic understanding.
DHS ICS Security Presentation
The document provides an overview of control systems security from the perspective of the U.S. Department of Homeland Security. It discusses critical infrastructure sectors, risk drivers like modernization and globalization, vulnerability lifecycles, findings from control system assessments, and several cyber incidents involving control systems that impacted industrial operations. The department works to improve control system security through assessments, training, partnerships with industry, and developing guidance on topics like cyber forensics and firewall deployment.
INFORM-Measuring and Monitoring Aircraft Turn Operations v3
This document discusses measuring and monitoring aircraft turn operations. It provides background on the aircraft turn process, which involves deplaning passengers, servicing the aircraft, and boarding new passengers. It describes how all components of the process are interconnected and how disturbances can impact the whole network. The document advocates for monitoring the various sub-processes of aircraft turns in real-time to proactively manage disruptions and identify issues.
DefCon_2015_Slides_Krotofil_Larsen
This document summarizes a presentation on hacking chemical plants for competition and extortion. It outlines the stages of a cyber-physical attack on an industrial control system, including gaining initial access, discovering details of the physical process, obtaining control of parts of the system without triggering alarms, developing attack payloads to cause economic damage through product loss or non-compliance, and cleaning up to misdirect forensic investigation away from the attacker. The presentation provides examples of techniques for each stage and emphasizes the need to understand process engineering and control theory to reliably manipulate a physical system for harmful purposes.
New Maint Philo
The document discusses new philosophies for aircraft maintenance including reliability-centered maintenance and condition-based maintenance. It emphasizes using data from enhanced sensors and diagnostics to enable predictive and proactive maintenance to improve aircraft availability and reduce costs over the life cycle. Emerging technologies like prognostics and health management will be integrated across all aircraft subsystems.
RCFA Success of Root Cause Failure Analysis
This document discusses how to make root cause failure analysis (RCFA) a successful business improvement strategy. It notes that while many companies adopt RCFA, they often abandon it when they do not see benefits. RCFA is more effective at finding systematic causes of problems and improving business systems rather than solving individual problems. The document outlines how RCFA works best when the learnings are used to improve broader business processes, not just fix single issues. It provides an example of how taking learnings from an RCFA and implementing them company-wide can prevent numerous future failures and significantly improve performance and profits over the long run.
Ch11 reliability engineering
The document discusses reliability engineering and fault tolerance. It covers topics like availability, reliability requirements, fault-tolerant architectures, and reliability measurement. It defines key terms like faults, errors, and failures. It also describes techniques for achieving reliability like fault avoidance, fault detection, and fault tolerance. Specific architectures discussed include redundant systems and protection systems that can take emergency action if failures occur.
Apres Cobem09
The document discusses reliability management for unmanned aerial systems (UAS). It outlines several key aspects:
1) Reliability is important for UAS as failures can impact safety and missions. Tools like FMEA and FRACAS can be used to analyze reliability.
2) Factors like MTBF, failure rate, and maintainability should be managed over the lifecycle. Tools like FTA can assess how failures affect overall reliability.
3) These reliability management tools can be implemented at different lifecycle phases from design to operation to improve UAS reliability and prevent failures.
Power station monitoring and cyber security
Power plants are increasingly monitoring equipment using internet-connected systems, but this connectivity also increases cybersecurity risks. A computer virus once infiltrated a US power plant network through an infected USB drive, shutting down the plant for three weeks. To address such risks, the US Federal Energy Regulatory Commission proposes strengthening cybersecurity standards for power grids, including expanding protections to more assets and implementing new security controls. However, many control systems still use outdated software and operating systems without adequate protection.
Cutting the Cord
This document summarizes a presentation about environmental monitoring technologies for facilities. It discusses the advantages and disadvantages of wired and wireless monitoring systems. Wired systems are reliable but difficult to scale and maintain, while wireless systems are easier to deploy but had concerns about battery life, interference and security. However, wireless technologies have improved with longer battery life, energy harvesting, better signals and encryption. The presentation concludes that the best solution depends on the specific facility and monitoring needs, and recommends researching technologies, vendors and determining key threat factors.
Software Testing Basics
This document is an introduction to software testing that discusses why testing is important and what activities are involved in testing. It notes that software is ubiquitous and critical in many applications, and failures can have huge financial and safety impacts. More testing is needed due to increased expectations for reliability, larger and more complex software, and new platforms like the web. The goal is to help reduce risks and costs from failures through systematic testing approaches.
20110204 alarm management seminar ureason v1 3
The document summarizes a seminar on alarm management principles and guidance. It discusses the importance of improving alarm systems to increase safety and operational effectiveness. It provides examples of how UReason has helped customers in various industries implement advanced alarm management systems to reduce alarm loads and prioritize critical alarms. Key aspects covered include establishing an alarm philosophy, monitoring performance metrics, rationalizing alarms, and using alarm management software.
Blackout Task Force Highlights SCADA System Woes
The interim report on the US Blackout of 2003
points to failures of SCADA systems and critical
software applications as the chief culprits. Companies
who operate SCADA systems and advanced
online applications should note carefully the role of
these systems in the Blackout events.
Computer system validation
This document provides an overview of computer validation and compliance with regulatory guidance. It discusses the need for computer validation and outlines key principles from guidance documents such as software validation, use of off-the-shelf software in medical devices, and validation of electronic records and signatures. Validation approaches for different systems and software are covered, including spreadsheets. The document provides references to FDA and international regulatory guidance on these topics.
Ch11 - Reliability Engineering
This document provides an overview of reliability engineering topics including software reliability, fault tolerance, and reliability requirements. It discusses key concepts such as availability, reliability, faults, errors and failures. It also describes different fault-tolerant system architectures and reliability metrics including probability of failure on demand, rate of occurrence of failures, and availability. Functional reliability requirements and examples are also presented relating to checking requirements, recovery requirements, redundancy requirements and development process requirements.
Similar to Software Failure Air Traffic Control System (20)
Cyber security in_next_gen_air_transportation_system_wo_video
Cyber security in_next_gen_air_transportation_system_wo_video
INFORM-Measuring and Monitoring Aircraft Turn Operations v3
INFORM-Measuring and Monitoring Aircraft Turn Operations v3
More from Shakeel Ahmed
Ict Sector In Pakistan
The software industry in Pakistan has grown significantly in recent years but still has room for improvement. It is currently considered a tier-3 nation in software exports but has the talent and capabilities to become a tier-2 or tier-1 country. Key challenges include law and order issues, software piracy, a lack of specialization, and insufficient focus on strategic management. However, the industry shows promise for continued growth as more firms are established and Pakistan further develops its ICT policies and technological potential.
Trade And Environnent
The document discusses the relationship between trade and the environment. It outlines several ways that trade can impact the environment, including through scale effects, composition effects, technique effects, and direct effects from transportation. It also discusses green certification initiatives and Pakistan's 2005 environmental policy, which aims to promote certifications and build capacity to safeguard the environment from the impacts of trade liberalization.
Climate Change Environmental Policy 2005, Pakistan
This document discusses climate change and global warming. It outlines the greenhouse effect and how human activities that produce greenhouse gases are the main cause of global warming. The document also summarizes Pakistan's environmental policy and action plan to address climate change through developing clean energy technologies, implementing emissions reduction programs, and raising public awareness. The conclusion calls for global cooperation to transition to renewable energy in order to cure the effects of climate change.
Waste Management
This document summarizes waste management issues in Pakistan. It categorizes different types of waste and identifies hazardous waste. It discusses problems with waste collection and disposal from hospitals and municipalities. Waste is often burned openly or dumped in improperly designed landfills, polluting the environment. The role of local governments in waste management is outlined, though capacity is limited. It concludes more attention and education is needed from the government to adopt best practices that reduce, reuse, and recycle waste.
Pakistan Technology Board
The document provides recommendations to improve the Pakistan Technology Board by modeling it after the United Kingdom's Technology Strategy Board. It recommends that the board forecast world market and technology trends to guide analysis of relevant technology areas, identify and select key technologies important for industry growth and competitive advantage, and propose incentives for developing and growing key technologies. It also recommends setting up joint ventures for knowledge sharing and manufacturing, providing special investment incentives, maximizing local engineering design, and promoting quality assurance systems and standards.
Impact of Livestock Sector on Pakistan Economy
The document discusses the impact of the livestock sector on Pakistan's economy. It notes that the livestock sector contributes 10.8% to Pakistan's GDP and employs 35 million people. Pakistan has great potential in the livestock sector due to its natural breeds of buffalo and cattle. The government has implemented innovative approaches to improve the sector, such as artificial insemination programs, establishing feed mills, and providing loans and training to farmers. The document concludes that further development of the livestock sector could significantly benefit Pakistan's economy.
Cyber Governemace In Pakistan
This presentation is about the Cyber Governemance in Pakistan, it clarifys the laws, Bills and Punishments for cyber crimes in the world and perticulary Pakistan.
Technology Transfer
Technology transfer involves applying technology developed for one purpose to a new use or user. It is important to choose the right technology - one that is not outdated, meets present and future demand, is cost effective and productive, and helps develop local skills. Models of technology transfer include licensing, science parks, hiring skilled employees, and technology transfer units. For inward technology transfer to be successful, organizations must be open to innovation adoption - from innovators and initiators to later adopters. The Intellectual Property Organization of Pakistan aims to integrate IP infrastructure to support achievement as an IP-based nation. Pakistan needs clear long-term policies to enhance technological capabilities through technology transfer and diffusion.
Manhattan Project
This Presentation is prepared by Shakeel Ahmed, the topic is about the Manhattan Project, the development is Atomic Bomb in USA.
Global Warming
This Presentation is regarding the Global warming, the causes and cure. This was made by Shakeel Ahmed to be presented at Mehran University Institute of Science and Technology Development Jamshoro Sindh Pakistan.
More from Shakeel Ahmed (11)
Climate Change Environmental Policy 2005, Pakistan
Climate Change Environmental Policy 2005, Pakistan
Recently uploaded
Executive Directors Chat Leveraging AI for Diversity, Equity, and Inclusion
Let’s explore the intersection of technology and equity in the final session of our DEI series. Discover how AI tools, like ChatGPT, can be used to support and enhance your nonprofit's DEI initiatives. Participants will gain insights into practical AI applications and get tips for leveraging technology to advance their DEI goals.
Thesis Statement for students diagnonsed withADHD.ppt
Presentation required for the master in Education.
Advanced Java[Extra Concepts, Not Difficult].docx
This is part 2 of my Java Learning Journey. This contains Hashing, ArrayList, LinkedList, Date and Time Classes, Calendar Class and more.
June 3, 2024 Anti-Semitism Letter Sent to MIT President Kornbluth and MIT Cor...
Letter from the Congress of the United States regarding Anti-Semitism sent June 3rd to MIT President Sally Kornbluth, MIT Corp Chair, Mark Gorenberg
Dear Dr. Kornbluth and Mr. Gorenberg,
The US House of Representatives is deeply concerned by ongoing and pervasive acts of antisemitic
harassment and intimidation at the Massachusetts Institute of Technology (MIT). Failing to act decisively to ensure a safe learning environment for all students would be a grave dereliction of your responsibilities as President of MIT and Chair of the MIT Corporation.
This Congress will not stand idly by and allow an environment hostile to Jewish students to persist. The House believes that your institution is in violation of Title VI of the Civil Rights Act, and the inability or
unwillingness to rectify this violation through action requires accountability.
Postsecondary education is a unique opportunity for students to learn and have their ideas and beliefs challenged. However, universities receiving hundreds of millions of federal funds annually have denied
students that opportunity and have been hijacked to become venues for the promotion of terrorism, antisemitic harassment and intimidation, unlawful encampments, and in some cases, assaults and riots.
The House of Representatives will not countenance the use of federal funds to indoctrinate students into hateful, antisemitic, anti-American supporters of terrorism. Investigations into campus antisemitism by the Committee on Education and the Workforce and the Committee on Ways and Means have been expanded into a Congress-wide probe across all relevant jurisdictions to address this national crisis. The undersigned Committees will conduct oversight into the use of federal funds at MIT and its learning environment under authorities granted to each Committee.
• The Committee on Education and the Workforce has been investigating your institution since December 7, 2023. The Committee has broad jurisdiction over postsecondary education, including its compliance with Title VI of the Civil Rights Act, campus safety concerns over disruptions to the learning environment, and the awarding of federal student aid under the Higher Education Act.
• The Committee on Oversight and Accountability is investigating the sources of funding and other support flowing to groups espousing pro-Hamas propaganda and engaged in antisemitic harassment and intimidation of students. The Committee on Oversight and Accountability is the principal oversight committee of the US House of Representatives and has broad authority to investigate “any matter” at “any time” under House Rule X.
• The Committee on Ways and Means has been investigating several universities since November 15, 2023, when the Committee held a hearing entitled From Ivory Towers to Dark Corners: Investigating the Nexus Between Antisemitism, Tax-Exempt Universities, and Terror Financing. The Committee followed the hearing with letters to those institutions on January 10, 202
ANATOMY AND BIOMECHANICS OF HIP JOINT.pdf
it describes the bony anatomy including the femoral head , acetabulum, labrum . also discusses the capsule , ligaments . muscle that act on the hip joint and the range of motion are outlined. factors affecting hip joint stability and weight transmission through the joint are summarized.
Pollock and Snow "DEIA in the Scholarly Landscape, Session One: Setting Expec...
Pollock and Snow "DEIA in the Scholarly Landscape, Session One: Setting Expec...National Information Standards Organization (NISO)
This presentation was provided by Steph Pollock of The American Psychological Association’s Journals Program, and Damita Snow, of The American Society of Civil Engineers (ASCE), for the initial session of NISO's 2024 Training Series "DEIA in the Scholarly Landscape." Session One: 'Setting Expectations: a DEIA Primer,' was held June 6, 2024.Top five deadliest dog breeds in America
Thinking of getting a dog? Be aware that breeds like Pit Bulls, Rottweilers, and German Shepherds can be loyal and dangerous. Proper training and socialization are crucial to preventing aggressive behaviors. Ensure safety by understanding their needs and always supervising interactions. Stay safe, and enjoy your furry friends!
Digital Artifact 1 - 10VCD Environments Unit
Digital Artifact 1 - 10VCD Environments Unit - NGV Pavilion Concept Design
How to Manage Your Lost Opportunities in Odoo 17 CRM
Odoo 17 CRM allows us to track why we lose sales opportunities with "Lost Reasons." This helps analyze our sales process and identify areas for improvement. Here's how to configure lost reasons in Odoo 17 CRM
DRUGS AND ITS classification slide share
Any substance (other than food) that is used to prevent, diagnose, treat, or relieve symptoms of a
disease or abnormal condition
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...Dr. Vinod Kumar Kanvaria
Exploiting Artificial Intelligence for Empowering Researchers and Faculty,
International FDP on Fundamentals of Research in Social Sciences
at Integral University, Lucknow, 06.06.2024
By Dr. Vinod Kumar KanvariaRecently uploaded (20)
Liberal Approach to the Study of Indian Politics.pdf
Liberal Approach to the Study of Indian Politics.pdf
Executive Directors Chat Leveraging AI for Diversity, Equity, and Inclusion
Executive Directors Chat Leveraging AI for Diversity, Equity, and Inclusion
Thesis Statement for students diagnonsed withADHD.ppt
Thesis Statement for students diagnonsed withADHD.ppt
Film vocab for eal 3 students: Australia the movie
Film vocab for eal 3 students: Australia the movie
June 3, 2024 Anti-Semitism Letter Sent to MIT President Kornbluth and MIT Cor...
June 3, 2024 Anti-Semitism Letter Sent to MIT President Kornbluth and MIT Cor...
Pollock and Snow "DEIA in the Scholarly Landscape, Session One: Setting Expec...
Pollock and Snow "DEIA in the Scholarly Landscape, Session One: Setting Expec...
How to Manage Your Lost Opportunities in Odoo 17 CRM
How to Manage Your Lost Opportunities in Odoo 17 CRM
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...
Exploiting Artificial Intelligence for Empowering Researchers and Faculty, In...
Software Failure Air Traffic Control System
- 1. Software Failure: Air Traffic Control System Presented by: S.A Arain & A.R Shaikh Dated: 10-11-2009 Mehran University Institute of Science and Technology Development