| Term |
Definition |
| AI Assistant |
Innoslate's AI, powered by ChatGPT, response assistant used to aid users on general inquiries. |
| Acronym Extractor |
The Acronym Extractor tool in Innoslate allows you to take all of the acronyms out of a current document and put them into a new document of just acronyms with their full names. |
| Action |
The "Action" class in Innoslate is one of the parent classes in the database schema. It is used to represent an action entity within the system as one of the primary nodes of events. |
| Action Diagram (LML) |
The Action Diagram is a visualization of the functional components of a system model traditionally known as a functional flow diagram. |
| Activity Diagram (SysML) |
The Activity Diagram is a behavior diagram showing flow in terms of actions, and inputs & outputs. |
| Activity Feed Report |
The Activity Feed Report allows you to take create a custom .csv report for all the activity feed on the project dashboard. |
| Admin Dashboard |
Each organization within Innoslate has an Admin Dashboard to manage users, licenses, roles, and teams. |
| All Matrices Output |
All Requirements Matrices - A workbook containing the RVTM, RVM, RTM, and RSM as a .xlsx file. |
| Artifact |
The "Artifact" class in Innoslate is one of the parent classes in the database schema. It is used to store information about artifacts, which can be documents, files, or any other tangible or intangible item that is produced, modified, or used during the course of a project. |
| Asset |
The "Asset" class in Innoslate is used to capture the physical components of a system. It represents a construct in the system model and can have various types specified in Innoslate's default schema |
| Asset Diagram (LML) |
The Asset Diagram is a diagram representation of the physical components of a system model traditionally known as a physical block diagram. |
| Attribute |
Specific characteristics or properties associated with an element, such as a requirement or component. |
| Auto-Number |
Automatically auto-number entities based on the hierarchy available in documentation. The feature will follow the hierarchy throughout the entire surface. |
| Banner |
The info header that appears at the top of a page in Innoslate. Used to declare project classifications when required. |
| Baseline |
Baseline your requirements documents, quickly see changes from the last baseline with the baseline indicator and create Baseline Change-Reports. |
| Baseline Requirements Documents |
Baselining your Requirements Document creates a snapshot of your requirements document at that moment in time when the baseline is created. All document entities, their relationships, and attributes will be captured. |
| Basic Document Output |
A dump of the document below to a .docx file. |
| Basic Tabular Output |
A dump of the document below to a .csv file. |
| Block Definition Diagram (BDD) (SysML) |
The Block Definition Diagram is a structure diagram showing blocks, their attributes, and their hierarchical relationships. |
| CAD Viewer |
Upload your CAD models in .obj or .stk format to see a 3D model that you can navigate in Innoslate. The CAD model will automatically develop high-level asset diagrams. |
| CONOPS |
The CONOPS Documents View allows creating Concept of Operations documents from scratch or a template and editing existing CONOPS documents. |
| Calendar |
Create a project calendar to keep track of important project events and view it in your Project Dashboard. |
| Cancel |
Exits a document or diagram without saving. |
| Change Password |
Directs users to change their login password. |
| Change Request |
Change Request feature allows for configuration management between Project Owners and Reviewers. Reviewers are able to request changes on entity elements such as relationships and attributes. The change request is communicated with Owners, where they have the option to Approve/Reject requests. |
| Characteristic |
The "Characteristic" class in Innoslate is one of the parent classes in the database schema. It is used to store information about a specific characteristic of an entity |
| Charts Dashboard |
Within ‘Charts Dashboard,’ you can create new charts for your project, as well as view two panels of existing charts: Most recently modified charts and all existing charts. |
| Chat |
Chat with an active team member anywhere in the project or group chat with all the team members. |
| Child |
The subordinate element, class, or entity that is directly associated with and contained within a higher-level parent element. |
| Class |
Predefined template that defines the attributes, relationships, and behaviors of a specific type of element within a project. |
| Class Diagram (General) |
A new Class Diagram has been added for specifying software and data models with ease. |
| Clear Sessions |
Clear Sessions is used to clear all "Innoslate Cache" and settings pre-existing, reseting the platform to its stock settings. |
| Clone Entity |
The action of creating a duplicate of a specific element, such as a requirement or document in a widget. |
| Comment |
Owners, collaborators, and reviewers can leave comments on any entity throughout an Innoslate project. |
| Comment Report |
A table of the user comments from the selected entities to a .xlsx file. |
| Compilation Dashboard |
Compilation Dashboard gives you the ability to create a comprehensive document that allows users to combine entities from all classes available on Innoslate to be combined into one. All entity relationships, labels, and attributes remain. |
| Conduit |
The "Conduit" class in Innoslate is used to capture the relationships between the physical components of a system. It represents a "Conduit" construct with a "connects to" relationship to each of the entities which represent the two connected constructs |
| Cost |
The "Cost" class in Innoslate is one of the parent classes in the database schema. It is used to store information related to the cost of a project or system. This class allows users to track and manage the financial aspects of their projects |
| Cross-Project Collaboration |
Cross Project Collaboration allows you to create relationships between projects and share data. If a user is not shared on a project that has cross project collaboration, the user will see the information has been redacted. |
| Database Dashboard |
Database Dashboard gives you the ability to create new entities as well as sort, filter, search, create reports, and perform bulk operations on any of the existing entities in your project. |
| Decision |
As defined in the LML Specification as “A Decision entity specifies a challenge and its resolution.” Typically, Decision Entities are used in conjunction with risks or to justify design decisions. |
| Dependency |
Dependency shows a relationship between two entities where one relies on or is influenced by the other. Dependencies indicate the interconnectedness of various entities in a project, illustrating how changes or developments in one entity can impact others. |
| Deselect |
Exits out of editing a specific entity. |
| Diagrams Dashboard |
Diagrams Dashboard displays thumbnails for every diagram in your project allowing for quick navigation between diagrams and ability to create, delete, filter, search, and sort any diagram available in Innoslate. |
| Discrete Event Simulator |
Innoslate's 'Discrete Event Simulator' facilitates in-depth analysis of a system or project's behavior and performance over time. This simulator leverages advanced modeling techniques, similar to the 'Monte Carlo Simulator', but introduces variability. It achieves this by simulating the sequence of operations based on discrete points in time, each representing a significant state change or event, to provide a detailed, event-driven perspective of the system or process model. |
| DoD CAC |
Innoslate can authenticate users with CAC Cards. |
| DoDAF Dashboard |
DoDAF Dashboard gives you access to create new or edit any of the existing DoDAF 2.02 products in your project all from a single screen. |
| Document |
A structured and organized representation of information that can include text, images, diagrams, and other content, providing a means to present and communicate project-related data. |
| Document Export |
A dump of the document below to an Innoslate .xml file. |
| Document Template Generation |
Innoslate allows you to create your own Document Templates to be used throughout your project. From ‘Documents View’, you can generate a snapshot of your document for further replication in the project. |
| Documents Dashboard |
Within ‘Documents Dashboard,’ you will be able to create new documents, as well as manage any of your ‘Existing Documents’ for your selected project. |
| Duplicate |
The act of creating an identical copy of a specific entity, diagram, or document within a project. |
| Entity |
An individual item, object, or concept that is part of the system being modeled, analyzed, or documented. |
| Entity Definition Report |
An output of all attributes, labels, and relationships for the selected entities to a .docx file. |
| Entity Notation |
In an entity description, you can add self-updating notations. These notations can be a name, number, or attribute of any entity in the project. |
| Entity Relationship Matrix |
A matrix of the selected entities' relationship to other entities through a single relationship. |
| Entity Table Report |
A table of the selected entities' attributes and optionally (See: Add Sibling) its selected related entities. |
| Equation |
The "Equation" class in Innoslate is one of the parent classes in the database schema. It is used to store information related to equations. |
| Errors |
Entities that break certain rules are highlighted as errors in Innoslate's Intelligence View. |
| Find and Replace |
The find and replace feature on Innoslate allows users to search for specific text strings within a document and replace them with desired content. |
| Gantt Chart |
Develop project schedules and view dependency relationships between activities and the current schedule status. |
| GitHub Integration |
The GitHub integration with Innoslate allows users to simultaneously create push/pull requests, issues, etc. The integration transfers all information from GitHub to the connected project on Innoslate. |
| Global ID |
Unique identifier assigned to a specific element or object within the entire project. |
| Hierarchy Diagram (General) |
The Hierarchy Diagram is a type of hierarchical organizational visualization used in Innoslate as a means of visualizing up to ten (10) levels of decomposition of entities top-down. |
| History |
View every version of every entity in Innoslate. History allows you to see all modifications, the date of the modification, and the user that made the modification. You’ll also be able to revert to previous versions. |
| History Report |
An output of the history and changes of the selected entities to a .docx file. |
| I-Squared Diagram (General) |
The I-squared diagram is a matrix that represents Assets and Conduits. |
| ICOM (A0) Diagram (General) |
The ‘ICOM (Inputs, Controls, Outputs and Mechanisms) Diagram’ is a structure diagram showing relationships between Inputs/Outputs, Actions, and Assets. |
| ID |
A unique label or code assigned to a particular element, entity, or item within a document or diagram. |
| IDEF0 Diagram (General) |
The ‘IDEF0 Diagram’ supports five (5) unique diagram constructs: a ‘Function’ a ‘Mechanism’, an ‘Input’, an ‘Output’, and a ‘Control’. |
| ILSPs |
The ILSPs Documents View allows creating Integrated Logistics Support Plan documents from scratch or a template and editing existing ILSP documents. |
| IV&V Plans |
The IV&V Plans Documents View allows creating Independent Verification & Validation Plan documents from scratch or a template and editing existing IV&V Plan documents. |
| Import Analyzer |
Import Analyzer guides you through the process of importing information from Microsoft Word, Microsoft Excel, Rational DOORS (.csv), Plain Text (.pdf, .txt, etc...), ReqIf, and previously exported Innoslate XML. |
| Innoslate Help |
Innoslate's AI-powered chat bot used to aid Help Center related questions. |
| Innoslate XML Output |
A dump of the database to a .xml or.inno file. Note XML files are only forwards compatible and must be imported to version 3.8.0.2 or later. To import to an earlier version contact support. |
| Innoslate ZIP Output |
An output of all database information of all entities into an .inno file. |
| Input/Output |
The "Input/Output" class in Innoslate represents a construct used to capture anything introduced into the system being modeled. It is used to represent an "Input" construct with a received by relationship to the entity which represents the "Function" construct being pointed to. |
| Intelligence Dashboard |
Intelligence analyzes your project’s model to assess traceability, model construction, naming conventions, and more. |
| Interface Control Diagram (General) |
The Interface Control Diagram (ICD) is a visual representation that depicts the flow of data, control, and interface relationships between different components or systems in a project. |
| Internal Block Diagram (IBD) |
The Internal Block Diagram is a structure diagram showing the internal structure of a block including their ports and relationships. |
| Issue |
The "Issue" class in Innoslate is a type of entity that can be created in each Innoslate repository. It can represent an issue within an entity to be related to other classes such as risk, etc. |
| Java SDK |
The JAVA SDK integration with Innoslate allows for the creation of software and features for specific frameworks, personalized to Enterprise Users. |
| Kanban Board |
Utilize the 'Kanban Board' to visualize and manage work-in-progress, track task status, and understand workflow patterns in real-time. |
| LDAP |
Innoslate can talk to your LDAP system to authenticate users. |
| Labels |
Descriptive tags or keywords that can be associated with elements, documents, or other objects. |
| Layer Diagram (General) |
The Layer Diagram visualizes multiple levels of physical decomposition and the Conduits linking those Assets together. |
| Lock Entity |
The action of restricting or preventing further modifications to a specific element or object within a project. When an entity is locked, it becomes read-only, ensuring that its content and attributes remain unchanged. |
| Logical |
The "Logical" class is a child class of the "Connection" class in Innoslate. It represents a logical connection between entities. |
| MATLAB Toolkit |
MATLAB Integration in Innoslate allows the interoperability functionality that enables users to execute MATLAB scripts and utilize MATLAB's numerical computing capabilities directly within the Innoslate platform |
| Manage Projects Dashboard |
This page allows a user to create, copy, delete, export, filter, search for, share, unshared yourself from, and edit the settings of Innoslate projects. |
| Measure |
The "Measure" class is a child class of the "Characteristic" class in Innoslate. It is used to define and store information related to measurements or metrics within a project. |
| Merge |
After Branching/Forking, users have the ability to merge the differences of the two projects into one comprehensive project. |
| Monte Carlo Simulator |
Innoslate’s ‘Monte Carlo Simulator’ allows for realistic analysis of a system or project’s cost, schedule, and performance. This simulator utilizes the same modeling techniques and technologies of the ‘Discrete Event Simulator’ but removes inherent uncertainty. This is accomplished by running the simulation repeatedly with different random seeds to achieve a more comprehensive view of the model. |
| My Profile |
Directs users to their profile page. |
| N-Squared Diagram (General) |
The N-Squared diagram represents functional or physical interfaces between entities. |
| Native |
Authentication can be handled through Innoslate. |
| Orbital |
The "Orbital" class is a child class of the "Location" class in Innoslate. It represents entities related to orbital locations. |
| Organization Dashboard |
Here you will find your recent projects and a description of your organization, as well as a guided tour to help you get started with Innoslate. |
| Package Diagram (SysML) |
The Package Diagram is a structure diagram showing packages and their relationships. This diagram is used to describe how a model is organized. |
| Parametric Diagram |
The Parametric Diagram represents mathematical equations. It is a restricted form of the Internal Block Diagram that shows the relationships between the Constraint (Equations) entities and the Parameter (Characteristics) entities. |
| Parent |
A higher-level entity or class that holds or contains other subordinate entities or sub-classes in a project's hierarchical structure. |
| Physical |
The "Physical" class in Innoslate is a child class of the "Location" parent class. It represents physical components of a system model. |
| Physical I/O Diagram (General) |
The Physical I/O Diagram is in a way a crossover diagram that displays the functional interactions and relationships between the physical components of a system model. |
| Pie Chart |
A Pie Chart in Innoslate is a widget that displays a breakdown of the entities within a project by Class, Label, or Enumeration in the form of a pie/doughnut chart. |
| Post Baseline Change Report |
Post Baseline Report - Report containing the changes since the last baseline. |
| Project |
An Innoslate project serves as a comprehensive compilation of entities, providing a systematic approach to organizing and managing your project's data efficiently. |
| Project Management Dashboard |
Each Innoslate project has its own 'Dashboard', here you can access helpful getting started links and keep up to date on your project’s status, database changes, and model maturity all in one place. |
| Project Management Plans |
The Project Plans Documents View allows creating Project Management Plan documents from scratch or a template and editing existing Project Plan documents. |
| Project Version Control (Branching/Forking) |
Users can use branching and forking to create duplicates of projects and track changes between the two after the event. |
| Quality Check |
Using Natural Language Processing within Requirements Document View, use the built-in AI to automatically check and score your requirements. This tool will also recommend ways to write more clear and complete requirements. |
| Query |
A structured command that can be used to retrieve specific information from a project's database. |
| REST API |
The Representational State Transfer (REST) API allows users to use a set of rules and script commands to interact with Enterprise Innoslate software available. |
| RSM Output |
Requirements Satisfaction Matrix - A table of requirements with the entities that satisfy each requirement as a .xlsx file. |
| RTM Output |
Requirements Traceability Matrix - A table of requirements with the entities that trace to each requirement as a .xlsx file. |
| RVM Output |
Requirements Verification Matrix - A table of requirements with the entities that verify each requirement as a .xlsx file. |
| RVTM Output |
Requirements Verification Traceability Matrix - A table identifying which test cases verify each requirement. |
| Radar Diagram (General) |
A Radar Diagram, is a graphical method of displaying multivariate data in the form of a two-dimensional chart, where three or more quantitative variables are represented on axes starting from the same point. |
| Relationship |
A connection or association between two or more elements, documents, or entities within a project. |
| Reqif Output |
ReqIF Output in Innoslate refers to the feature that allows users to export selected requirements entities' attributes as an .reqif file. |
| Requirement (class) |
The "Requirement" class on Innoslate is a construct that represents a specific requirement in the system model. It is a rounded block with two sections. The top section contains the name of the requirement, while the bottom section contains the identifier, text, and rationale of the requirement. |
| Requirement (definition) |
Requirement refers to a specified condition, capability, or constraint that must be met by a system. |
| Requirement Diagram |
The Requirement Diagram displays requirements, their hierarchy, and their relationships to model entities. |
| Requirements Document |
Requirements Document is a hierarchical, document-like display of Statements and Requirements with collapsible sections, inline entity editing, sorting on any attribute column, and customizable attribute columns. |
| Resource |
The "Resource" class in Innoslate represents a physical object that is consumed, produced, or seized by a function. It provides a visual representation of the resource and its usage can be monitored during simulation |
| Risk |
The "Risk class in Innoslate is a parent class that allows users to store and manage information related to risks. The Risk class is used to visualize the severity of consequence versus probability using a Risk Diagram or Risk Matrix. |
| Risk Burn-Down |
View how risk could affect project completion in the risk burn down chart. |
| Risk Diagram (General) |
A Risk Diagram is a visual tool used for analyzing, assessing, and communicating project risks, representing the likelihood and impact of potential hazards. |
| Rollup Model |
Innoslate has the ability to calculate and display an entity’s rolled-up attribute values up to 25 levels of hierarchy. With Numbers, Durations, Enumerations, and Multiselects, the Rollup Tool can easily roll up their values and allow you to apply those values as the attribute value in the parent entity. |
| SOPs |
The SOPs Documents View allows creating Standard Operating Procedure documents from scratch or a template and editing existing SOP documents. |
| SRD Generator |
A System Requirements Document can be generated easily from an asset diagram. |
| STK API |
STK API Integration in Innoslate's Enterprise version refers to the implementation of the Systems Tool Kit (STK) API, facilitating interoperability between Innoslate and STK, allowing users to model, analyze and visualize complex systems. |
| Save |
Saves all changes made to a document or diagram. |
| Schema Editor |
The Schema Editor enables power users to extend their project’s current database schema to better meet their needs. |
| Sequence Diagram (SysML) |
The Sequence Diagram is used to visualize the order and direction of message flow/interaction between lifelines/assets. |
| Spider Diagram (LML) |
The Spider Diagram is a type of hierarchical organizational chart used in Innoslate as a means of visualizing traceability. |
| State Machine Diagram (SysML) |
The State Machine Diagram is a behavior diagram showing states and their transitions. |
| Statement |
The "Statement" class in Innoslate is one of the parent classes in the database schema. It is used to store information related to statements or assertions made within a project. The attributes and relationships associated with the "Statement" class allow users to define and manage statements in their projects |
| Sub-Class |
Specialized template derived from a parent class, inheriting its attributes and behaviors while allowing for additional customization to represent a more specific type or variation of the parent element within a project. |
| Support Dashboard |
The Support Dashboard allows a user with Admin or Support access to send/copy users’ password reset links and activation links – that way users who cannot remember their passwords can simply contact their support team or an administrator, and their password links can be sent to them without inconvenience. |
| Suspect Assist |
Suspect Assist will automatically identify related entities which have few similarities and a low confidence of correctness. The suspect relationships will highlight in red. The darker the color red, the higher confidence a relationship should not be present. |
| TVM Output |
A table identifying which requirement each test case verifies. |
| Table Notation |
In an entity description, you can add self-updating tables. These tables can include names, numbers, or attributes of any set of entities in the project. |
| Task |
The "Task" class is a child class of the "Action" class in Innoslate. A Task entity specifies an Action that must be completed for a particular project. It served as a "To-Do" for the Project. |
| Test Case |
The "Test Case" class is a child class of the "Action" class in Innoslate. A Test Case entity represents a set of conditions utilized to determine whether a system works as intended. |
| Test Cases Output |
A dump of the test cases below to a .docx file. |
| Test Center Dashboard |
Test Center is a hierarchical, document-like display of Test Suites & Test Cases. |
| Test Cycle |
A "test cycle" on Innoslate refers to the process of running all the procedures to execute all the tests against a product, service, or system. It involves selecting the test suite, creating a new test cycle, and setting the attributes of the test cases. |
| Test Plans |
The Test Plans Documents View allows creating Test Plan documents from scratch or a template and editing existing Test Plan documents. |
| Test Suite Export |
A dump of the test suite below to an Innoslate .xml file. |
| Test Suite ZIP Export |
A dump of the test suite below to an Innoslate .xml files, stored in a ZIP compressed file. |
| Time |
The "Time" class in Innoslate is a parent class that allows entities to specify points or periods when something occurs or during which an action, asset, process, or condition exists or continues. |
| Timeline Diagram (General) |
The Timeline Diagram is used to graphically depict a chronological sequence of events. |
| Traceability Assist |
Traceability Assist will automatically identify likely relationships using pre-trained machine learning models. The suggested relationships will highlight in green. The darker green signifies higher confidence a relationship should be present. |
| Traceability Matrix |
The Traceability Matrix displays an entity’s hierarchy to other entities. This matrix will show the chosen relationship between the chosen entities. |
| Transform To |
The action of converting or changing an entity from one type or class to another. This action allows you to redefine an entities data, attributes, and relationships. |
| Transition |
The "Transition" class is a child class of the "Action" class in Innoslate. A Transition entity specifies an action that, once completed, transitions one state (Characteristic) to another state (Characteristic). |
| Tree Diagram (General) |
The ‘Tree Diagram’ is a type of hierarchical organizational chart used in Innoslate as a means of visualizing unlimited levels of decomposition of entities horizontally from left to right. |
| Use Case Diagram (SysML) |
The Use Case Diagram is a behavior diagram that shows how an actor interacts with a system under different use cases and their relationships. |
| VCRM Output |
Verification Cross-Reference Matrix - A table identifying each requirement’s verification method(s). |
| Virtual |
The "Virtual" class is a child class of the "Location" class in Innoslate. A Virtual entity specifies a location within a digital network. |
| Warning |
Warnings can be found and highlighted in Innoslate's Intelligence View. |
| Widget |
Widgets can display various types of information, such as project descriptions, notes, countdowns, diagrams, test suite summaries, images, and more. |
| Workflow |
Create workflows to manage your whole team. |
| X/Y Plot |
Innoslate can capture results from simulations and tests as XY Plots. Import output from other tools to create the Innoslate objects automatically. |
| XMI importer |
Importer specifically for exports from MagicDraw, Enterprise Architect, or Rational Software Architect. |
