Jasmine Sun

We decided to remove Docker from our stack because we realized that pipenv and npm are enough to manage our frontend and backend dependencies. We also found Docker a bit difficult to set up and it will take us another few hours to set up. Therefore, for time constraint, we will leave off Docker for now and only use pipenv and npm instead

Communication:

• We will use Slack for real-time text communication and use Zoom for virtual team meetings. Both communication tools have clean but powerful features (threads for Slack, share screen for Zoom) to make the team have effective conversations.

Testing:

• We will choose one testing framework for each frontend and backend. For the frontend, we will use Jest; for the backend, we will use Pytest. They both work well with the development stack, and our team has some previous knowledge of them. Additionally, we will use Postman for API testing to further simplify our work in writing test cases.

DevOps:

• For hosting, we will use Heroku because it is very simple to use and we can use their free student credits to reduce costs. We chose Github Action to be our CI/CD because it’s a fully managed service and can save a lot of time in setup. We will also use Docker to help manage dependencies and to test locally without breaking the local system.

Backend:

• Considering that our main app functionality involves data processing, we chose Python as the programming language because it offers many powerful math libraries for data-related tasks. We will use Flask for the server due to its good integration with Python. We will use a relational database because it has good performance and we are mostly dealing with CSV files that have a fixed structure. We originally chose SQLite, but after realizing the limitations of file-based databases, we decided to switch to PostgreSQL, which has better compatibility with our hosting service, Heroku.

Frontend:

• For our web app frontend, we decided to use TypeScript as our programming language because it supports all functionality of JavaScript and supports optional typing to the language, which can help us take advantage of OOP.
• We chose ReactJS as our frontend library because its state management would be very handy for our single-page app. React is also component-based, which can help us improve the modularity and extensibility of the project.
• Aside from the standard web technology HTML/CSS, we will useBootstrap to style UI components and make our web app responsive to different screen sizes.