ITEE FE key terms

A long-term plan that aligns an organization's information technology investments and capabilities with its business goals, priorities, and competitive position.

The degree to which technology activities, spending, and priorities match the organization's business objectives so that IT genuinely supports value creation.

The decision rights and accountability framework that determines who makes technology decisions, how they are made, and how performance is monitored and controlled.

A time-sequenced plan showing which initiatives, systems, or capabilities will be delivered in which phases, and how they build on one another.

Any person or group affected by or interested in a project or system, such as users, managers, sponsors, suppliers, or regulators, whose needs must be considered.

The senior person who authorizes a project, secures its funding and resources, and is accountable for its business outcomes and escalation decisions.

A short authorizing document that states a project's purpose, objectives, scope, key stakeholders, and high-level constraints before detailed planning begins.

The defined boundary of what a project or system will and will not deliver, including functions, users, and interfaces covered by the agreement.

A documented statement of what a system must do and the qualities it must have, forming the basis for design, development, and acceptance testing.

A statement describing a specific behavior or function the system must perform, such as calculating a total or sending a notification.

A statement describing a quality or constraint of the system rather than a behavior, such as performance, security, availability, usability, or maintainability targets.

The ongoing process of identifying, assessing, prioritizing, and responding to uncertainties that could affect project or system outcomes.

A formal process for requesting, evaluating, approving, and recording changes to scope, requirements, or baselines so that impacts remain visible and managed.

A significant, date-bound point in a plan used to mark completion of a major deliverable or decision, typically with no duration of its own.

A contract between a provider and a customer that specifies expected service levels, such as uptime, response time, and remedies for misses.

Documented procedures for keeping essential business functions running during and after a disruption, including alternate arrangements and recovery priorities.

The technical and procedural arrangements for restoring systems, data, and services after a major failure, including backups, standby sites, and recovery testing.

A system structure in which client programs request services and server programs provide them, typically over a network, separating presentation from shared resources.

A layered design separating presentation, application logic, and data storage into distinct tiers that can be developed and scaled independently.

A defined interface through which one software component requests services or data from another, hiding internal implementation behind documented operations and formats.

A set of agreed rules governing how data is formatted, transmitted, and acknowledged between systems, enabling reliable communication across different implementations.

The transformation of readable data into ciphertext using a key so that only authorized parties can restore and read the original content.

The process of verifying that a user, device, or system is who or what it claims to be, typically through credentials or cryptographic proof.

The process of deciding which resources and actions an authenticated identity is permitted to access, based on roles, policies, or attributes.

The structured design of relational tables to reduce duplicated data and update anomalies by organizing attributes into related tables with defined keys.

One or more columns whose values uniquely identify each row in a table and therefore cannot be duplicated or left empty.

A data store that organizes information into tables of rows and columns and supports querying through a declarative language such as SQL.

A software-defined computer that runs its own operating system on shared physical hardware, isolated from other virtual machines by a hypervisor.

A lightweight isolated runtime package containing an application and its dependencies, sharing the host operating system kernel instead of emulating full hardware.

An independently deployable service that implements a narrow business capability and communicates with other services through well-defined interfaces.

The delivery of computing resources such as servers, storage, and services over a network on demand, with usage-based provisioning and management.

The ability of a system to handle growing load by adding resources, either vertically by enlarging a machine or horizontally by adding more machines.

The proportion of time a system is operational and able to serve requests, often expressed as a percentage and supported by redundancy and recovery mechanisms.

The structured set of phases through which software passes, typically including planning, requirements, design, implementation, testing, deployment, and maintenance.

A sequential development approach in which each phase is completed and approved before the next begins, with limited revisiting of earlier phases.

An iterative approach that delivers software in short increments, emphasizes working results and customer collaboration, and welcomes changing requirements.

A fixed, short iteration in a Scrum-based process during which a selected set of work is completed and made ready for review.

An ordered list of desired work items, such as features, fixes, and improvements, that is continuously refined and prioritized for future delivery.

The practice of automatically building, testing, and delivering code changes through a pipeline so that software can be released frequently and reliably.

A system that records changes to files over time, allowing developers to retrieve earlier versions, work in parallel branches, and merge contributions.

The disciplined identification, recording, and control of system components and their versions so that builds and environments remain consistent and reproducible.

The planned execution of software or reviews to find defects and provide evidence about whether specified requirements and quality expectations are met.

An automated check that exercises a single small piece of code, such as a function or class, in isolation to verify its behavior.

Re-running selected tests after changes to confirm that previously working behavior has not been broken by new code or configuration.

An unplanned interruption or degradation of a service that requires response, diagnosis, and restoration, often tracked against service targets.

The process of detecting, logging, prioritizing, resolving, and learning from service incidents so that normal operation is restored quickly.

A structured investigation that traces a problem back to its underlying cause rather than its symptoms, so that recurrence can be prevented.

A copy of data stored separately from the original so that it can be restored after accidental deletion, corruption, or a disruptive event.