Portrait of NoorAl Sammarraie
Nooruldeen
ORACLE / DATABASE PROGRAMMING
CONTACT
COURSEWORK / DATABASESORACLE · PL/SQL · IMMIGRATION

Managingcase data.

A second-semester database project that extends an immigration-system schema with PL/SQL logic, reusable routines and audit features.

BACK TO RESEARCH
ORACLE DATABASE / PL/SQL APPLICATIONSEMESTER 2 · GROUP 1074
01 / THE DATABASESCHEMA · BUSINESS RULES · AUDIT

IMMIGRATION DATABASE PROJECT · SEMESTER 2

Move from a relational design to database-side behavior.

ORACLE COURSE PROJECT · PL/SQL REPORT

This report describes a Semester 2 continuation of an immigration database project. It develops the earlier conceptual schema into an Oracle implementation with added tables and fields, PL/SQL procedures and functions, packages, triggers, control structures, cursors, collections and exception handling.

A step forward from the earlier schema

This is a different report from Managing Immigration Papers, the seven-table coursework design shown elsewhere on the site. The Semester 2 document focuses on database programming and behavior built around an expanded model; the two projects are related, but their descriptions and deliverables remain separate.

01 / STRUCTURE

Refined schema

Revises the database model with additional tables and columns, maintaining relationships and constraints for an immigration workflow.

02 / OPERATIONS

Procedures & functions

Encapsulates repeatable tasks and reusable calculations as stored PL/SQL routines.

03 / REUSE

Packages & triggers

Groups related database routines and uses triggers to enforce selected rules or record changes.

04 / CONTROL

Queries & exceptions

Exercises conditions, loops, cursors, collections and exception handling for more involved operations.

From tables to business logic

The report brings together schema refinement and procedural database work. Its examples progress through data definition and manipulation, data copying and backup, dynamic SQL, aggregate queries and conditional logic, then apply PL/SQL constructs to the project.

Across approximately 30 code examples, the document explores routines, sequence-based operations, packages, triggers and audit logging.

Why these pieces matter

Stored routines can keep common operations together; constraints and triggers can help enforce selected rules; audit records can make changes easier to review. Cursors, collections and exception handling extend the kinds of tasks a database program can perform.

Those features still need careful design and testing. The report is coursework documentation, not a deployed immigration service or production-ready security review.