AIYING · AI ENGINEERING: A PRACTITIONER’S APPROACH · LESSON #001
What Is AI Engineering? From a Model to a Working System
By Ravindra Dastikop
AI engineering makes a model useful within a complete system
For this series, AI engineering means designing, building, evaluating, operating, and maintaining systems that use AI capabilities to meet human needs under real constraints.
A model can classify an image, estimate a value, or generate text. A working system must also obtain suitable inputs, control access, connect components, handle failures, and provide a useful result to someone.
This systems perspective is consistent with Carnegie Mellon University’s Software Engineering Institute, which connects AI engineering with software engineering, systems, computer science, and human-centred design. Google’s production-ML teaching likewise places the model within a wider ecosystem of data, infrastructure, and monitoring. Sources
You do not have to train a model from scratch to do AI engineering. Integrating an existing model into a useful application still requires engineering decisions.
The discipline also extends beyond chatbots: a forecasting service, defect detector, recommendation system, and document assistant all raise questions about requirements, data, evaluation, and operation.
Worked example: a document-help assistant
Imagine a training centre where staff repeatedly ask questions about an approved programme handbook. We want to help them find the right information more easily.
This is our fictional running case. We will develop it progressively; this lesson does not assume that a generative-AI solution is already the best choice.
The handbook contains this sample rule:
Participants must bring a laptop. Loan devices are not provided.
Someone asks: “Can I attend without bringing a laptop?”
A language model might draft a response. But choosing that model leaves several system questions unresolved:
| Part | Decision to make |
|---|---|
| User and purpose | Who needs help, and which task should become easier? |
| Source data | Which handbook version is approved, and who maintains it? |
| Model | What capability is needed, and how will we compare candidates? |
| Application workflow | How will relevant handbook text reach the model and the user? |
| Verification and fallback | How will we check source support, and what happens when information is absent? |
| Operation and ownership | Who handles access, updates, cost, availability, and reported errors? |
For our sample question, a satisfactory answer would preserve the laptop requirement and show the supporting passage. It should not promise a loan device.
If asked about transport and the handbook says nothing about it, the designed response should acknowledge the gap and direct the person to a named support route. That behaviour needs testing; writing it in an instruction does not guarantee it.
Four terms to keep separate
- Model: A computational component that maps inputs to outputs; in machine learning, its behaviour is shaped through learning from data.
- Inference: Running a trained model on an input to obtain an output.
- Application: Software that combines a user interface, workflow, data access, and other components to deliver a service.
- Evaluation: A structured assessment of whether a component or system meets stated criteria.
Better model performance does not automatically establish a better application. A capable model supplied with the wrong handbook can still produce an unsuitable answer. Likewise, a correct answer delivered too late may fail the user’s task.
The engineering responsibility is to examine the complete path from need to outcome.
Your first practical accomplishment: write the system brief
Use the running case or choose a small problem you understand. Complete these eight fields before selecting a model or framework:
1. User: Who will use this?
2. Need: What are they trying to accomplish?
3. Input: What will they supply?
4. Approved information: Which sources may the system use?
5. Useful output: What should the user receive?
6. Boundary: What must the system not decide or do?
7. Success check: What observation would show that it helped?
8. Owner and fallback: Who maintains it, and what happens when it cannot help?
For example, our boundary might be: “Explain the approved handbook; do not grant exceptions or alter enrolment records.” Our proposed success check might be: “Staff can answer selected handbook questions correctly and locate supporting passages faster than with their current method.”
That is a criterion to investigate, not an achieved result. We still need to define a representative question set and measure the existing method.
Verify your brief
- Give it to another person. Can they identify the intended user, task, boundary, and owner without asking you?
- Write three trial questions: one answered by the source, one absent from it, and one requesting an action outside scope.
- Describe an acceptable response for each. If you disagree about what counts as acceptable, refine the brief before implementation.
Practitioner extension: apply the same brief to an existing AI feature. Identify one requirement with no test, one dependency with no clear owner, and one failure with no defined fallback.
Next lesson: When Does a Problem Need AI? Establishing a Baseline.
Sources and evidence note
- CMU Software Engineering Institute: Artificial Intelligence Engineering Body of Knowledge — the discipline’s systems and human-centred perspective.
- Google Machine Learning Crash Course: Production ML systems — the wider components surrounding a model.
Sources checked on 17 November 2026. The working definition, fictional training-centre case, system brief, and exercises are original AIYING teaching adaptations. They are not quoted standards, tested outcomes, or an endorsement by the cited organizations.


No comments:
Post a Comment