SAUDI NATIONAL ALIGNMENT · CPIT-455 · 28 SEPTEMBER 2026

National reference points.
Evidence of student capability.

Jaheziah focuses attention on learning outcomes. The NELC framework guides the design of AI-supported learning. Here we show how both reference points translate into work that can be reviewed in every chapter.

COURSE SPECIFICATION · ETEC T-104

Course specification

CPIT-455 Software Engineering (II), which corresponds to IT 456 Dependable Systems in the revised IT program plan, presented in the sections of the ETEC course specification template, with the iSCARB teaching and assessment framework mapped to each section. Open the course specification.

USE OF GENERATIVE AI · FCIT POLICY

Use of Generative AI

The course follows the FCIT Generative AI Policy Guide for Course Syllabus of the Faculty of Computing and Information Technology and adopts its Option C, Mixed Approach. Each assessment has its own permitted level: the examinations and the in-class check are AI-Free; Part A of Assignments 6–9 is AI-Free; the Python build and the work after commitment are AI-Assisted, as stated on each assignment page; no assessment is AI-Integrated. Students declare any AI use, and use beyond the permitted level may be treated as academic misconduct. The AI level of every assessment.

Education and Training Evaluation CommissionJaheziah · Learning outcomesNational eLearning CenterNELC · Learning design

National belonging and digital awareness

In the week from 25 October 2026, each section gives ten minutes at the start of one lecture to the four themes set by the university: the Kingdom's standing and the blessing of security; unity, trust in the leadership and appreciation of those who protect the country; digital awareness and responsibility in publishing; and the student's role in awareness and reassurance. In this course the activity uses the course's own reasoning: a message is treated as a claim and checked with FIT, EVIDENCE, BOUND and ACT before it is shared, and a vulnerability is reported through the official channel rather than published. The activity and the lecturer's plan are on the activity page (in Arabic).

01 · Jaheziah

What can the learner do independently?

Chapter concepts build knowledge. Applying them develops skills. Decision boundaries and accountability demonstrate values. Each chapter specifies evidence and a review criterion while retaining its existing objectives and assignments.

Knowledge

Explain an engineering concept from its source and distinguish it from a related concept.

Skills

Apply the concept to the case and produce an inspectable calculation, test or contract.

Values and responsibility

Disclose assistance and limits, name the responsible owner, and revise judgment when evidence changes.

This proposed educational mapping supports readiness. It does not assign official Jaheziah specialization codes or exam weights; those require the approved program crosswalk. Practice questions are authored for this course, not taken from the Jaheziah examination.

02 · NELC · September 2026 framework

Five principles translated into design decisions

01

Learning first

The five objectives and named readings come before the choice of AI assistance.

Evidence: chapter map + source review

02

Clear educational value

AI supports critique of an alternative or examination of an assumption tied to the chapter concept.

Evidence: chapter-specific AI challenge; assistance is optional unless assigned

03

Human-centered design

The learner produces the attempt and argument; the instructor verifies and retains judgment.

Evidence: independent attempt + explanation + human review

04

Responsible design

Use non-sensitive teaching inputs, disclose assistance and check claims independently.

Evidence: AI-use gate + source + claim boundaries

05

Evidence-based improvement

Review the quality of reasoning and revision, then adjust teaching when misconceptions appear.

Evidence: initial and revised decisions + rubric + feedback

Six stages and where to find their evidence

StageApplication in iSCARBEvidence location
1 · DefineFive fixed objectives, the chapter learning need and the required evidence.Chapter map and objectives
2 · DesignOne case, a mechanism explanation, three stations and source review.Lecture and readings
3 · EnhanceCritique, alternatives or simulation with a defined learning purpose.AI lens and application challenge
4 · Assign rolesThe learner explains and decides; AI assists; the instructor designs and reviews.Disclosure, decision owner and reviewer
5 · EvaluateCommit an initial argument before STRESS, then justify REFIT.Mastery v2 + rubric + independent verification
6 · Verify and improveReview the error type and evidence before changing the activity or support.Evaluation and improvement plan below

These pages and activities are designed with reference to the framework. Their presence does not establish educational impact; the instructor checks independent performance and retains final judgment. This site does not call an AI service or provide AI grading.

Two reference slides inside every lecture

Open “Jaheziah readiness” or “NELC alignment” from the lecture toolbar. Each opens a full reference slide for classroom use. “Return to lecture” restores your position. The twenty scientific slides keep their order, alongside the twenty iSCARB rules, objectives and assignments.

Restored vector diagrams preserve the relationships in the original source figures. Detailed explanations, required readings and source links remain available.

9 CHAPTERS · OBSERVABLE EVIDENCE

Connect each chapter to the required work

CH 10

Dependable Systems

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 10.1Distinguish the five properties using one example.FIT + source application
Objective 10.2Trace one failure through people, process and technology.FIT + transfer question
Objective 10.3Explain redundancy, diversity and common-cause failure.BOUND + source application
Objective 10.4Identify evidence from a dependable process.ACT + EVIDENCE
Objective 10.5Explain what formal verification assumes and what it cannot establish.REFIT + EVIDENCE

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

CH 11

Reliability Engineering

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 11.1Distinguish reliability from availability and explain how use and recovery affect them.FIT + transfer question
Objective 11.2Select and calculate POFOD, ROCOF, MTTF and AVAIL; write a measurable requirement.MEASURE
Objective 11.3Compare fault-tolerant architectures and justify a choice with its independence assumptions.ACT + EVIDENCE + source application
Objective 11.4Apply the eight dependable programming guidelines to a failure scenario.ACT + EVIDENCE (source application)
Objective 11.5Design a statistical reliability test using an operational profile and explain its limits.BOUND + REFIT

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

CH 12

Safety Engineering

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 12.1Separate hazard, accident and risk.FIT
Objective 12.2Explain avoidance, detection/removal and damage limitation.TRACE + source application
Objective 12.3Read a fault tree and identify its assumptions.transfer question + TRACE
Objective 12.4Link a safety requirement to a verification method.TRACE + EVIDENCE
Objective 12.5Explain a safety case and the limits of formal/static analysis.BOUND + REFIT

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

CH 13

Security Engineering

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 13.1Distinguish assets, threats, attacks and vulnerabilities.FIT
Objective 13.2Translate a policy into testable requirements.TEST + source application
Objective 13.3Build a misuse case and a control.TEST + transfer question
Objective 13.4Explain layered protection and secure defaults.ACT + EVIDENCE
Objective 13.5Design a negative test and state its coverage limit.BOUND + REFIT

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

CH 14

Resilience Engineering

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 14.1Explain recognition, resistance, recovery and reinstatement.FIT
Objective 14.2Identify organizational and technical dependencies.RECOVER
Objective 14.3Interpret the Swiss Cheese model without assuming independence.transfer question + BOUND
Objective 14.4Perform the stages of survivability analysis.RECOVER + source application
Objective 14.5Trade off degraded service against confidentiality and integrity.REFIT + EVIDENCE

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

CH 15

Software Reuse

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 15.1Compare benefits and costs of reuse.COMPARE
Objective 15.2Select an approach using planning factors.FIT + BOUND
Objective 15.3Explain MVC and inversion of control.transfer question + source application
Objective 15.4Distinguish product-line specialization and configuration.COMPARE + ACT
Objective 15.5Compare COTS solution, COTS integration and ERP.REFIT + EVIDENCE

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

CH 16

Component-Based Software Engineering

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 16.1Describe component characteristics and interfaces.FIT
Objective 16.2Compare development for and with reuse.source application + BOUND
Objective 16.3Choose sequential, hierarchical or additive composition.CONTRACT
Objective 16.4Diagnose interface incompatibility and specify an adapter.transfer question + lab record
Objective 16.5Read an OCL precondition/postcondition and design a test.lab test cases + lab record + REFIT

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

CH 17

Distributed Software Engineering

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 17.1Explain distributed-system design issues.FIT
Objective 17.2Compare RPC and message-based interaction.transfer question + interaction trace
Objective 17.3Distinguish layers and tiers.source application + architecture
Objective 17.4Choose among the five source architectural patterns.FAILURE + lab record
Objective 17.5Explain SaaS configuration, multi-tenancy and scaling.transfer question + BOUND + REFIT

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

CH 20

Systems of Systems

Five objectives and opportunities to demonstrate them
ObjectiveWhat you should be able to doWhere you show it
Objective 20.1Recognize operational and managerial independence.FIT
Objective 20.2Classify SoS and explain three kinds of complexity.transfer question + BOUND
Objective 20.3Explain why reductionist assumptions can fail.source application + FIT
Objective 20.4Plan interfaces, staged deployment and cross-system tests.INTEGRATE + EVIDENCE
Objective 20.5Compare data-feed, container and trading architectures.ACT + REFIT

These are the current chapter learning objectives, not official Jaheziah codes. Performance is reviewed against the rubric; a page visit or one answer does not establish mastery.

A plan to evaluate and improve learning

What to reviewEvidenceImprovement decision
Independent understandingAn instructor-reviewed explanation or new case, with explicit conditions for AI use.Revisit the misunderstood concept and check understanding again.
Value of assistanceThe first attempt, the revision and the reason for accepting or rejecting it.Adjust the hint or reduce support if it starts to replace the learner’s effort.
Quality of reasoningFIT–BOUND–ACT–EVIDENCE followed by STRESS–REFIT, assessed using the rubric.Adjust the case or feedback to address the observed weakness.
Workload and accessibilityLearner and instructor feedback, including reading and navigation difficulties.Simplify presentation and support while preserving the learning outcome.

Student drafts are saved locally and can be exported. Official submission, deadlines and grades remain in Blackboard. Experience feedback informs improvement but is not sufficient evidence of learning.

Sources and alignment scope

The logos identify the reference organizations. Alignment does not imply certification, endorsement or partnership with NELC or ETEC. Official codes, approval of the program crosswalk and verification of educational impact remain separate steps.

This page covers the nine published chapters. Code Coverage, listed in the syllabus, is practised in the coverage step of every build in Assignments 3–9; see the course-outcome map (outcome 11).