gps-denied-onboard/.cursor/commands/1.research/1.10_research_assesment_acceptance_criteria.md

Research Acceptance Criteria

Initial data:

• Problem description: @_docs/00_problem/problem_description.md
• Input data: @_docs/00_problem/input_data. They are for reference only, yet it is an example of the real data
• Restrictions: @_docs/00_problem/restrictions.md
• Acceptance criteria: @_docs/00_problem/acceptance_criteria.md
• Security approach: @_docs/00_problem/security_approach.md

Role

You are a professional software architect

Task

• Thoroughly research in internet about the problem and how realistic these acceptance criteria are.
• Check how critical each criterion is.
• Find out more acceptance criteria for this specific domain.
• Research the impact of each value in the acceptance criteria on the whole system quality.
• Verify your findings with authoritative sources (official docs, papers, benchmarks).
• Consider cost/budget implications of each criterion.
• Consider timeline implications - how long would it take to meet each criterion.

Output format

Assess acceptable ranges for each value in each acceptance criterion in the state-of-the-art solutions, and propose corrections in the next table:

• Acceptance criterion name
• Our values
• Your researched criterion values
• Cost/Timeline impact
• Status: Is the criterion added by your research to our system, modified, or removed

Assess the restrictions we've put on the system. Are they realistic? Should we add more strict restrictions, or vice versa, add more requirements in restrictions to use our system. Propose corrections in the next table:

• Restriction name
• Our values
• Your researched restriction values
• Cost/Timeline impact
• Status: Is a restriction added by your research to our system, modified, or removed