Here are the first three chapters of my arc42-based architecture documentation. Next time we are doing the architecture constrains and maybe the system scope. It is necessary if I want to make it right, but if you are bored, please wait for 2–3 posts, when we will start describing the system structure 🙂

Introduction and Goals

This project is an effort of establishing a development workflow via practical product development.

There are two main requirements for the project:

• The product should be a working and entertaining for a cat autonomous toy.
• Components, processes and libraries of the project must be developed to be reusable in other projects.

The project is based on the following principles:

• Architecture-oriented
  • Develop the right architecture using architectural best practices
• Result-oriented and minimalistic
  • Progress over perfection
• Integration-oriented
  • Reusing existing libraries, projects, etc. Minimum development of individual pieces
• Reusable in my other projects
  • It should be done automatically with a good architecture. But I want to make several special decisions to make the project easy to transfer to my another robotic project.

Quality Goals

Stakeholders