Project Documents for Development Pattern
1) Customer project description
2) Project backlog (better in price-list table with time and $)
3) Tech Task Specification
Tech Task Specification Stucture:
1) MAIN Requirements (Back-end)
2) Framework, Core Classes Requirements (Back-end)
3) Admin Panel (Back-end)
4) DataBase (Back-end)
5) Every Page Description:
HTML+CSS Design (Front-End)
Load data from PHP+DataBase and Logic (Back-End)
Dynamic JavaScripts and AJAX: Front-End Logic / Back-End Logic (Front-End/Back-end)
Content Management
Advanced features: SEO, Multi Languages, Users etc.
After all will be done: 2 NEW Documents: New Updates and Bug Fixes.
And QA Test Cases document
Parent (Базовый синтез) Частью чего может быть этот объект?
Deeper then text, simply than code
- Keep hierarchical structure
- Separate text blocks (paragraphs)
- Briefly and concisely writing
- соблюдать иерархическую структуру
- явно отделать разные по смыслу блоки (абзацы)
- писать максимально
Wisdom Tree
Project Documents for Development Pattern
2) Project backlog (better in price-list table with time and $)
3) Tech Task Specification
Tech Task Specification Stucture:
1) MAIN Requirements (Back-end)
2) Framework, Core Classes Requirements (Back-end)
3) Admin Panel (Back-end)
4) DataBase (Back-end)
5) Every Page Description:
HTML+CSS Design (Front-End)
Load data from PHP+DataBase and Logic (Back-End)
Dynamic JavaScripts and AJAX: Front-End Logic / Back-End Logic (Front-End/Back-end)
Content Management
Advanced features: SEO, Multi Languages, Users etc.
After all will be done: 2 NEW Documents: New Updates and Bug Fixes.
And QA Test Cases document
Этот объект часть других / Parent
Make detail specification