CLC/TR 50501-1:2007

Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Reference architecture
  4.1 Introduction
  4.2 Reference Architecture concept
  4.3 Requirement for the STD1 Reference Architecture
      definition
  4.4 Interacting objects
  4.5 Functional Architecture
5 Methods for functional modelling
  5.1 Functional modelling framework
  5.2 Functional modelling activities
  5.3 Process of function class decomposition
  5.4 Modelling accessibility of entities and functions:
      the pattern view
  5.5 General modelling rules
  5.6 Metric Evaluation Criteria
  5.7 Testing
  5.8 XML usage
  5.9 Deliverables
6 The Data Dictionary
  6.1 Introduction
  6.2 Structure
  6.3 Requirements for management of the Data
      Dictionary/model repository
Annex A (informative) Related works
Annex B (informative) Functional addressing in
        railway specifications
Annex C (informative) Process of function class decomposition
Bibliography

This Technical Report will define -requirements for the methods to be used for functional standardisation, in the standards to be prepared for data exchange involving railway vehicles, in two contexts 1)inter-consists communication, within a train formation, 2)communication with ground based installations. -the Reference Architecture defining the essential functional interfaces, -the concept of a central Data Dictionary/repository to be applied to freight and passenger traffic functions. In this context, data are to be limited to basic information elements, which are necessary to define standard messages required for interoperability, and displayed on the interfaces of the communicating entities. Entering Data Dictionary will provide full definition of a data element, along with its essential attributes at conceptual level. The purpose, in the perspective of the standards to be prepared, is to document the data element pertinent to the functional area and essential for interoperability, to allow the reuse of data element among functional area systems, and facilitate data interchange among the systems. NOTEData Dictionary shall be designed to provide a structural framework that enables continued growth and enhancement of the scope of defined data. Rationale for this requirement is that it is difficult, when defining the scope of a proposed system to fully define the application domain and all included interoperability related data. In addition over time, functional requirements will expand.