How should we propose architecture design?
For past few months, Tier IV has been conducting a new architecture design for Autonomous Driving stack along with feasibility study of the designed architecture. We would like to feedback what we have came up with into Autoware.Auto, and we want to know what is the best way to proceed this architecture proposal.
For the architecture, please see this PDF from the the last TSC meeting minutes and this repository for the details. Note that the documents in the repository are still way in progress, and is planned to be finished by the end of April.
The questions are:
- Are there any templates in Autoware.Auto for design documents? Currently, we are planning to describe Use Case, Requirements, role of the module, final input/outputs of each modules.
- Where should we create MR? there seems to be design folder, but there are also
design
folder in src folder as well, e.g. in Localization. Where is good place to create MR? - I have a concern that assumed use cases of our proposal is different from current Autoware.Auto. Our proposal aims to achieve autonomous driving in public urban/suburban road, whereas current Autoware.Auto sets milestones to achieve AVP. We think our architecture is also feasible for AVP, but it includes unnecessary components for current Autoware.Auto milestone. Therefore, I think we should continue with current architecture until the demo is over, but I think it is worth starting discussion for future Architecture from now. However, I am worried that it might be confusing for some developers if there are MRs for architecture that that not does not comply with current development for the demo.
Any comments and suggestions are appreciated.
Edited by mitsudome-r