Which Symbol?

Model Based Systems Engineering Drawings

Model-based Systems Engineering represents systems engineering components in domains, gathering together the data and functions in a formalised manner. This helps with the exchange of data between different disciplines, stakeholders and customers within a common frame work. Element details are often represented as a symbol on a diagram.

A common systems modelling technique, for say the functional aspects, would be to show them in a multi-tier, time-sequenced, step-by-step flow diagram or eFFBD. The diagrammatic format makes it much easier to assimilate the whole concept.

Whilst our help offers good coverage of the modelling capabilities in Cradle. We understand getting to grips with the details of the tool can be complex. When you are working with a new diagram type for the first time, some of the symbols can look very similar. The palette on in the sidebar shows tootips, but hovering over each is not very efficient. If you are confused about which symbol is which, select ‘Draw‘ button from Tools ribbon. You will then see the name of each symbol alongside its icon.

Selecting different symbols
Diagram Drawing Palette
Article Updated 16/05/2018

Hiding Information

Teams / Skills / Roles and Visibility

Not all data in all projects should be visible to all users and roles. Hiding information in Cradle can be done in a number of ways.

Classification

A hierarchical access control is provided with Item Classifications. These Classification values restrict a user’s ability to see an item based on their clearance level. The values are a sequenced list, those users with a higher classification will be able to see items equal or at a lower classification than the level they hold. The classification is set on an item by item basis.

Screenshot of user privileges dialog
Classifications

Item Types

Entire item types can be hidden from users based on their skill. If you don’t want some users to see finance information, then ensure you create a finance item type. Create and assign a finances skill to this item type and then only give the skill to those who warrant it.

Read Only Items

The same mechanism that controls complete access to an item type can also be used to assign RO accessibility. Regardless of the item’s state (draft/baselined etc.) users are only allowed RO access based on the skill they possess.

Read Only Categories

You can protect certain bits of information within an item from alteration by setting a skill which prevents updates by those without the skill.

Frame Access Control

Frames are used to hold larger blocks of data within an item. These could be paragraphs of text,  binary documents (such as a spreadsheet) or just a date. Access to individual frame types can be controlled by a skill. Users without the skill will either not see the frame at all or will see it Read Only.

Privileges

The privileges a user holds can control whether they can see information based on ownership. The normal pattern being users and the teams they belong to being able to see items owned by the users and their team. Access to information owned by teams to the side, above or below the current user is controlled by the User’s Privileges

Screenshot of user privileges dialog
User Privileges
Article Updated 04/02/2019 – Added images

Show Link Types in HIDs with Colour

Looking for a way to brighten up your day?!

What better way than using Hierachy Diagrams (HIDs) that show link types in colour!

Hierarchy Diagrams (HIDs) are an excellent way to show the relationships between items in your database. The boxes in the diagrams are the items and their connecting lines are the cross references.

You can define a colour for each cross reference link type in the schema. If you do, then these colours are used to draw the cross references in HIDs.

This means that you can easily interpret the connections shown by the HID as, for example ‘has child’ or ‘is satisfied by’, or ‘allocated to’ relationships.

If you have not tried setting colours for your cross reference link types, please try it and see how this will transform the ease with which your HIDs can be interpreted!

Screenshot showing Example Hierarchy Diagram
Example Hierarchy Diagram