Section 8

Technical Requirements Template

Purpose:

Technical requirements are specifications that guide usage of: data, software, processing environments/platforms., outputs, and hardware needed during solution production. This template walks the solution team through technical components required for a solution and that should be considered and included in solution design.

Proactively considering the technical requirements of a solution early in the co-development process is vital for efficient collaboration and meeting deadlines. Though most dialogue on the user's technical requirements will arise during co-design, keep in mind that important information about needs and preferences is likely to arise even earlier. For example, a user may mention their preferred software or computing limitations during preliminary stakeholder engagements.

Also, note that some stakeholders who are newer to geospatial tools or Earth observations may not have clear preferences or may be unsure of certain technical specifications, so they may require more thorough conversation to fully understand their requirements. Teams should be attentive to user needs that come up during Phase 1 and other Phase 2 tools and remember to document them in this template.

NASA Earth Action Solutions Co-Development Toolkit, v0.1 | 72

How and When to Use This Template:

How and when

This template is used at the beginning of Phase 2 of the co-development framework once a solution team starts designing the solution. Referencing the Stakeholder mapping, Needs Assessment, and the Design for Impact tools provides understanding of the needs and the objectives of the solution, it documents who the stakeholders are, the beneficiaries and the deliverables.

Key Questions for Co-Development Partners

Agreements
Refer to Co-Design Process Guidance (provide Link)

Do you need to establish agreements to co-design with partners? If yes, provide a link to the collaboration agreement as feasible. If agreement is not shareable, just indicating that there's an agreement in place that enables collaboration and captures the elements indicated in this section should be sufficient. Types of sample agreements (all indicating collaboration roles) include:

  • Email confirmation
  • Signed meeting minutes confirming collaboration and partner roles
  • Letter of collaboration
  • Interagency agreement
  • DAACS agreement
  • Legal collaboration agreement
  • External partners collaboration agreement

Do you need to establish data-sharing agreements? If yes, provide a link to the data sharing agreement. Include confidentiality and non-disclosure agreements NDAs) where necessary.

Is the data available under open access mechanisms or is it private data? Does the data access and sharing need encryption? Do you have a mechanism for data encryption? If yes, ensure to include a data encryption tool in the list of software needed.

NASA Earth Action Solutions Co-Development Toolkit, v0.1 | 73

What are the roles and responsibilities for each partner? Include a link to the roles and responsibilities for partners

Please ensure these agreements are in place to streamline co-development processes.

What are the data sharing mechanisms between partners?
Refer to the Data Governance and Storage Plan
Communication with partners
  • Do you need to establish communication channels for co-developement?
  • Do you have tools/software in place for everyday exchange and meetings?
Existing partner capabilities
Reference to the Stakeholder Mapping tool
User feedback
Refer to the User Co-Design Process Guidance and the User Centered Design Tool

How will user feedback be collected before production? Identify the timing of when to collect feedback at different stages of the solution co-development lifecycle. Feedback will need to be integrated into the new design.

Inputs
Refer to the Solution Implementation and Impact Monitoring and the Designing for Impact tools

What are the inputs at different stages of development?

  • Inputs for Development and Testing
  • Inputs for Deployment
  • Inputs for System Maintenance
Outputs
Refer to the Solution Implementation and Impact Monitoring and the Designing for Impact tools
  • What are the outputs desired?
  • What is the minimum viable product?
  • Does it address the user's needs? Feedback from stakeholders at this stage should determine the outputs are satisfactory
  • Does it integrate stakeholders feedback?
  • Does it have considerations for future use?
Deliverables
Refer to the Solution Implementation and Impact Monitoring Plan and the Design for Impact tools
End user requirements
Refer to the Solution Adoption Sustainability Plan and User-Centered Design Guidance

NASA Earth Action Solutions Co-Development Toolkit, v0.1 | 74

Technical Requirements | Example Specifications

Existing data and tools
  1. Data source 1 (can be cloud-based such as Cloud Optimized GeoTIFFs (CoGs) or downloadable to local stations)
    • Access: (Open Access, purchase required)
    • Spatial Resolution: (m, cm)
    • Spectral Resolution: (no of bands)
    • Latency: (Days, Hours)
    • Level of Analysis Readiness: (Processing Level)
  2. Data source 2
  3. Data source 3
Existing methods and approaches
Provide reference links (Select approach from list)
Existing codes
Provide links and dependencies for the codes
Relevant tools prior to design
Refer to the following tools:
  • Stakeholder mapping tool (provide link)
  • Needs Assessment tool (provide link)
  • User Centered Design (provide link)
User-centered design
Review can be made to the User Centered Design Guidance and the Designing for Impact tool
System architecture and workflow
Diagram
Codes to be leveraged and their dependencies
  • Code 1:
    • Dependencies
  • Code 2..
  • Code 3...
Information security and responsible AI use
Refer to the "Information Security and Responsible AI Use" section of the Solution Co-Development in Practice document and integrate relevant considerations
Input data
List
Field data / in situ data requirements
Required for validation of outputs
Output data and data formats
  • Output 1, format (can be cloud-based or downloadable)
  • Output 2, format
Metadata
Refer to the Data Governance and Storage Plan
Processing environment (platform)
  • Spec 1
  • Spec 2...

NASA Earth Action Solutions Co-Development Toolkit, v0.1 | 75

File naming convention
Refer to the Data Governance and Storage Plan
Versioning strategy
Refer to the Data Governance and Storage Plan
Storage location & backups
Refer to the Data Governance and Storage Plan
User co-design
Refer to the User Co-Design Inputs and integrate relevant considerations
Validating results and system testing
  • Do the results meet the validation thresholds?
  • Test and retest prototype/system before deployment.
  • If successful then you can proceed to deployment.
  • Does the system and results meet intended needs?
  • Does the UI/UX meet user requirements?
Deployment environment (platform)
  • Spec 1
  • Spec 2...
Key considerations
  • Is deployment Successful?
  • Did it meet the Minimal Viable product?
  • Does it meet the user requirement based on the User Centered Co-Design Guidance?
Sharing permissions
Refer to guidance provided in the Data Governance and Storage Plan
Branding and acknowledgment requirements
User co-design
Refer to the User Co-Design Inputs and integrate relevant considerations
System maintenance and transfer
Refer to the Solution Adoption and Sustainability Plan
Existing technical capacities
E.g., servers, compute resources, data...
Additional required technical capacities

NASA Earth Action Solutions Co-Development Toolkit, v0.1 | 76