Hello all!
As I promised in my first blog post (Smart Exhibit: Blog #1: Let's start!), I will write each week about the latest updates in the development of my project, Smart Exhibit. This week I chose, installed (what had to be installed and what I didn't have already installed) and set up the software tools which I will use. Here is a list of my choices:
- For storing and versioning my code (but also for other files (e.g. designs)), I will use a GitHub repository: https://github.com/alexandru-cohal/SmartExhibit
- I will use the development branch for the development of different features and I will merge it with the master branch when a stable version will be obtained.
- For the documentation, I will use the GitHub Wiki which is connected to the repository and is available here: https://github.com/alexandru-cohal/SmartExhibit/wiki .
- As a Git client on my computer (I am using Windows as OS), I will use Sourcetree due to its nice GUI and easiness to handle the repository.
- For the code development, I will use Arduino IDE. I will start with the version 2.0.0 which even if it still in the beta status, I am taking the risk to use it due to its newest features (I am very happy especially about the autocompletion). If I will find some issues while using it, I will happily report them in order to improve it. If I will not get along with this version for various reasons (which I highly doubt), I will return to version 1.8.13 which I used before and I know that it works fine.
- For tracking the tasks of this project, I will use a Kanban board within Trello: https://trello.com/b/qwcDuQMy/smartexhibit. I will split my work in sprints of 1 week long. At the end of each sprint I will evaluate the tasks not finished and the ones not started yet (from the respective sprint) and I will make the planning for the next sprint, considering also the tasks from the general backlog. Each sprint will start on Monday and will finish on the following Sunday. Also, at the end on each sprint I will write a blog post summarizing the latest updates from the respective sprint.
- For unit testing (I will try to do as much unit testing as possible
), I will use the AUnit Testing Framework: https://www.arduino.cc/reference/en/libraries/aunit/ .
- For drawing schematics, I will use Fritzing. I never used it before but the visual part looks interesting, so I will try it. If I will not get along with it, I will switch to the good old Eagle
- For drawing different diagrams (e.g. architecture), I will use diagrams.net (formerly draw.io) https://app.diagrams.net/.