Business Systems Design

Course Description

Business Systems Design is a project-based introduction to the principles of business information systems design, including the basic methods and procedures involved in planning and controlling the development and modification of a computer-based information system in an organization. UWF states that students use modern microcomputer-based, computer-aided systems design tools and techniques to complete design projects, and that the course focuses on the importance of end-user specifications for information systems projects.

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 7 Florida institutions.

⚠ UWF says "project-based" first, and the word governs the course. This is not a course you pass by reading — you will design systems, in a team, against a deadline, and the workload is concentrated toward the end of term in a way the credit value does not signal. Plan for it.

The sentence that matters most is the last one: the importance of end-user specifications. Information systems projects fail far more often on requirements than on technology — the system was built correctly and it was the wrong system. Learning to elicit what users actually need, as against what they first say they want, is the core professional skill of a systems analyst.

⚠ That skill is mostly not technical. It is interviewing, listening, noticing what people do rather than what they report doing, and having the nerve to tell a stakeholder that their stated requirement will not solve their stated problem. Students who came to information systems to avoid dealing with people find this course a surprise.

The team project is the part employers ask about in interviews, and not because of the artefact. They ask what went wrong, what you did about it, and what you would do differently — so pay attention to how the team works, not only to what it produces.

⚠ 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 systems development life cycle and the role of design within it.
• Compare waterfall, iterative, agile, and hybrid approaches and their fit.
• Describe project planning, scheduling, and control for systems projects.
• Describe feasibility analysis: technical, economic, operational, schedule.
• Elicit requirements through interviews, observation, and document analysis.
• Distinguish stated wants from underlying needs in requirements work.
• Write clear, testable functional and non-functional requirements.
• Describe the importance and role of end-user specifications.
• Model business processes and produce process diagrams.
• Produce data flow diagrams and describe system boundaries.
• Produce entity-relationship models and logical data designs.
• Apply normalisation to a logical data model.
• Produce use cases and user stories appropriately.
• Design user interfaces with attention to usability.
• Design system outputs, inputs, and controls.
• Apply computer-aided systems design tools to produce design artefacts.
• Evaluate build, buy, and configure alternatives.
• Describe testing strategies and acceptance criteria.
• Describe implementation, conversion, and change management approaches.
• Describe maintenance and system modification control.
• Work effectively in a project team and manage scope.
• Present and defend a system design to stakeholders.

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

• The SDLC and the place of design
• Waterfall, iterative, agile, hybrid
• Project planning and control
• Feasibility analysis
• Requirements elicitation techniques
• Wants versus needs
• Writing testable requirements
• End-user specifications
• Business process modelling
• Data flow diagrams and system boundaries
• Entity-relationship modelling
• Normalisation
• Use cases and user stories
• Interface design and usability
• Output, input, and control design
• Computer-aided design tools
• Build, buy, or configure
• Testing and acceptance
• Implementation, conversion, change management
• Maintenance and modification control
• Team working and scope management
• Presenting and defending a design

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 systems analysis text the instructor assigns — Dennis, Wixom and Roth's Systems Analysis and Design is the most widely used; Valacich and George's Modern Systems Analysis and Design is the common alternative.
• draw.io / diagrams.net — free; process diagrams, data flow diagrams and entity-relationship models without a licence. Lucidchart and Microsoft Visio are the common commercial equivalents, and UWF may license one.
• Figma — free tier, and free education plan; the current industry standard for interface mock-ups, and a genuinely marketable thing to have used.
• Microsoft Project, or free alternatives such as ProjectLibre and GanttProject — for the planning and control material.
• A version control habit — GitHub is free and free for students. Even for documents, a team that can see who changed what avoids the commonest cause of group-project chaos.
• The BABOK guide from IIBA — the business analysis body of knowledge; worth knowing exists, since ECBA and CBAP certifications are built on 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

Information systems is one of the fields where generative AI has changed working practice fastest, and pretending otherwise would not serve a student. The honest position is that these tools are genuinely useful, genuinely unreliable, and that the professional remains accountable for the output regardless of what produced it.

• Where AI tools help in this domain: drafting and explaining code and SQL, generating test data, summarising documentation and standards, producing first-draft requirements and process descriptions, writing spreadsheet and BI formulas, and explaining an unfamiliar error message — which is a large share of what stalls a beginner.
• ⚠ Where they fail, specifically: they invent plausible functions, libraries, and API endpoints that do not exist; they produce code that runs and is subtly wrong; they are confidently wrong about anything niche, recent, or organisation-specific; and they cannot know your data, your business rules, or your regulatory constraints unless you tell them.
• ⚠⚠ The failure mode that matters most here is a wrong answer that looks right. A query that returns rows is not a query that returns correct rows. Verify against known values before you trust an analysis, and be especially careful with joins, filters, date handling, and anything involving aggregation.
• ⚠⚠⚠ Never paste confidential, personal, or regulated data into a public AI tool. Organisational data, customer records, health information, and anything under FERPA, HIPAA, GLBA or PCI-DSS must not leave a controlled environment. This is a genuine and common way that early-career employees cause serious incidents, and "I did not know" is not a defence that helps anyone. Use synthetic or anonymised data for anything you take outside a sanctioned system.
• Academic integrity: the course policy governs, and policies differ. Some instructors encourage AI use with disclosure, some restrict it to specified tasks, some prohibit it. Read the syllabus and ask if it is unclear — assuming is how students end up in an integrity process.
• ⚠ The professional argument for learning without it first is real, not moralising. If you cannot read and evaluate the output, you cannot catch it when it is wrong — and an employer is paying for the judgement, not the typing. Use AI to go faster on things you understand; do the learning yourself.
• Cite and disclose what you used, when the policy asks. This is becoming a normal professional expectation as well as an academic one.

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.

⚠⚠ Why information systems projects fail, and what this course is really teaching

• The dominant causes of project failure are requirements and scope, not code: unclear or changing requirements, absent stakeholder engagement, scope growth without schedule change, and unrealistic estimates.
• ⚠ Fixing a requirements error late is dramatically more expensive than fixing it early. That relationship is the reason design is treated as a discipline rather than as preamble to building.
• Users describe solutions when asked about problems. "I need a spreadsheet with these columns" is a solution; the analyst's job is to find the problem behind it, which is frequently better solved another way.
• ⚠ Watch what people do, not only what they say. The documented process and the actual process differ in almost every organisation, and the workarounds people have invented are usually the most informative thing you will find.
• Scope management is a professional skill and it is mostly a communication skill. Saying "yes, and here is what that costs in time" is the difference between a project that ships and one that does not.

⚠ Getting the most out of the team project

• Agree roles, a meeting rhythm, and a shared file location in week one, before there is anything to disagree about.
• ⚠ Raise a non-contributing team member early and through the instructor, not in the final week. Instructors can act on a problem they hear about in week four and generally cannot in week fifteen.
• Keep the artefacts. A cleaned-up design document, process model and interface mock-up is a portfolio piece, and portfolio pieces outperform transcripts in this field.
• Interviews will ask what went wrong on the project. Have an honest answer, including your own part in it — that answer is what the question is actually for.

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.

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