Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Architectural decisions

Responsibility for high level implementation of architecture

iTransition (Sergey V); accountable to Mark Blair, Alon Kovner

Responsibility for overseeing high level implementation

Indigina (Mark with Sergey)

  • microservices scope

  • database types (SQL, NoSQL eg. CosmosDB)

  • communication of ideas and decisions through agile process with Sergey V and Mark B speaking regularly

Concerns

Concerns about the number of projects running concurrently (outside of Suez) and amount of time available

  • Back end team may need to be expanded

  • QA team required

  •  Will there be enough overview on an ongoing basis once the project is in full swing?

Responsibility for database meta schema

iTransition

  • Responsibility for contributing to database design and duplication

  • Responsibility for implementation

iTransition team tasks in the early stages

  • Read documentation from Steven Bennett regarding product functionality and scope of project

  • Getting toolkits and work spaces set up

  • Research on microservices, noSQL, other functionality which is new to them

  • Concentrate on getting one microservice correctly written end to end to serve as a reference for future

    • UI

    • Back end

    • CI/CD

    • Deployment

Back End

  • CI/CD skeleton microservice – setting up organisation – user iterate it

  • Helm – templating engine

  • API Gateway

Front End

  • Kendo library and components

  • Angular Components

User stories

  • What level of detail is important for user stories

  • What is seen as valid acceptance criteria in user stories

  • What level of overview is appropriate for user stories

Action Points

  • No labels