Information technology

As for Home or Building Electronic Systems (HBES) this resulting European Standard specifies, for the domain of Building Automation and Control System Application and Building Management (BACS), common rules for a class of multi-application bus systems where the functions are decentralized and linked through a common communication process. This European Standard sets the basic requirements for products and systems. The requirements may also apply to the distributed functions of any equipment connected in a home or building control system if no specific standard exist for this equipment or system.

Consequently with its reference to the EN 50090 series this European Standard sets requirements for the BACS area as regards Architecture and Hardware, Application and Communication of systems based on HBES by amongst others specifying the basic requirements for interoperability (between products and systems).

Aspects like environmental conditions/external influences, electrical safety, EMC, etc. used to be also contained in the EN 50090-2-2, which will be superseded by the now available EN 50491 series. The latter European Standard series was jointly developed between CENELEC/TC 205 and CEN/TC 247 and will in the future also include aspects like functional safety in normal use (now contained in the EN 50090-2-3). The EN 50491 series apply together with the relevant product standard for the device, if any.

This International Standard deals with the tools and methods of technical management for software products, software services, software-intensive systems  (including System Architecture and excluding hardware)  within a product line. The scope of this standard is as follows:

-          Enable the users of this standard to holistically understand, adopt, and enact the processes, tools, and methods for product line technical management. And this standard helps the users evaluate and select relevant tools and methods based on business and user-related criteria.

-          Help product line engineers, developers, and tool vendors make informed about capabilities of tools and methods that are required for supporting product line implementation from technical aspects.

-          Provide product line-specific processes and capabilities of tools and methods in technical management.

This International Standard does not concern processes and capabilities of tools and methods for technical management for a one-of-a-kind system but rather deals with those belonging to a family of systems.

NOTE: System Architecture is a set of logical and physical principles used to achieve a mission within a given environment. From System Architecture are derived components that can be subsystems, software products, human-based products like crew or operators or hardware product like mechanical structures, electronic boards, chemicals, etc. The scope of the standards spans from the system, to sub-systems and software products. Other types of components and especially those related to human beings and to hardware parts are not within the scope of this standard.

This International Standard deals with the tools and methods of requirements engineering for  software and systems product line. The scope of this standard is as follows:

-   provide the terms and definitions specific to  requirements engineering for software and systems product lines.

-   define process groups and their processes performed during product line requirements engineering. Those processes are described in terms of purpose, inputs, tasks, and outcomes.

-   define method capabilities to support the defined tasks of each process.

-   define tool capabilities to automate/semi-automate tasks or defined method capabilities.

This International Standard does not concern processes and capabilities of requirements tools and methods for a single system but rather deals with those for a family of products.

NOTE: This standard is not suitable to handle physical artifacts. In the Systems arena, the word Product must be understood as System-level artefacts like requirements documents, architectural data, validation plans, Behavioral Models, etc. In any case, the word Product must not be understood as physical items such as electronic boards,  mechanical parts or qualified human operators. In the case of the Software components of a Systems, this Standard can apply twice: once to handle the System-Level Product Line and a second time to handle the Software Part Product Line, if any. The Product Line processes are recursive within the different levels of Products.

Part 2 of this series contains Identification, Authentication and Digital Signature (IAS) services in addition to the SSCD mechanisms already described in Part 1 to enable interoperability and usage for IAS services on a national or European level.

It also specifies additional mechanisms like key decipherment, Client Server authentication, identity management  and privacy related services.

The scope of this part of ISO 15638 is to define generic basic vehicle and core application data  (4.8)  provision to application service provider  (4.4) to be supported by in-vehicle system  (4.11) (IVS) for cooperative telematics applications for regulated commercial freight vehicles (4.19) (TARV), and to provide basic vehicle data  (4.6) for cooperative intelligent transport systems.

This part of ISO 15638 provides the specifications for generic basic vehicle data  (4.6) that it is required for all TARV  IVSs (4.11) to support and make available to application service providers  (4.4) via a wireless communications link supported by the IVS, in order to support the provision of regulated and commercial application services.

Some further data concepts, while not required in all cases for every TARV in every jurisdiction  (4.13), may be required generically for all equipment within a particular jurisdiction, or class of TARV within a jurisdiction, in order for the jurisdiction to achieve its regulation of TARVs.

Equipped vehicles operating internationally will need to carry all of the additional data concepts required by all of the jurisdictions  (4.13) within which they operate, in order to determine their core application data  (4.8). This part of ISO 15638 provides standard definitions for these commonly expected additional data concepts.

A second set of (largely complementary) ‘basic vehicle’ data is required to support interoperable cooperative intelligent transport systems and this is also specified within this part of ISO 15638. The framework architecture and many of the protocols are common between both TARV the wider cooperative ITS (C-ITS) sector.

The scope of this part of ISO 15638 is to define provisions to enable monitoring and enforcement of regulated vehicles and certification authority  (4.10) approval procedures, specifically:

a)     Definition of the roles and responsibilities of key entities: user (4.29), service provider (4.25), jurisdictions (4.16), and ‘certification authorities’

b)    Operating requirements ensuring that a cooperative in-vehicle platform can deliver a range of services to both government and industry through open standards and competitive markets

c)     Basic service requirements for service providers that are generic and independent of a specific application

d)    Requirements for the certification authority approval of in-vehicle systems (4.12) and service providers  (4.25)

e)     Legal, regulatory (4.20), and enforcement aspects.

The scope includes the requirements for the IVS  (4.12) capability in the vehicle, and the definition of the roles of the service provider  (4.25), IVS installer (4.13), IVS  maintainer (4.14), certification authority  (4.10), and the user  (4.30).

for cooperative telematics applications for regulated commercial freight vehicles  (4.22) .

NOTE: The specific ‘certification’ procedures for specific application services are a matter for the jurisdiction (4.15) and are outside the scope of this (or any) part of 15638. However certification authorities(4.10)  are recommended to use the guidance of ISO 17000 and ISO guide 65 when developing and implementing such procedures.

The scope of this part of ISO 15638 is to define a generic cooperative ITS service (4.3) platform for TARV using CALM, including protocol of coding, timing, and performance and support interfaces (such as driver ID card/USB or similar etc.).

.