Handle cosmetics LPV

[flomonster]

User

Study officer

Description

The user can see LPV.

Acceptance criteria

• When the speed limits are enabled on the map, the user should see the speed sections corresponding to the max speed of the line (if no train composition code is selected) or the max speed for the specific train composition (when this is specified). In both cases, the user can activate the LPV botton to display the speed sections corresponding to LPV.
• The LPV speed sections are displayed as dotted lines superposed to the other speed sections. The color of the dotted line rapresents the value of the speed (as for the other kinds of speed sections displayed).
• When the LPV speed sections are displayed, these are labeled as "speed limitation zone".
• When the botton "All the signals" is activated, we should see the pannels with the speed value, the Z and the R together with all the other signals.
• When the botton "speed limits" in the signaling part is activated, we should see the pannels with the speed value, the Z and the R.
• Different types of speed value pannels should be displayed (regular fixed TIV, TIV B, TIV C).

Definition of ready

• The user story is well defined
• Acceptance criterias are defined
• The individual responsible for validating the user story is assigned
• The team should understand how to demonstrate the features
• Does not depend on an missing feature
• Negociable with the implementation team
• Valuable to the end users
• Estimable by the implementation team
• As small as it can be
• Testable by the implementation team

Definition of done

• Acceptance criteria are met
• Automated tests are written against acceptance criteria
• Project deployed to the testing environment
• Story ok-ed by Product Owner
• Documentation updated