[go: up one dir, main page]

0% found this document useful (0 votes)
217 views24 pages

Real Time System Assignment

The document discusses real time systems and provides explanations and examples for several statements regarding real time systems: 1) It clarifies that a hard real time application may contain both hard and non-real time tasks. 2) It explains that not all safety critical systems contain fail-safe states as failure in some could lead to loss of life. 3) It confirms that a deadline constraint between stimuli is a behavioral constraint on the system environment. 4) It distinguishes the differences between hard, firm, and soft real time systems and their tolerance for missing deadlines.

Uploaded by

Chandia Panda
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
0% found this document useful (0 votes)
217 views24 pages

Real Time System Assignment

The document discusses real time systems and provides explanations and examples for several statements regarding real time systems: 1) It clarifies that a hard real time application may contain both hard and non-real time tasks. 2) It explains that not all safety critical systems contain fail-safe states as failure in some could lead to loss of life. 3) It confirms that a deadline constraint between stimuli is a behavioral constraint on the system environment. 4) It distinguishes the differences between hard, firm, and soft real time systems and their tolerance for missing deadlines.

Uploaded by

Chandia Panda
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/ 24

Real time system Assignment

Unit-1
2 marks
State whether the following statements are TRUE or FALSE. Justify
your answer.

1) A hard real‐time application consists of only hard real‐time tasks.

 A hard real‐time application consists of only hard real‐time tasks. It is


FALSE.
 A hard real‐time application may also contain several non‐real‐time
tasks such as logging activities etc.

2) Every safety‐critical real‐time system contains a fail‐safe state.

 Every safety‐critical real‐time system contains a fail‐safe state. It is


FALSE.
 It is false because having fail‐safe states in safety‐critical real‐time
systems is meaningless because failure of a safety‐critical system
can lead to loss of lives, cause damage, etc. E.g.: a navigation
system on‐board an aircraft.

3) A deadline constraint between two stimuli is a behavioral constraint on


the environment of the system.

 A deadline constraint between two stimuli is a behavioral constraint


on the environment of the system. The statement is TRUE.
 This is because it is a behavioral constraint since the constraint is
imposed on the second stimulus event.

4) Hardware fault‐tolerance techniques are easily adaptable to provide


software fault‐tolerance.
 Hardware fault‐tolerance techniques are easily adaptable to provide
software fault‐tolerance. The statement is FALSE.
 This is because Hardware fault‐tolerance is usually achieved using
redundancy techniques. However, the propertyof statistical
correlation of failures for software renders the technique ineffective.

5) A good algorithm for scheduling of hard real‐time tasks tries to complete


each task in the shortest possible time.

 A good algorithm for scheduling of hard real‐time tasks tries to


complete each task in the shortest possible time. The statetement is
FALSE.
 This is because a scheduling algorithm for hard real‐time tasks is
only concerned with completing the tasks before the deadlines.
 Unlike desktop applications, there is no benefit in completing each
task in the shortest possible time.

6) All hard real‐time systems usually are safety‐critical in nature.

 All hard real‐time systems usually are safety‐critical in nature. The


statetement is FALSE.
 This is because not all hard real‐time systems are safety‐critical in
nature. E.g.: computer games, etc.

7) It is ensured by the performance constraints on a real‐time system that


the environment of the system is well‐behaved.

 It is ensured by the performance constraints on a real‐time system


that the environment of the system is well‐behaved. The statetement
is FALSE.
 This is because Behavioral constraints on a real‐time system ensure
that the environment of the system is well‐behaved.

8) Soft real‐time tasks do not have any associated time bounds.

 Soft real‐time tasks do not have any associated time bounds. The
statetement is FALSE.
 This is because Soft real‐time tasks also have time bounds
associated with them.
 Instead of absolute values of time, the constraints are expressed in
terms of the average response times required.

9) The objective of any good hard real‐time task scheduling algorithm is to


minimize average task response times.

 The objective of any good hard real‐time task scheduling algorithm is


to minimize average task response times. The statetement is FALSE.
 This is because a good hard real‐time task scheduling algorithm is
concerned with scheduling the tasks such that all of them can meet
their respective deadlines.

10) The goal of any good real‐time operating system to complete every
hard real‐time task as ahead of its deadline as possible.

 The goal of any good real‐time operating system to complete every


hard real‐time task as ahead of its deadline as possible. The
statetement is FALSE.
 This is because a good real‐time operating system should try and
 by real time system? Compare the notation of real complete the tasks
such that they meet their respective deadlines.

5 marks
1) What do you understand time and hard real time? Explain with suitable
example?
 Real time is a level of computer responsiveness that a user senses
as sufficiently immediate or that enables the computer to keep up
with some external process (for example, to present visualizations of
the weather as it constantly changes.
  Real-time is an adjective pertaining to computers or processes that
operate in real time. Real time describes a human rather than a
machine sense of time.
 Real time system means that the system is subjected to real time,
i.e., response should be guaranteed within a specified timing
constraint or system should meet the specified deadline. For
example: flight control system, real time monitors etc.
 In a real‐time application, the notion of time stands for the absolute
time which is quantifiable. In contrast to real time, logical time, used
in most general category applications, deals with a qualitative notion
of time and are expressed using event ordering relations.
 For example, consider the following part of the behavior of library
automation software used to automate the bookkeeping activities of a
college library: “After a query book command is given by the user, the
details of all the matching books are displayed by the software”.
2) Explain the significance of the term real. What do you mean by a real
time system explains with example?

 If you say that someone does something for real, you mean that


they actually do it and do not just pretend to do it.
 But in real time system real mean a particular reliable environment.
 Real time is a level of computer responsiveness that a user senses
as sufficiently immediate or that enables the computer to keep up
with some external process (for example, to present visualizations of
the weather as it constantly changes).
  Real-time is an adjective pertaining to computers or processes that
operate in real time. Real time describes a human rather than a
machine sense of time.
 Real time system means that the system is subjected to real time,
i.e., response should be guaranteed within a specified timing
constraint or system should meet the specified deadline. For
example: flight control system, real time monitors etc.
Types of real time systems based on timing constraints:
Hard real time system:-

 This type of system can never miss its deadline. Missing the deadline
may have disastrous consequences.
 The usefulness of result produced by a hard real time system
decreases abruptly and may become negative if tardiness increases.
Tardiness means how late a real time system completes its task with
respect to its deadline.
 Example: Flight controller system.

Soft real time system:-

 This type of system can miss its deadline occasionally with some
acceptably low probability. Missing the deadline has no disastrous
consequences.
 The usefulness of result produced by a soft real time system
decreases gradually with increase in tardiness.
 Example: Telephone switches.
3) Using a block diagram represent the hardware component of a real time
system. Explain their rules and interaction?

 Real time is a level of computer responsiveness that a user senses


as sufficiently immediate or that enables the computer to keep up
with some external process (for example, to present visualizations of
the weather as it constantly changes.
 We have already pointed out that this book confines itself to the
software issues in real-time systems. However, in order to be able to
see the software issues in a proper perspective, we need to have a
basic conceptual understanding of the underlying hardware. We
therefore in this section try to develop a broad understanding of high
level issues of the underlying hardware in a real-time system.
Sensor:-
 A sensor converts some physical characteristic of its environment into
electrical signals. An example of a sensor is a photo-voltaic cell which
converts light energy into electrical energy.
 A wide variety of temperature and pressure sensors are also used. A
temperature sensor typically operates based on the principle of a
thermocouple.
Actuator:-
 An actuator is any device that takes its inputs from the output
interface of a computer and converts these electrical signals into
some physical actions on its environment.
 The physical actions may be in the form of motion, change of thermal,
electrical, pneumatic, or physical characteristics of some objects.
 A popular actuator is a motor. Heaters are also very commonly used.
Besides, several hydraulic and pneumatic actuators are also popular.
Signal Conditioning Units:-
 The electrical signals produced by a computer can rarely be used to
directly drive an actuator. The computer signals usually need
conditioning.

4) Explain the important differences between hard, firm and soft real‐
time systems?

 A hard real‐time task is one that is constrained to produce its results


within certain predefined time bounds.
 The system is considered to have failed whenever any of its hard
real‐time tasks does not produce its required results before the
specified time bound.
 Unlike a hard real‐time task, even when a firm real‐time task does not
complete within its deadline, the system does not fail.
 The late results are merely discarded. In other words, the utility of the
results computed by a real‐time task becomes zero after the
deadline.
 Soft real‐time tasks also have time bounds associated with them.
 However, unlike hard and firm real‐time tasks, the timing constraints
on soft real‐time tasks are not expressed as absolute values. Instead,
the constraints are expressed in terms of the average response times
required.

5) Identify the timing constraints in your task given with the example and
how they can be categorized into hard, soft, firm real time task?

 The different timing constraints associated with a real‐time system


can be broadly classified into the following categories:
 1) Performance constraints
 2) Behavioral constraints
 Real‐Time Systems:  Each of the performance and behavioral
constraints can further be classified into the following types:
 1) Delay constraint
2) Deadline constraint
3) Duration constraint
 Performance constraints are the constraints that are imposed on the
response of the system. Behavioral constraints are the constraints
that are imposed on the stimuli generated by the environment.
 Behavioral constraints ensure that the environment of a system is
well‐behaved, whereas performance constraints ensure that the
computer system performs satisfactorily.
 Delay constraint means there is a relaxation of time where we can
increase the time period.
 For example train time scheduling.
 In deadline constraint there is no time relaxation that the work should
be complete in given time.
 For example submission of project or in college submission of
assignment that will be done in particular time period.
 But duration constraint a particular time period already given to the
person and within that duration a project should be complete.

6) Explain the key difference between a soft real time task and non real
time task with example?

 A soft real-time system on the other hand will tolerate such lateness,
and may respond with decreased service quality (e.g., omitting
frames while displaying a video).
 Soft real-time systems are typically used where there is some issue
of concurrent access and the need to keep a number of connected
systems up to date with changing situations.
 A non real time tasks are batch processing jobs, e –mail and
background tasks such an event loggers.
 We may, however, argue that even these tasks, in the strict sense of
the term, do have certain time bounds.
 An email is expected to reach its destination at least within a couple
of hours of being sent.
 similar is the case with a batch processing job such a pay-slip printing
what then reality is the difference between a non real task and a soft
real time task for non real time tasks
 The associated time bounds are typically of the order of a few
minutes hours or even days .in contrast the time bounds associated
with soft real time tasks are at most of the order.

7) Explain the important characteristic of two type of task?

 The system is subjected to real time, i.e. response should be


guaranteed within a specified timing constraint or system should meet
the specified deadline. For example flight control system, real-time
monitors etc.
There are two types of tasks in real-time systems:
1. Periodic tasks
2. Dynamic tasks
Periodic Tasks
 In periodic task, jobs are released at regular intervals. A periodic task
is one which repeats itself after a fixed time interval. A periodic task is
denoted by five tuples
Ti = < Φi, Pi, ei, Di >
Where,
 Φi – is the phase of the task. Phase is release time of the first
job in the task. If the phase is not mentioned then release time of
first job is assumed to be zero.
 Pi – is the period of the task i.e. the time interval between the
release times of two consecutive jobs.
 ei – is the execution time of the task.
 Di – is the relative deadline of the task.

Dynamic Tasks
 It is a sequential program that is invoked by the occurrence of an
event. An event may be generated by the processes external to the
system or by processes internal to the system. Dynamically arriving
tasks can be categorized on their criticality and knowledge about their
occurrence times.
1. Aperiodic Tasks: In this type of task, jobs are released at arbitrary
time intervals i.e. randomly. Aperiodic tasks have soft deadlines or no
deadlines.
2. Sporadic Tasks: They are similar to periodic tasks i.e. they repeat at
random instances. The only difference is that sporadic tasks have hard
deadlines. A speriodic task is denoted by three tuples: Ti =(ei, gi, Di)
Where
ei – the execution time of the task.
gi – the minimum separation between the occurrence of two
consecutive instances of the task.
Di – the relative deadline of the task.

Characteristics of Real-Time Systems

Time constraints

 Every real-time task is associated with some time constraints. One


form of time constraints that is very common is deadlines associated
with tasks.
 A task deadline specifies the time before which the task must
complete and produce the results. Other types of timing constraints
are delay and duration.
 It is the responsibility of the real-time operating system (RTOS) to
ensure that all tasks meet their respective time constraints.
New Correctness Criterion

 The notion of correctness in real-time systems is different from that


used in the context of traditional systems. In real-time systems,
correctness implies not only logical correctness of the results, but the
time at which the results are produced is important. A log

8) Mention any two important sensors devices and two actuator devices
use in real time applications and mention their working principle?

Temperature sensors

 By definition, “A device, used to measure amount of heat energy


that allows detecting a physical change in temperature from a
particular source and converts the data for a device or user, is
known as a Temperature Sensor.”
 Proximity sensors are largely used in the retail industry, as they
can detect motion and the correlation between the customer and
product they might be interested in. A user is immediately notified
of discounts and special offers of nearby products.
 Another big and quite an old use-case are vehicles. You are
reversing your car and are alarmed about an obstacle while taking
reverse, that’s the work of proximity sensor.
Pressure sensor
 A pressure sensor is a device that senses pressure and converts it
into an electric signal. Here, the amount depends upon the level of
pressure applied.
 There are plenty of devices that rely on liquid or other forms of
pressure. These sensors make it possible to create IoT systems
that monitor systems and devices that are pressure propelled. With
any deviation from standard pressure range, the device notifies the
system administrator about any problems that should be fixed.
 Deployment of these sensors is not only very useful in
manufacturing, but also in the maintenance of whole water systems
and heating systems, as it is easy to detect any fluctuation or drops
in pressure.

Actuators

 Actuator is an element that manipulates one or more of the variables


of the plant being controlled in such a way that the required output is
achieved. Actuator receives a signal proportional to the difference
between the reference input and the output.

Robotic arms

 One actuator is robotic arms that are mainly used in the manufacture
company of any car and bike. The robotic adjusts the parts of car
inside the cabinet.

 There is a lot of work associated with robotic or prosthetic arms,


devices which need to bend and move – for which actuators are
needed. Most industrial robots are based on gears and continuously
rotating motors. However, just as some sensors can be inspired by
nature, as in echo location, so are some actuators. So let’s consider
the human arm and hand.

 The human arm and hand is very intricate and dexterous - it is a


challenge to make an artificial one. To illustrate the challenge,
although a robot with six joints can be programmed to move to a
specific position if there are no objects, a human will typically use at
least 27 movements allowing us to reach around, under or into
objects as well as going to the right position.

9) Design a model for highlighting the component of hard real time system
also explain how to perform digital to analog and analog to digital
conversion via different interface?

Designing component based real-time systems

 In this section we present a method for system development using


real-time components. This method is an extension of, which is also
in use in developing real-time systems within a Swedish automobile
manufacturing company.

 It is a standard top-down development process to which timing and


other real-time specific constraints have been added and precisely
defined at design time.

 The idea is to implement the same principles, but also taking into
consideration features of existing components which might be used in
the system.

 This means that the system is designed not only in accordance with
the system requirements, but also with respect to existing
components. This concept assumes that a library of well-defined real-
time components is available.

 The development process requires a system specification, obtained


by analyzing the customer's requirements. We assume that the
specification is consistent and correct, in order to simplify the
presentation of the method.

Analog to digital conversion

 Digital-to-analogue conversion is frequently required in a digital


system used to control some external analogue circuitry.
 The D/A converter gives a controlled analogue output voltage or,
in certain specialist applications, a controlled analogue output
current or another circuit parameter such as resistance, whose
value corresponds to an input digital word.

 Here it will be assumed that the digital input is a conventional


positive base 2 integer. If the digital input is in some other
numerical format, it can be converted to base 2 as described
elsewhere in this text.

 If the output is required to be bipolar, that is, the numerical input


may have either positive or negative polarity to produce either
positive or negative output voltages or currents, and then this may
be most easily handled by two separate converters.

10) In a hard RTS is it necessary that every task in the system will be of
hard real time type? Explain with example.

 Contain only tasks with no hard timing constraints. Also known as


“best effort” systems.

 Most modern operating systems can serve as the base for soft real
time systems. Examples: multimedia transmission and reception,
networking, telecom (cellular) networks, web sites and services,
computer games.

 Contains tasks with hard timing constraints. Requires formal


verification/guarantees of being to always meet its hard deadlines
(except for fatal errors).

 Examples: air traffic control , vehicle subsystems control, medical


systems

 There are two different execution models:

 In a preemptive model of execution a task may be interrupted during


its execution and another task run in its place.

 In a non-preemptive model of execution after a task that starts


executing no other task may execute until this task concludes or
yields the CPU.
 The task model for a real time system has two main types.

11) In the context of real time fault tolerance explain software and hardware
failure?

Fault Tolerance

 Fault tolerance is defined as how to provide, by redundancy, service


complying with the specification in spite of faults having occurred or
occurring.
 There are some important concepts buried within the text of this
definition that should be examined. Primarily, Laprie argues that fault
tolerance is accomplished using redundancy.
 This argument is good for errors which are not caused by design
faults, however, replicating a design fault in multiple places will not
aide in complying with a specification. It is also important to note the
emphasis placed on the specification as the final arbiter of what is an
error and what is not.

Software Fault Tolerance

 Software fault tolerance is mostly based on traditional hardware fault


tolerance. N-version programming closely parallels N-way
redundancy in the hardware fault tolerance paradigm. Recovery
blocks, are modeled after what Rendell discovered was the current
ad hoc method being employed in safety critical software. 
 Current software fault tolerance methods are based on traditional
hardware fault tolerance.

 The deficiency with this approach is that traditional hardware fault


tolerance was designed to conquer manufacturing faults primarily,
and environmental and other faults secondarily.

 Software fault tolerance tries to leverage the experience of hardware


fault tolerance to solve a different problem, but by doing so creates a
need for design diversity in order to properly create a redundant
system.

Hardware Fault Tolerance


 Current software fault tolerance is based on traditional hardware fault
tolerance.
 Both hardware and software fault tolerance are beginning to face the
new class of problems of dealing with design faults.
 Hardware designers will soon face how to create a microprocessor
that effectively uses one billion transistors; as part of that daunting
task, making the microprocessor correct becomes more challenging.
In the future, hardware and software may cooperate more in
achieving fault tolerance for the system as a whole.

Failure
 A failure is a term used to describe an issue with the computer or a
device that prevents it from functioning properly. For example, when
a hard drive fails (hardware failure), it prevents the computer from
booting and prevents it from working again until it is replaced.

Hardware Failure

 Hardware failures are inevitable but random events in the useful life


of any batch chemical plant. If such incidents are not efficiently
diagnosed, the consequences may be very serious and sometimes
even catastrophic.
 The present study aims to develop a systematic procedure-synthesis
strategy for generating the test plans that minimize the chance of
misjudgments.
  By modeling the components in the given system with timed
automata, all possible fault propagation scenarios and their
observable event traces (OETs) can be enumerated. 

Software Failure

 Software failures or incorrect software requirements can have severe


consequences including customer dissatisfaction, the loss of financial
assets and even the loss of human lives. 
 Software Quality Models (SQMs) can be used toward providing a
reliable and high-quality software product.
 By detecting likely faulty modules, SQMs allow improvement efforts to
be focused on software modules with higher risks.
 Resources can then be allocated for software testing, inspection, and
quality enhancement of the most likely faulty modules prior to system
release. In the context of two-group classification, SQMs
can classify modules as either fault-prone (fp) or not fault-prone (nfp).

12) Describe different software fault tolerance technique with their


advantages?

Software Fault Tolerance

 Software fault tolerance is mostly based on traditional hardware fault


tolerance. N-version programming closely parallels N-way
redundancy in the hardware fault tolerance paradigm. Recovery
blocks, are modeled after what Rendell discovered was the current
ad hoc method being employed in safety critical software. 
 Current software fault tolerance methods are based on traditional
hardware fault tolerance.

 The deficiency with this approach is that traditional hardware fault


tolerance was designed to conquer manufacturing faults primarily,
and environmental and other faults secondarily.

 Software fault tolerance tries to leverage the experience of hardware


fault tolerance to solve a different problem, but by doing so creates a
need for design diversity in order to properly create a redundant
system.

Software Fault-Tolerance Techniques

 Two methods are now popularly being used to achieve software fault-
tolerance: N-version programming and recovery block techniques.
These two techniques are simple adaptations of the basic techniques
used to provide hardware fault-tolerance. We discuss these two
techniques in the following.

N-Version Programming:

 This technique is an adaptation of the TMR technique for hardware


fault-tolerance. In the N-version programming technique, independent
teams develop N different versions of a software component.
 The redundant modules are run concurrently. The results produced
by the different versions of the module are subjected to voting at run
time and the result on which majority of the components agree is
accepted.
 The central idea behind this scheme is that independent teams would
commit different types of mistakes, which would be eliminated when
the results produced by them are subjected to voting. However, this
scheme is not very successful in achieving fault-tolerance, and the
problem can be attributed to statistical correlation of failures.
 Statistical correlation of failures means that even though individual
teams worked in isolation to develop the different versions of a
software component, still the different versions fail for identical
reasons.
 In other words, the different versions of a component show similar
failure patterns. This does not mean that the different modules
developed by independent programmers, after all, contain identical
errors. The reason for this is not far to seek, programmers commit
errors in those parts of a problem which they perceive to be difficult -
and what is difficult to one team is usually difficult to all teams. So,
identical errors remain in the most complex and least understood
parts of a software component.

Recovery Blocks

 In the recovery block scheme, the redundant components are called


try blocks.
 Each try block computes the same end result as the others but is
intentionally written using a different algorithm compared to the other
try blocks.
 In N-version programming, the different versions of a component are
written by different teams of programmers, whereas in recovery block
different algorithms are used in different try blocks.
 Also, in contrast to the N version programming approach where the
redundant copies are run concurrently, in the recovery block
approach they are run one after another. The results produced by a
try block are subjected to an acceptance test. If the test fails, then the
next try block is tried.
13) Explain check pointing and rollback recovery method for fault tolerance
real time computing. List the fault it can tolerate along with the fault it
cannot tolerate?

Checkpoint-Recovery

 Checkpoint-Recovery is a common technique for imbuing a program


or system with fault tolerant qualities, and grew from the ideas used
in systems which employ transaction processing.

 It allows systems to recover after some fault interrupts the system,


and causes the task to fail, or be aborted in some way. While many
systems employ the technique to minimize lost processing time, it
can be used more broadly to tolerate and recover from faults in a
critical application or task.

 The basic idea behind checkpoint-recover is the saving and


restoration of system state. By saving the current state of the system
periodically or before critical code sections, it provides the baseline
information needed for the restoration of lost state in the event of a
system failure. While the cost of checkpoint-recovery can be high, by
using techniques like memory exclusion, and by designing a system
to have as small a critical state as possible may minimize the cost of
check pointing enough to be useful in even cost sensitive embedded
applications.

 When a system is check pointed, the state of the entire system is


saved to non-volatile storage. The check pointing mechanism takes a
snapshot of the system state and stores the data on some non-
volatile storage medium. Clearly, the cost of a checkpoint will vary
with the amount of state required to be saved and the bandwidth
available to the storage mechanism being used to save the state.

Rollback recovery

 Rollback recovery is a backward error recovery technique for


recovering from transient faults in computing systems.
 Real-time systems employing fault tolerance and reconfiguration
generally have time-dependent constraints.
 The author presents a novel rollback point insertion strategy which
evaluates the rollback conditions on-line.
 The technique minimizes both time and space overhead associated
with rollback, thereby making it applicable to real-time systems with
dynamic constraints. The algorithm presented attains a near-optimum
solution in terms of the time spent in saving the states of the system.
 Details of the simulation conducted to validate the technique are also
given.
 The simulation study has established that the degradation in
performance due to using the proposed algorithms is insignificant and
the precomputation time is very small for programs that can be
represented by general acyclic graphs. On the other hand, for
structured programs that can be represented by a simple sequence of
tasks, the computation overhead is almost zero.

14) What are the main technique available to achieve hardware fault
tolerance and why it is easier than software fault tolerance?
 The popular technique to achieve hardware fault‐tolerance is through
redundancy.

The Concept of Redundancy

 Redundancy is simply the addition of information, resources, or time


beyond what is needed for normal system operation.

 Hardware redundancy is the addition of extra hardware, usually for


the purpose either detecting or tolerating faults.

 Software redundancy is the addition of extra software, beyond what


is needed to perform a given function, to detect and possibly tolerate
faults.

 Information redundancy is the addition of extra information beyond


that required to implement a given function; for example, error
detection codes.

 However, it much harder to achieve software fault‐tolerance


compared to hardware fault‐tolerance.

 A few approaches have been proposed for software modeled on the


redundancy techniques used in achieving hardware fault‐tolerance.

 The reason is the statistical correlation of failures for software.

 The different versions of a software component show similar failure


patterns, i.e., they fail due to identical reasons.

 Moreover, fault‐tolerance using redundancy can only be applied to


real‐time tasks if they have large deadlines.

 Time redundancy uses additional time to perform the functions of a


system such that fault detection and often fault tolerance can be
achieved.

 Transient faults are tolerated by this approach. The use of


redundancy can provide additional capabilities within a system. But
redundancy can have very important impact on a system's
performance, size, and weight and power consumption.
15) What do you mean by fail safe state of a system? What do you mean
by the statement safety critical real time system, do not have a failsafe
state?

 A fail‐safe state of a system is one which if entered when the system


fails, no damage would result.
 All traditional non‐real‐time systems do have one or more fail‐safe
states.  
 However, safety‐critical systems do not have a fail‐safe state.
 A safety‐critical system is one whose failure can cause severe
damages. This implies that the reliability requirement of a safety‐
critical system is very high.

 A safety-critical system  or life-critical system is a system whose


failure or malfunction may result in one or more of the following
outcomes:

1) Death or serious injury to people

2) Loss or severe damage to


equipment/property

3) Environmental harm

 Examples of Critical Systems-: Safety-Critical Medical Devices,


Aerospace Civil aviation, Military aviation, manned space travel
Chemical Industry, Nuclear Power Stations, Traffic control, Railway
control system, Air traffic control. Road traffic control, Automotive
control systems. Other military equipment.

17) State the technique to be adopted for developing a high reliable


software product?

 It will crash, and it wastes lot of time and money to create a new
system, and if the system is crash it will not work as a real time
system.
 It loses the reliability, therefore it is necessary to hard real time
systems that safety and reliability depends on each other, and thus
system works as a true hard real time system.

 In traditional systems, safety and reliability are normally considered


to be independent issues.

 It is therefore possible to identify a traditional system that is safe and


unreliable and systems that are reliable but unsafe.

 For ex- word processing software may not be a reliable but is safe,
Software Reliability is an important to attribute of software quality,
together with functionality, usability, performance, serviceability,
capability, install ability, maintainability, and documentation. Software
Reliability is hard to achieve, because the complexity of software
tends to be high. While any system with a high degree of complexity,
including software, will be hard to reach a certain level of reliability,
system developers tend to push complexity into the software layer,
with the rapid growth of system size and ease of doing so by
upgrading the software.

 For example, large next-generation aircraft will have over one million
source lines of software on-board; next-generation air traffic control
systems will contain between one and two million lines; the upcoming
international Space Station will have over two million lines on-board
and over ten million lines of ground support software; several major
life-critical defense systems will have over five million source lines of
software. While the complexity of software is inversely related to
software

18) What is a safety critical system? Is all real time system safety critical? If
not then justify why such system cannot be exits?

Safety critical system

 Safety-critical systems are those systems whose failure could result


in loss of life, significant property damage or damage to the
environment.
 There are many well-known examples in application areas such as
medical devices, aircraft flight control, weapons and nuclear systems.
 Many modern information systems are becoming safety-critical in a
general sense because financial loss and even loss of life can result
from their failure.
 Future safety-critical systems will be more common and more
powerful. From a software perspective, developing safety-critical
systems in the numbers required and with adequate dependability is
going to require significant advances in areas such as specification,
architecture, verification and the software process.
 The very visible problems that have arisen in the area of information
system security suggest that security is a major challenge too.

Non all real time system are not safety critical because

 The successful design of safety-critical systems is difficult and


demands significant attention to detail. Fortunately, an operating
system's emphasis on protection and resource guarantees can make
the job of application developers less arduous.
 Whether we are designing a telecom switch, a piece of medical
equipment, or one of the many complex systems aboard an aircraft,
certain critical parts of the application must be able to operate under
all conditions.
  Indeed, given the steadily increasing speed of processors and the
economically-driven desire to run multiple applications, at varying
levels of criticality, on the same processor, the risks continue to grow.
Consider a blood gas analyzer used in an intensive care unit.
 In order for threads of varying importance to safely coexist in the
same system, the operating system that manages the processor and
other resources must be able to properly partition the software to
guarantee resource availability.
 The key word here is guarantee. Post-design, post-implementation
testing cannot be counted on. Safety-critical systems must be safe at
all times.

19) In a real time system state the difference between a performance


constraint and a behavioral constraint with example?
 Real time system means that the system is subjected to real time,
i.e., response should be guaranteed within a specified timing
constraint or system should meet the specified deadline. For
example: flight control system, real time monitors etc.
 Performance constraints are the constraints that are imposed on the
response of the system. Behavioral constraints are the constraints
that are imposed on the stimuli generated by the environment.
 Behavioral constraints ensure that the environment of a system is
well‐behaved, whereas performance constraints ensure that the
computer system performs satisfactorily.
 Real‐Time Systems:  Each of the performance and behavioral
constraints can further be classified into the following types:
 1) Delay constraint
2) Deadline constraint
3) Duration constraint
 Performance constraints are the constraints that are imposed on the
response of the system. Behavioral constraints are the constraints
that are imposed on the stimuli generated by the environment.
 Behavioral constraints ensure that the environment of a system is
well‐behaved, whereas performance constraints ensure that the
computer system performs satisfactorily.
 Delay constraint means there is a relaxation of time where we can
increase the time period.
 For example train time scheduling.
 In deadline constraint there is no time relaxation that the work should
be complete in given time.
 For example submission of project or in college submission of
assignment that will be done in particular time period.
 But duration constraint a particular time period already given to the
person and within that duration a project should be complete.

You might also like