This is where it gets fun for coders. Right now, I'm just coding DirectX and trying to get things working. I'm staying as organized as possible, but I really need a solid code architecture to go off of.

How should we organize the engine? Here's what I've got:

class WindowsShell
Exposes static members and methods for dealing with Windows

class DXEngine
Exposes static members and methods for DirectX initialization and cleanup as well as for drawing frames, playing sounds/music, and receiving input

class TileEngine
Exposes static members and methods for handling tilesets

class SpriteEngine
Exposes static members and methods for handling sprites

class ParticleEngine
Exposes static members and methods for handling particles (snow, rain, dust, fog, fire, smoke, etc.)

class PhysicsEngine
Exposes static members and methods for handling gravity, wind/water currents, and collision detection

Suggestions? I've never done this before, so brutal criticism would be fine.

-Nag