Business Information Processing

Course Description

Business Information Processing covers information processing concepts and the use of business software application programs, so that managers can effectively use the interaction between technology and information to increase personal and organizational competitive advantage.

Within the SCNS taxonomy, ISM is the Information Systems Management prefix. Daytona State publishes this at 3 credits, prerequisite GEB1011, offered fall, spring, and summer, giving approximately 45 contact hours.

The framing in the catalog description is worth noticing: this is not a software course wearing a business title. The subject is the relationship between information and decisions, and the software is how that relationship gets operated. A student who leaves knowing keyboard shortcuts has taken half the course; one who leaves able to structure a problem so a spreadsheet can answer it has taken all of it.

Learning Outcomes

Required Outcomes

• Describe information processing concepts and the distinction between data, information, and knowledge.
• Describe the role of information systems in organizational decision-making and competitive advantage.
• Describe the components of an information system: hardware, software, data, people, and process.
• Describe major categories of business software and select an appropriate tool for a task.
• Create, format, and produce professional business documents in a word processor.
• Apply document features appropriately: styles, templates, mail merge, and review tools.
• Build spreadsheets with correct formula construction and cell referencing.
• Apply spreadsheet functions for business analysis, including logical, lookup, and financial functions.
• Build charts that represent data accurately and communicate a point.
• Analyze data using sorting, filtering, and pivot tables.
• Apply what-if analysis to support a business decision.
• Describe database concepts: tables, records, fields, keys, and relationships.
• Build and query a simple relational database.
• Design and deliver an effective business presentation.
• Use collaboration and cloud tools appropriately in a business context.
• Integrate data across applications.
• Evaluate the accuracy and reliability of information sources.
• Describe information security, privacy, and data protection responsibilities.
• Describe ethical and legal issues in business information use.
• Apply file management, naming, and version control practices.

Optional Outcomes

• Describe enterprise systems and their role in organizations.
• Describe business intelligence and data visualization tools.
• Describe generative AI tools and their appropriate business use and limits.
• Apply automation or macro features to a repetitive task.
• Describe e-commerce and digital business models.
• Prepare for a recognized software certification.

Major Topics

Required Topics

• Data, information, and knowledge
• Information systems and competitive advantage
• System components and architecture
• Categories of business software
• Word processing for business documents
• Styles, templates, mail merge, and review
• Spreadsheet construction and cell referencing
• Business functions: logical, lookup, financial
• Charting and data representation
• Sorting, filtering, and pivot tables
• What-if analysis and scenarios
• Database concepts and structure
• Building and querying a database
• Business presentation design and delivery
• Collaboration and cloud tools
• Cross-application integration
• Evaluating information sources
• Security, privacy, and data protection
• Ethics and law in information use
• File management and version control

Optional Topics

• Enterprise systems
• Business intelligence and visualization
• Generative AI in business
• Automation and macros
• E-commerce and digital business models
• Software certification preparation

Resources & Tools

• Microsoft Office 365: In Practice, the Shelly Cashman series, or an equivalent applications text — programmes vary, and the edition matters because interfaces change.
• Using MIS (Kroenke) or Management Information Systems (Laudon) for the concepts half.
• Microsoft 365 — frequently free to students through your institution; check before buying anything. Google Workspace and LibreOffice are free alternatives, though coursework usually assumes Excel specifically.
• Microsoft Learn — free, official, and structured training for every Office application.
• ExcelJet and Chandoo — free, well-organized Excel references aimed at practical business use.
• Microsoft Office Specialist (MOS) certification — an inexpensive, recognized credential; many colleges are testing centres with student pricing. Worth having on a résumé for administrative and analyst roles.
• Power BI Desktop and Tableau Public — free, and the standard business intelligence tools; learning one is a genuine differentiator.
• SQLite or Microsoft Access for the database component; SQLBolt and Mode's SQL tutorial are free and excellent.
• FTC business guidance and the Florida Information Protection Act (§ 501.171, F.S.) — free, and the operative data breach requirements in this state.

Career Pathways

• Administrative and office professional — the most direct application, and software fluency is the differentiator at hiring.
• Business analyst — spreadsheet and data skills are the entry requirement for the role.
• Operations and logistics coordinator.
• Accounting and bookkeeping support — Excel is the working environment.
• Data analyst — with additional training in SQL and a visualization tool; a strong and growing path from this starting point.
• Marketing and sales support — CRM systems, reporting, and campaign analysis.
• Human resources assistant — HRIS reporting and records.
• Project coordinator.
• Small business owner — where you are the whole information systems department.
• Bridge to further study — this course underpins the ISM sequence, including the published ISM4011 in this repository, and supports business degrees generally.
• SOC codes 43-6014 Secretaries and Administrative Assistants, 13-1199 Business Operations Specialists, and 15-2051 Data Scientists for the analytical track.

Special Information

⚠ Excel is the actual language of business — learn it properly, not superficially

The most consequential practical advice in this guide, and it is worth saying plainly because students routinely treat the spreadsheet unit as the boring middle of the course.

Spreadsheet competence is the single most transferable skill in this course and one of the most requested in job postings across every business function. It is also a skill with a wide gap between "can use" and "is good at," and employers can tell the difference within one interview task.

What separates genuine competence from surface familiarity:

• Understand relative, absolute, and mixed references. The $ is not decoration — it is what lets one formula be written once and copied correctly across a table. Not understanding it is the most common cause of broken spreadsheets.
• Learn lookup functions properly — XLOOKUP, or INDEX/MATCH where older versions require it. Combining two data sets is the most common real-world spreadsheet task.
• Learn pivot tables. They summarize data faster than anything else available and they are what "analyze this" usually means in practice.
• Never hard-code a number inside a formula. Put assumptions in labelled cells and reference them. A model with a tax rate buried in twelve formulas cannot be updated and cannot be checked.
• Separate inputs, calculations, and outputs. This single structural habit makes a workbook auditable by someone else, which is what makes it professional rather than personal.
• Check your own work. Build a total that must equal another total. Spreadsheet errors are common, consequential, and well documented in the research literature — real organizations have lost real money to them.

The credential note: MOS certification in Excel is inexpensive, recognized, and a concrete signal for administrative and analyst roles. If your college is a testing centre, take it while the student rate applies.

⚠ Software skills date; concepts do not — and this course teaches both

An honest observation about a course of this type, and a strategy for getting lasting value from it.

The specific menus, ribbons, and shortcuts you learn will change. Interfaces are redesigned, features move, and cloud versions diverge from desktop ones. What does not change is the conceptual layer, and orienting your study toward it is what makes the course worth more than a tutorial:

• Structuring a problem so a tool can solve it is the durable skill. Deciding what the inputs are, what relationship connects them, and what output answers the question survives every version change.
• Relational data thinking — tables, keys, relationships, normalization — underlies databases, spreadsheets used well, and every business system you will ever touch.
• Knowing which tool fits the job. A spreadsheet used as a database is a recurring organizational failure; so is a database built for something a spreadsheet would have handled in ten minutes.
• Data quality reasoning — where numbers came from, how they were collected, what they exclude — is what separates analysis from arithmetic.
• Presenting information honestly, which is covered below.

The practical corollary: learn to find answers rather than memorize procedures. Every application has documentation and a large community, and the professional skill is knowing what the thing you want is called so you can search for it.

⚠ Charts can mislead, and doing it accidentally still damages your credibility

A short, high-value section, because presenting data is where business communication most often goes wrong.

• Truncated axes exaggerate differences. A bar chart starting at 90 rather than 0 turns a 2% change into a visual cliff. Sometimes a truncated axis is appropriate; it must be labelled clearly.
• Choose the chart for the comparison. Bars compare quantities, lines show change over time, and pie charts work only for a few parts of one whole — and poorly even then.
• 3D effects and gratuitous decoration distort perception and add nothing. Business audiences read them as unserious.
• Label the axes, state the units, and cite the source. An unlabelled chart is an assertion, not evidence.
• Show the denominator. "Sales up 200%" from two units to six is technically accurate and practically meaningless.
• Correlation shown on a chart is still not causation, and putting two lines on one graph implies a relationship whether or not you meant it.

The professional stance: the goal is for the audience to understand the situation, not to be persuaded of your conclusion. An analyst who is caught overstating once is discounted permanently.

⚠ Data you handle at work is not yours, and Florida has a breach law

Compliance content that belongs in a business course and is usually skipped.

• Business data carries legal obligations. Customer records, employee records, payment data, and health information are each governed — by contract, by sector regulation, or by statute.
• Florida's Information Protection Act (§ 501.171, F.S.) requires businesses to take reasonable measures to protect personal information and to notify affected individuals and the Attorney General of a breach within defined timeframes. The obligations attach to businesses of any size.
• Payment card data is governed by PCI DSS through your merchant agreement, and non-compliance carries contractual penalties.
• Health information triggers HIPAA obligations in a wide range of businesses, not only healthcare providers.
• Everyday practices matter more than policy documents — unencrypted spreadsheets of customer data emailed as attachments, shared logins, personal cloud accounts used for work files, and USB drives are how most small-business breaches actually happen.
• Access should be limited to what the role requires, and the fact that you can open a file does not mean you are authorized to.

Rule 11 applies — data protection law is moving quickly at both federal and state level; verify current requirements rather than relying on a textbook.

⚠ Generative AI: useful, confidently wrong, and governed by rules you must check

Worth addressing directly, since these tools are now part of business information work.

They are genuinely useful for drafting, summarizing, explaining a formula, and generating a first version of something. They also have properties that matter in a business context:

• They produce fluent, confident output that can be wrong, and the fluency is not evidence of accuracy. Verify anything factual, and check every formula or calculation independently.
• What you paste in may leave your organization. Entering customer data, financial records, or confidential information into a consumer AI service can be a disclosure — and, under the obligations above, potentially a reportable one. Know your employer's policy before pasting anything.
• Your instructor's policy governs your coursework, varies by course, and using a prohibited tool is an academic integrity violation regardless of how much it helped.
• Understand the output you submit. Being unable to explain your own spreadsheet in a meeting is worse than not having built it.

Rule 11 applies — institutional and employer policies in this area are being written and rewritten continuously. Ask; do not assume.

How Florida course levels affect transfer

The first digit of an SCNS number denotes the year of offering, not transferability. Courses at the 1000 and 2000 levels transfer transparently between Florida public institutions, and 3000 to 4000 is unproblematic since both are upper division. The boundary that actually matters is 2000 to 3000, where lower-division credit generally cannot satisfy an upper-division requirement.

ISM2000 is 3 credits and approximately 45 contact hours, assessed largely by hands-on software deliverables — documents, workbooks, a database, and a presentation — alongside concept examinations. It transfers on the ordinary lower-division basis, and it underpins the upper-division ISM sequence including the published ISM4011. Students continuing to a business baccalaureate should confirm whether their programme requires this specific course or accepts a general computer applications course in its place, since the two are not always treated as equivalent.