To benefit the most from OrbusInfinity and its ecosystem, you may refer and get familiar with the following terms and abbreviations as you are working with the OrbusInfinity application.
| Term | Description |
|---|---|
| Attribute | Metadata associated with Objects and Relationships in the OrbusInfinity repository. Attributes are defined and assigned to Object Types and Relationship Types in the Configure Area. |
| Identifying Attribute | An Attribute that is used to uniquely identify an Object or Relationship in the OrbusInfinity repository. Items in the same Model may not have the same Identifying Attribute values. |
| Category | Categories are used to provide a cross-Model and cross-Solution classification of repository content. Categories are hierarchical and may be used as a folder structure for the OrbusInfinity repository content. |
| Commercial Solution | A pre-packaged set that consists of Metamodel, Reports, Views, Toolset, and content to quickly enable business value and outcomes within a specific domain and associated Use Cases. |
| Configure Area | The OrbusInfinity Area that is mostly accessible by administrators and is used for configuring the OrbusInfinity system, managing metamodel items, user rights, and permissions. |
| Counterpart | A registered SharePoint Document or a Lucidchart Document that is represented by an Object in OrbusInfinity. Adding a Counterpart integrates a Document into your OrbusInfinity repository. |
| Document | Documents (Microsoft Word, Excel, PowerPoint) and Diagrams (Microsoft Visio) that are stored in SharePoint and are also integrated with OrbusInfinity. |
| Document Type (DT) |
A type of the Document defined by a Document template: Microsoft Word DT (*.dot, *.dotx, *.dotm files) Excel DT (*.xlt, *.xltx, *.xltm files) PowerPoint DT (*.ppt, *.pptx, *.pptm files) Visio DT (*.vstx, *.vstm files) Custom DT (another file type, like PDF, JPG, and so on) |
| Document Type Component | Object Types or Relationship Types that are mapped to a Visio Document Type. Based on this mapping Document Component might be used on the Visio diagram as visual representations. |
| Hub Solution | Enabling capabilities that provided through Solutions Hub to expand and enrich your repository content and connect the OrbusInfinity repository with Content, Toolsets, Reports, and Report Packs. |
| Matrix | Two-dimensional view of Objects and their Relationships in the form of the Matrix. |
| Metamodel | All the types of building blocks and taxonomies that may exist within OrbusInfinity. Showing how these building blocks can be described and related to one another, and represented in Document or Diagram. In OrbusInfinity, these types are called Object Types (OTs), Relationship Types (RTs), Document Types (DTs), and Attributes. |
| Metamodel Item | A type of building block for the model. Either an Object Type or Relationship Type. |
| Metamodel Solution | A set of Metamodel Items that are used to direct the creation of Model content. |
| Model |
A set of Objects and their Relationships that may represent a state or time period in the organization. Models can be compared to libraries. Do not confuse Models with SharePoint libraries. Source Model: a Model where the original Model Item exists. Target Model: a Model that is aimed to be used for any further action. |
| Model Area | The OrbusInfinity Area that is used for managing Model Items, creating Visualizations, creating Views, managing Document registration, and navigating to SharePoint. |
| Model Item | An instance that exists inside the Model, either an Object or Relationship. |
| MSC | Abbreviation for the Model-Solution-Category filter. |
| Object | A building block that may exist in any number of occurrences, can have associated metadata and can be related to other Objects, Documents, and Diagrams. |
| Object Type (OT) | The definition, or blueprint, for a specific type of building block. They define the metadata recorded against the Objects based upon them. For example, Application or Business Capability can be referred to as Object Type. |
| Relationship | A form of interaction between two Objects. |
| Relationship Type (RT) | A specific type of interaction between certain Object Types. |
| SharePoint library | It is used to store Documents and Diagrams, and to provide a portal to display views and Model content across the whole organization. |
| Variant | A reused Object or Relationship that has Attribute values different than the original Object. |
| View | A tailored representation of Model Items. A View shows a particular perspective of the architecture or may show the entire architecture or just a part based on the specified criteria. |