Validation Request WP3 First Iteration Release

[BerndHekele]

Dear WP4 Partner,
WP3 just has completed the first iteration release.
The release is tagged with https://github.com/openETCS/modeling/releases/tag/v0.1-D3.6.1

You find the details to the release in the Architecture and Design Description:
https://github.com/openETCS/modeling/blob/master/openETCS%20ArchitectureAndDesign/FirstIteration/openETCSArchitectureAndDesignSpecification.pdf

Verification Object is the Scade model being center of the release.
Verification goal is the conformity to the architecture description and the conformity to the SRS 26.

Specification References are part of the architecture document.

Kind Regards
Bernd

[MarcBehrens]

Looking through the content of the release, the complete snapshot of the modeling repository seems to be included within, including the second and the third iteration.

Since no further overview is given which artifacts of the release are included the assumption is taken only to verify the artifacts explicitly described in the documents containing the details of the release.

[janWelte]

Based on the lead document - openETCS System Architecture and Design Specification this verification covers the following model parts

Verification Task:

• Overall Architecture First Iteration openETCS/modeling@b330fc1

Model Components

• F.1 Manage Balise
  • F.1.1 Receive Eurobalise from API openETCS/modeling@0ddbc56
  • F.1.2 Build BG Group Message openETCS/modeling@dd50f53
  • F.1.3 Check BG Consistency openETCS/modeling@1576a00
  • F.1.4 Determine BG-Orientation and LRBG openETCS/modeling@cd957d9
  • F.1.5 Select Usable Info openETCS/modeling@f05aecd
• F.2 Manage Train Position
  • F.2.1 Validate Data Direction openETCS/modeling@e92c358
  • F.2.2 Calculate Train Position openETCS/modeling@1576a00
  • Provide Position Report openETCS/modeling@1576a00

All other parts of the SCADE model are only part of verification if they are part of one of these functions.

[MarcBehrens]

Grooming session 7.1.2015:

• The verification expected from WP3 should reference the following requirement document: ERA. System Requirements Specification, SUBSET-026, v3.3.0 edition, March 2012
• Only the functional correctness of the model is expected to be verified, not the timing parameters

[MarcBehrens]

refers to product backlog openETCS/product-backlog#28

[MarcBehrens]

Grooming 21.01.2014 the first model component parts have been assigned for verification:

• F.1 Manage Balise
  • F.1.1 Receive Eurobalise from API openETCS/modeling@0ddbc56 assigned to @jensgerlach
  • F.1.2 Build BG Group Message openETCS/modeling@dd50f53 --> including Project Library: BG_Types assigned to @jensgerlach
  • F.1.3 Check BG Consistency openETCS/modeling@1576a00 (designer: @Farhangi ) @AbdelnasirMohamed
  • F.1.4 Determine BG-Orientation and LRBG openETCS/modeling@cd957d9 relocated to F.1.3, see 1 (designer: @Farhangi )
    • as subfunction CheckBGConsistency_Pkg::SubFunction::WriteDirection2PassedBG/ for Balise Groups with at least two Balises
    • as subfunction CheckBGConsistency_Pkg::CaseLinkingNotInUse/ for Balise Groups with a single Balise
  • F.1.5 Select Usable Info openETCS/modeling@f05aecd assigned to @janWelte
• F.2 Manage Train Position
  • F.2.1 Validate Data Direction openETCS/modeling@e92c358 @MarcBehrens
  • F.2.2 Calculate Train Position openETCS/modeling@1576a00 assigned to @MarcBehrens
  • Provide Position Report openETCS/modeling@1576a00 @idelatorre will check if it is possible to contribute