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 2 Next »

  1. Get aware and consume information

    1. First point of contact and Awareness of Compliance Opportunity (Event, Website, Impact Exchange)

    2. Informing about Compliance Process (Confluence)

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

  2. Conduct and publish Self-Assessment based on a template (Confluence)

    1. Deployment Compliance: Link to container and documentation (Manual)

    2. Interface Compliance: Provide report of the executed test harness (Automated)

    3. Requirement Specification Compliance: Conduct FitGap Analysis (Manual)

  3. Offer Software (and optionally adapt software)

    1. Once software achieves at least one compliance category level 1, the software gets listed on GovMarket with a badge visualizing the degree of compliance and a link to confluence Self-Assessment (Website)

    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