Please enable JavaScript.
Coggle requires JavaScript to display documents.
spidr (actions (Analyse split BACK BBP into microservices to make a "…
spidr
actions
Meeting DEVOPS to analyse possibilites CDCI
Analyse possibilities to have a CDCI shared with BBP/SPIDR
Meeting with ARCHITECT team to define the good practices to SPIDR case
Define the architecture
Change the BBP DAT to add SPIDR
Create new schemas ❤️
Print and build the physical architecture board with the schemas
Create architectures pages
Analyse split BACK BBP into microservices to make a "kernel" shared by BBP/SPIDR
authentication + authorization
toolbox
relational data
vcd (elastic) ❤️
kubernetes (Orchestration :
https://kubernetes.io/
) ?
Analyse user requirement for the UI
do we need to be in the same FRONT ?
List pages mockups
List new components
study the POC ENIOKA
benchmark lib
gojs (
https://gojs.net
)
vis (
http://visjs.org/
)
...
define graph library
library license
Analyse input data
define formats
define imports
browser requirements (ie? chrome? performance?)
improve the moniotoring CDCI / JIRA / INTERDENPENDENCIES
risks
merge and deploy BBP/SPIDR
same repository
same amazon environments
same DB
same FRONT
same BACK
tests and validations
input data
benefits
Use the same DB with the shared data needed by both projects
User flow / UI (mech and vech)
Basic services (ARCA)