Assignment 64 Instructions: Engineering Report on Development of autonomous driving systems

This engineering report functions as the central evaluative artefact for the module and carries the full weight of the assessment. It has been designed to examine how effectively you can interpret, analyse, and communicate complex engineering developments within the domain of autonomous driving systems. The task values engineering judgment over surface description and rewards intellectual independence grounded in evidence.

The completed report must remain within a 3,000 to 5,000 word range. Work that substantially exceeds or falls below this range often reflects uneven analytical planning. Submission is accepted only through the university’s authorised digital platform. Reports delivered through alternative channels cannot be processed under assessment regulations.

Your identity must not appear anywhere in the document. Only your Student Reference Number (SRN) should be used. The marking scheme allocates 100 marks, with institutional progression dependent on achieving at least 50%.

All external material, including algorithms, architectural diagrams, sensor performance data, standards, and regulatory sources, must be acknowledged using the Harvard referencing system. Any material presented without attribution will be reviewed under academic integrity procedures.

Artificial intelligence tools may assist with proofreading and surface-level language refinement. They must not be used to generate analytical content, engineering interpretations, or evaluative conclusions.

Locating Autonomous Driving within Contemporary Engineering Practice

Understanding Autonomy as a System, Not a Feature

Autonomous driving systems should be approached as multi-layered engineering ecosystems rather than isolated technological upgrades. Perception modules, decision-making algorithms, actuation systems, communication networks, and safety redundancies operate in continuous interaction. The report should demonstrate awareness of this interdependence.

In the UAE context, autonomous vehicle development intersects with smart city initiatives, advanced road infrastructure, extreme environmental conditions, and ambitious mobility strategies. Treating autonomy purely as a software challenge would miss the broader engineering reality.

Selecting a Coherent Technical Emphasis

Rather than attempting to cover the entire field of autonomy, you are expected to anchor your report around a defined engineering dimension. Appropriate focal points may include, but are not limited to:

Sensor fusion architectures integrating LiDAR, radar, and vision systems
Machine learning models for perception and path planning
Control systems and real-time actuation reliability
Safety engineering and fault-tolerant system design
Autonomous driving performance in high-temperature and sand-rich environments

The chosen emphasis should allow for sustained technical depth and critical comparison.

Intent, Audience, and Engineering Responsibility

Professional Orientation of the Report

This report should be written as if addressed to engineering professionals or technical decision-makers engaged in intelligent transportation systems. The intended reader understands engineering fundamentals and expects clarity, justification, and measured reasoning.

The purpose is not advocacy for autonomous vehicles but evaluation of engineering maturity, system readiness, and unresolved challenges.

Establishing Analytical Purpose

Strong reports articulate purpose implicitly through their analytical choices. This usually becomes evident when the report consistently answers:

What engineering problem limits autonomous driving performance or adoption?
How do current system designs attempt to resolve this problem?
What technical compromises accompany these solutions?

Purpose emerges through what you analyse and how you connect evidence, not through declarative statements.

Capabilities Being Assessed Through the Work

Although not itemised as a checklist, this task is designed to surface several advanced competencies, including:

Systems-level thinking across hardware, software, and infrastructure
Interpretation of experimental and simulation-based data
Comparative evaluation of competing design approaches
Awareness of safety, reliability, and ethical constraints
Ability to translate engineering findings into reasoned insight

These capabilities should be visible through the structure and depth of the report rather than explicitly stated.

Analytical Pathways to Be Developed

System Architecture and Technical Foundations

Early sections of the report should establish the technical architecture relevant to your chosen focus. For instance, a report centred on perception systems should explain sensing principles, data pipelines, and latency considerations without drifting into unnecessary abstraction.

Clarity matters more than complexity. Well-explained engineering logic is valued over dense theoretical exposition.

Operational Performance and Environmental Constraints

Autonomous driving systems are sensitive to operational context. UAE conditions introduce challenges related to lighting variation, temperature extremes, dust interference, and infrastructure layout. Your analysis should consider how system performance shifts under these constraints.

Where appropriate, compare controlled test results with real-world deployment data and discuss performance gaps.

Evidence-Driven Evaluation

The analytical core must rely on secondary engineering sources, including peer-reviewed journals, industry white papers, safety reports, and international standards. Comparison across sources is essential.

Effective analysis often highlights disagreement between studies, limitations in experimental design, or assumptions embedded within performance claims.

Safety, Reliability, and System Trust

No discussion of autonomy is complete without attention to safety engineering. This may involve redundancy design, fail-safe mechanisms, validation protocols, or regulatory benchmarks. The report should treat safety as an engineering discipline, not merely a policy concern.

Structural Composition of the Report

While flexibility is encouraged, the following elements should be present and arranged to support a coherent engineering narrative rather than a linear checklist:

Preliminary Components

Academic integrity declaration
Title page
Contents list
Register of figures, tables, and abbreviations where applicable

Core Analytical Elements

A reflective technical overview written after analysis
Contextual positioning of autonomous driving systems
Focused technical evaluation sections
Integrated discussion linking subsystems and outcomes
Forward-looking engineering recommendations

Supporting Documentation

Complete Harvard-formatted reference list
Appendices for extended data, models, or schematics

The report should read as a continuous argument, not a sequence of disconnected responses.

Indicative Word Distribution

The following breakdown is suggestive rather than prescriptive:

Technical overview and framing: ~400 words
System context and engineering background: ~700 words
Core technical evaluation: ~1,500 words
Integrated discussion of implications: ~800 words
Engineering recommendations and synthesis: ~800 words

Adjustments may be made to suit the chosen focus and depth of analysis.

Academic Voice, Style, and Presentation Standards

Your writing should reflect the tone of a developing engineer: precise, analytical, and evidence-aware. Avoid promotional language, speculative claims, or unsupported predictions. Assertions must be grounded in data or clearly framed as reasoned interpretation.

Figures and tables should serve analytical purposes and be fully integrated into the discussion. All symbols, units, and terminology should align with accepted engineering conventions.

Quality of engagement with sources outweighs quantity. A carefully selected body of well-analysed references is preferable to extensive but shallow citation.

Closing Perspective

Autonomous driving systems represent one of the most demanding engineering challenges of the current generation, requiring coordination across sensing, computation, control, and infrastructure. In the UAE, this challenge unfolds within a distinctive environmental and strategic context.

This report is an opportunity to demonstrate that you can move beyond surface familiarity and engage with autonomy as a complex engineering system shaped by real constraints. Approach the task as an engineer contributing to informed technical decision-making. The strength of your submission will be measured by how convincingly your engineering reasoning unfolds across the entire report.