A.11. Core Workflows

These are core business processes of the TRRS organization. They provide supporting information for the primary use cases.

UC004 Product Entry Workflow

Key Actors: Product Vendor

Context: Workflow initiating with the creation of a new product entry in the TRRS system.

  1. Vendor collects product data sheets and standards references to prepare for submission to TRRS.

  2. Vendor selects product features from TRRS categories to create a class features list.

  3. Vendor selects standards for asserting product conformance by completing conformance forms.

  4. Vendor identifies product's interoperability capabilities, completing interoperability forms.

  5. Vendor establishes linkages to own product information and external documentation.

  6. The product entry is committed to the TRRS system product directory.

  7. The product conformance and interoperability templates are entered into a workflow queue to solicit the following kinds of TRRS entries (see use cases UC005 and UC006):

    1. Standards Testing

    2. Independent Testing

    3. User Experience Reports

    UC004 Extension: Vendor nominates an additional feature category.

UC005 COTS Validation Workflow

Key Actors: Testing Labs, Solution Providers, IT Users, Product Organizations Context: Workflow initiated when new conformance statements are asserted.

  1. Conformance statements are sent to independent evaluators, including Testing Labs, Solution Providers, and IT Users, soliciting test and experience inputs.

    1. Independent laboratory test generates test results, entered in TRRS system as experience report (see UC003).

    2. Solution providers using the product in systems development submit integration testing experience reports (UC003).

    3. IT Users submit usability results as experience reports (UC003).

  3. Continue with UC007.

UC006 Interoperability Validation Workflow

Key Actors: Independent Evaluators: IT Users, Testing Labs, Solution Providers, two or more Product Vendors.

Context: Workflow initiated when new interoperability statements are asserted.

  1. Interoperability statements are sent to independent evaluators.

  2. Evaluators perform interoperability tests, product integrations, and usability experiments.

  3. Evaluators submit results to the TRRS as experience reports.

  4. Continue with UC007.

    Extension (from Step 3 above): Interoperability Solution

  1. Solution provider or third-party vendor may create an interoperability solution between two or more products.

  2. The interoperability solution can be registered with the TRRS as a product with these asserted interoperability statements.

  3. Solution providers can report their level of effort to create the interoperability solution.

UC007 Experience Report Update

  1. Vendor assesses the experience report submissions.

  2. Vendor concurs with each report(See Extensions A and B.)

  3. Report is stored and published in TRRS system.

    Extension A: Vendor does not concur (as in Step 2 above).

  1. Vendor does not concur with experience report

  2. TRRS returns report to author with comment.

  3. Author modifies report and resubmits. (Resume from Step 2 above.)

    Extension B: Deadline Passes

    Context: Vendor does not concur

  1. Sixty days pass since vendor has received report without concurring.

  2. Report is stored and published in TRRS system.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
52.15.231.106