Visitor not logged in, You are: Home > Products > Functional
| |
Cradle Functionality
Cradle supports a full development lifecycle and can be distributed across a full team and licences utilised as and when needed to complete a project. Cradle can also be used with your current tools.
Below is outlined a brief example generic project lifecycle and what module licences could be required to complete it and which Cradle components could be used in each stage.
Requirements capture/Requirements Management:
Initial lead team receives requirements from the customer. Data is entered into Cradle via the plug-ins for Word or Excel or via our Document Loader. Any other form of data can be captured into Cradle as items called 'Frames' Frames can contain data in the form of text, images, documents, video etc etc.
Cradle Capture launched from Microsoft® Word®
The documents are registered in the database and the requirements derived from these documents can then be traced through the system.
Cradle (PDM) Toolset using a REQ licence would be required at this stage along with Document Loader. Analysis:
Models are considered for the system requested. Models can be developed in Cradle Toolset utilising a wide range of recognised modelling methodologies. Each diagram contains symbols which contain specifications and have DD entries, all of which can be linked to the initial requirements, so that at all stages of the development process, each aspect of any model can be traced to one or many requirement(s) as necessary to show how the model satisfies the requirement(s). |
Cradle Behaviour Diagram
|
|
Current functions may be analysed and measured. Performance analysis may be required to evaluate or validate functional requirements of a current system. It is possible to look at, drill into and analyse the relationships between any item, (spec, function, stakeholder statements, features, risks, DD entries, functions, requirements, etc.) and those items linked to and through them. These relationships can be viewed, analysed and amended in a hierarchy diagram. |
Cradle Hierarchy Diagram
showing the links or relationships between items starting at Requirement 1.4.1
|
|
After this. there is often the stage of a phase review, or a gateway. Document Publisher can quickly output data directly from the database into a preformatted document structure. Documentation of the system to date can be produced, in whatever level of detail required, very quickly and automatically as Microsoft word Documents.
Multiple versions, baselines and projects can be handled by the Cradle database.
Cradle (PDM) REQ, SYS, MET, PERF, DOC licences and Toolset required. Systems Design:
Keeping to the requirements of the requested system, a model can be developed that will meet those needs. Constraints and risks have been highlighted and accounted for and the system can be developed confident in the knowledge that the requirements are being met.
Lead teams can keep track of the process with WorkBench(WRK). Other stakeholders, in remote locations, can keep a track of and keep control of the system with Web Access (WEBA). Managers and engineers can view any part of the system and see how it relates to any other part of the system. Any changes made that may impact another part of the system will automatically raise an alert, so that other stakeholders will be notified of that change.
Cradle Alerts shown here in WorkBench
Any item changed by any user becomes locked by that user. At this stage, any other user, with the correct permission, can still open and see that item as a read only item and see how it is linked or related to other parts of the system. Users do not need to check items out of a central depositary to work on them, thus hiding them from the other users of the development or management teams. With Cradle, the whole system can be viewed by any user subject to user permissions.
Because of the full system lifecycle, the requirements for the system are still linked to the functionality described by the models and the architecture required to create the functionality of the system and full traceability exists.
These relationships can viewed in many different ways through hierarchy diagrams(above) or (MET) metrics views. |
Cradle WorkBench showing the metric display of Requirement Coverage
|
|
At this stage another phase review can take place with the documentation produced through Document Publisher going forward to the review panel. Documents that take live data from the Cradle database can demonstrate clearly how the initial requirements can be satisfied by the functionality and architecture proposed.
Links exist in the system and transient links can be viewed in a matrix that show how architecture satisfies requirements via functional specifications
Information can be gathered and published online read-only for external stakeholders to view with WEBP (Web Publisher) |
Cradle WEBP. From here you can view the status of the Project down to the item level and view and follow links to explore the system.
|
Cradle WEBA. From here you can edit or delete items, create new items, new siblings, child items or create links between items and more ...
|
|
The data can be accessed and reviewed live online and amended as necessary by stakeholders with the necessary access privileges with the WEBA (Web Access, as above). This allows globally distributed teams to collaborate on a project, through firewalls and through VPN's with our SSL secure connection. Cradle WEBA is a secure distributed collaboration environment.
Final phase documentation can then be easily produced for formal review by the (DOC) Document Publisher Component.
Cradle (PDM) REQ, SYS, PERF, MET, DOC, WRK, WEBA licences and Toolset, WorkBench, Web Access, Document Publisher may be required. Testing:
Cradle also supports systems testing. 3SL's internal development testing is managed by Cradle. Linking the initial requirements to specific functions to specific architecture to specific tests to test results shows clearly in a definable, traceable and verifiable way, how every requirement can be satisfied and that it genuinely is satisfied. |
Cradle WorkBench. Showing verification tests linked through the system to the system requirements
|
|
Cradle (PDM) REQ, SYS, MET, WRK, licences and Toolset, WorkBench, Document Publisher may be required. Implementation:
Implementation works best when the requirements have been managed properly. Cradle achieves this. The requirements have been tracked since the initial capture and all models and proposed solutions regularly checked against these requirements. changes to the requirements have been managed and any impact upon the system will have been discovered by the alert system
A completed system can be implemented confidently in the knowledge that there will be no sudden hidden surprises or unexpected costs arising from data unknown to the system. Unexpected costs can arise at anytime from external sources (new taxes, new government legislation impacts, new red tape, other external factors can and do arise at any time). The system itself having specifications linked to functions linked to requirements can be implemented safely and successfully. A roll out plan allows the installation of hardware and software to run smoothly
Cradle (PDM) REQ, SYS, PERF, MET, DOC, WRK, WEBA licences and Toolset, WorkBench, Web Access, Document Publisher may be required. Formal Delivery:
The final delivery documentation can be produced showing clearly how every requirement of a contractually agreed system has been satisfied and implemented and tested and that it works. That the contract has been produced and delivered exactly as agreed. The documentation can be produced quickly and easily once the template has been created. It automatically runs queries in a Microsoft Word template and generates the final formal document on the fly. |
Document Publisher, generating documentation automatically
|
|
A final list of tick boxes with every part of a requested system developed to a successful conclusion. Nothing missed, nothing left out and every box ticked
From concept to creation. One choice, One tool, Cradle!
Cradle (PDM) REQ, SYS, PERF, MET, DOC, WRK, WEBA licences and Toolset, WorkBench, Web Access, Document Publisher may be required.
|
| |
|
|
|
|
|
