The aim of this paper is to trigger a conversation about the assessment, definition of metrics and testing procedures of software-defined GNSS receivers. While the evaluation of traditional (i.e., built on application–specific integrated circuit technology) GNSS receivers is now well–understood, and enjoys both a solid testing industry providing the required equipment and universally agreed figures of merit, the particularities of software–defined radio technologies claim for a more comprehensive approach. In order to account for such a multi–faceted nature, the authors identify sixteen design forces, or dimensions in which a software-defined GNSS can improve. Upon those definitions, a wide list of performance indicators, metrics and procedures are then proposed for each of the identified thrusts. The list can be used as a generative source of ideas when defining key performance indicators in projects, products or services involving a software–defined GNSS receiver.
[1]
James A. Whittaker,et al.
How Google tests software
,
2012,
CSIIRW '10.
[2]
References
,
1971
.
[3]
Sharon Poggenpohl,et al.
Open Design Now: Why Design Cannot Remain Exclusive
,
2011
.
[4]
G. Petit,et al.
IERS Conventions (2010)
,
2010
.
[5]
Werner Gurtner,et al.
RINEX - The Receiver Independent Exchange Format - Version 3.00
,
2007
.
[6]
Stewart Teasley,et al.
Summary of the Initial GPS Test Standards Document: ION STD-101
,
1995
.
[7]
C. Hay.
Standardized GPS Simulation Scenarios for SPS Receiver Testing
,
2006,
2006 IEEE/ION Position, Location, And Navigation Symposium.
[8]
Michel Avital,et al.
The generative bedrock of open design
,
2011
.