MBSE with CORE 100821

Bridging from Problem and Externals to Behavior: The Role of Threads • Define distinct classes of threads based on use cases, system I/O, and/or conditions • Start with one thread per use case, class of system input, and/or conditions • Preserve each thread (for thread testing, concept of operations, etc.) Step 1a. Define threads

Step 1b. Partition threads

Step 2. Integrate threads to define system behavior

403

Four Threads to elaborate Four Use Cases

• T.1 Product in Inventory • T.2 Product not in Inventory • T.3 Customer Certification • T.4 Performance Assessment

uc Operate Geospatial Library

Geospatial Library

<>

Collect and Deliver New Product

Assess Performance

Collectors

Deliver Image

Retrieve Existing Product

Customers

Thread names should follow the function naming convention of verb or verb noun statement. These names have been chosen to avoid confusion with the corresponding use cases.

<>

Certify User

Certification Authority

404

MBSE with CORE