Tangram Pro™ is built to help you solve software integration challenges with tools to understand, adapt, and protect critical systems. It has a web-based interface with features designed for component management and model-based systems engineering. This section introduces the major features of Tangram Pro™. The capabilities of each feature will be detailed in later sections, including Tangram's automated workflow engine and plugins for test and assurance tools.
There are two ways to navigate to the major sections of Tangram Pro™: through the Tangram Pro™ Dashboard and from the Navigation Menu
The Dashboard is the first screen shown when you log in to Tangram Pro™. It provides quick access to all of the resources in your instance. The tools in Tangram Pro™ are organized into three sections: Component Library, Repositories, and Your Teams.
The Navigation Menu is another way to access the resources in your instance. It persists as you move through different sections of the app and has a link to return you to your Dashboard
Teams are groups of users in a Tangram Pro™ instance who work together on a shared set of resources. The team owns, administers, and manages the Components created by its members and any repositories they connect to Tangram Pro™. The Your Teams Tab displays all of the Teams to which you belong.
Clicking on a Team list item opens the Team Details Page. Team Members can view a list of all users who belong to the team and have the option to leave the team. Team Owners can also add new Members, edit the Team details, and manage the users in the Team.
TEAM OWNERS are users with administrative roles for the Team to which they belong. They can add, manage, and remove other users from the Team and edit the Team's settings.
TEAM MEMBERS are users with non-administrative roles for the Team to which they belong.
All of the Components and Repositories in an instance are owned by a Team. Every Tangram Pro™ user can view every resource in the instance, but only users who are part of the Team that owns the resource can edit or update it.
Tangram Pro™ currently supports integrations with GitHub, GitLab, and Bitbucket, and can be used to connect to repositories via Distribution Key. You can see your Teams' existing integrations and add new ones in the Repositories Tab.
Tangram Pro™ allows users to view and model systems hierarchically by describing components and the way they connect together. The Component Library section of Tangram Pro™ houses all of your instance's Components and gives you access to tools to define Component Types and create Component Implementations.
A COMPONENT TYPE is the external view of a component which includes the interface ports used to exchange data or events. Each component type is a clearly defined element that can exist as a standalone function or be used in different implementations.
A COMPONENT IMPLEMENTATION is the internal view of a component where its functions and subcomponents are structured. Users can construct component-based systems by connecting Component Types together in an implementation.
Components are owned and managed by Teams but can be viewed in the Component Library by every user in the Tangram Pro™ instance.
Every Component in your Tangram Pro™ instance is shown in the Component Library List. You can search the list by Component name and filter it by category and the team who owns it for quick access to the resources you need.
Clicking on a Component expands its details pane where you can view the Component's ports, properties, and implementations. The details pane also provides a Copy button so you can quickly duplicate the Component for your own use.
Creating a new Component is a one-step process initiated with the New Component button.
Components require a Name, Category, and Team. All Teams you belong to are shown in the Select Team dropdown. The team you select will own the Component, and all the users in that team can edit its type and create implementations for it.
You can define the Component Type for your new Component after it is created. Clicking Edit Type allows you to add ports and properties to extend its capabilities.
The Component Library is the starting point where core tools for building Component Implementations are accessed in Tangram Pro™. A single Component can have multiple implementations, and similarly can be used as part of other implementations. All of a Component's existing Implementations are listed and accessed in its Details Pane.
Implementations can be viewed by Tangram Pro™ users, but only users who are part of the team that owns the Component can add or edit its Implementations.
Creating a new Implementation is a simple process initiated by clicking the Add Implementation button in a Component Details Pane.
Subcomponents and the connections between them within a Component Implementation are added and edited in Workspaces. Workspaces are accessed from the Implementation Details view by clicking on Open Workspace.
You can edit the Component Type in the Workspace and also access the Component Library to add subcomponents and build the Component Implementation. Please see the Component Implementations section for more details.
Tangram Pro™ allows users to create Workflows for their components. Workflows are triggered manually or through webhooks and run with Tangram\'s Workflow Engine.
The WORKFLOW ENGINE is under-the-hood technology where Tangram Pro™ runs user-defined workflows.
WORKFLOWS are a series of tasks run against components. Workflows can be used to generate Component Software Interfaces, documentation, and assurance artifacts.
Tangram Pro™ provides a diverse set of tools for customizing workflows and their outputs. Workflow tools are accessed in Component Implementation Workspaces.
All of a Component Implementation's existing Workflows and details about their most recent run can be seen from the Component Library by viewing the Implementation in the Component Type Details pane and in the Component Implementation Workspace.
Workflows for a Component Implementation can be viewed by all Tangram Pro™ users, but only users who are part of the team that owns the Component Type can add, edit, or run workflows for it.
Creating a new workflow is a quick process initiated by clicking the New Workflow button in the Workflows Pane of a Component Workspace.
Workflows require a name and can be given a description. Once created, the new Workflow is shown immediately in the Workflows Pane and is ready to be configured.
Clicking on the new Workflow opens its Details View in the Workflow Pane. This is where you can edit the Workflow's name and description and add Tasks and Webhooks to automatically trigger the workflow to run.
Workflows require at least one Task before they can be run. Tasks are customized workflow steps run against a component. Tangram Pro™ provides Plugins for users to configure and add to the workflow as Tasks.
PLUGINS are third-party tools provided in Tangram Pro™ as configurable workflow tasks.
Each plugin has its own configuration options to review and select. Tasks can be added and organized to display dependencies in the Workflow Tree space.
Tangram Pro™ supports the use of Webhooks to automatically trigger Workflow runs from your own source code platform. This is optional and is also set up from the Workflow Details Pane.
Workflows in Tangram Pro™ are run with the click of a button. Simply select the workflow you want to run and click Run. The workflow will begin immediately and show real-time status of each task in the Jobs List.
The status of every workflow run is displayed in real-time. Logs and other results of workflow tasks can be viewed and downloaded after the task completes. Workflow tasks may output generated code, assurance documentation, and other types of artifacts depending on the type of plugin selected. Two typical types of workflow task outputs are Component Software Interfaces and Assurance Artifacts.
A COMPONENT SOFTWARE INTERFACE (CSI) is also known as "glue-code". It is the code Tangram Pro™ generates which enables components to communicate and work together.
ASSURANCE ARTIFACTS are the output from Assurance Tool Plugins run in workflows.
Logs, results, and artifacts are viewed and downloaded from the Jobs List. The Workflows section includes detailed information about creating, managing, and running workflows, as well as understanding workflow plugins, tasks, and jobs.