Scribd
Upload
6 views

SE Assignment 1

Uploaded by

Isra Asif
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
6 views

SE Assignment 1

Uploaded by

Isra Asif
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

FATIMA JINNAH WOMEN UNIVERSITY

Department of Computer Science

Name:- Isra Asif Course:- Software Engineering

Reg.No:- 2023-BCS-045 Session:- 2023-2027

Sem/Sec:- BCS-III-A Instructor:- Ma’am Rabail

History’s Biggest Software Failures

No.1:- Therac 25-Software Failure

The Therac-25 incident refers to a


progression of mishaps including a
radiation treatment machine called the
Therac-25 during the 1980s. It was
intended to convey designated radiation
therapy for disease patients, however,
programming blemishes prompted
gigantic excesses of radiation being
directed now and again.

The central questions included:

Programming Bugs: The framework


had basic programming bugs that permitted administrators to convey deadly
dosages of radiation incidentally.

Absence of Wellbeing Elements: The machine's plan didn't have sufficient


security interlocks to forestall inadvertent excesses, depending vigorously on
programming control.

Human Variables: Administrators were now and again deficiently prepared, and
the framework's UI was not natural, which added to the blunders.

Delayed Response: When occurrences happened, there was a sluggish reaction


from the producer to explore and redress the issues.

Somewhere in the range of 1985 and 1987, something like six patients got extreme
excesses, bringing about serious wounds. The Therac-25 case is often referred to in
conversations about programming unwavering quality, well-being in clinical
gadgets, and the significance of thorough testing and security conventions in
FATIMA JINNAH WOMEN UNIVERSITY
Department of Computer Science

programming advancement. It highlighted the requirement for better well-being


measures and administrative oversight in medical care innovation.

No.2:- The Morris Worm, 1988

The Morris Worm, delivered in 1988 by


Robert Tappan Morris, is viewed as one
of the first significant computer worms
to spread across the web. It was
intended to take advantage of
weaknesses in Unix frameworks and
plan to quantify the size of the web. In
any case, because of a coding mistake,
it reproduces itself unreasonably,
causing huge disturbances. The worm
Morris created got out of control and
broke the internet.

The central questions included:

Propagation: The worm spread quickly by taking advantage of known weaknesses


in different Unix frameworks, for example, frail passwords and imperfections in the
Sendmail program.

Impact: It tainted roughly 6,000 PCs to 60,000 PCs, a significant part of the web at
that point. Numerous frameworks became slow or crashed because of the worm's
over-the-top asset utilization.

Response: The episode featured the weakness of organizations and the


requirement for further developed security rehearses. It likewise prompted an
increased familiarity with network protection issues and the foundation of additional
hearty safeguards.

Legal and Moral Consequences: Morris was indicted under the PC


Misrepresentation and Misuse Act, becoming perhaps the earliest person to confront
legitimate ramifications for making a worm. He was condemned to probation, local
area administration, and fines.

Legacy: The Morris Worm is much of the time concentrated on in network


protection courses and is an essential case in conversations about PC security,
FATIMA JINNAH WOMEN UNIVERSITY
Department of Computer Science

moral hacking, and the significance of capable coding rehearses. It likewise


prompted the formation of the main PC Crisis Reaction Group, Computer Emergency
Response Team (CERT) to help oversee and answer network protection episodes.

Overall, the Morris Worm incident was a crucial crossroads throughout the entire
existence of online protection, highlighting the expected outcomes of programming
weaknesses and the significance of organization security.

No.3:- The Mariner 1 Spacecraft, 1962

The Mariner 1 incident in 1962 involved the failure


of the Mariner 1 spacecraft, which was expected
to be the first U.S. mission to Venus. The shuttle
was sent off on July 22, 1962, however, it
experienced a basic failure soon after takeoff.

The central questions included:

Launch Failure: Approximately 293 seconds


after launch, Mariner 1 became sidetracked
because of a direction framework mistake. The
mission was aborted, and the shuttle was
destroyed by the range safety officer to keep it
from turning into a danger.

Cause: The main cause was followed back to a


missing hyphen in the spacecraft's guidance software. This error incorrect
calculations of the spacecraft's trajectory, delivering the direction framework
incapable.

Outcomes: The loss of Mariner 1 resulted in significant financial costs and


postpones in the Mariner program. It featured the significance of programming
confirmation and thorough testing in aerospace projects.

Impact on Future Missions: The incident prompted an expanded examination of


programming improvement rehearses in aeronautic design. Resulting missions
embraced more severe testing conventions and better documentation standards to
prevent similar errors.
FATIMA JINNAH WOMEN UNIVERSITY
Department of Computer Science

Regardless of this mishap, NASA effectively sent off Mariner 2 sometime thereafter,
which turned into the main shuttle to arrive at Venus and accumulate information
about the planet effectively. The Mariner 2 incident remains a basic illustration of
the significance of programming precision and quality in high-stakes engineering
undertakings.

No.4:- Mars Climate Orbiter, Sep 23 1999

The Mars Climate Orbiter incident, which


occurred on September 23, 1999, was a
huge disappointment in a NASA mission
planned to concentrate on the Martian
environment and climate. The shuttle was
lost because of a basic error connected
with software and unit conversion.

The central questions included:

Mission Objectives: The Mars Climate


Orbiter was intended to give significant
information on Mars' environment, climate,
and surface circumstances. It was essential
for NASA's Mars investigation program.

Loss of the Spacecraft: Shortly before entering Mars' orbit, the spacecraft failed
to accomplish the expected direction and on second thought crumbled in the
Martian climate. The misfortune happened because it plunged excessively low and
excessively quickly.

Cause of Failure: The root cause was followed to a mismatch in units: the
engineering team at NASA's Jet Propulsion Laboratory (JPL) used metric units, while
the product given by Lockheed Martin used imperial units (pounds-force rather than
newtons). This inconsistency prompted wrong estimations for the shuttle's direction.

Influence: The occurrence brought about the total loss of the $327 million space
apparatus and incited a broad survey of undertaking the executives and designing
practices inside NASA.

Lessons Learned: The Mars Climate Orbiter incident featured the significance of
thorough quality control, exhaustive documentation, and successful correspondence
FATIMA JINNAH WOMEN UNIVERSITY
Department of Computer Science

between groups, particularly when various units of estimation are involved. Thus,
NASA carried out additional rigid checks and better reconciliation rehearses for
future missions.

The disappointment of the Mars Climate Orbiter remains a wake-up call in advanced
plane design, underlining the basic idea of accuracy in both programming
improvement and between group joint effort.

No.5:- 12X F-22 Raptor, 2007

The "12X F-22 Raptor" incident refers to a notable event that happened in 2007
during a training exercise including different F-22 Raptor fighter jets, specifically
including 12 aircraft. The incident highlighted issues related to communication and
coordination among the planes.

The central questions included:

Context: The F-22 Raptor is a fifth-generation stealth air superiority fighter created
by Lockheed Martin. In 2007, the U.S. Flying Corps was leading a progression of
preparing activities to test the airplane's capacities.

Occurrence Outline: During one specific activity, numerous F-22s participated in a


situation that reenacted an air battle. Issues emerged because of disarray in
correspondence and coordination, prompting issues in the activity of the airplane
during the drill.

Technical Issues: Even though particulars of the specialized issues were not
broadly itemized out in the open reports, such occurrences frequently highlight the
difficulties of overseeing progressed frameworks that demand continuous
correspondence and situational mindfulness among numerous airplanes.

Lessons Learned: The occurrence filled in as a sign of the significance of


compelling correspondence and order and control in complex military tasks. It
likewise supported the requirement for continuous preparation to guarantee that
pilots and ground groups are capable of dealing with both the mechanical and
human variables in high-stakes conditions.

This incident is essential for a more extensive story regarding the functional
difficulties faced by cutting-edge military frameworks, underlining the requirement
for vigorous preparation and coordination among staff.
FATIMA JINNAH WOMEN UNIVERSITY
Department of Computer Science

You might also like