What level of detailing is sufficient for software architecture documentation?
Developing software with no documentation is not uncommon. It could be that the bulk of software is developed like that. I have seen even the significantly large systems and product suites with no documentation about architecture, design or other technical aspects. Even though the documentation process could be seen as a burden by some developers, documentation provides multiple benefits to development teams. How to determine what level of detailing is sufficient for software architecture? Put in another way, at what level should we stop documenting?