Typical pattern of technical specifications for the development of the site
OFFTOP: I want to express my gratitude to everyone who added to my previous post and karma, this allowed me to invite some more good people to Habr.
In many studios there is no uniform format TZ, we also did not have it. After reviewing many different formats and GOSTs, we chose the most significant points and developed a typical TK template for our company .
Perhaps this will be useful to other studios as well. if we all work according to the same standards, the advantages are obvious both for the studios and for the customers.
')
The structure of the technical specifications:
1. Terms used in the terms of reference
2. General provisions
2.1. Name of the site
2.2. Name of enterprises (associations) of the developer and the customer (user) of the site and their details
2.3. The list of documents on the basis of which the site is created
2.4. The composition and content of work on the creation of the system
2.5. The order of registration and presentation to the customer of the results of work on the site
3. Purpose and purpose of the site
3.1. The purpose of the site
3.2. Problems solved by the site
4. Site and software requirements
4.1. Site software requirements
4.2. General requirements for the design and layout of pages
4.3. Requirements for the number and qualifications of personnel serving the site
4.4. Administration System Requirements
5. Site structure
6. Language versions of the site
7. User groups
8. Site Design
9. Site Navigation
9.1. Main navigation menu
9.2. Additional site navigation
10. Description of site pages
10.1. Description of static pages
10.2. Description of dynamic pages
11. Site functionality
12. Content and site content
12.1. The format of the provision of materials for the site
13. Additional information
14. The order of control and acceptance of work
15. Details and signatures of the parties
PS This TK does not pretend to a single format, it is not a dogma. We will be happy to take into account all the comments and remarks habrayuzerov.
Download TK template in .doc format
In many studios there is no uniform format TZ, we also did not have it. After reviewing many different formats and GOSTs, we chose the most significant points and developed a typical TK template for our company .
Perhaps this will be useful to other studios as well. if we all work according to the same standards, the advantages are obvious both for the studios and for the customers.
')
The structure of the technical specifications:
1. Terms used in the terms of reference
2. General provisions
2.1. Name of the site
2.2. Name of enterprises (associations) of the developer and the customer (user) of the site and their details
2.3. The list of documents on the basis of which the site is created
2.4. The composition and content of work on the creation of the system
2.5. The order of registration and presentation to the customer of the results of work on the site
3. Purpose and purpose of the site
3.1. The purpose of the site
3.2. Problems solved by the site
4. Site and software requirements
4.1. Site software requirements
4.2. General requirements for the design and layout of pages
4.3. Requirements for the number and qualifications of personnel serving the site
4.4. Administration System Requirements
5. Site structure
6. Language versions of the site
7. User groups
8. Site Design
9. Site Navigation
9.1. Main navigation menu
9.2. Additional site navigation
10. Description of site pages
10.1. Description of static pages
10.2. Description of dynamic pages
11. Site functionality
12. Content and site content
12.1. The format of the provision of materials for the site
13. Additional information
14. The order of control and acceptance of work
15. Details and signatures of the parties
PS This TK does not pretend to a single format, it is not a dogma. We will be happy to take into account all the comments and remarks habrayuzerov.
Download TK template in .doc formatSource: https://habr.com/ru/post/84422/
All Articles