3SL Blog (Structured Software Systems Ltd)

22nd June 201710th July 2018

How do I receive alerts via email?

Can I set Cradle so that I can receive alerts via email?

To be certain not to miss a modification or change to the project without even having to open Cradle to check, you can have alerts sent by email. This can be especially important when a user is ‘away from base’ or is in a role that doesn’t warrant them logging into Cradle daily.

Setting up alerts to be sent via email

When setting up alerts in project setup you have three choices on how you and users will send/receive user and system alerts:

Cradle message – Alerts are dispatched as Cradle alerts and appear in users’ lists of alerts.
Email or message – Alerts are dispatched as emails (if available) to users, and as Cradle alerts if not.
Both – Each alert is dispatched both as a Cradle alert and an email.

Email dispatch to a user is only possible if the user has an e-mail address in their User Profile.

On Linux emails are dispatched using the contents of the E-mail command attribute that is set in User Preferences

On Windows®, emails are despatched by calling an extended MAPI client. If an extended MAPI client doesn’t exist, e-mails will be despatched using a MAPI compliant e-mail client on the machine where the alert is being generated. If a MAPI compliant mail client doesn’t exist, or cannot be launched, then e-mail despatch will fail.

Follow these three simple steps to set this up

In Project Setup set alert delivery to be either “Email or message” or “Both”
Alert Delivery option on Project Setup
Ensure that users in your project have email addresses set in their User Profile so that Cradle knows where to send the email
Set mail address in Users Profile
Have a valid mail program and account setup on the client machine which is using Cradle.

It’s as simple as that, your users will now receive Cradle alerts via email.

Alerts being recieved via email — Alerts being received via email

To read more on alerts please refer to this previous post.

21st June 2017

Installing New Security Codes

What is a Security Code?

All Cradle licences are configured by 3SL Security Codes. This new Security Code must be installed on the host running the CDS (Cradle Database Server). It does not need to be installed on any machines were Cradle clients are installed.

Security Codes are in the file:

$CRADLEHOME\.c_config – Linux
%CRADLEHOME%\c_config.dat (usually c:\Program Files\Cradle\c_config.dat) – Windows

WARNING: Please be careful NOT to change any part of this file! If you do, you can easily prevent your Cradle system from working!

The Security Code contains the Cradle system’s serial number that identifies the Cradle system, and provides some basic information about it. The composition of the serial number is:

Security Code Structure — Composition of Security Code

The serial number contains the system sequence number that is the unique identifier of the Cradle system. The serial number itself may change if, for example, you purchase additional licences to increase the number of simultaneous users that the system will support, but the system sequence number within the serial number will remain unchanged.

To obtain the serial number of your Cradle system (on Linux) at any time, enter the following command:
c_serial

Installing Security Codes on Windows

Shut down all Cradle tools and servers
Select Cradle Utilities > New Security Code from the Windows Start menu:
Security Code Configuration Utility
Copy and paste the Security Code into the Security Code Configuration Utility dialog and select Decode
If the decoded details are correct, click Configure to apply the new Security Code
Once this is complete, you should reboot the machine, or (if not possible) restart the Cradle servers

Installing Security Codes on Linux

Shut down all Cradle tools and servers
Run the following command, you can then restart the CDS and CWS servers:

c_config -i security-code

where security-code is the 92 character Security Code issued by 3SL. Further information on c_config can be found in the help pages.

20th June 201724th August 2022

How to Make Use of User Variables in Document Publisher

Where can Variables be Placed

All User Variables in Document Publisher can be used throughout the template. You can use the variables within Headers, Footers, boilerplate text and document titles.

What are Variables?

The Variables store bits of data to be used in tags that allow the use of either a variation of data or static data.

For example the variable $UserName is static will only output the currently Logged in Users Name within the document. The User Name will also be output if the template is being generated through the Phase sidebar in WorkBench.

Some variables can be used to hold items identities in a static list like $IDList or lists of item identities collected from Hierarchy Tables like $ItemList. The lists for $ItemList can change depending on cross references and/or if the template uses parameters.

Creating User Variables is easy. Read How to Create a Variable to find out.

User Variables in Headers and Footers

The variable tags can be used within a Header and/or Footer in conjunction with Microsoft® Word’s own data fields.

In the Word tab, select the Header or Footer option. Then select the Edit Header/Footer option. Once the Header/Footer is open, select the User Variable button and the variable you wish to use.

Several variable tags can be placed to output within the Header/Footer so you get the output required. These tags can also be formatted.

When editing the Header or Footer the View will change to Print View as they don’t show in Draft view.

Doc Pub user variables in a header — Using variables in a Word Header.

Doc Pub user variables in a footer — Using variables and Word fields in a Footer.

The final output looks like this:

User Variables in Boilerplate

The variable tags can be placed within any boilerplate text. This allows for changes in data like the date or user publishing the document.

Boilerplate text and User variables — Boilerplate text with User Variables.

The User Name and Todays date within the Boilplate text.

User Variables in Title Text

A User Variable or a Paragraph Group tag can be used to set the Document Title. A variable is quicker but does not allow for parameters are used in a field tags.

Title Variables — `$TemplateName` User Variable

So the output looks like this:

Or you can have the Title only output when you are generating a Formal Document. Use any of the $FormalDoc variables and they are only generated during a Formal Publish. In this example I have used $FormalDocTitle:

Using $FormalDocTitle means the title will output as to the same as the User entered in the Title in the Publish Formal Document UI.

Title Formal Output — Document Title set by the words entered by a User during a Formal Publish.

19th June 201716th February 2023

June 2017 Newsletter

Summer Arrives in June

Looking out of the windows here in Cumbria, summer has well and truly arrived. However, 21^st June marks the summer solstice.

It also marks the start of the holiday season. This can be both a trying time for projects and a quieter time in the office. With fewer people and distractions over the coming months, now could be your ideal time to set up trial Cradle projects. Take some time to run a few operations in parallel. Compare how pushing a requirement/design/test through Cradle compares with the manual or tool based version you use now. Even seasoned Cradle users will find there is some project or operation not yet in Cradle, yet ripe to be imported. It could be your ongoing Process Improvement Plan. Whether formally following CMMI or just ensuring you raise, resolve and measure issues in your company’s working processes, then controlling, recording and measuring formally in Cradle makes it easier to manage. Use a summer vacation student or intern to set up a schema and enter data as a pilot project.

3SL Blog

Thanks to new bloggers Mikki, Jan, Phil, Stuart, Cameron, Ciaran for their input to the Blog. Don’t forget to drop us a line to social-customer@threesl.com with any topic requests.

G-Cloud 9

We are pleased to announce that our Cradle software is now available through the Government’s Digital Marketplace – G-Cloud 9. For details, please see government site and search for any of: 3SL, Cradle, requirements management, agile, business analysis, systems engineering, or application lifecycle management.

White Papers

Cradle’s combination of requirements management, process and architecture modelling make it an ideal choice for business analysts. Download our new presentation that outlines some of Cradle’s significant capabilities for business analysts from the Presentations area.

Twitter

May Day 2017 Madness Giveaway. We reported last month that @baguettio had won, however, they did not respond to the direct messages we sent asking them to contact us and claim their security code. They have since deleted/hidden their account. We have, therefore, awarded the prize to the second person drawn @FPreobrazhensky

Reviews

We have been contacted by Capterra an independent review company. They would like to update the reviews they hold on Cradle.

We would like your permission to pass your email address to them. They will then choose from all respondents who to contact, to request you write a review about Cradle. Their scheme offers a reward for the first respondents. It would be really great if you could consider doing this, please reply using Yes I’m happy to consider writing a review

Hints of the Month

Here are some links to helpful topics since our last newsletter, they should improve your Cradle experience:

As a project progresses a requirement can grow from being atomic to containing multiple phrases and components. See how to split items in this article.

Now that you have torn the items apart, see how to merge items together!

Authenticating through LDAP (Lightweight Directory Access Protocol)? Do you want to use LDAP with Cradle, and need some help getting up and running, we’ll show you some trouble shooting tips.

Use document tags to enable publication of any data from within the Cradle database into a document via Document Publisher.

You can read Hints & Tips in the 3SL Blog.

19th June 20174th February 2019

Capturing New Document Versions

Capturing New Document Versions using Document Loader

You can capture new versions of source documents in the same way as regular documents. Document Loader compares the two versions of your document and identifies any new or modified source statements. You can select which of these revisions to load into your Cradle project database.

Adding a new version of document and Overwite/Merging

When you load the new version of your document, Document Loader adds or updates the appropriate items in your project database. A new set of bookmarks is created around each source statement and linked to the new version of your source document

Please note that Document Loader does not delete items in your project based on deleted paragraphs in your new version.

As long as you have all items baselined in the previous captured document. When making a new version of the document, Document loader will create a draft of the items.

Document Loader relies on an accurate correlation between the source statements in the current version and the new version of your source document. Before loading a new version it is necessary to consider the nature of the modifications in your document.

We advise taking a backup prior to loading a new version.

Your new version will contain minor revisions to requirement statements with new sections and subsections added. These modifications should have been made with Word’s Track Changes enabled.

If however, the new version contains strong modifications, such as restructured sections or entire sections deleted, then it may be necessary to load your document as a new source document instead. You may still update the existing items in your project, provided that your document contains the items’ identities. To do this you must set the Overwrite option to Merge.

The Document Loader dialog is shown below showing a new document version ready to be captured. As you can see the changes are highlighted:

New document version to be captured using Document Loader — Document Loader Screen

Click here for step by step instructions on capturing new document versions using the Document Loader tool.

Article Updated 04/02/2019 – Updated to include new version with baselined items

16th June 201716th June 2017

Table Generation Method in Document Publisher

There are two ways to generate a Document Publisher table. The first table generation method is the Default, this outputs each item row by row. This generation is slower but allows for different styles and formatting in a cell.

The second table generation method is XML which is faster but does not allow for different styles and formatting within a cell. If the user is outputting a simple table then XML is the way to go, especially if it is a large table.

This article highlights some of the limitations and pitfalls with XML output.

A Simple Table Generation

Outputting a simple but large table is quicker by setting the Generation Method to XML.

A simple and none formatted, Document Publisher Table

Hierarchy Table — A hierarchy table I use for this example.

Outputting the above table using a hierarchy as above is much faster using the XML method rather than the Default method.

Differences in Styling Text in a Cell When Using the XML Generation Method

Taking the table above and formatting all the tags in different ways to make them stand out can cause some problems in the XML. For instance the user may wish the Verification Method to be output in a different colour to the rest of the Verification information at present this would cause issues with an XML Table Generation Method.

Differently coloured tags

In the above screen-shot, I have made the Identity and Name of the Verification blue and the Method green. This currently limitation means when generated using the XML Generation method, none of the text is seen under the Verification column.

Setting the Verification Method to the Automatic Font colour, the text is output but the Identity and Name will still not show.

Coloured and auto coloured atgs — The output if some tags are coloured and others are set to automatic in the same cell.

The only way to have the output show correctly is to put the Font Colour on the whole cell:

All tags in the cell are the same colour.

Coloured cell output — The output from the colour placed on the cell not the text.

The user can even have all the different columns in different colours and this will output each item and column correctly.

All coloured cells Output — All cells are coloured differently in the table output

The same goes for making text bold, italic or underlined; unless it is on the whole cell it will cause issues with the output.

Differences in using Formatting Marks in a Cell

Placing formatting marks like between tags in the same cell is also subject to limitations. Placing a single carriage return (new line) between 2 tags can cause the second tag to not be output if placed incorrectly:

Using formatting incorrectly

When done correctly can still output as the user requires, make sure the cursor is before the bookmark and press Shift+Enter:

Using formatting correctly

Or just putting a full carriage return (paragraph end) between the tags, making sure the cursor is between the 2 bookmarks and not inside one of them:

Using formatting correctly

Correct formatting output. — The output when formatting is used correctly.

The alignment of text within a cell must also be the same, the user cannot have one tag as left aligned and another right or center aligned unless there is a full carriage return between them.

You also cannot use Ctrl+Tab for a single tag in the cell as the data will not show in the output.

For more information on Tables in Document Publisher click here

15th June 201723rd August 2022

Customise your Quick Access Bar to your needs

Quick Access Bar

The Quick Access Bar (QAB) is intended to provide quick and easy access to all of the types of information in your Cradle database that are relevant to you. It provides easy access to the Automatic scope queries for all item types as a scrollable list of controls, each of which provide access to an automatic menu for an item type.

Controllability

But what about if you only want the bar to display a specific set of item types or you want them in a specific order?

You can customise how the QAB will look for you in User Preferences. Choose which items are to be shown and in which order you wish them to be displayed you even have the option to set whether you want the Quick Access Bar to be shown when WorkBench starts.

Quick Acces Bar in User Preferences — Customising your Quick Access Bar

For further information on customising your UI see this previous blog post.

If you need to set these values for everyone in the project, it can be achieved with the Cradle initialisation file.

UPDATED: April 2020 – Related article

14th June 201714th June 2017

Column Sorting in WorkBench

Column Sorting

WorkBench can perform column sorting in Table and Document view styles. This can easily be performed by clicking on a column heading.

Sort Options

Selecting a column heading will display four sort options. When one of these options is chosen the items will be sorted and then displayed based on that selection.

Sort ascending – Case insensitive

The first sort option will sort the items from A to Z, based on the item’s value for the selected column. This is done regardless of whether the characters are upper-case or lower-case.

Sort descending – Case insensitive

For the second sort option the items are returned from Z to A, based on the item’s value for the selected column. Again, as this option is case insensitive the returned items can be upper-case or lower-case.

Sort ascending – Case sensitive

The third sort option will sort the items from A to Z; but this time all upper-case items are returned first:

Once there are no more upper-case items the remaining items are then displayed a to z:

Sort descending – Case sensitive

The final sort option will sort the items from z to a; meaning all lower-case items are shown first:

Once there are no more lower-case items the remaining items are displayed Z – A:

Note:

This sorting only re-arranges the current data brought back in the current query. It does not retrieve new data from the database. In order to retrieve data from the database in a particular order, then one of the database key fields must be selected in the Sort by: field of the query. However, because the sorting occurs on the data in the table it does have the advantage of being able to order the table by frame content or other non key fields.

13th June 201713th June 2017

Project Planning and Work Breakdown Structures

Overview

Most projects have a formal project plan by which their work can be planned and the progress of this work can be monitored. A project plan will typically divide the project’s work into activities which can be grouped into a hierarchy that is usually called a Work Breakdown Structure (WBS). At its simplest, the WBS is a hierarchical description of the work that is required to complete a project.

The use of, or interest in, a WBS may not be confined to the group that maintains the project plan. Often, a project will want to have a representation of the project plan that is accessible to the systems engineering data, so that:

Parts of the project plan can be assigned to people working in the systems engineering environment
Individuals can have task lists prepared for them from the project plan
Information used by, or generated by, the activities in the project plan can be linked to the activities in the plan
Updates to the project plan can be made from within the systems engineering environment

These needs are particularly apparent in those organisations that undertake a large number of small projects. It is particularly common in manufacturing companies, who will typically have many projects under-way concurrently.

Planning Tools

Tools that manipulate project plans are usually called project planning tools or project management tools. There are many such products, including Microsoft Project, Artemis and Oracle Primavera.

Cradle provides a bi-directional integration with Microsoft Project that allows a Cradle project to be associated with any number of Project plans (sometimes called programmes or schedules) whereby:

1. The activities in each plan become a hierarchy of items in Cradle

2. Data can be bi-directionally exchanged between Cradle and Project, either:

From Cradle, pushing Cradle updates to Project or pulling updates into Cradle from Project
From Project, pushing Project updates to Cradle or pulling updates into Project from Cradle

3. The activities in Cradle can be assigned to users, creating task lists

4. Each user can see his/her task list, colour-coded by the progress of the task based on the current date and the date information in the task, showing the immediacy or delinquency or completion of the task

Image showing the project plans process — Project plans process

Planning within Cradle

Continue reading “Project Planning and Work Breakdown Structures”

12th June 20177th December 2022

Publish a Formal Document Using a Batch File

Running Document Publisher in the Background

Publishing a Draft or Formal Document can take time. If you need to use Microsoft® Word for other work, is a nuisance when having to wait.

Users can run a batch file to create the documents either as a Draft and/or as a Formal document. The batch file can be used in a task while the user is not using their computer; for example at night or a weekend if many documents are being generated.

The command line needs to have all the options set the same as they would be through the UI (User Interface):

Formal Document Command line Options

The normal batch file command line options for just a draft document are:

Draft Options for batch file — Command Line Draft Options

Each of the following shows what the command line options for each Formal option in the User Interface:

Formal Options for batch file — Formal Options needed in a batch file

All the above -fdoc options are requirements within the command line except -newversion. Only use the -newversion option, if a new version of the document is required.

The final command line to generate the DEMO Template will look like this: (NOTE: Options with more than a single word are required to be in quotes e.g. -fdoccomment “Published DEMO Template Using Batch File”)

"%CRADLEHOME%\bin\exe\windows\DocPub.exe" -login MANAGER,MANAGER,demo -file "DEMO Template" -location PROJECT -type DOCX -output "C:\Temp\DEMO Template.doc" -formal -fdocname "DEMO Template" -fdoctype REQUIREMENTS -fdoctitle "DEMO Template" -fdocissue 1 -fdocdate Jun -fdocref DEMO1 -fdocclass UNCLASSIFIED -fdoccomment "Published DEMO Template Using Batch File" –log

Any template that generates through Document Publisher can generate through a batch file.

As you can see in the command window below, 3 templates are being generated, a doc, a docx and a docm.

Command line window — Command Window showing 3 types of document being generated

Once the documents are generated, they can be seen in WorkBench in the Project sidebar under the Formal Document sections:

Project sidebar Formal Documents sections — Project sidebar – Formal Documents sections showing the 3 generated documents

Using parameters within a batch file

The great thing about using a command line batch file is that parameters can be set, as long as the template has parameters setup. This means you can run the same document many times but use different parameters for each run with a different document output name. For example if you used ?reqID within the Key or Identity you could output different Requirement Documents.