1 / 30

3SL and Cradle From Concept to Creation…

3SL and Cradle From Concept to Creation…. INCOSE Tool Vendor Challenge. 3SL’s Approach. SYSTEM APPROACH A tool should support a customer-designed engineering process

tana
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. 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 system modeling and requirement management solution PRESENTATION APPROACH • Scope and User Requirements • Derived System Requirements and Architecture • Trade Study • Verification and Test • Impact and Gap Analysis • Customer Deliverables Additional details for the slides may be found in the Notes Page view

  3. Initial Scope and User Requirements

  4. Disaster Relief: User Requirements Using Cradle’s System Modeling module, we modeled out the provided user requirements using a Use Case diagram. Decompose

  5. Decomposed Emergency Supply Management Use Case We decomposed the Emergency Supply Management use case into subordinate use cases. Later, we will focus on our Supply Ice use case to develop our two operational scenarios.

  6. Operational Scenario: On-site Production The first Operational Scenario is to produce the ice in the shelters. This diagram links to the Supply Ice use case shown in the last slide.

  7. Operational Scenario: Procuring Ice The second Operational Scenario shows the events occurring if we procure the ice from an ice distributor. This diagram links to the Supply Ice use case for traceability.

  8. Operational Scenario: Hybrid Solution The second Operational Scenario shows the events occurring if we procure the ice from an ice distributor. This diagram links to the Supply Ice use case for traceability.

  9. Input and Manage Stakeholder Requirements We input our provided text-based stakeholder requirements, to be linked to the Use Cases and Operations as applicable. By tracking the requirements at an item level you push maturity at each step. Each requirement is linked to the modeling element in which it was derived

  10. System Context We created a Context Diagram showing our high-level system of interest and the external interfaces needed to meet the stakeholders needs.

  11. System Requirements and Architecture

  12. System Architecture We have identified our subsystems and their internal and external interfaces.

  13. Diagram Items - Traceability Each diagram object contains a specification that links to requirements and other data objects within the project.

  14. Requirement Management System and subsystem requirements are derived and managed then linked to other requirements and diagram elements as applicable.

  15. Trade Study

  16. Trade Study - Item A Trade Study item was created to capture the trade study criteria. Each constraint is linked to the corresponding Trade Study. Trade study options were: • Procure Ice • On-site production • Hybrid solution Factors/Constraints: • Transportability • Cost • Space (equipment)

  17. Trade Study Constraints Constraint items were created to capture the details of each of the 3 trade study factors as well as the impacts. The mean value for the constraints, for each option determines the option that is chosen. Below is an example of the Cost constraint for on-site production.

  18. Candidate Ice Supply Architecture: Procure Ice

  19. Candidate Ice Supply Architecture: On-site Production

  20. Candidate Ice Supply Architecture: Hybrid Solution

  21. Trade Study Results After calculating the constraint/risk values, the trade study results were revealed. Here, we are showing that the hybrid solution (shown in green) poses the least amount of risk, and therefore was the chosen solution.

  22. Verification and Test

  23. Verifying System Requirements We have queried our system requirements to show detailed requirement and verification matrix in a single report.

  24. Impact and Gap Analysis

  25. Impact Analysis If we decide to change REQ-12, modifying the amount of coolers required at each shelter, here a diagram depicting the impact it will have on our existing data.

  26. Gap Analysis Cradle allows for various reports to assess the gaps in your engineering data. The use of queries, reports, matrices and metrics will show any immature data and missing traceability within your project. Below is a simple report created to show orphaned system requirements:

  27. Customer Deliverables

  28. Document Publishing Document Publisher – • Draft/Formal Word Documents • Completely Customizable • Built-in templates • Reusable

  29. Benefits of Using Cradle Provides end-to-end traceability • Requirements trace to models • Functional modeling traces to physical modeling • Test cases trace to modeling components • Transitive relationships Integrated change/configuration management • Change management • Baseline • Version control Multiple reporting mechanisms • Draft/formal document publishing • Built-in reports

  30. Contact For further information, contact: Sara Danford Sumner 3SL, Inc. Sara.sumner@threesl.com (256) 971-9500

More Related