3SL attended the SEC 2016 conference in Washington at the end of last month. We presented a tutorial on how SysML can be used in a MBSE process that is integrated into the rest of the systems lifecycle, including initial needs and requirements capture and following with links to test and delivery.
That presentation can be downloaded from our website here:
3SL attended the SEDC 2016 conference and presented a view of SysML and MBSE in the systems context, for executives. The essence of this presentation is that MBSE is good, SysML is one form of model and associated notations for MBSE, but these cannot be useful unless they are part of an overall process for the complete lifecycle.
We have recently seen cases where a Document Publisher template – which is an ordinary Word document – contains references to other Word templates that have been created by an organisation.
Generally, this is OK, everything works correctly as you would expect.
However, if the Word templates (.dot or .dotx files) are not available, or are corrupted, then problems can occur because Word (running inside Document Publisher) may display error messages and prompt you to re-try access to the template, or repeat an attempt to save changes back to it, and so on.
You can either accept that these messages will occur over and over again, or you can disconnect your Document Publisher template (the Word document) from the Word templates.
It is difficult for us to offer general advice as every organisation is different, but our inclination would be to sever connections to these Word templates if you ever seen any warning or error dialogs from Word.
We are pleased to announce that we have a new white paper available for download from our website. This paper discusses some key issues for compliance with regulations affecting product definition, design and development.
We are pleased to announce that the following platforms will be supported by Cradle-7.1:
– Linux. Any variant with a version 2.6.32 or later kernel
– Windows: – Windows 7 (SP1, 32-bit and 64-bit) – Windows 8 (32-bit and 64-bit) – Windows 8.1 (32-bit and 64-bit) – Windows 10 (32-bit and 64-bit) – Windows Server 2008 (SP2, 32-bit and 64-bit) – Windows Server 2008 R2 (SP1, 32-bit and 64-bit) – Windows Server 2012 (64-bit) – Windows Server 2012 R2 (64-bit)
– Office: – 2007 (SP3, 32-bit) – 2010 (SP2, 32-bit and 64-bit) – 2013 (SP1, 32-bit and 64-bit) – 2016 (32-bit and 64-bit) – Office 365
The changes from Cradle-7.0 are that we have dropped support for Windows Vista and added support for Windows 10, Office 365 and Office 2016. In fact, Cradle-7.0 already runs on Windows 10 and Office 365, but they were not officially supporting by Cradle-7.0. The Cradle-7.1 release adds formal support for these products, and introduces support for Office 2016.
We hope that this is helpful as you plan your migration to Cradle-7.1 and as you consider how Cradle’s platform support fits into the overall Linux/Windows/Office strategy in your organisation.
We are pleased to advise that we will soon be releasing our SysML extension to Cradle as part of the Cradle-7.1 release in the next couple of months.
This will be unique in the world of SysML, and we encourage you to investigate what we can offer.
SysML is the UML ‘dialect’ for systems engineering. It has many capabilities. It is, fundamentally, just another modelling notation through which MBSE (model based systems engineering) can be conducted. In that sense, it is nothing new. There have been many other notations in the past, all of which permitted MBSE.
What is different now is that by integrating the latest SysML notation into Cradle’s unique ability to support the entire lifecycle in a single tool, with a single database, we can offer MBSE using the latest notation with complete traceability from requirements and into test management, defect tracking, release, maintenance and ultimate system disposal.
This is unique! We are very excited about it!
We hope that you will join us in the new opportunities that Cradle-7.1 will provide!
We will announce details of the Beta programme very soon, and hope that you can be a part of it!
Cross references are links between items in the database. They are how you show that an item is dependent on another item in some way. For example, one item may satisfy another item, or an item may be a decomposition (a child) of another item.
How are Cross References created?
Drag and Drop
You can select a group of items in a tree and then drag and drop them onto another item. Cross references will be created from the item that you dragged onto, to the items that you dragged.
You can select an item and choose Make Link From and then select another item and choose Make Link To. A cross reference is created between the items. This is available from the right click popup menus, and Item menus, and has the advantage that it can be used anywhere:
Selecting items in a tree
Selecting items in a table
For an item in a form
Selecting an item in a matrix
So it has the advantage that you do not need to have both items open in trees.
You can display the Link Details dialog that shows the details of a cross reference, including the user-defined attributes inside it. You can manually enter ‘from’ and ‘to’ Identities into the dialog and select Save to create cross references. This is sometimes the fastest way to create a set of cross references.
Of course, you can also import cross references from other tools, from Word tables and Excel spreadsheets. Cross references will also be created automatically when you import from source documents.