Advertisement

Railway-Control Product Families: The Alcatel TAS Platform Experience

  • Julio Mellado
  • Manuel Sierra
  • Ana Romera
  • Juan C. Dueñas
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1951)

Abstract

Railway-control systems must cope with strict dependability requirements. Typically, a product or installation is composed by several applications, different operating systems, and a number of hardware pieces. The range of combinations is large and thus the range of products in the family. In order to keep this figure small, handle the development process efficiently (unavoidably delayed by the validation efforts required) and to isolate software and hardware elements, Alcatel Transport Automation Systems (TAS) took a strategic decision: to choose an operating system able to hide hardware variability, and provided by a third party. This paper describes the concept of product family used by Alcatel TAS, organized around an operational platform for applications in the product line, reports the experience carried out in Alcatel Spain, in porting existing railway control applications to the Alcatel TAS Platform (an operating system developed by Alcatel) and discusses some advantages of this approach.

Keywords

Fault Tolerance Software Architecture Product Family Springer Lecture Note Message Queue 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    ANSII/IEEE Std 1003.1 and ISO/IEC 9945-1, Information Technology - Portable Operating System Interface (POSIX ®) - Part1: System Application Interface (API) [C Language], 2nd Edn. (1996)Google Scholar
  2. 2.
    Bowen, J., Isaksen, U., Nissanke, N.: System and Software Safety in Critical Systems, Technical Report RUCS/97/TR/062/A, Reading University, Computer Science Department England (1997)Google Scholar
  3. 3.
    Comité Europeén de Normalisation Électrotechnique CENELEC, prEN 50128, Railway applications - Software for railway control and protection systems (1997)Google Scholar
  4. 4.
    Dolan, T., Weterings, R., Wortmann, J.C.: Stakeholders in Software-System Family Architectures. Development and Evolution of Software architectures for Product families. In: van der Linden, F.J. (ed.) Development and Evolution of Software Architectures for Product Families. LNCS, vol. 1429, pp. 172–187. Springer, Heidelberg (1998)CrossRefGoogle Scholar
  5. 5.
    Doppelbauer, J., Lennartz, K., Veider, A., Warlitz, J.: Basisystem für signaltechnisch sichere Anwendungen, Signal+Draht 10/98, pp. 8-12 (1998)Google Scholar
  6. 6.
    Maschek, U.: Elektronische Stellwerke - ein internationaler Überblick, Signal+Draht 03/97, pp. 8-23 (1997)Google Scholar
  7. 7.
    Meekel, J., Horton, T.B., Mellone, C.: Architecting for Domain Variability. In: van der Linden, F.J. (ed.) Development and Evolution of Software Architectures for Product Families. LNCS, vol. 1429, pp. 205–213. Springer, Heidelberg (1998)CrossRefGoogle Scholar
  8. 8.
    Perry, D.E.: Generic architecture descriptions for product lines. In: van der Linden, F.J. (ed.) Development and Evolution of Software Architectures for Product Families. LNCS, vol. 1429, pp. 51–56. Springer, Heidelberg (1998)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2000

Authors and Affiliations

  • Julio Mellado
    • 1
  • Manuel Sierra
    • 1
  • Ana Romera
    • 1
  • Juan C. Dueñas
    • 1
  1. 1.Alcatel Transport Automation Systems Spain, Depto Ingeniería de Sistemas TelemáticosUniversidad Politécnica de Madrid 

Personalised recommendations