Define the AI task before choosing a model
A capstone should state the prediction or decision target, available data, success metric, and practical constraint before comparing algorithms. This keeps the project focused on a measurable problem.
AI and data science project support for student capstones, prediction models, dashboards, and documentation. This page focuses on the methods, files, checks, and submission issues that are specific to this subject rather than repeating a generic data science workflow.
Share the exact brief so the method and deliverables follow the course rather than a generic template.
An AI capstone may combine data collection, preprocessing, baseline modelling, several experiments, evaluation, report writing, and presentation. The project becomes easier to defend when each experiment is logged and every conclusion traces back to a reproducible result.
A capstone should state the prediction or decision target, available data, success metric, and practical constraint before comparing algorithms. This keeps the project focused on a measurable problem.
A simple experiment log can record preprocessing, features, model version, parameters, metrics, and observations. That makes later comparison and report writing much more reliable.
Bias, class imbalance, privacy, explainability, uncertain labels, and misuse of predictions may be relevant to an AI project. These issues should be tied to the dataset and scenario rather than added as generic ethics text.
A defensible project can explain the problem, dataset, method, strongest result, baseline, limitation, and next improvement in a few slides. The code and report should support the same story.
Large tasks are easier to review when each milestone produces a visible output.
Confirm this milestone before moving to the next so errors do not propagate through the project.
Confirm this milestone before moving to the next so errors do not propagate through the project.
Confirm this milestone before moving to the next so errors do not propagate through the project.
Confirm this milestone before moving to the next so errors do not propagate through the project.
Confirm this milestone before moving to the next so errors do not propagate through the project.
The course brief should decide the environment. Switching to a different tool only because it is familiar can make an otherwise correct solution unsuitable for submission.
Answers are kept specific to this page so students can check requirements, method, files, and limitations without reading repeated site-wide text.
A clear problem statement, dataset description, preprocessing, baseline, experiment comparison, evaluation, limitations, and presentation-ready summary are common components.
Yes. Keeping the same data split and metrics makes model comparisons much easier to defend.
When they are relevant to the dataset and use case, bias, privacy, label quality, explainability, and misuse should be addressed specifically rather than as generic text.
Yes. The brief and rubric should be shared before work begins so the required tool, output format, method, and file structure can be followed.
Reasonable corrections can be reviewed against the original brief. A new dataset, method, analysis section, or changed requirement may be a separate scope.
Send the assignment brief, dataset, deadline, tool requirement, and grading rubric. A clear quote can be shared after reviewing the exact task.