| Name | Kind | Description |
| backend | package | sourcecode package Data backend classes here... |
| Backend Components | class view | |
| backend use cases | use case diagram | |
| backend-components | component diagram | |
| BackendLayer | package | |
| build | operation | |
| build flow | activity diagram | |
| build necessary? | decision activity node | |
| build process | collaboration diagram | This figure shows the process of building and starting a RenderEngine |
| build Processors | expansion region | |
| build Render Engine | opaque activity action | |
| build Request | activity parameter | |
| build Tool | activity object | |
| Buildable | class | |
| buildable | artifact | marker interface denoting any MObject able to be treated by Tools |
| buildEngine | operation | Main Operation of the Builder: create a render engine for a given part of the timeline |
| Builder | component | |
| Builder | package | |
| builder | package | sourcecode package The Builder creating the Render Engine, located within the MObject Subsystem |
| Builder Entities | class diagram | |
| Builder Workings | class view | |
| BuilderFacade | class | Provides unified access to the builder functionality. While individual components of the builder subsystem may be called if necessary or suitable, it is usually better to do all extern invocations via the high level methods of this Facade |
| builderfacade | artifact | Facade and service access point for the Builder Subsystem |
| BuilderTool | class | Used according to the visitor pattern: each Tool contains the concrete implementation for one task to be done to the various MObject classes |
| buildertool | artifact | Interface, any tool for processing MObjects |
| building the Engine | activity | |
| BuildInstruct | class | (Interface) building instructions to be executed by the Builder on the render node network under construction. |
| buildinstruct | artifact | Instructions for building some configuration of render nodes. |
| buildProcessor | operation |