Data integrity refers to the accuracy, completeness and reliability of data stored within your Cradle database. Checking database integrity is important as it guarantees both the traceability and searchability of your data. It also increases the performance and stability of your data. Maintaining the integrity of your data is essential. As you collect more and more data within your Cradle project, it is a priority to maintain the integrity of this data, otherwise the data is worthless.
Error checking ensures that your Cradle data hasn’t been compromised, e.g. during upgrades/imports etc. We recommend that integrity checks are done on a regular basis.
In Cradle, there are a couple of ways to check the integrity of your database:
Please note that these checks must only be run when there are NO other users active in the database. If you are in doubt as to whether you are the only user active in the database, then DO NOT run these checks. If you do, damage can occur.
The Item Integrity option allows you to perform integrity checks on your Cradle database. This option is available from the Project tab in WorkBench:
The Frame Version Checks detect missing versions of any frames or missing records in any version of any frame for the item type specified. Errors can be fixed using the Fix button.
There are many Item Checks which are explained here.
Many of these checks can be made subject to one of the following scopes:
Superseded or retired – Selects items with a status of S (Superseded) or T (Retired)
Latest baseline – Selects items with a status of B (Open Baseline)
Deleted – Selects items with a status of D (Deleted)
Current – All current items
If you want to produce a report of the item integrity check, ensure to select the Generate a report checkbox.
Cross Reference Integrity
The Cross Reference Integrity Check option checks the cross references in your Cradle database.
The current set of cross references is scanned to find any cross references that are invalid. Any cross reference is only counted once in these checks. So if a cross reference is dangling and also invalid, it will only appear once in the counts.
Change Requests (CHRs) which are concerned with general statements of the issue to be addressed, or the problem to be solved, or the defect to be corrected
Change Tasks (CHTs) which are concerned with the mechanics of implementing and effecting the change(s) required by one or more CHRs
Both CHRs and CHTs are distinct types of items in the Cradle database and can contain any number of frames. As with standard item types, CHRs and CHTs are provided with some default frames to populate when raising either the CHR or CHT. These are TEXT and NOTES where TEXT is a mandatory frame as this provides the detail.
However, you can also specify in Project Setup whether these item types have any additional frames defined. This can be:
or any other format defined as a frame type:
You can also specify the frames to be mandatory so that the CHR or CHT cannot be raised until those frames are populated. As you can see in the example above the Mandatory checkbox is selected for the JUSTIFICATION frame.
This allows you to ensure that all information is provided for your formal changes.
Are you upgrading/updating your servers? Here we explain moving Cradle projects from an old server to a new server. There are two ways to do this:
Moving projects to a new server with the same Cradle version
Moving projects to a new server and upgrading to a new Cradle version
Both of these scenarios are detailed below.
Please note if users have Personal definitions, e.g. if they are are using Sessions, these will either need to be copied or exported and imported to the new server. Personal definitions are located in $CRADLEHOME\admin\definitions\personal and the folders have the users names. If copying the definitions they need to be placed in the same location within the personal folder.
New Server with Same Cradle Version
If you are not upgrading Cradle at this time, this is really simple to do.
Create the Cradle projects on the new server with the same project code as previously created on the old server. Ensure the pathname is the location where the databases will be stored.
Copy the contents of the Cradle projects on the old server to the new server. The directory contains all of the data including user profiles, project setup, definitions etc.
New Server with New Cradle Version
If you are upgrading the Cradle version as well as migrating to a new server, this is slightly more complex.
The safest method (although can be time consuming) is to create export files of the existing Cradle databases and then import them into the new server installation.
When exporting the information from the “old” server, ensure Owner is set to Everything as shown below:
In the new project you can then import the data exported from the old server . When importing, ensure Owner is set to As in file, Overwrite is set to On and the top four validation checkboxes are selected:
Repeat this for all projects
Another way to achieve this is to copy the project directories from the old server on to the new server and then manually convert the projects.
Create the Cradle projects on the new server with the same project code as previously created on the old server with the pathname being the location where the databases will be stored.
Copy the contents of the Cradle projects on the old server and overwrite the contents of the newly created projects on the new server. The directory contains all of the data including user profiles, project setup, definitions etc.
Manually run the necessary converters to ensure the new projects are in the same format as the new Cradle version installed. Please note this may be several converters if converting from a much older version.
Note: Please ensure the projects have been converted BEFORElogging in.
Welcome to the latest newsletter from 3SL that provides a mixture of news and technical information about us, and our requirements management and systems engineering tool “Cradle”. We would especially like to welcome everyone who has purchased Cradle in the past month and those who are currently evaluating Cradle for their projects and processes.
We hope that we, and Cradle, can deliver real and measurable benefits to all of the exciting development projects that we see every day through your regular contacts with our support team. If you have any problems, please do not hesitate to contact 3SL support here.
Showing Cell Titles in Views
Sometimes when displaying a nested view the cell titles take up a lot of space on the screen.
Within the View Details dialog you have the option to choose whether you want to display the cell titles:
As you can see you can choose to either:
Show the cell titles
Hide the cell titles
Show the cell titles only when the view is top-level
You can change the visibility of any of the component views that are being used to show linked items. In practice, most people either hide everything or show everything.
Following on from our recent Cradle-7.7 release, if you are not already a customer and would like more information about Cradle, you can download the software and a free evaluation licence. You can find this on our website, or you can request a webinar. If you are a customer and would like to upgrade, please contact 3SL for a Security Code and for any assistance you may require with the upgrade.
Upcoming Training Courses
We still have places available on our September Risk Management course. Learn how to identify, analyse, evaluate, treat and monitor the risks associated with activities or events within your business. This course is designed for project team leaders or managers who administer and manage risks.
To book a place on one of our online courses please click here!
Cradle offers two packages Cradle Software as SaaS and Cradle Training and Consultancy.
The software package includes Cradle licences, a pre-defined schema and a comprehensive support package. This can be used in both unclassified (IL0) and OFFICIAL (certified IL3) deployments and covers the following elements:
Application Lifecycle Development
Application Lifecycle Management
Agile Software Development
Agile Software Management
Business Process Modelling
Integrated Risk Management
Integrated Test Management
MBE Model Based Engineering
MBSE Model Based Software Engineering
MBSE Model Based Systems Engineering
Requirements and Testing
Advanced Lifecycle Training
Prices start from as little as £50.00 per user per month. Including email and phone support and full documentation included. Optional onsite support and training is available. This can be supplied on Windows® or Linux®.
A wide range of user customisation is available including:
Items’ (attributes, links and properties)
Display of chosen data and layout through queries, views, forms,
Processing data to give graphs, reports, documents, metrics, KPIs/dashboards, process
CM (Configuration Management) system workflows
UI (User Interface) layout and content
Authentication and access control
For details, see here:
or search for 3SL Cradle. For an overview of Cradle, see our video here: We look forward to helping you achieve success on your future projects, or migrating existing ‘manual’ or disparate works into a fully encompassed solution.
We have created some links between Cradle items but we only want to see a filtered set of these links in our table.
Cradle has a unique ability to follow cross referencestransitively. This means that although an item might not be directly cross referenced from it’s source, it might be linked indirectly through another item/item type.
Cradle also has the ability to name cross references referred to as link types and even group sets of link types together referred to as link groups.
Combining these features can allow flexibility for the output of items that have some relationship to the source which will reduce the number of direct cross references required.
For example, we would like to show dependencies between item type A and item type C but ONLY those that have a yellow and blue link type.
We can see in the screenshot below that only A-6 and A-11 are transitively linked to items of item type C with both a blue and a yellow link:
Navigations allow us to specify how we would like to follow the links that have been created between items. This is a very powerful feature as we can also specify that we would like to follow links transitively:
Using the Navigation in Views
We can now use the navigation to specify that we want to show links between item type A and item type C that are followed transitively but we ONLY want to show the group of links YELLOW AND BLUE. Remember that there are NO DIRECT links between these two item types. The cross references are from item type A to item type B and also from item type B to item type C:
Applying this view, we can see that only the YELLOW AND BLUE links are shown in the table. The remainder appear blank:
Using the Navigation in Queries
We might wish to only show items in our table that have these links in preference to showing all items and just appearing blank where the transitive link does not exist. We can achieve this in the Query Details dialog:
This will now filter out of the list any items that do not match the navigation criteria:
Showing Path in a Tree Style
If we followed the path in a tree style showing downward links, we can see that item type A (A-6 and A-11) are not directly linked to item type C (C-1). They go through item type B (B-2):
Cradle provides a unique ability to allow cross references to be followed transitively (through other items).
Transitive navigations can be applied to views and queries. This provides a very powerful filtering mechanism that allows us to show non-direct dependencies between items.
With the release of 7.7 coming very soon, we thought we’d test Cradle on additional platforms.
So here’s Cradle 7.7 running on a Steamdeck, in Desktop mode.
As SteamOS is based on Arch Linux, our 64 bit Linux version can be installed.
Both the CDS and WorkBench are running on this very capable device. A keyboard and mouse may work better than the on screen keyboard.
If you install the service manager (systemd script) then the Cradle Database Server (CDS) will start on boot up of the Steamdeck, so you might not want to do that if its primarily used for Steam. However, once started the CDS will stay running in the background when you switch to Gaming Mode. If you have others connecting to your CDS then they can continue to work while you improve your hand-eye coordination in your favourite game.
Although Steamdeck is not an officially supported platform, you can see Cradle does indeed run on additional platforms
*If you will have the same users in the new project that are in the existing project.
To avoid the Personal and/or User definition files being part of this import, we would suggest the following:
Log in to the existing project as MANAGER
Select Project > Export
In the Export dialog set Owner to Everything and Info Type to ProjectSchema and User Profiles (if users are required, see comment above)
Press Export to create the export file and close the Export Status dialog but do NOT close the Export Information dialog:
In the Export Information dialog, change the Info Type to ONLY show Definition Files:
You will see that some new options appear – Definition Type and Location:
The Definition Type option allows you to specify the types of definition file to be included in the export. For this example, we will leave this as All:
The Location option defines which location you are exporting the definition files from.
Users may have created Personal or User definition files that might not be relevant to the new project. Personal and/or User definitions might only have been useful to an individual person rather than the project so could be omitted.
In this case, we would only need to select Team*, User Type* and Project
* It may only be necessary to select Project
Press the Export button again. This will present you with the option to Overwrite, Append or Cancel. Select Append:
Select Project > Import and set Owner to As in File and Overwrite to On:
You will see that your new project contains:
All the Project Setup information including the phase hierarchy and all supporting definition files
If you had NOT chosen to append the definition files, it is highly likely that the phase hierarchy from the existing project would not work in the new project and would produce errors.
These definition files are important to define the WorkBench environment.
Also, if you had chosen to export all the definition files, this may have resulted in numerous views, forms, queries, documents etc., that are not particularly relevant or accepted into project definitions.
Open Database Connectivity (ODBC) is an application that allows different types of databases to interface through the use of a library containing data access routines. Cradle now supports connections to DISAM, Oracle and MySQL.
Before installing check the minimum hardware and operating system requirements for ODBC. The following are necessary for a successful installation:
An Oracle or MySQL installation accessible to the CDS preferably on the same machine
An ODBC driver manager
An ODBC driver for the data source you wish to access. For example, Oracle in Oracle for Windows or SQL Server
Please ensure the versions are the following or greater:
Oracle in Oracle from Oracle Corporation version is 18c
MySQL ODBC 8.0 Unicode Driver from Oracle Corporation is version 8.0.16
Windows ODBC Data Source Administrator appropriate for your Windows release
unixODBC driver Manager 2.3.7 or later
*Cradle install will not work with Oracle databases that have been setup using the ‘Create as Container Database’ option.
ODBC is a licence option which can allow Oracle or SQL or both to work with our Cradle Enterprise version. This new licence is not available for any other version of Cradle. For enquires about the new ODBC licence, please email firstname.lastname@example.org.
Cradle and ODBC
The users can still import and export standard export, CSV, XML and now ReqIF files. If a user is on Windows they can still use our Toolsuite applications. The only difference is the access to databases either directly (DISAM) or through ODBC (Oracle and MySQL).
With Cradle supporting ODBC, a user can now install Cradle on the same database server farm as the Oracle/MySQL databases. A separate server is no longer required. Although projects can be on a separate server and linked to the Cradle database using a UNC path e.g. \\hostname\path\projects\mmh1. Click for more information on Storing Project Databases in NAS.
The CDS requires an installation of ODBC on the same machine for either Linux or Windows. Client machines which don’t have the CDS on them don’t need to have ODBC installed at all.
If the Linux distribution you are installing on does not have v2.3.7 of unixODBC as a package, then you’ll need to build this from source. You can download and find installing steps for it from http://www.unixodbc.org/download.html. Ensure the user installing is the System Administrator or a user with administrator privileges for installing both ODBC and Cradle.
Check for the following files on your Linux installation:
If the Windows platform you are installing on does not have ODBC please install the latest Oracle in Oracle for Windows which can be found here. You can find installing and upgrading documents for Oracle Database here and select the release you are on from the drop-down.
Certain settings are required to be selected when using Oracle in Oracle. Check and enable or disable the following options in the Oracle ODBC Driver Configuration checking all numbers:
Turn on the Connection Pooling attributes and use the default options:
Setting up with Cradle
After installation of both Oracle and Cradle, the administrator is required to check and alter the following files correctly:
Support file for the driver when required on Windows usually in ‘Oracle <version>\network\admin’
The following example of a tnsnames.ora file, shows it can have more than one Oracle database location set within it.
Correctly configure the ODBC file for Cradle in %CRADLEHOME%\admin\db_config\odbc called odbc_config
All options are hashed out in the file until an administrator changes them. All options show an example of what can be entered. This is an odbc_config example for just Oracle on one of our installations.
Correctly configure the file create_CRADLE_CDS_USER in cradle\admin\db_config\odbc\setup_scripts
The default user tablespace and users within your Oracle database need to be set within this file. This is to allow the altering and creating privileges for the users. In our original it has:
DEFAULT TABLESPACE “USERS”
The privilege options in create_CRADLE_CDS_USER should be changed to your own tablespace and user names used in the odbc_config file.
Creating New Projects
Users get the same Cradle interface as before but with a new section it now allows connects to 3 different types of database. The different databases can be created through Project Manager by selecting a different Data Source.
Once a source is selected, a new section allows the default settings from the odbc_config file to be bypassed if required:
Projects can be still be created through a command line using c_prj using the new -odbc_src option.
Both -odbc_user and -odbc_pwd are left blank so the default user and password from the odbc_config file will be used. They will only be filled when an override is required. When creating a database for Oracle then the -odbc_sch DEFAULT would be used. For an SQL database then -odbc_sch DATABASE would be used.
All items requirements, system notes and diagrams etc., will be located in an Oracle database but there are some files that are kept in a project folder like in a DISAM project.
The ‘prj_params’ file can be found in the project folder with a new file called ‘connection_config’. The ‘prj_params’ is the same as before, with all the options for the project schema and user interactions. The new ‘connection_config’ file holds the version, type, database source and odbc schema used. It also holds the User and Password to override the DEFAULT USER / PASSWORD from the odbc_config.
The definitions e.g. views, queries and reports etc., are still held in the definitions folder under the different user types. Source and FormalDocuments are also held as before in the doc and fdoc folders.
Direct manipulation of data in Cradle’s data files held in DISAM or an ODBC supported database is not recommended under any circumstance. The inherent integrity of the data and its internal relationships can only be maintained by accessing through Cradle’s defined UI, command-line or API tools.
We do not provide any information about Cradle’s use of Oracle and
MySQL other than which we provide in our documentation
We do not provide any information or assistance to anyone who is
proposing to access Cradle’s data that is stored in Oracle or
MySQL other than through Cradle
Anyone who accesses, either read-only or read-write, Cradle data
that is stored in Oracle or MySQL without using Cradle as the only
means to access that data, does so entirely at their own risk and
3SL will not accept any responsibility for, nor provide any
assistance to, anyone who accesses Cradle data in that way and then
subsequently finds that their data is no longer accessible through,
or manipulable by, Cradle