Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

  1. Get aware and assess relevance

    1. Learn about GovStack and get aware of compliance opportunity (Event, Website, Impact Exchange)

    2. Inform about Compliance Process (Confluence) → Page on Website GovStack.Global

    3. Select matching BB(s) to own Software Product (Gitbook)

  2. Conduct and publish Self-Assessment Compliance Concept

    1. Deployment Compliance: Link to container and documentation

      1. Option 1: Manual, Confluence Compliance Evaluation: Template (automatically filled in with BB Requirements) Link to Docker File

      2. SELECTED FOR SHORT-TERM Option 2: Manual, Form on Testing Website

    2. Interface Compliance: Provide report of the executed test harness (Automated, Test Harness Steps to check compliance against a GovStack API spec )

      1. Option 1: Impact Exchange gets Test Results transferred (long-term)

      2. SELECTED FOR SHORT-TERM Option 2: Enter percentage and add link to test run (web app of test harness, e.g. https://testing.govstack.global/camunda/bb-workflow/649ca3124a07ca928b7aa184 )

    3. Requirement Specification Compliance: Conduct FitGap Analysis

      1. Option 1: Manual, Template on Confluence Compliance Evaluation: Template

      2. SELECTED FOR SHORT-TERM Option 2: Manual, Form on Testing Website

    4. Hand-in (Creation of Jira Ticket, notification that ticket is being created)

    5. Wait for verification of submission regarding completeness and plausibility by GovStack Team (Track via Jira Ticket) Who? TC? PC?

      1. Invalid: Do at least one of a-c again

      2. Valid:

        1. SELECTED FOR SHORT-TERM Option 1: Manual listing on GovStack.Global

        2. Option 2: Automatic listing on Impact Exchange which get embedded into GovStack.Global (Q4 2023)

  3. Offer your Software

    1. Once software achieves at least one compliance category level 1, the software gets listed on GovMarket (GovStack.global or/and Impact Exchange) with e.g. a badge visualizing the degree of compliance and a link to Testing website (Website and Impact Exchange)

    2. Once software achieves deployment compliance category level 2, the software is a candidate to be integrated into the GovTest Sandbox (Sandbox)

  4. Take Opportunities

    1. Get contacted by governments or other clients via GovMarket contact details

    2. Monitor GovMarket RFP Radar, apply and demonstrate compliance in a transparent manner via linking to GovMarket

    3. Create a “Vendor Storefront” to increase visibility and state offered services/products more clearly

  • No labels