Username:
Password:
Please type the Two words with a space between them to prove you are a real human being.
All users of Cradle are assigned a Cradle username giving them a unique identity in the project. Users can be assigned skills, roles, clearance levels and individual module access rights to control what features and what information they can use and see.
Projects can have a team hierarchy. A team hierarchy is simply a user-defined hierarchy of the names of teams in the project. The team hierarchy allows a project to contain an arbitrary number of levels of team, and therefore an arbitrary number of levels of user. This hierarchy of users and teams extends the project’s access control. Creating a hierarchy of teams creates a hierarchical access control mechanism for the project’s database.
A project can define any number of roles, each is simply a name for a collection of User Profile attributes, and in particular a set of user privileges.
The phase hierarchy is a hierarchy of elements to describe the process or project lifecycle of your project. You can think of these as phases, activities, or tasks. A phase hierarchy should be defined so that it is easy to have Cradle display appropriate items of information at each stage in your project. Users access the phase hierarchy and then select the associated queries, matrices, reports, graphs, metrics, commands or documents to be run.
This allows a project to present its process as a hierarchy to the users, each element of the process having an associated view of project data. From the user’s perspective, he/she does not need to know anything about Cradle to access project information. By simply clicking through the hierarchy of organisation-specific and project-specific terms that he/she will recognise, Cradle can present the correct information in the correct manner.
Performance Modelling allows any part of a design to be assessed in terms of the characteristics that it needs in order to be viable when built. This allows the effects of performance requirements on the design to be studied. Assumptions can be tested as early as possible, saving time and corrective development later. In particular, the viability of the system can be verified before it is designed in detail, or indeed built.
The performance results are read from the PERF DATA frames of the specifications and data definitions in the symbols along the path defined by the thread, and are displayed in a graph.
The Code Generator generates source code from design information in the Implementation Domain. You can use the Code Generator to:
The Reverse Engineering tool parses one or more source files, and normally produces a Structure Chart to represent the source code within it.
The tool optionally:
The Web Publisher tool allows you to publish sections of your Cradle databases as fully hyper-linked websites. You can export some, or most of the database items into a set of HTML files that can be browsed as a structured hierarchy. A set of small linked pages that can be browsed is often preferable to traditional documents, which are linear, and cannot meet all users’ needs. Instead of printing the same data in different document styles, a hyper-linked website can often meet all user expectations.
Being read-only, websites can be distributed on CD-ROM or to customers, reviewers and/or suppliers whether or not they have a Cradle installation.
The main cradle interface is shipped with a number of language options these currently include Chinese, Dutch, French, German, Korean and Welsh. We also supply a tool to allow users to alter UI phrases to meet their locale such as altering a Canadian French entry if it differs locally to that in the main French language Catalogue. Users are also free to add their own language catalogue if they wish, or 3SL will furnish a quote for providing Cradle in most modern languages.
Alerts are messages that can be sent to Cradle users, by other users or automated based on system events for example, the Configuration Management System (CMS) generates an alert to you when an item is submitted for review and you are a reviewer. Each alert has a subject, a priority, a recipient and a message.
Alerts either appear in a Cradle user's Alerts dialog or can be sent by email to an appropriate recipient.
The Cradle Application Programming Interface (API) is a set of routines that can be used to create applications that use the database and supporting features in 3SL’s Cradle Requirements Management and Systems and Software Engineering environment.
You can use the API to extend the facilities of your Cradle system, or to create a bridge between Cradle and another piece of software by connecting the APIs of Cradle and the other tool.
The Cradle API can be used on Windows®, UNIX® or Linux systems. We will use UNIX to mean both commercial and open source UNIX/Linux systems in the remainder. Except where may be stated to the contrary, all facilities of the Cradle API are available on all platforms.
The Cradle API consists of:
On Windows, the Cradle API is provided as DLLs to be used by your applications at runtime and a .lib file (and a further DLL for Visual Basic) to be used at compile time. On UNIX, it is a library in the native format for the operating system, typically a static a library. On Windows, the Cradle API can be used with:
On UNIX, the Cradle API is only supported for use with C/C++. If your preferred programming language and operating system supports cross-language development, then it may be possible for you to use the Cradle API with other languages, but any such use will be unsupported by 3SL.
The Cradle API provides a full range of facilities, including:
Licensing of Cradle is very flexible 3SL are happy to discuss solutions which match your needs. The whole suite is shipped and optionally installed whenever you download Cradle. You can then simultaneously access the components of Cradle you need. You only need to licence the number of components you want to use and in the ratio of your usage. For example you may have 5 or 500 requirements engineers and would purchase sufficient licences for them all to work simultaneously. You would likely have fewer managers needing to run metrics on your site. Should the balance of your project change in the following years and you find you need more system engineering personnel adding to the installation, you can upgrade your licences, install the new code and take advantage of the new connections without any additional installation on the client machines.
Cradle licences are floating as they can be accessed from anywhere in the network, so can be shared between multiple projects. Licences are dynamic as they are released as soon as you stop using the licensed component of the suite.
There are also ways that these licences can be accessed and controlled. The most flexible being read write (RW) connections any member of you team can be given a Cradle user ID and can connect provided there are connections sufficient available. However, in smaller setups we can offer named user (NU) licences which restrict the personnel allowed to run Cradle which also offers a cost reduction. If you need to allow auditors and managers to access the system in a read-only manner (RO) at all times regardless of the number or RW connected, then an RO licence can be a purchased.
