What is a 'good' requirements specification for the site?

Site development begins with a competent technical reference (TOR). As a rule, the development of TK by specialists who have experience of similar work. If future site owner wants to try to make himself competent TK or control this process, you will not be amiss to know: What is a good specification for the site? From which point the sum of TK? What aspects should be covered in the specification for the site?In this article we will explain the benefits of a good specification for the site, as well as answer all the questions outlined above.

Measuring the success of the work done on the creation, optimization and promotion of the site, in other words, the quality of the final product depends on the conditions specified by the customer in the specifications. That is, as eventually earn a resource, it must be a customer. And not only represent, but also competently present his vision of the future site of TK. Case a web designer to achieve full compliance with the resulting products to customer requirements. On this basis, requirements specification is a very important process from which ultimately depends on the success or failure of the site.

How can make a competent technical requirements for manufacturing a web site?
First of all, you need to know that TK - just as important a document as a contract. The agreement regulates the organizational and financial relationship between the customer-performer, while TK - process and outcome of development.

For whom is meant TK? First and foremost, of course, for developers - programmers and designers of the project, but also, equally, for the customer. Ideally, the specification should be written to automatically answer all the questions that arise in all the aforesaid persons involved in the process.

Necessary sections of the literate specification.
A. Introduction. General information about the project:

1.1. For information about the customer and the artist with the obligatory indication of the responsible persons from each side, details of the contract or other document regulating their joint activities, issues of confidentiality, etc.
1.2. For information on the appointment of the project, its ultimate goals and objectives.Clearly-written and clearly thought that he wanted to see and what the customer expects from a finished product.
1.3. The audience of the project.First of all, you should specify the goals and objectives of potential users visiting the site, it is desirable to analyze their marketing, demographic and social data.
1.4. The definition and interpretation of the terms of the project.
Sub-paragraph is to prevent discrepancies in the multi-valued semantics of a term or expression, as well as in the case of penetration into the documentation is not very competent in technical matters of the superior manager.

Two. The boundaries of the project.

This section should be considered, so far without specifying which areas and to what extent will affect the project. It is important to make the data understandable only unambiguous way, and the internal content areas is extremely transparent so that everyone reading this section outlines imagine what the results will be achieved eventually. The most successful to describe this part of the TK is a genre script user relationship site that describes the overall functionality and interaction with the interface.

Three. The architecture and interface.

Under the architecture of the site means the information architecture that defines how it will look, and how it will work with the users of the site is under construction.Describe the information architecture best from top to bottom, from the large - to the small, of the total - in particular:

3.1. The structure of the website.

Clearer and easier to use - to perform as a site map, on a mandatory basis by numbering each page of the card.

For greater convenience and clarity:

3.1.1. Units have maps so that they did not merge with each other,
3.1.2. Use a readable font,
3.1.3. To build a page in one line. This will help the perception of levels of nesting,
3.1.4. Do not cross the lines of communication with each other, as in the drafting of functional circuits, such as
3.1.5. To avoid confusion in future use, not only to put a signature on the card itself as a whole, but on every single block it.

3.2.Stranitsy and templates that describe the interface.

Description of patterns do as follows:

3.2.1. Describes the list of templates, page types and their use
3.2.2. We describe a typical pattern and the basic building blocks of pages
3.2.3. Each template is included in the list displays the graphics package and is described.

3.3. List of content. The content of each page of the resource in the tablets.

The most time-consuming and thorough look at this stage of the site.

Includes:

3.3.1. Description of each page of the resource is formed and contains text, pictures, videos, etc.
3.3.2. Used for the page template (see Section 3.2.).

For greater clarity, it is recommended to perform in a table.

4. Description of the functional.

This is one of the most important sections of TK. When you write better and easier to follow the provisions of GOST 34.602-89, in detail, lucidly, and, most importantly, well-paints all the necessary items:

4.1. Description of the system as a whole, including the overall functionality of its constituent subsystems and modules
4.2. The relationship with each other subsystems and modules
4.3. A list of these subsystems and modules with a fairly detailed description of their operation,
4.4. A detailed description of the created or used for each module programs, etc.

Five. Requirements for the project.

This section also includes requirements for the project to the environment:

- To the system as a whole,
- To support staff,
- To ensure the reliability,
- The aesthetic,
- To protect against unauthorized access to project information
- The parameters of preservation of information in case of accidents,
- The diversity of software,
- The means of programming
- To provide information
- To ensure tehsredstvam,

- Other requirements dictated by the specific project.

6. Other terms and conditions.

Quite often while working on a project-specific issues arise and situations beyond the already approved and signed into law the technical tasks. An opportunity not to miss the sight of such a situation, as well as the sequence of actions to address it, and prescribed in this section.

Summary.

A good requirements specification can be called TK, which clearly spelled out in any action arising during the work on the site issue, including the sequence of actions in case of emergencies. Good terms of reference - a pledge that the Executive will make, and the customer gets exactly the product, which wished.