π Project Summaryο
π Introductionο
This document outlines my general understanding of the project without delving into its technical details. The information is sourced from the projectβs Technical Specification and from the meeting held on December 13, 2023.
π― Project Goalsο
The aim of this project is to create a publicly accessible portal that displays all available plastic waste initiatives. In addition to describing initiatives, the portal provides access to an inventory of plastic waste. The data for the portal are prepared by the Secretariat from materials provided by regional and national stakeholders. The benefit of the portal is that it consolidates data from many sources and offers interactive reports, which can be used, for example, to make high-level decisions in the field of plastic waste management.
π Main Tasksο
Analyze existing data on initiatives and inventory. π
Refine the current scheme for initiatives based on the analysis of existing data. π οΈ
Develop a new scheme for inventory based on the analysis of existing data. π
Create an API for reading from the database. π
Upload external data:
Develop programs to upload data from external sources into the internal database with the data scheme created in the previous step. For example, program can create Excel file which can be directly imported to CRM database. πΎ
For data sources which provides Web API we need investigate how to use it directly from our Portal, without storing the data in our database. π
Develop the front end of the portal for searching and generating reports on initiatives and inventory. Data is read using the API created earlier. π»
π¨ Risksο
Diversity of External Data Schemas. The primary uncertainty lies in the variety of external data schemas and their representation in the database being developed. Designing a data schema that supports all possible data formats is fundamental and impacts all further project development, as changes in the schema lead to cascading changes throughout the project.
Likelihood: High, given the range of data sources. π
Impact: Moderate to High, as it can lead to delays and increased development time. β°
Mitigation Strategy: Develop a flexible data schema that can accommodate a wide range of data formats. Regularly review and update this schema in response to new data types π‘οΈ.
Evolving Technical Specifications. The technical specification of the project will be refined as questions, such as those about the data schema, are clarified. For example, the appearance and functionality of portal elements depend on the data schema. Our task is to keep this document up-to-date.
Likelihood: Moderate, as the project progresses π.
Impact: Moderate, as changes can affect project timelines and resource allocation. π
Mitigation Strategy: Implement an agile project management approach, allowing for flexibility in adjusting to specification changes .πββοΈπ¨