design document in software development
Dear Experts
While developing the application functional requirement is first step and convert the functional requirement to detailed design document with sub processes, my understanding is as following but would like to please help in adding or modifying
1. design document should have all possible use cases with flow
2. covers the expected outputs/results against each of the use cases
3. KPI’s reports
4. Integrations
experts, my first request is to correct about my understanding on the above and then please let me know does the test strategy comes under design document or it is separate document also does the security comes under design document or it comes under technical architecture /tech specifications, thanks in advance.
While developing the application functional requirement is first step and convert the functional requirement to detailed design document with sub processes, my understanding is as following but would like to please help in adding or modifying
1. design document should have all possible use cases with flow
2. covers the expected outputs/results against each of the use cases
3. KPI’s reports
4. Integrations
experts, my first request is to correct about my understanding on the above and then please let me know does the test strategy comes under design document or it is separate document also does the security comes under design document or it comes under technical architecture /tech specifications, thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.