SystemEngineering

eVectors

SystemEngineering

eVectors > eVectors

eVECTORS

Introduction

eVECTORS is an acronym from french words: VEhicule a ConsommaTiOn ultRa-baSse. The English translation is ultra-low consumption vehicle.

eVECTORS is initially developed by two Swiss universities:

Both universities are part of the HES-SO: Haute Ecole Specialisée de Suisse Occidentale

Licence

The current system model is provided with NO WARRENTY under Creative Common licence 4.0, BY (see list of authors below), Share Alike

CC-BY-SA

List of Authors

Luc Dominique Blecha, Associate Professor at HEIG-VD

Samson Deriaz, Engineer at HEIG-VD

Model Description

eVECTORS main purpose is to provide a sober alternative to passenger car for daily mobility needs in Switzerland.

To achieve this overall aim, the system is analysed at four different levels:

  1. The Operational Analysis defines what the user has to accomplish with the use of eVECTORS
  2. The System level defines what eVECTORS has to accomplish for the user to fulfill the Operational objectives
  3. The Logical level defines how eVECTORS works so as to fulfill system expectations
  4. The Physical level defines how eVECTORS is actually built

Operational Level

eVECTORS main operational capabilities or mission are:

The following diagrams illustrate how these three capabilities are linked to operational stakeholders:

The operational stakeholders are listed in [OEBD] Operational Entities.

System Level

To accomplish the Operational capabilities, the eVECTORS has to provide the following missions:

Each of these missions is then broken down into smaller System capabilities. The structure of these breakdowns and the 20 System capabilities identified are described in the following diagrams :

19 System Data Flow diagram are created : one for each of these 20 System capabilities, except for "Pass homologation (CH)". These diagrams describe the system functions that will be used to realise the capabilities.

Finally, a System Architecture diagram is created: [SAB] eVectors. This diagram brings together all the system functions that were previously identified, attributing them either to the system (eVECTORS) or to one of the stakeholders.

Logical Level

At logical level, each System Data Flow diagram is re-used: the System functions are broken down into one or more Logical functions. Logical functions are more precise and specific. A total of 19 Logical Data Flow diagrams then illustrate how eVECTORS operates at a logical level:

The System Architecture diagram is also re-used to create the Logical Architecture diagram: [LAB] EVectors. Functions are still attributed either to the system (eVECTORS) or to external stakeholders. This time, however, the functions attributed to the system are more precisely attributed to Logical Component created within it.

Physical Level

The genral eVECTORS product tree can be found in the [PCBD] eVECTORS Product Tree

Once again, each Logical Data Flow diagram is re-used and Logical functions are broken down into more precise Physical functions. This process is described in the following diagrams:

The Logical Architecture diagram is finally re-used to create the Physical Architecture diagram: [PAB] EVectors. The attribution of Physical functions is now done to the Physical Components themselves.

Content