0.7.17 Oral Final Study Guide

The Oral Final Is About Connections

FIT introduced many individual tools and concepts.

The strongest preparation is not memorizing isolated definitions.

Focus on explaining how the ideas connect.

A useful pattern is:

Performance-Based Technical Work

A structured technical process can move through:

Activity diagram showing need, then requirement or user story, then planned work, then technical artifact, then evidence, then revision.
Need.
  • New
  • Changed
  • Removed

Examples of evidence in FIT include:

  • compiler results;
  • debugger observations;
  • Feedback System messages;
  • spreadsheet summaries;
  • authoritative sources.

Be able to explain why evidence matters rather than saying only that a tool "checks the work."

Abstraction and Models

A model is a purposeful simplification.

Abstraction answers:

A useful model includes needed information while leaving out irrelevant detail.

The model type should fit the question.

UML Object Diagrams

Object diagrams answer:

They can show:

  • object identity;
  • object type;
  • field values;
  • relationships between specific objects.

Example idea:

Activity diagram showing memory, then write, then file, then read, then memory.
Memory.
  • New
  • Changed
  • Removed

FIT used:

System.IO.File.WriteAllText(....)
System.IO.File.ReadAllText(....)

to illustrate that movement.

HTML and CSS

HTML describes webpage structure and meaning.

CSS controls presentation.

A browser interprets both to render a webpage.

Hexadecimal can represent CSS colors.

Internet and Web

The Internet provides network connectivity.

The Web uses that connectivity for web resources and request/response interactions.

A browser is a client.

A web server receives requests and sends responses.

URLs and Query Parameters

A URL can include:

  • scheme;
  • host;
  • path;
  • query.

Example:

Activity diagram showing row record, then column field, then cell field value.
RowRecord.
  • New
  • Changed
  • Removed

A CSV can represent the same tabular information as plain text.

Clean data uses consistent representations.

Unique IDs and Relationships

A unique ID distinguishes one record from another.

Related tables can connect records using identifiers.

Example:

Activity diagram showing Songs.Artist ID, then Artists.Artist ID.
SongsArtistID.
  • New
  • Changed
  • Removed

That relationship can be modeled in an ERD.

Data Analysis

Sorting changes record order.

Filtering limits the current view.

A PivotTable creates a grouped summary.

A chart visualizes selected data.

A visualization can reveal patterns, but it does not automatically explain why those patterns exist.

The source data still controls the quality of the result.

DataGrid

A DataGrid displays structured records in a C# application.

The FIT data path is conceptually:

Activity diagram showing CSV, then application data, then DataGrid.
CSV.
  • New
  • Changed
  • Removed

The displayed rows and columns should preserve the record-and-field relationships from the source.

AI-Supported Information

Generative AI produces output.

Generated output is not guaranteed fact.

Evaluate:

  • accuracy;
  • credibility;
  • relevance;
  • bias;
  • missing context;
  • limitations.

Important claims may require verification with an authoritative source.

Responsible AI Use

Use data minimization.

Do not share:

  • passwords;
  • authentication secrets;
  • information you are not permitted to provide.

Follow the AI-use requirements for the course or workplace.

Be transparent about AI assistance when required.

Accept, Revise, Verify, or Reject

This framework describes your next action after evaluating technology-supported output.

The decision should be based on:

  • the task;
  • evidence;
  • risk;
  • rules;
  • the quality of the result.
Human Judgment Connects the Entire Course

FIT repeatedly places a person between evidence and action.

Examples:

debugger evidence → decide what code to revise
chart → decide what observation the data supports
web information → decide how to interpret the result
AI output → decide whether to accept, revise, verify, or reject

The common skill is not memorizing tool buttons.

It is using appropriate representations and evidence to make and explain a technical decision.

A Strong Oral Explanation

When explaining a FIT concept, try this structure:

  1. Name the problem or question.
  2. Identify the representation or tool.
  3. Explain what information it provides.
  4. Explain what it does not prove.
  5. Describe the evidence you would use.
  6. State the human decision that follows.

That structure demonstrates understanding across the course rather than recall of isolated vocabulary.