1 / 24

3SL and Cradle From concept to creation…

3SL and Cradle From concept to creation…. INCOSE Tool Vendor Challenge. Who, From, What. David Freytag 3SL Incorporated Cradle Requirement Management and Systems Engineering software See Notes View for comments. 3SL’s Approach. SYSTEM APPROACH

stone-kirk
Download Presentation

3SL and Cradle From concept to creation…

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 3SL and CradleFrom concept to creation… INCOSE Tool Vendor Challenge

  2. Who, From, What • David Freytag • 3SL Incorporated • Cradle Requirement Management and Systems Engineering software • See Notes View for comments

  3. 3SL’s Approach • SYSTEM APPROACH • A tool should support a customer designed engineering process • For the purpose of the INCOSE Tool Vendor Challenge, 3SL will demonstrate the use of Cradle for a Model Based Systems Engineering process • 3SL’s utilization of Cradle allows for an integrated modeling method linking requirements and other text based information directly to physical, operational and behavioral models • PRESENTATION APPROACH • Scope and Initial Definition • Development and Maturity • Traceability and Verification • Management and Output

  4. Scope and Initial Definition

  5. “Initial” Requirements How this project likely started…..

  6. Data Based Requirement Management By tracking the requirements at an item level you push maturity at each step. Managing by document provides updates at meetings with stale data between them.

  7. Concept of Operations

  8. Model Items Each model object contains a specification to link to requirements and other objects within the project

  9. Operational Scenario

  10. System Context Move from Concept to Basic Context

  11. Development and Maturity

  12. Requirement Details • Added details to categorize requirements, indentify priority, assign ownership

  13. Decomposed Subsystems Continuing evolution to show the Context – how will the system really connect?

  14. Behavioral Diagram

  15. Traceability Analysis and Verification

  16. Nested Table to Show Relationships

  17. Requirement Coverage

  18. Develop Verification

  19. Management and Reporting

  20. Earned value

  21. Hierarchy Diagram Utilization of Hierarchy Diagrams to manage change and traceability questions. Highlights scope and impact of proposed changes

  22. VCRM

  23. Formal Output

  24. Thank you For more information on Cradle, the process used or to school us on Traffic Management Engineering, see us at our booth.

More Related