GS Dev Requirements

Design icon.png This page contains the design document for an enhancement or feature. The design should be considered a work in progress and may not represent the final design. As this is a collaborative design, contributions and participation from other developers and users is encouraged. Use the discussion page for providing comments and suggestions.

Geometry Service Requirements

  • Geometry versioning: revision history of geometry changes such as who did what to the model and for which analysis, when changes were made, by whom, etc.
  • Direct association of stored geometry with external data
  • Multi-user access controls that allow multiple people to work on the same models at the same time
  • Programmable access-controlled interface that utilizes reuseable code for consistent end-to-end access to geometric data.
  • Dynamic geometry
  • Geometry articulation and editing constraints
  • Unified repository of geometry in one storage location.
  • Reuse of identical geometry parts (single instancing).
  • Improved/advanced collaboration.

Identified Executables

  • Geometry Engine
    • C++
    • Provides:
      • Geometry Management (via SVN)
      • Geometry Conversion, Import, Export
      • RayTracing
      • Communications with external Geometry Engines
      • Communications with external Geometry Repositories
      • Communications with any other application that implements the GS Protocol
    • GS Dev Geometry Engine Requirements

Visual Conception

GS Concept local.jpg
A Thin Client connected to a Geometry Service, all running on one physical machine

GS Concept Multi med.jpg
Thin Clients connected to Geometry Services, each running on independent physical machines, but connected to a 'headless' Geometry Service. The 'headless' geometry service also serves other enterprise level applications.