{"id":11003,"date":"2022-07-18T13:59:05","date_gmt":"2022-07-18T11:59:05","guid":{"rendered":"https:\/\/sxe-consulting.com\/?p=11003"},"modified":"2024-10-08T14:46:32","modified_gmt":"2024-10-08T12:46:32","slug":"tout-ce-que-vous-devez-savoir-avant-decrire-un-cahier-des-charges-technique","status":"publish","type":"post","link":"https:\/\/sxe-consulting.com\/en\/tout-ce-que-vous-devez-savoir-avant-decrire-un-cahier-des-charges-technique\/","title":{"rendered":"Everything you need to know before writing a technical specifications document"},"content":{"rendered":"

Qu’est ce qu’un cahier des charges<\/em><\/strong><\/p>\n

It is a structured, formal document that lists all the data required for the completion of a project, whatever the field concerned.<\/p>\n

It is the reference document for all those involved in developing the project, whether it is used internally by the company\u2019s teams or externally by the chosen service provider.<\/p>\n

Particularly in the context of a call for tenders, the specifications document is a contractual document. It allows the client to define the selection criteria for the project manager.<\/p>\n

Functional specifications and technical specifications: what is the difference?<\/em><\/strong><\/p>\n

It is necessary to distinguish between 2 types of specifications document:<\/p>\n

The functional specifications document<\/strong>. It defines the broad outlines of the project. It specifies the company\u2019s needs (in terms of functionalities) that the proposed solution must meet.<\/p>\n

The technical specifications document<\/strong>. It details the constraints and technical specificities required to meet the functional needs. It also specifies the various constraints surrounding the project.
\nIn practice, the technical specifications and the functional specifications are often combined into a single document.<\/p>\n

Good to know <\/u>:<\/p>\n

since February 2013, the European standard EN 16 271 has defined the structure to adopt and the sections to include when drafting functional specifications.<\/p>\n

Why write a specifications document?<\/em><\/strong><\/p>\n

For a project manager, the specifications document is the first step that must not be overlooked in order to ensure success<\/strong>. But it is also a valuable document for every stakeholder.<\/p>\n

Indeed, the specifications document makes it possible to:<\/p>\n

Facilitate the internal and external management of the project <\/strong>and save time for all the parties involved.
\nGuarantee the project promoter\/owner that their expectations will be met.
\nProvide the client\/supplier\/service provider with a means of understanding the needs.
\nLimit financial risks since it sets a budgetary framework.<\/p>\n

Writing a specifications document: the information to provide <\/em><\/strong><\/p>\n

A technical specifications document may be only one part of the overall specifications.<\/p>\n

Content of a specifications document <\/strong><\/p>\n

Depending on the nature of the project, the precise content of the specifications document will differ. However, the structure and sections are common to all. Here are the main elements to include when drafting a specifications document:\u00a0<\/strong><\/p>\n

Present the company and the context<\/strong>: internal teams involved, targets. . .<\/p>\n

Detail the objectives <\/strong>(financial, commercial. . . ) and the expected results.<\/p>\n

Determine the needs <\/strong>to be met, the expected functionalities and the technical constraints of the project.
\nSpecify the planned budget<\/strong>.
\nSet deadlines <\/strong>(completion, delivery. . . ) to allow the various stakeholders to plan their work accordingly.<\/p>\n

Focusing on drafting a technical specifications document<\/p>\n

Whatever the type of project, a technical specifications document must:<\/u><\/p>\n