System Requirements Document

Introduction

Purpose of the document

The aim of this document is to enumerate a set of system requirements.

Scope of the document

The document identifies a set of system requirements to be considered as a main guidline in a rover design process. The guideline is based on ERC rules, URC rules and Team’s considerations discovered in an analysis phase.

The document presents requirements in the following sections:
  • Safety requirements
  • Teleoperations and telemetry requirements
  • General rover requirements
  • Robotic arm maneuverability requirements
  • Power consumption requirements
  • Mission-related requirements:
    • Scientific mission requirements
    • Maintenance mission requirements
    • Collection mission requirements
    • Autonomous traversal requirements

Acronyms

Acronym matrix
Acronym Full form Description
AR Acceptance Review A phase in which the product is verified on customer’s infrastructure
COTS Commercial, Off-The-Shelf A product that can be purchased/obtained freely in the market and utilized in a project
CDR Critical Design Review A development phase in which the project is reviewed critically, ideally by the external entity. It is to check compilance with requirements and test a so-far developed device.
FOV Field of View An area that is perceived by a camera
HMI Human-Machine Interface Any interface that facilitates sending/receiving commands to/from software or hardware
SW Software A set of commands to be executed on a computer, expressed in a human-readable format
SFR Simple Fetching Rover A type of a Mars rover that supposed to quickly transport an object, e.g. a boxed specimen, to the ground control

Terms and definitions

Terms and definitions
Term Definition
Ground control A place where a team can send commands to the rover and receive feedback data.
Rover A remotely controlled robotic platform.

Applicable documents

Applicable documents
Reference ID Title Short document description
[ERC-2018] European Rover Challenge 2018 - STUDENT Rules Rules and formula of ERC2018

Requirements

Note

Consider split the requirements identified below into groups

General information

Whenever the document mentions a word, it supposed to be mean the following:
  • shall - any requirement that contains the word shall is considered to be mandatory.
  • should - any requirement that contains the word should is considered to be optional yet expected in the final implementation.
  • may - any requirement that contains the word may is considered to be a nice to have feature but not critical for the overall mission.

Each identified requirement shall be given a unique identifier that follows the pattern:

(?<REQ>\w{3})-(?<CATEGORY>\w{4})-(?<NUMBER>\d{4})(/(?<TASK>\w{4}))?
Group label definitions:
  • REQ - the group is a keyword for ‘Requirement’, denoted as ‘REQ’
  • CATEGORY - the group accepts 4-character category name
  • NUMBER - the group accepts 4-digit identification number
  • TASK - the optional group that assigns the requirement into a specific subgroup

Note

Examples:

  • REQ-SAFE-0010: Requirement - Safety requirements - ID 10
  • REQ-SCIE-0010/GEOL: Requirement - Scientific mission requirements - ID 10 / GEOLogical task

[SAFE] Safety requirements

Safety requirements table
ID Requirement Description
REQ-SAFE-0010 The rover shall be equipped with an emergency stop button The stop button shall provide the very basic level of safety in case of the rover is out of control
REQ-SAFE-0011 The emergency stop button shall be red The red stop button is the industry-known standard for marking safety buttons
REQ-SAFE-0012 The emergency stop button shall be Commercial, Off-The Shelf component The COTS stop button provides the greatest reliabilty
REQ-SAFE-0013 The emergency stop button shall isolate the batteries from the system by single button hit. The stop button shall cut the power circuit and keep it in such state until the rover is reset. The only exception is batteries installed in laptops that are not mandatory to be separated.
REQ-SAFE-0014 The emergency stop button shall be installed in an easily accessible location. The location shall not inflict any injurers to anyone who hits the button. The requirement is to provide minimal safety standard to anyone who has to kill the rover abruptly.
REQ-SAFE-0015 The emergency stop button shall withstand hard hit Anytime the button is hit, anyone who hits it must be assured the button acts correctly.
REQ-SAFE-0020 The rover shall be equipped with an activity indicator The activity indicator informs everyone in the vicinity the rover is operational and may/may not cause injuries to the people around.
REQ-SAFE-0021 The activity indicator shall be visible in radius of 10m The activity indicator warns people around the rover is operational.
REQ-SAFE-0022 The activity indicator shall blink or flash Non-continuous visual signals are easily noticable by humans thus safer.
REQ-SAFE-0023 The activity indicator should be of either yellow, orange or red color These colors are usually associated with danger and keep people vigilant.
REQ-SAFE-0024 The activity indicator should be COTS This is to provide reliability
REQ-SAFE-0025 The activity indicator should be active 5 seconds before the rover performs any action. During this time the rover should remain still.

[TELE] Teleoperation and telemetry requirements

Teleoperation and telemetry requirements
ID Requirement Description
REQ-TELE-0010 The rover shall use one of the following wireless communication systems: Radio amateur bands, WiFi 2.4GHz, WiFi 5GHz, ISM bands, Other frequencies if an appropriate license is acquired The Team shall meet communication requirements
REQ-TELE-0020 The Team shall prepare a Radio Frequency Form. The From shall provide wireless system information, frequencies used and RF spectrum.
REQ-TELE-0030 Telemetry data should be stored for further evaluation Logs such as power parameters, accelerations, send/received commands can become handy for further rover development and debugging.
REQ-TELE-0040 Team may be asked to provide access to power circuits in non-invasive manners to measure power consumption of the rover independently by the jury. This is to provide an exteral logging system.

[GNRL] General rover requirements

General rover requirements
ID Requirement Description
REQ-GNRL-0010 A rover shall be a standalone, mobile platform. No thethers are allowed
REQ-GNRL-0020 The mass of the rover should not exceed 50-60kg The heavier rover will be penalized and lighter one rewarded.
REQ-GNRL-0030 It should be possible to inscribe the rover into an envelope shape of 0.75m diameter General advise when building a rover
REQ-GNRL-0040 The maximum speed of the rover shall not exceed 0.5 m/s Real Mars rovers move even slower. Speed of 0.5 m/s provides additional safety margin in case the rover is out of control
REQ-GNRL-0050 The rover shall keep its connection with a ground control facility at up 100m distance General terrain conditions that can occur during the Challenge
REQ-GNRL-0060 The Team shall be ready to deploy an antenna mast in a distance of 20m out of the ground control facility Ground control facilities are unknown til the Challenge is started
REQ-GNRL-0070 The rover shall withstand temperatures between 15 and 30 degrees Celcius Usual temperatures in September in Poland
REQ-GNRL-0080 The rover shall withstand wind gusts, light drizzle and high sunlight levels The Challenge site may be outdoor
REQ-GNRL-0090 The rover shall be able to traverse sandy, non-cohesive soil, hard and dry terrain as well as cobbled roads or other industrial surface types. It expected the rover shall operate in off-road conditions as well as in industrial ones.
REQ-GNRL-0100 The rover shall transmit video signal to the ground control for tele-operation purposes Video feedback is essential to perform reliable, robust, human-driven, in-field scenarios

[ARMM] Robotic arm maneuverability requirements

Robotic arm maneuverability requirements
ID Requirement Description

Integration, verification and other requirements