2011
Report
Unknown
CBTC preliminary report
Ferrari A.
CBTC are modern railway signaling systems used in urban railway lines for light rail (e.g., tranvia), heavy rail (e.g., metro) and APM (Automated People Mover, e.g., Airport metros). Sometimes, they can be deployed also on commuter lines (rails going to suburban areas, e.g., S-Bhan). This document summarizes the main features that a generic CBTC shall support, based on the current IEEE standards and on the currently analyzed implementationsSource: ISTI Technical reports, 2011
Ferrari A.
CBTC are modern railway signaling systems used in urban railway lines for light rail (e.g., tranvia), heavy rail (e.g., metro) and APM (Automated People Mover, e.g., Airport metros). Sometimes, they can be deployed also on commuter lines (rails going to suburban areas, e.g., S-Bhan). This document summarizes the main features that a generic CBTC shall support, based on the current IEEE standards and on the currently analyzed implementationsSource: ISTI Technical reports, 2011
See at: CNR ExploRA
2011
Report
Unknown
Evaluation of the IBM rhapsody tool for modeling automatic train protection (ATP) systems: the restrictive signal confirmation (RSC) button
Ferrari A., Illiashenko Oleg, Parfenov Sergii
The current document reports the evaluation of the IBM Rational Rhapsody tool for the modeling of Automatic Train Protection (ATP) systems software. The focus of the activity is on the Restrictive Signal Confirmation (RSC) button, a typical control component that, through not used in every ATP system, is considered a good representative of the expected functionality of an ATP software.Source: ISTI Technical reports, 2011
Ferrari A., Illiashenko Oleg, Parfenov Sergii
The current document reports the evaluation of the IBM Rational Rhapsody tool for the modeling of Automatic Train Protection (ATP) systems software. The focus of the activity is on the Restrictive Signal Confirmation (RSC) button, a typical control component that, through not used in every ATP system, is considered a good representative of the expected functionality of an ATP software.Source: ISTI Technical reports, 2011
See at: CNR ExploRA
2011
Journal article
Restricted
Adoption of model-based testing and abstract interpretation by a railway signalling manufacturer
Ferrari A., Magnani G., Grasso D., Fantechi A., Tempestini M.
Introduction of formal model-based practices into the development process of a product in a company implicates changes in the verification and validation activities. A testing process that focuses only on code is not comprehensive in a framework where the building blocks of development are models, and industry is currently heading toward more effective strategies to cope with this new reality. This paper reports the experience of a railway signalling manufacturer in changing its unit level verification process from code-based testing to a two-step approach comprising model-based testing and abstract interpretation. Empirical results on different projects, on which the overall development process was progressively tuned, show that the change paid back in terms of verification cost reduction (about 70%), bug detection, and correction capability.Source: International journal of embedded and real-time communication systems (Online) 2 (2011): 42–61. doi:10.4018/jertcs.2011040103
DOI: 10.4018/jertcs.2011040103
Metrics:
Ferrari A., Magnani G., Grasso D., Fantechi A., Tempestini M.
Introduction of formal model-based practices into the development process of a product in a company implicates changes in the verification and validation activities. A testing process that focuses only on code is not comprehensive in a framework where the building blocks of development are models, and industry is currently heading toward more effective strategies to cope with this new reality. This paper reports the experience of a railway signalling manufacturer in changing its unit level verification process from code-based testing to a two-step approach comprising model-based testing and abstract interpretation. Empirical results on different projects, on which the overall development process was progressively tuned, show that the change paid back in terms of verification cost reduction (about 70%), bug detection, and correction capability.Source: International journal of embedded and real-time communication systems (Online) 2 (2011): 42–61. doi:10.4018/jertcs.2011040103
DOI: 10.4018/jertcs.2011040103
Metrics:
See at:
International Journal of Embedded and Real-Time Communication Systems 
| CNR ExploRA