Member Avatar for augie0216

I'm trying create a system flowchart which shows ms access as the database. I'm going to create a patient database and a invenroty database and a few others. I believea system flowchart does not show individual programs but rather the computer devices that make up the system and the basic software programs as a whole. I understand the concept but i'm unsure how to draw the system flowchart. I just want a example the book i'm learning from falls a little short in pictures showing actual flowcharts. Remember just want a example to start me out in the right direction.

Thanks
Augie

  • 4 Contributors
  • 6 Replies
  • 209 Views
  • 3 Years Discussion Span
  • Latest Post Latest Post by riz17

Dani AI

Generated

A system flowchart is a high-level map of where data travels and which physical or major logical components touch it — workstations, scanners, servers, printers, and the database(s) — not the line-by-line logic inside a program. That distinction explains 's confusion and answers : yes, system flowcharts differ from program (logic) flowcharts. pointed toward flowchart examples; is right that a system view is more about data routing and devices than decision diamonds.

Practical steps to draw one for a patient + inventory Access solution:

  1. Define scope (admissions, inventory, billing, reporting).
  2. List external entities (patients, suppliers, insurers, lab systems).
  3. List physical nodes (reception PC, inventory terminal, barcode scanner, file/server where Access backend lives, printer, backup device, internet gateway).
  4. Represent major software/data: draw a cylinder for the Access backend (Patients.accdb / Inventory.accdb) and boxes for top-level modules (Patient Management, Inventory Control, Billing).
  5. Draw labeled arrows for each data flow (e.g., "patient record create/update", "inventory decrement", "invoice -> insurer") and note frequency or trigger (real-time, nightly batch).
  6. Add backup/archive flows, scheduled exports, and any ODBC/SQL bridges if a server DB is used.

Practical tips: include a short legend (symbols, arrow meaning), mark where the Access file physically resides (shared folder vs. SQL server), and call out concurrency or performance risks (file-based Access under heavy multi-user load). Keep the diagram readable: group client/front-end boxes on one side, the Access backend as a central cylinder, and external entities at the edge. Common tools: Visio, diagrams.net (draw.io), Lucidchart, or even PowerPoint.

Recommended Answers

All 6 Replies

Member Avatar for augie0216

These images are regular flowcharts. I think system flowcharts are a little different. That's why I'm having a problem

Member Avatar for thekashyap

Unfortunately a flowchart is a flowchart. It can even be made for the process of deciding which TV to buy !
Given all the basic elements remain same I donno what else you're looking for.. ?

Member Avatar for augie0216

ok ! thanks for the help

Member Avatar for QUOSAIN

Is thereb any diference between flowchatrs and system flowcharts

Member Avatar for riz17

System Flowchart is Different to PROGRAM FLOWCHART.. System Flowchart is little bit HARDER than program flowchart.. Because System flowchart is a graphic of the procedures involved in coverting data on input media to data in output form.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.