From concept to creation
We are pleased to announce the third in our new series of white papers that will discuss the role of different types of information in systems engineering processes, and how to deploy each of them in Cradle.
The third white paper in this series discusses system requirements. It is available here:
Visit the Resources section of our website: www.threesl.com for this and many other useful resources!
We hope that this white paper is interesting, the next one will appear quite soon!
We have updated the white papers in our website:
https://www.threesl.com/downloads/white-papers.php
from where you can download the revised white papers related to Cradle:
– Document management
– Project management
– Information assurance
– Reuse and adaptations
– Regulation compliance
and also the white papers focused more on systems engineering concepts and their support in Cradle, specifically:
– Needs in Systems Engineering
– User Requirements in Systems Engineering
We hope that these are helpful!
Visit our site, download the papers and take a look!
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.
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.
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.
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.
You can protect certain bits of information within an item from alteration by setting a skill which prevents updates by those without the skill.
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.
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
The INCOSE 2016 show has now ended and we would like to send our thanks to everyone who visited us during the conference!
We would also like to thank those customers who presented papers during the event that included Cradle screen shots!
As #3SL was very busy during the event, If we were not able to spend as much time with you as you needed, then please contact us through LinkedIn or salesdetails@threesl.com
Once again, we would like to thank everyone for making the INCOSE show a success!
With best regards
We are pleased to announce that our July 2016 newsletter is available here:
https://www.threesl.com/pages/news/webletter-July16/index.php
which provides home useful tips for customising your Cradle environment, describes a new range of videos for our Russian colleagues, summarises the SysML support in Cradle-7.1.1 and invites you to visit us on stand B4 at INCOSE 2016.
We hope that you find it interesting and helpful!
We are delighted with the many visitors to our stand at INCOSE 2016 over the first day. Thank you very much for visiting us!
If you are at the show and what to see SysML integrated into the lifecycle, or see how requirements management and full document traceability should be done, then please visit us at stand B4 for a chat!
We have a new trailer video that is being featured on our stand B4 at the INCOSE show and is now on our website’s homepage:
Please take a look and tell us what you think!
With best wishes from a sweltering UK!
Trees are a common way to explore the information in a database and controlling tree labels is important as:
• Any query’s results can be shown in Tree style
• Trees are available for each item type from the Project sidebar
• The Phase hierarchy can contain nodes that run queries whose result item are shown as nodes in the phase hierarchy tree
A default tree view can be set for individual items. This view is used to construct the text label whenever a tree node is added for an item of that type. Any frames, linked items, discussions are ignored.
As shown in the screenshot below, “REQ-1” in the DEMO project as the top level item, using the tree view you can see all items which are linked to REQ-1
Cradle has a default for the labels of the nodes in these trees. This default uses an item’s Identity, Name, Key, Version and Draft attributes. This label may not be what you want to see, particularly if:
• Your items are auto-numbered, so the Identity is generated by Cradle and is not important to you,
• If most of this type of item do not have anything in their Name attributes
You can control the contents of labels in tree nodes. To do this:
1. Login to WorkBench as a user who can modify the schema and can create project-wide views
2. Define a new view that lists the attributes that you want to appear in the labels. This view can include any attributes except calculations and frames. Only the first row in the view will be used. Save the view with Project scope, to ensure that everyone can use it.
3. Start Project Setup from the Project tab, set Options to Item Definitions and select the Item Types tab
4. Select the item type whose tree labels are to be set and choose your view from the Tree view: drop-down list
5. Save the schema and close Project Setup
Now when any user sees any items of this type in any tree, the labels for these tree nodes will only contain the information defined by the view.
Setting up tree labels for item types can be a very efficient tool when using Cradle to help your team save time when browsing through the tree nodes for items types, as this will only show the pre determined information the user is looking for.
If you want your reports to match you Corporate style, you can create your own Report Styles in Cradle. Although this example of the Vibrant Corporation takes it to the extreme!
You can save the style and apply it to each report generated throughout Cradle. This applies to HTML and RTF styles, plain text and CSV are not altered. See Cradle help for more details. Whether you are printing a list of items from the database, or the component parts of a data definition or a baseline summary, you can pick from the built in styles or create your own.
Reports can be run from within the Phase hierarchy (great if you need the same report running regularly) or directly through the Reports tool.
We need a software engineer to join the Cradle development team and contribute to the specification, design and build of the current and next generation of Cradle products.
If you are interested, please see here:
https://www.threesl.com/opportunities
where you can download details of the opportunity.