wdes 2015 paper: designing a software architecture for a railway safety platform

17
Designing a Software Architecture for a Railway Safety Platform Adailton Lima, Rodrigo Reis, Melina Alberio, Carlos Lopes, Cleidson de Souza

TRANSCRIPT

Page 1: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

DesigningaSoftwareArchitectureforaRailway

SafetyPlatform

AdailtonLima,RodrigoReis,MelinaAlberio,CarlosLopes,Cleidson deSouza

Page 2: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brContexto

905KM110milhõesTON/ANO

892KM115milhõesTON/ANO

Page 3: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brContexto

Page 4: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brProblemas

Page 5: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brDesafio

• Como projetar tecnologias para melhorar onível de segurança dos funcionários,prestadores de serviço e cidadãos que vivemao longo dessas ferrovias?

Page 6: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brServiçosDesejados

• Informações adicionais de sinalização e segurança;– Pulseiras de proximidade, sensores de quedas, mapeamento de

funcionários emoperação, etc.

• Integração de aplicações e bases de dados de controlede operações;– Log integrado de operações, mapeamento online de zonas de risco,

integração com bases meteorológicas, integração com provedores detecnologia externos, etc.

• Serviços de informações à população;– Alertas de proximidade de locomotiva, notificações através de aplicativos

e mensagens,API aberta para acesso a serviços, etc.

Page 7: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brVisão daPlataforma

Please comment on the format: your feedback is highly valuable!

#PDCanvas is now v. 0.2 Community Comments to v 0.1 have been processed

See original v. 0.1 here: http://bit.ly/PDCanvas_v01

Key Platform Stakeholders

Key Community Support Services

Key Platform Components

Value Proposition

What are the key stakeholders contributing to the platform operation and mission? Typically includes the platform owner(s), key partners of the platform owner(s), external entities that can contribute to the success of the platform

Key Transactions

What are the services that stakeholders create to support Community development and value creation among peers?

What are the key components of the platform? (shared resources, standardized formats, common infrastructures)

How is the value exchanged? Map the type/forms of value that is exchanged during transactions. Typically each transaction should corresponds to a channel and to a type of value exchanged.

Through which Channels do the peer segments get in touch, execute transactions and exchange any form of value?

How is the value extracted by the stakeholders and in what forms? This value is extracted in exchange of the services and components that stakeholders provide

What are the recurring Transactions happening between the different peer segments?.

What are the peer segments interacting with the platform? Start from the value, product and content producers and consumer then focus on other ancillary segments

What problem does the platform solve for peer segments? What are the intrinsic motivation for peers to participate?

Peer Segments

Channels

Value Extractions Value Exchanges

The Platform Design Canvas (Part of the Platform Design Toolkit) Iteration #

www.meedabyte.com This work is a fork ofthe Business Model Generation Canvas by Alex Osterwalder (http://www.businessmodelgeneration.com) and is licensed under the Creative Commons Attribution-Share Alike 3.0 Unported License , To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/.

2 1 35

4

7

8

69

Legend:X Small numbers represent the

suggested step-by-step procedure to compile the canvas

X Green represents P2P dynamics (exchanged value)

8 Red represents Social / Community dynamics (shared value)

Simone Cicerov 0.2

Designed by:

Vale

PrestadoresdeServiço

Sociedade

Melhor imagemdaempresa

Aumentodasegurançadasoperações

Menorcustodeintegraçãodeinformações

Acessoaserviçosintegradosviaplataforma

Vale

Hackathons

Licitações deSoluções

RededeFibraÓptica

ServiçosnaCloudHíbrida

Consultadedados

Logdeoperações

Registroeacessoanovosserviços

Page 8: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brLiteratura

• Trabalhosrelacionadosaplataformas:

– Evoluir deumproduto oulinha deprodutopara

plataforma;[Costaetal.2013][Bosch2009]

– Comoplataformasevoluem;[Monteith 2013]

– APIs eestilosarquiteturais;[Bosch2009]

Page 9: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brMetodologia• Como construir uma plataforma?– Optou-se pelo projeto da plataforma ao invés defocar um problema/solução específico de cada vez;

– ATAM como modelo para processo de projeto daarquitetura;

Present ATAM

Identify Business Drivers

Architecture Design

Analysis and Tradeoffs

Page 10: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brStakeholders

• S1: Grupo de TI;

• S2: Pesquisadores construindo protótipos de novas

soluções para segurança;

• S3: Desenvolvedores de soluções que precisam ser

integradas aos novos serviços e serviços existentes

na empresa;

Page 11: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.br

Railroad Safety

Platform

Safety Monitoring Services

Existing Safety Systems

Client Applications

Monitoring Devices

BusinessDrivers

Page 12: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.br

Styles and Platform-based Ecosystems

The simplest “style”: APIs“value-adding” products call into the platform

Note: The bigger the vendor the less elegant the APIs need to be; the less there needs to be any evidence of a clear, coherent style

IComponent

I

ComponentI

ComponentI

ComponentI

ComponentI

Added

Component

Original Application

Exposed Interface

(API)

Interface Binding

(connector)

EstilosArquiteturais

API

Event-based Styles

Added

Component

I

ComponentI

ComponentI

ComponentI

ComponentI

ComponentI

Original Application

Incoming Event

Interface

Outgoing Event Interface

Event Mechanism (connector)

I

Key benefit: very strong decoupling of components

BaseadaemEventos

[Taylor 2013]

Page 13: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brTradeoffs

• Custo de criar infraestrutura de miniservidores ao longo da ferrovia;

• Comunicação e notificações sempre como umservidor central pode representar um gargaloao sistema;

Page 14: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brSemsuporteaservidoreslocais

Page 15: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brConsideraçõesFinais

• ATAM ajudou a explorar soluções dos problemasconhecidos e de contextos similares;

• Forneceu um ponto de partida para entender osrequisitos gerais;

• Processo segue em novas investigações paraavaliar a evolução da arquitetura;

Page 16: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

www.labes.ufpa.brEmAndamento

• Avaliação de tecnologias para integração deaplicações (SOA e APIManagement);

• Prototipação de componentes de segurança:– Sensores de posicionamento;– Sensores e aplicativos de quedas e procedimentos desocorro;

– “Sonar” para locomotiva;• Integração de serviços na Cloud privada da Vale;

Page 17: WDES 2015 paper: Designing a Software Architecture for a Railway Safety Platform

DesigningaSoftwareArchitectureforaRailway

SafetyPlatform

AdailtonLima,RodrigoReis,MelinaAlberio,CarlosLopes,Cleidson deSouza