I have doubts regarding the process of collecting customer expectations and turning then into a functional document that we both can follow up to measure if the project reaches expectations.
I have a rough idea in this regard - such as: 1 - The document should specify the different pages and their content 2 - The document should specify what actions the user can do in them 3 - The document should specify what sort of behavior the project should have when facing errors
But I am not sure about this.
Any help, tutorials, videos, books or whatever related will be very appreciated.
Update My client asked for a website and sent a PDF with a design of what he wants. The design showed some parameters from where I could extract the database requirements and the approximate logic I would have to build. There are even pages that do not appear in such document, like the admin section which they obviously need.
My question is about a document, I believe it's called functional document, that would be build before starting to create the software. In that document there should be specifications regarding:
- Database entities
2.1. - How they relate to each other
2.2. - Parameter validation (min length, max length, Names without non-alphabetic characters, etc)
- Application pages
2.1 - Content
2.2 - Actions