10Ch.
Dependable Systems
Distinguish the properties before choosing a mechanism.
Reading, map, offline copy
Your review mark stays on this device.
CPIT-455 · Software Engineering II
Understand the system.
Defend your decision.
افهم النظام، ثم دافع عن قرارك.
Nine chapters from Sommerville. In each one you learn a single mechanism, check it against the named source, and submit one decision on Blackboard.
Code Coverage is practised in every Python build of Assignments 3–9: the build record measures which lines and branches your own tests run; you change one input, run again, and name the branch still untested.
Taught by Professor Adeeb Noor · Faculty of Computing and Information Technology, Jeddah
هذا الأسبوع · عشر دقائق
وطن آمن ووعي رقمي
المحاور الأربعة التي وجّهت بها الجامعة، ونشاط قصير: تحقّق قبل أن تنشر، نفحص فيه الرسالة كما نفحص أي ادعاء هندسي، بخطوات الواجبات نفسها: FIT · EVIDENCE · BOUND · ACT. افتح النشاط
Safe homeland, digital awareness: a ten-minute activity this week. Open it.
Course at a glance
What each chapter is assessed by
| Ch. | Chapter | Course outcomes (CLO) | Assignment | Examinations |
|---|---|---|---|---|
| 10 | Dependable Systems | 1, 2 | Assignment 1 | Midterm · final |
| 11 | Reliability Engineering | 1, 2, 3 | Assignment 2 | Midterm · final |
| 12 | Safety Engineering | 4, 11 | Assignment 3 | Midterm · final |
| 13 | Security Engineering | 2, 5, 11 | Assignment 4 | Midterm · final |
| 14 | Resilience Engineering | 6, 11 | Assignment 5 | Midterm · final |
| 15 | Software Reuse | 7, 11 | Assignment 6 | Final |
| 16 | Component-based Software Engineering | 8, 11 | Assignment 7 | Final |
| 17 | Distributed Software Engineering | 9, 11 | Assignment 8 | Final |
| 20 | Systems of Systems | 10, 11 | Assignment 9 | Final |
| — | Test cases and code coverage | 11 | Coverage step, Assignments 3–9 | Final |
Grade: assignments 30, midterm examination 30, final examination 30, participation 10 (how the course is graded). The final examination covers the whole course, including test cases and code coverage (CLO 11). The outcomes are listed in the course specification. In the revised IT program plan, this course is IT 456 Dependable Systems.
الدرجة: الواجبات 30، والاختبار النصفي 30، والاختبار النهائي 30، والمشاركة 10. الاختبار النهائي يشمل المقرر كله، ومنه حالات الاختبار وتغطية الشيفرة (دليل المراجعة). ويقابل هذا المقرر في الخطة المحدثة المقرر IT 456.
Sommerville 10–17 and 20
Chapters
Showing all 9 chapters.
01
Dependable systems
Name the failure before you choose a control.
11Ch.
Reliability Engineering
Make the denominator and operating profile explicit.
Reading, map, offline copy
Your review mark stays on this device.
12Ch.
Safety Engineering
Trace one hazard to a requirement and a verification activity.
Reading, map, offline copy
Your review mark stays on this device.
13Ch.
Security Engineering
Turn a misuse case into an observable security test.
Reading, map, offline copy
Your review mark stays on this device.
14Ch.
Resilience Engineering
Preserve the essential service while naming the recovery risk.
Reading, map, offline copy
Your review mark stays on this device.
02
Reuse, with a contract
Judge what you inherit, then verify the composition.
15Ch.
Software Reuse
Compare fit and lifecycle constraints before selecting a product.
Reading, map, offline copy
Your review mark stays on this device.
16Ch.
Component-based Software Engineering
Check semantic compatibility as well as interface signatures.
Reading, map, offline copy
Your review mark stays on this device.
03
Across a boundary
Remote failure, other owners, and behavior you did not design.
17Ch.
Distributed Software Engineering
Explain what happens when a remote response is lost.
Reading, map, offline copy
Your review mark stays on this device.
20Ch.
Systems of Systems
Make a useful decision when constituent owners retain control.
Reading, map, offline copy
Your review mark stays on this device.
Notes
Assessment
How a chapter is assessed
Class is twenty slides and one shared case. The assignment uses a different case. State the fit, the bound, the act and the evidence. Commit before the stress test, then justify any refit. Export and submit on Blackboard.
Practice
An assistant that questions you
It reads the approved lecture and presses a vague claim. It does not write the assignment. AI is a transfer/practice layer inside the chapters. The assessed assignment stays the chapter task, not a separate AI-only outcome. Part A, the stress test and the submission stay on this site.
Read https://adeebnoor.github.io/CPIT/ai/iscarb-coach.md and https://adeebnoor.github.io/CPIT/ai/ch13.md, then coach me on Chapter 13.
Change the chapter number. Declare any AI use. Do not share your name or student ID. If a link will not open, download the file and attach it.
Saudi alignment
Jaheziah and NELC
Each lecture has two reference slides. They do not change the route or the assessment. Formal outcome codes need program approval. This is consistency with the NELC framework, version 1.0, September 2026 — not certification, endorsement or approval by NELC.
Scope
What this site is, and is not
Sommerville chapters 10–17 and 20. Code Coverage is practised in the coverage step of every build in Assignments 3–9. The outcome map shows which course outcomes each chapter supports.
Feedback on Qeeem is optional and does not affect your grade. Say what you actually experienced. No private details, and no claim you cannot support.