Graphics Software and Software Standards

Theory of Computation & Computer Graphics — Introduction of Computer Graphics, NEC licence examination syllabus (Nepal Engineering Council).

Graphics Software and Software Standards

Why the same 3D game engine code can (mostly) run on very different graphics hardware.

💻 General vs Special-Purpose Software

General-purposeProvides broad drawing primitives (lines, circles, fills) usable for many different applications.

Special-purposeBuilt for one specific domain (e.g. CAD software, medical imaging tools), with domain-specific features baked in.

📐 Graphics Standards

GKSGraphical Kernel System — one of the earliest standardized graphics APIs.

PHIGSProgrammer's Hierarchical Interactive Graphics System — extended GKS with hierarchical 3D object support.

OpenGLThe modern, widely-used cross-platform graphics API — this is what lets a game's rendering code run across different GPU brands.

💡 One-liner: "Why do graphics standards like OpenGL matter?" → They let software written once run correctly across many different hardware vendors' graphics cards, instead of needing separate code per GPU brand.

What a graphics standard is actually for

The list of acronyms means little without the problem they solve, and it is the same problem the ISA solves for processors.

Without a standard, a program must be written against one specific graphics device — change the hardware and the drawing code must be rewritten. A standard defines an interface: the application calls draw_line, and the driver for whatever hardware is present carries it out. The application never learns which device it is talking to.

📐 What each standard was for

GKSThe first international standard, 2D only — established the idea that graphics could be device-independent at all.

PHIGSAdded 3D and, importantly, a stored hierarchical model the system remembers, rather than commands that draw once.

OpenGLThe one that survived: 3D, cross-platform, immediate-mode, and designed around what hardware could actually accelerate.

💡 The reason OpenGL displaced PHIGS is worth knowing. PHIGS kept the scene database inside the graphics system, which was elegant but slow and inflexible; OpenGL made the application own its data and simply issue drawing commands. That matched how graphics hardware was actually built, so it could be accelerated where PHIGS could not.

The same layering as everywhere else

Application "draw this scene" ↓ Graphics API standard calls — OpenGL, Vulkan, DirectX ↓ Device driver vendor-specific translation ↓ Hardware the actual GPU

This is the identical argument as the ISA being a contract between software and hardware, and the transport layer hiding the network from applications. A stable interface in the middle means either side can change independently — a new GPU needs a new driver, not new applications.

💡 It is also why the same game runs on cards from different vendors. The vendors compete on the hardware and the driver; the API they must implement is fixed, which is precisely what makes the competition possible without fragmenting software.

Syllabus points

General vs special-purpose software
Standards: GKS, PHIGS, OpenGL

Create a free account to tick topics off, take notes as you read, watch the video lessons and get a day-by-day study plan built around your exam date.