Engineering Editorial draft

Writing requirements from an Earth observation need in irrigated rice systems — a validation guide

Explore writing requirements from an earth observation need in irrigated rice systems. Practical guidance for validation and defensible observations.

ShareLinkedInFacebookXWhatsApp

Editorial draft. This generated working guide combines technical guidance with an illustrative context and requires individual editorial review.

Editorial illustration: Writing requirements from an Earth observation need in irrigated rice systems — a validation guide
Original editorial illustration for this article. Shapes and colours are conceptual, not measured observation data.

A method that produces a plausible result has not automatically demonstrated that it works for its intended users. Validation requires a defined question, suitable reference evidence, and an evaluation design that reflects how the method will be used. This perspective examines which observations should be compared, how they should be sampled, and which errors matter in practice. It also considers the difference between evidence used to develop a method and evidence reserved for evaluating it. The objective is a test that can reveal weaknesses as well as confirm useful performance.

This working guide considers writing requirements from an earth observation need in irrigated rice systems. The immediate decision is to identify fields needing irrigation review. Useful reference evidence includes field stage, inundation records and irrigation observations. The case is an illustrative planning context, with assumptions to check against the actual sensor, landscape and project requirements.

Translate a user decision into measurable behavior

A mission requirement should connect to a decision that someone needs to make with the observations. Begin by defining the target phenomenon, geographic area, relevant season and consequence of delay or error. A request to monitor crops is too broad to guide a spacecraft design. The useful question is which crop condition must be distinguished, at what field scale, how often, and with what confidence.

Translate these needs into product requirements before allocating spacecraft specifications. Consider spatial detail, spectral information, radiometric performance, location accuracy, usable revisit and delivery latency. Geometric revisit describes observation opportunities; clouds and acquisition constraints can make usable observations much less frequent. Define terms carefully so that a requirement for delivered, cloud screened coverage cannot be satisfied merely by showing an orbit access calculation.

Keep traceability through design and verification

Write individual requirements that can be checked using a stated method and acceptance criterion. Identify the conditions under which each applies, such as target brightness, viewing angle or operating temperature. Avoid combining several unrelated promises in one sentence. Retain a rationale and a link to the higher level need, allowing reviewers to understand why the requirement exists and what would change if it were relaxed.

Allocate performance across the payload, spacecraft, ground segment and processing chain. Image sharpness may depend on optics, detector sampling, motion and resampling. Delivery time may depend on acquisition planning, onboard storage, ground contacts and processing queues. Budgets make these contributions visible and expose conflicts between objectives. Preserve margin where uncertainty remains, and record assumptions rather than hiding them inside an optimistic headline specification.

Plan verification while writing the requirement. Inspection, analysis, demonstration and testing each provide different kinds of evidence. Define the test configuration, reference measurement, uncertainty and pass criterion early enough to influence the design. Verification asks whether the implemented system meets its requirements; validation asks whether that system serves the intended use. Representative users and realistic application examples can reveal an inadequate requirement even when every hardware test passes. Manage revisions through a controlled record that describes their consequences for dependent requirements, budgets and tests. This turns requirements into a working design tool rather than a document assembled only before a review.

The setting: Irrigated rice systems

An irrigated rice landscape changes from preparation and inundation to crop establishment, canopy development and harvest. Water and vegetation contribute differently to the observed signal at these stages. A field should therefore be interpreted with its planting calendar and irrigation status, not only its latest colour on a map. Accurate paddy boundaries are valuable because bunds, channels, neighbouring fields and settlements can occupy a substantial share of a small observation unit.

Organise the analysis around field-level sequences rather than a mosaic assembled from unrelated dates. In cloudy periods, identify gaps explicitly and consider which complementary observations are suitable for the question. Optical and radar measurements describe different physical properties, so their agreement or disagreement needs interpretation. An observation consistent with inundation is not by itself a complete account of irrigation delivery, field depth or the cause of a management problem.

A practical field visit records crop stage, water condition, planting method and the time of inspection. Irrigation managers may need a list of fields with unusual timing, while crop specialists may need areas of uneven development. These outputs require different validation records. Evaluate whether the information arrives early enough to support a decision, and retain observations of fields that were not flagged to understand missed events as well as false alerts.

Prioritise observations within delivery constraints

An observation has practical value only if it can reach the processing and user workflow in a suitable form and time. Delivery planning therefore belongs alongside acquisition planning. Identify the volume and priority of expected data, the opportunities available for transfer, and the consequences of delay. A system may collect more information than it can deliver promptly, so the handling of that difference should be an explicit design choice.

Define priorities using the information need rather than only the order in which files were created. A small set of timely, qualified observations may support a decision more effectively than a larger volume delivered after the relevant opportunity has passed. Preserve enough metadata to recognise each observation and its completeness during transfer. If compression, reduced products, or staged delivery are considered, evaluate how those choices affect the interpretation and subsequent processing of the information.

Test the delivery sequence with representative conditions, including interruptions and incomplete transfers. Establish how the receiving system verifies integrity, identifies missing components, and requests or schedules recovery where that is supported. Keep a record of actual delivery age and usable coverage. For a mission concept, these tests can be performed with simulated data flows before an operational claim is made. The objective is a delivery plan whose constraints are visible in the service that users receive.

Maintain the geographic units of analysis

Many observation services summarise measurements within a field, management block, catchment, forest unit, or other mapped boundary. The meaning of that summary depends on whether the boundary accurately represents the unit being discussed. Start with a clear source for the geometry and record its date, coordinate reference, and intended use. A boundary drawn for visual orientation may require additional checking before it becomes a measurement unit.

Inspect overlaps, gaps, narrow fragments, and features that may have changed since mapping. A geometrically valid polygon can still describe an outdated operational unit. Ask the responsible team how divisions, mergers, new infrastructure, and management changes are recorded. Where pixels or reference measurements cross a boundary, define how they are assigned or excluded so that results remain comparable between analysts and processing runs.

Version the boundaries alongside the observations. If a unit changes, preserve a relationship between the previous and revised geometry rather than replacing the history without explanation. Comparisons through time should identify whether they use a constant spatial unit or the operational units valid at each date. This makes it easier to distinguish a change in the measured surface from a change introduced by the geography used to summarise it.

Bring the evidence back to the decision

The validation record should explain the population represented by the test, the reference observations used, and the limitations of the comparison. Report meaningful errors alongside useful successes, and retain examples that challenge the method. Treat wider deployment as a new opportunity to evaluate transfer across relevant conditions. A well-designed validation programme gives users a defensible basis for deciding where the method is useful, where additional evidence is needed, and where another approach may be appropriate.

Sources & further reading

  1. NASA: Systems engineering handbook appendices
  2. NASA: Systems engineering handbook

Explore the bhumisat spacecraft concept and our vision towards 2030, or return to the journal.

ShareLinkedInFacebookXWhatsApp
A CONVERSATION STARTS HERE

Build the next
perspective with us.

Tell the TechnoGIS team where you would like to collaborate.

Opens your email app so you can review and send your enquiry.