In our guide we will describe a step-by-step process of preparing technical documentation that will allow you to create a “skeleton” for the project based on the user interface. We will also focus on the necessary minimum of online documents which the team members can rely during the development and testing.
Questions that we will try to answer in this guide:
- How to expand the project documentation so that it is easier for the developer to prepare the project structure by himself or herself?
- How to organize team interaction on the basis of a single technical documentation?
- How to use the technical documentation as a checklist?
Our guide is aimed at a wide range of mobile application developers and software engineers. In general, the described approach, with small modifications, can be applied for software design of any classes of applications with a user interface: web, desktop, mobile and embedded. However, it can be redundant for small projects (less than 10 screens), as it was created for large applications (from 40 screens).
We really hope that the approach described in the guide will allow you and your colleagues to speed up the release of quality products due to more efficient work with documentation.
Here is a guide: https://books.binwell.com/software-design-of-mobile-applications
We’ll be happy to get a feedback from you!