90 likes | 203 Vues
The project focuses on establishing a reference architecture for three pilot sites to enhance smart electro-mobility. Key goals include defining common principles, identifying a unified Information Model, and specifying ICT services that integrate electro-mobility with public transport systems. The open architecture approach emphasizes public specifications, easy add-on capabilities, common terminology, interoperability, and data availability through standard interfaces. This bottom-up methodology seeks to build robust systems by combining existing subsystems, leveraging real-world use cases from pilot sites.
E N D
MOLECULES ARCHITECTURE www.molecules-project.eu ETRA - M.JoséDurà 27th – 28th March
Objectives Open Architecture for smart connected electro-mobility Objectives: • To define a reference architecture and principles common for the three pilot sites, considering the requirements and use cases specified in the project. • Identify a common Information Model. • Specify ICT Services granting integration of the electro-mobility modes of transport with the rest of public transport systems.
Objectives Open architecture • Specifications are public • Easy add-on products: Allow third-parties to evolve the application • Common terminology • Interoperability • Availability of data: Standard (open) interfaces
Approach Bottom-up approach Piecing together of systems to give rise to grander systems, thus making the original systems sub-systems of the emergent system.
Approach Startingfromthe use cases in eachpilotsite. • General Open electromobilityArchitecture • Molecules Open Architecture • Other CIP projects • MoleculesBerlin • Architecrure • Molecules Grand Paris Architecrure • Molecules Barcelona Architecrure
Workflow Workflow
Workflow UML diagramtypes Dynamicmodel Staticmodel Componentsdiagram Deploymentdiagram Use cases diagram Sequencediagram
Principles Thearchitectureis a highlevelstructureof thesystem, specifyingthediferentcommponents, itsproperties and theexternalrelationshipsbetweenthem. BASIC PRINCIPLES TO CONSIDER: • Hide complexity. • Separate concerns. • Design using interfaces. • Separate / distribute responsibilities.
Thanks for your attention. • Any questions? • mjdura.etra-id@grupoetra.com • asolar.etra-id@grupoetra.com