Business Analytics with AI

Course Description

Business Analytics with AI is designed to equip students with the necessary knowledge and competencies in Artificial Intelligence (AI)-driven analytics to analyze data in business contexts and provide effective data visualization. UWF states that students will explore how AI and machine learning techniques enable organizations to transform data into actionable insights, addressing business problems and enhancing decision-making processes, with emphasis on practical applications, including the use of AI tools to develop data-driven strategies, optimize performance, and support organizational objectives.

Within the SCNS taxonomy, ISM is the Information Systems Management prefix. The University of West Florida publishes this at 3 semester hours through the Department of Business Administration, College of Business. It is offered at approximately 6 Florida institutions.

⚠⚠ The statewide inventory carries this number as "Visual Analytics I"; UWF publishes it as "Business Analytics with AI." Visualization is part of UWF's course — the description names it explicitly — but the emphasis is AI and machine learning applied to business data, which is a substantially different centre of gravity from a visualization course. See the note below, and check the description against any requirement written against the statewide title.

This is the most current course in the prefix and the one most likely to change between catalog years. That is a feature: the field is moving quickly enough that a stable syllabus would be a warning sign. Expect the tools named in the syllabus to differ from any list written more than a year ago, including this one.

⚠ Be clear about what this course is and is not. It is applied AI for business decision-making — using techniques and tools competently, understanding what they can and cannot support, and communicating the result. It is not a machine learning theory course; you will not derive the algorithms. If you want that, take it in mathematics or computer science, and note that the two together are a strong combination.

The framing that will serve you longest is scepticism paired with competence. A great deal of what is currently claimed for AI in business is vendor marketing, and a graduate who can distinguish a real application from an expensive one is worth more than one who is merely enthusiastic.

⚠ The contact-hour figure is derived — the University of West Florida publishes none

UWF's catalog publishes a credit value in semester hours, the college and department, and prerequisites. It does not publish contact hours, a lecture and laboratory split, or terms of offering for any course. Every contact-hour value in a UWF guide in this repository is derived. The figure applies the standard lecture convention of 15 contact hours per credit, giving 45 hours for 3 semester hours. ⚠ Note that ISM courses are project-heavy, and scheduled contact hours understate the real time commitment considerably — budget for project work outside class. Confirm the meeting schedule and delivery mode with the department.

Learning Outcomes

Required Outcomes

• Describe the scope of AI and machine learning in business analytics.
• Distinguish artificial intelligence, machine learning, and generative AI.
• Describe supervised, unsupervised, and reinforcement learning approaches.
• Frame a business problem as an analytics or machine learning problem.
• Recognise when a problem is not suited to a machine learning approach.
• Prepare, clean, and engineer features from business data.
• Describe training, validation, and test splits and why they are needed.
• Apply classification techniques to a business problem.
• Apply regression techniques for business prediction.
• Apply clustering and segmentation techniques.
• Evaluate model performance with appropriate metrics.
• Explain why accuracy is inadequate for imbalanced problems.
• Interpret precision, recall, and the cost of each error type.
• Describe overfitting, underfitting, and model generalisation.
• Describe model drift and the need for monitoring after deployment.
• Describe bias in training data and its consequences at scale.
• Describe explainability techniques and when they are required.
• Apply AI tools to text and unstructured business data.
• Produce effective data visualizations communicating analytical results.
• Select visualization forms appropriate to audience and message.
• Build a dashboard supporting a defined business decision.
• Describe data governance, privacy, and consent constraints on AI use.
• Communicate model results, confidence, and limitations to decision-makers.
• Evaluate an AI-driven business proposal critically.

Optional Outcomes

• Apply the material to a real organisation or a case study.
• Use AI-assisted tools appropriately and verify their output.
• Communicate technical findings to a non-technical audience.
• Work effectively in a project team with defined roles.
• Build a portfolio artefact suitable for showing an employer.

Major Topics

Required Topics

• Scope of AI in business analytics
• AI, machine learning, generative AI distinguished
• Supervised, unsupervised, reinforcement learning
• Framing business problems as analytics problems
• Recognising unsuitable problems
• Data preparation and feature engineering
• Training, validation, and test splits
• Classification techniques
• Regression for prediction
• Clustering and segmentation
• Model evaluation metrics
• Imbalanced problems and accuracy
• Precision, recall, and error costs
• Overfitting and generalisation
• Model drift and monitoring
• Bias in training data
• Explainability techniques
• Text and unstructured data
• Principles of data visualization
• Visualization selection
• Dashboard design for decisions
• Governance, privacy, and consent
• Communicating results and limitations
• Critical evaluation of AI proposals

Optional Topics

• Applied case studies and live organisations
• AI-assisted tooling and its verification
• Communicating findings to non-technical stakeholders
• Team project practice
• Portfolio development

Resources & Tools

• The text and tools the instructor assigns — ⚠ in this course above all others, the syllabus supersedes any list, because the tooling changes between offerings.
• Power BI Desktop, including its AI visuals and Copilot features — Desktop is free; the most likely platform in a College of Business analytics course.
• Python with pandas and scikit-learn, via Google Colab — Colab is free and needs no installation, which removes the commonest obstacle for business students meeting Python for the first time.
• Tableau Public and Tableau for Students — free; the visualization half, and Tableau Public doubles as a portfolio host.
• Kaggle — free; datasets, worked notebooks, and short courses. Reading other people's notebooks is an efficient way to learn what good practice looks like.
• Google Machine Learning Crash Course and the fast.ai materials — free; strong conceptual grounding without the mathematics being the barrier.
• NIST AI Risk Management Framework (nist.gov) — free; the emerging standard for governing AI systems responsibly, and increasingly what organisations are asked to demonstrate against.
• Storytelling with Data — book and free blog; the visualization half of this course deserves it.
• The UWF library's business databases — included in enrolment; practitioner sources such as Gartner and industry reports are behind paywalls a student already has, and most never find out.
• LinkedIn Learning — frequently free through UWF or a Florida public library card; strong on specific tools, weak on judgement. Use it for the software, not the thinking.

Career Pathways

• Business or systems analyst (SOC 15-1211, computer systems analyst) — the most common destination for this major, and the role this prefix is most directly built for: translating business needs into system requirements.
• Data analyst and business intelligence analyst (SOC 15-2051, data scientist; SOC 13-1111, management analyst) — the fastest-growing destination, and the reason the analytics courses in this prefix matter.
• Information security analyst (SOC 15-1212) — strong demand and strong pay in Florida, particularly around defence contracting in the Panhandle and Space Coast. Note that this prefix teaches security management, not penetration testing — a real and separate career.
• Database administrator and data engineer (SOC 15-1242, 15-1243).
• IT project manager — commonly entered after several years as an analyst; PMP or CAPM certification is the usual credential.
• ERP functional consultant — SAP, Oracle, Workday, Microsoft Dynamics; a well-paid path that is under-advertised to undergraduates.
• ⚠ Florida employer landscape: defence and aerospace contractors (Lockheed Martin, Northrop Grumman, L3Harris, and the Navy presence around Pensacola), healthcare systems (AdventHealth, Orlando Health, BayCare, Baptist, Ascension Sacred Heart), hospitality and theme parks (Disney, Universal, the cruise lines out of Miami, Port Canaveral and Tampa — all of which run substantial IT organisations), financial services (Raymond James in St. Petersburg, Fidelity in Jacksonville), logistics, and state and county government.
• ⚠ Security clearance is a genuine career asset in this state. Northwest Florida's defence concentration means clearable candidates have access to roles others do not — worth knowing early, because the process is slow and starts with an employer sponsoring you.

AI Integration

⚠⚠⚠ In this course AI is the subject, not a tool used alongside it. The guidance below therefore covers both what the course teaches about AI and how AI tools should be used while studying it — and the professional standard is the same in both directions: you remain accountable for output you did not personally derive.

What the course teaches about AI in business

• Where AI-driven analytics genuinely earns its place: pattern detection in data too large or too high-dimensional for a person, forecasting at scale, anomaly and fraud detection, segmentation, text and document analysis, and automating repetitive analytical work so analysts do the judgement instead.
• ⚠ Where it fails, and these failures are well documented: models learn the biases in their training data and reproduce them at scale; they degrade silently as the world changes underneath them (drift); they are confident on inputs unlike anything they were trained on; and they find correlations that do not survive contact with a new population.
• ⚠⚠ A model is not a decision. The output is an input to a human judgement that carries context, constraints and accountability the model does not have. Organisations that forget this produce the failures that end up in the news.
• Explainability is a business and legal requirement, not a technical nicety. Regulated decisions — credit, insurance, employment, healthcare — require reasons. Choose a model you can explain when the setting demands one, even at a cost in accuracy.
• Measure what matters, not what is easy. Overall accuracy is a poor metric for a rare event; a fraud model that predicts "not fraud" every time can be 99% accurate and completely useless. Precision, recall and the cost of each error type are the real questions.
• ⚠ Data governance and privacy constrain what you may build. Consent, purpose limitation, retention limits, and sector rules (HIPAA, GLBA, FERPA, PCI-DSS) apply to training data as much as to any other data. "We had the data" is not the same as "we were permitted to use it for this."
• The most valuable graduate skill here is translation — explaining to a decision-maker what a model does, how confident it is, and what it cannot tell them. That skill is scarcer than the ability to fit the model.

Using AI tools while studying this course

• They are useful for code, formulas, and explanations, and unreliable in the specific ways described above — inventing functions and libraries, producing code that runs and is subtly wrong, and being confidently wrong about anything niche or recent.
• ⚠⚠⚠ Never paste confidential, personal, or regulated data into a public AI tool. Use synthetic or anonymised data outside a sanctioned environment. This is a common way early-career employees cause serious incidents.
• The course policy governs and policies differ. Read the syllabus; ask if it is unclear; disclose what you used when asked.
• ⚠ Learning to evaluate the output requires understanding the method. If you cannot tell when the tool is wrong, you cannot use it professionally — and in a course about AI, that gap is the one thing you cannot afford.

Special Information

⚠⚠ ISM3011 is the gateway to the entire prefix

• Every undergraduate ISM course at UWF except ISM3011 itself requires it. ISM3116, ISM3323, ISM4113, ISM4320, ISM4321, ISM4400, ISM4481 and ISM4483 all name it. Nothing else in the prefix opens without it.
• ⚠ That makes it a single point of failure in your schedule. Delaying or failing ISM3011 delays everything downstream, and there is no alternative route around it. Take it as early as you are eligible.
• Only ISM3323 offers an alternative — it accepts ISM 3011 OR COP 2253, a programming route. It is the sole exception in the prefix.
• ⚠ ISM3011 itself has an unusual prerequisite: not a course, but completion of 45 hours of college coursework. See the note on standing requirements below.

⚠⚠ The statewide title and the UWF title differ — read the description, not the name

• Statewide inventory title: Visual Analytics I. UWF publishes it as: Business Analytics with AI.
• ⚠⚠ This is significant drift and possibly a different centre of subject. A visual analytics course is organised around visualization as the method of analysis; UWF's course is organised around AI and machine learning techniques, with visualization as one component rather than the frame. The two overlap substantially and are not the same course. If a requirement was written against "Visual Analytics," confirm this satisfies it before registering, and note that the "I" in the statewide title implies a sequence UWF does not appear to run.
• ⚠ The practical advice is the same in every case of title drift: carry a syllabus. A transfer evaluator matching on the number will accept it; one matching on the title may query it, and one comparing content may reach a different conclusion again.
• Search on the number, not the name, when looking for equivalents at other institutions. SCNS equivalency runs on the number and the content.

⚠⚠ What to be sceptical about, specifically

• A demonstration on clean data proves very little. The hard part of every real analytics project is the data, and vendor demonstrations are run on data that has already been cleaned.
• ⚠ Ask what happens when the model is wrong. Who notices, how fast, what does it cost, and who is accountable. A proposal that has no answer to this is not ready.
• Ask what the baseline is. A model that beats nothing is not an achievement; compare it against the current process, or against a simple rule, before claiming value.
• ⚠⚠ Beware of leakage. A model that performs implausibly well is usually seeing information at training time that will not exist at prediction time. This is the single commonest cause of a model that works in testing and fails in production.
• Automation shifts work rather than removing it. Monitoring, retraining, governance and exception handling are real ongoing costs, and they are routinely omitted from the business case.

Where this sits in the analytics line at UWF

• ISM3116 is the spreadsheet-based entry point; this course is the AI-driven continuation; ISM4400 covers decision support and data integration and ISM4481 covers business data management.
• ⚠ Add a statistics course and a database course from outside this prefix. Analytics employers expect all three — the analysis, the data handling, and the inferential reasoning — and a transcript showing only one looks thinner than it is.
• Build a portfolio as you go. In this field specifically, a public notebook or dashboard you can talk through beats a course title on a transcript.

Certifications worth knowing about

• ⚠ A degree and a certification do different jobs. The degree is the durable credential; certifications are current, specific, and expire. Employers in this field ask for both, and neither substitutes for the other.
• Analytics and data: Microsoft Power BI Data Analyst (PL-300), Tableau Desktop Specialist, Google Data Analytics, AWS and Azure data certifications. Several have free or heavily discounted student pricing — ask the College of Business.
• Security: CompTIA Security+ is the standard entry credential and is frequently a hard requirement for defence-adjacent work under DoD 8570/8140; CISSP and CISM are management-level and require documented experience.
• Project and process: CAPM, PMP, and the Scrum credentials.
• ⚠ Do not collect certifications instead of building things. A portfolio of real projects — a dashboard, a database, an analysis with a written recommendation — outperforms a list of badges in almost every hiring conversation in this field.

Transfer, articulation, and how Florida course levels work

In the Florida Statewide Course Numbering System the first digit is the level: 1 and 2 are lower division, 3 and 4 upper division, 5 and above graduate. ⚠ A lower-division course generally cannot satisfy an upper-division requirement, which matters in this prefix — ISM2000 and ISM3011 both introduce information systems, and only the second is upper division.

⚠⚠ Business programmes add a layer that SCNS does not. Many Florida business colleges are AACSB accredited, and AACSB programmes commonly limit how much upper-division business coursework may transfer in — frequently requiring a substantial share to be taken in residence. A course can articulate under SCNS and still not count toward the major. Check the receiving programme's residency rule before you rely on a transfer.

Many business programmes also impose an admission-to-the-major step with its own grade point requirement, and a minimum grade in each core course. Confirm both against your own catalog year.

Course format and position in the curriculum

• Lecture with substantial project and applied work. ⚠ ISM courses are consistently more time-consuming than their credit value suggests, because software work expands to fill the debugging available.
• ⚠ No "permission is required" marking appears anywhere in the ISM prefix, and no fee notices — enrolment is gated by ISM3011 and by standing.
• Ask about delivery mode. UWF offers substantial online provision in the College of Business, and an online section of a project-based course demands more self-management, not less.
• UWF publishes no contact hours or terms of offering. A course offered in one term only will delay a sequence by a full year if missed — confirm with the department.

ISM4545 is 3 semester hours at the University of West Florida.