Real – time Systems

BITS G553
Introduction
Biju K Raveendran
 Instructor(s)
• Instructor – in – Charge
Biju K Raveendran
Associate Professor
A – 413 / D – 253, Dept. of Computer Science
[email protected]
Consultation time: 10:00 A.M to 6 P.M [Dress
decently when you visit me!!]
Sunday, January 12, 2020 Prof.Biju K Raveendran 2
 Class
• Class Room: D - 101
• Monday – Wednesday – Friday
• 12:00 Noon to 12:50 P.M
• Mid – Semester Examination:
– 2nd March 2020, Monday
– 4:00 P.M to 5:30 P.M
• Comprehensive Examination:
– 10th May 2020, Sunday
– 9:00 A.M to 12:00 Noon
Sunday, January 12, 2020 Prof.Biju K Raveendran 3
 Expectations from you!!
• No entry after 12:03 P.M
• Not allowed to leave in between the class
• Take this course only if you have enough
time to attend almost all the classes
• Keep your mobile phone in pocket [Please
don’t keep it on table]

Sunday, January 12, 2020 Prof.Biju K Raveendran 4

 Course Administration
• Mid – semester: 25% [75 Marks]
• Attendance : 10% [30 Marks]
• Assignments / Projects: 30% [90 Marks]
• Comprehensive: 35% [105 Marks]

Sunday, January 12, 2020 Prof.Biju K Raveendran 5

 Marks for attendance
• GE 90% 30 Marks
• GE 85% and LT 90% 25 Marks
• GE 80% and LT 85% 20 Marks
• GE 75% and LT 80% 15 Marks
• GE 70% and LT 75% 10 Marks
• LT 70 00 Marks

Sunday, January 12, 2020 Prof.Biju K Raveendran 6

 Project / Assignments / Quiz / Online
• Total weightage: 30%
• Project/Assignments: Programming in nature
• No makeup for Project / Assignments / Quiz / Online
• Submitting a blank file is preferred over copying
– If found copied [–1*(weightage of assignment)]
as penalty.
• I use turnitin software for finding copy cases
• See Handout for Malpractice Regulations

Sunday, January 12, 2020 Prof.Biju K Raveendran 7

 Malpractice Regulations
• Any student or team of students found involved
in mal practices in working out assignments will
be awarded negative marks equal to the
weightage of that assignment and will be
blacklisted.
• Any student or team of students found
repeatedly – more than once across all courses
– involved in mal-practices will be reported to
the Disciplinary Committee for further action.
This will be in addition to the sanction
mentioned above.
Sunday, January 12, 2020 Prof.Biju K Raveendran 8
 Malpractice Regulations
• A mal-practice - in this context - will include but not be
limited to:
– Submitting some other’s / team’s solution(s) as one’s own;
– Copying some other’s / team’s data or code or other forms
of a solution;
– Seeing some other’s / team’s data or code or other forms
of a solution;
– Permitting some other student / team to see or to copy or
to submit one’s own solution;
– OR other equivalent forms of plagiarism wherein the
student or team does not work out the solution and/or
uses some other solution or part thereof (such as
downloading it from the web).
Sunday, January 12, 2020 Prof.Biju K Raveendran 9
 Malpractice Regulations
• The degree of mal-practice (the size of the solution
involved or the number of students involved) will
not be considered as mitigating evidence. Failure
on the part of instructor(s) to detect mal-practice at
or before the time of evaluation may not prevent
sanctions later on.

Sunday, January 12, 2020 Prof.Biju K Raveendran 10

 What is expected [technical] ??!!
• Operating Systems, DSA [Adv. Algo.]
– Need not do the course to master it!!
• Decent programming skill [C / C++ / Java]
• Good reading habit [technical books]

Sunday, January 12, 2020 Prof.Biju K Raveendran 11

 Course Outline
• Introduction to RTS and RTOS
• RTS scheduling Algorithms
• Concurrency & access control for OS and RTS
• Virtual memory issues in RTS
• File-systems (Real-Time)
• Data structures & algorithm for RTS
• Real-Time Database
• Real-Time programming and Programming
languages
Sunday, January 12, 2020 Prof.Biju K Raveendran 12
 Course Outline
• Compilers and runtime environment for RTS
• Fault tolerance, Exception handling and Fail safe
design in RTS
• Performance measures for RTS
• Mixed Criticality Real-time Systems
• Real-Time communication & Networking
• Real-Time multi processor & distributed systems
Sunday, January 12, 2020 Prof.Biju K Raveendran 13
 Books
• Text Book:
– You are the best BOOK if you attend and understand
classes. All other books listed are just for reference
• Books
– Jane W S Liu: Real - Time Systems
– G.C. Buttazzo: Hard Real‐Time Computing Systems
– H. Kopetz: Real-time Systems - Design Principles for
Distributed Embedded Applications
– Shaw: Real-Time Systems and Software
– Class notes / Reference papers
• Course Material: http://photon.bits-goa.ac.in/lms/
Sunday, January 12, 2020 Prof.Biju K Raveendran 14
 Application Driven OS - Real-time Systems
• Correctness = Logical result of computation +
time at which the result is produced
• Deadline and Timing constraints
• Usually part of a large cyber physical
system
• Response time = Turn Around Time
– Response time analysis
– Safety / Reliability
• RTS is mostly Reactive systems
Sunday, January 12, 2020 Prof.Biju K Raveendran 15
 • Types
Real-time Systems
– Every practical system is real-time system
– Hard Real Time
• Timing constraint or deadline is hard (if fails it
result in fatal fault)
– Firm real Time
• N deadline miss  complete failure
– Soft Real Time
• A few misses in deadlines do no serious harm,
only the system’s over all performance
becomes poorer and poorer
Sunday, January 12, 2020 Prof.Biju K Raveendran 16