Module 1 · AI Foundations

The Complete AI Lifecycle Explained

Learn the AI lifecycle from business problem and data preparation through training, deployment, monitoring, and improvement.

Core idea

AI is a lifecycle, not a one-time model build

An AI system begins with a measurable business problem and continues after deployment. Data, model behavior, software, users, risk, and the real world all change. A reliable team therefore treats monitoring, feedback, and improvement as part of the product—not as optional maintenance.

Success rule: A model metric matters only when it supports a useful, safe, and measurable business outcome.

Lifecycle diagram

Eight connected phases

The final phase loops back to the beginning: production evidence can change the problem definition, data, features, model, or operating process.

What happens in each phase

01

Problem and success criteria

Define the user, decision, baseline, expected value, acceptable error, constraints, and whether AI is appropriate.

02–03

Data collection and preparation

Gather representative data, understand consent and ownership, clean errors, label when needed, split carefully, and prevent leakage.

04

Model development

Select an approach, create a baseline, engineer useful inputs, train candidates, and record reproducible experiments.

05

Evaluation

Measure technical quality, business value, fairness, robustness, safety, latency, and cost on data not used for training.

06

Deployment

Integrate the model with application logic, access controls, fallbacks, observability, versioning, and human workflows.

07–08

Monitoring and improvement

Watch data drift, model quality, service health, user feedback, incidents, and business outcomes; retrain or redesign when evidence requires it.

Practical example

Predict delivery delays

GoalWarn operations early enough to intervene, not merely produce a high model score.
DataHistorical routes, carriers, weather, shipment attributes, timestamps, and confirmed delay outcomes.
EvaluationMeasure precision and recall for delays, intervention value, false-alarm cost, and performance across routes.
DeploymentScore active shipments, show reasons and confidence, and route high-risk cases to operations staff.
MonitoringDetect route changes, seasonal drift, missing inputs, declining recall, and whether interventions actually reduce delays.

Offline metrics and production reality

Model metrics

Accuracy, precision, recall, F1, error measures, calibration, and robustness describe model behavior on evaluation data.

Business metrics

Cost saved, time reduced, defects prevented, customer outcomes, adoption, and return on investment show whether the system creates value.

Operational metrics

Latency, throughput, availability, failure rate, resource use, and cost show whether the service works reliably.

Responsible-AI metrics

Fairness, privacy, explainability, harmful-output rate, escalation rate, and human override patterns reveal risk.

AWS Certified AI Practitioner

Exam signals

  • Business problem and success criteria come before model selection.
  • Training, validation, and test data serve different purposes; avoid data leakage.
  • Evaluation includes business and responsible-AI concerns, not accuracy alone.
  • Deployment is not the end—monitor drift, quality, cost, and operational health.
  • MLOps emphasizes repeatability, versioning, automation, monitoring, and controlled improvement.

Key takeaways

  • Define the business problem first
  • Prepare representative and secure data
  • Train and evaluate against suitable metrics
  • Monitor performance after deployment

Check your understanding

  1. Can you explain this concept in two sentences without using jargon?
  2. Can you identify the input, process, output, and validation step in the example?
  3. Can you name one suitable use case and one case where another approach is better?
  4. Which risk or limitation should a responsible implementation address?

Research references

Public sources and further reading

This lesson is original educational writing informed by the public references below. Use the sources to explore definitions, technical details, and current AWS exam objectives.