General

This chapter talks about data side of projects: describes the existing ones and explain how to proceed when creating a new one.

How to proceed when starting a new project

  1. Inform the Data team about new need - creation of a new feature, new locale or a new project.

  2. Provide a data sample from the Business. Please note, every changes of format (new informations, additional files, new order) needs to communicated to the Data team as the analysis and connector development depends on file structure.

  3. Data team informs Lizeo about new project to come - need of new export rules creation and development of the importer (Lizeo needs to be informed at least a month before the start new project).

  4. Data team analyse the structure of the data sample provided by Business.

  5. If the existing data model cannot be reused, Data team creates a new Data Model.

  6. Based on Data Model, Data team creates its specifications. -> Data structure and content can influence the design and some key structuration needs to be discussed with FA, back end team and Project Owners.

  7. Business provides full database.

  8. Based on the database, data model and specifications Lizeo develops the importer and pushes data to Datafeed/Datastream.

  9. Data team tests if all the information was received without any errors.

  10. If tests were successful, developers can start working on a proper data feed.

This is the first step of creating a new project, that is follow by:

  • design creation,

  • Tyre Selector development, if needed -> Tyredating needs to be warn in advance and the ticket needs to be created via tsu@tyredating.zendesk.com. All the information about how to create a TSU ticket can be found here (please note! for new project, when its requesting the development of the new TSU project/algorithm, this step can be long and needs to be prioritized with Tyredating).

Last updated

Was this helpful?