OARIS 1.0 FTF Avatar
  1. OMG Issue

OARIS — Manage Frequency Usage classes don't all follow class naming convention

Open Closed All
  • Key: OARIS-59
  • Status: closed  
  • Source: BAE SYSTEMS ( Mr. Simon Mettrick)
  • Summary:

    The naming convention for OARIS is to suffix all classes with "_type". This was laid down in the REG's modelling guidelines. The following classes don't follow this guideline: -
    frequencies_set_request
    freqency_range_set
    all_frequencies_state
    reported_frequency_state
    selected_frequency_list
    transmission_frequency_state
  • Reported: OARIS 1.0b1 — Mon, 30 Mar 2015 08:38 GMT
  • Disposition: Resolved — OARIS 1.0
  • Disposition Summary:

    Rename Sensor Control Classes to have "_type" suffix

    All classes in the Sensor Control domain model should follow the convention and have the _type suffix. Consistency will aid understanding and usability (particularly at the programming level).
    This impacts: -
    frequencies_set_request (to be deleted by proposal 58)
    freqency_range_set (to be deleted by proposal 58)
    all_frequencies_state
    reported_frequency_state
    selected_frequency_list
    transmission_frequency_state
    and also from other use cases: -
    test_target_scenario_state
    control_emission_state
    test_target_scenario_common_parameter_target
    test_target_scenario_independent_target
    test_target_plus_scenario
    test_target
    test_target_scenario_id
    test_target_scenario
  • Updated: Tue, 22 Dec 2015 15:07 GMT