Functional Requirement Document creation about openflutterecommerceapp HOT 3 CLOSED

I was thinking about a more detailed explanation of use cases. The functional requirement document description is here.
It is a very detailed document usually. I do not think we need to make it that deep. But what we can do is a description of use-cases the way we see it so by the time we start the actual development we have a clear understanding of how it should be. It is a common practice and helps get the tasks done with fewer iterations.

The detailed explanation of functionality implementation may include the UML diagrams like this one.

Since we have WooCommerce API described we know what is on the backend and we have UI that shows us what a user can click we can make a high-level overview of the list of all use cases and what should happen. That will represent the task list for implementation that each on of us can take. If we find a missing use case we just add it and add the task itself as an issue on Github.

To make a long story short, I think we can start with a complete list of use-cases we want to implement so everybody can add a description and vision of what should happen within that use-case. The use cases will be group by features (products, product rating, cart, etc).

from openflutterecommerceapp.

If we can add a flow diagram of Application Layer in this document like the one that is in this blog, then it would be very helpful in visually understanding the layers and purpose of each layer of the app.

from openflutterecommerceapp.

https://medium.com/@openflutterproject/open-flutter-project-e-commerce-app-use-cases-and-features-6b7414a6e708 use-case description for the app.

from openflutterecommerceapp.