Linguistic standardization of requirement specifications and functional specifications

Risk assessments, design plans and standardized protocols: These are the documents that first come to mind when thinking of internal documentation. Documents for internal company use, which must be provided mandatorily by law or due to internal process requirements, but which do not usually leave the company. Quite different on the other hand are requirement specifications and functional specifications: They are also typical documents of development processes for internal documentation, but are created to cross the company’s borders and coordinate the cooperation with external partners. And that puts these documents in the sphere of technical writing.

Text by Johannes Dreikorn

Inhaltsübersicht

Linguistic standardization of requirement specifications and functional specifications

For several years, technical writers have called for early involvement in the development process. Meanwhile, these requests are bearing fruit in all companies that have recognized the value of technical writers as "advocates of users." But as usual, it is also seen now that new tasks entail a new understanding of the role. Because, once developers have recognized the strengths of technical editors, the call for support outside traditional product documentation will become louder.

Two types of documents where technical writers can exploit their strengths fully are requirement specifications and functional specifications. They are at the beginning of the development process and can be understood as a kind of documentation about what should be done from the client view (the requirement specification) or what the contractor plans to do (the functional specification).

Core element of ...