Skip to main content

General Description of the Software Product: Intended Purpose & Versions

The first part of your Technical Documentation, as outlined in Annex VII, point 1, is a general description of your software product. This section sets the stage, providing a high-level overview for anyone, like a market surveillance authority, reviewing your file.

Intended Purpose​

You must clearly state your software's intended purpose. This should align with what you communicate to users in promotional materials and instructions.

  • For a game, this could be "An entertainment software product for mobile devices, designed for single-player puzzle-solving."
  • For an app, "A utility application for managing personal tasks and calendars on desktop operating systems." This is crucial because your cybersecurity risk assessment is based on this intended use (Article 13, Paragraph 3).

Software Versions​

Your documentation must specify the versions of the software that it covers. Software evolves rapidly, and security measures can change between versions.

  • Best Practice: Be specific. For example, "This documentation applies to 'PixelPioneer Photo Editor' versions 2.5.0 through 2.5.x."
  • Updates: When you release a new major version or make a substantial modification, you will need to update your technical documentation and be clear about which versions the new documentation applies to.

Other Identifying Information​

Annex VII also requires other elements like "photographs or illustrations". For intangible software, this can be interpreted as key screenshots of the user interface or high-level architecture diagrams that help identify the product and its features. A copy of the user instructions (from Annex II) is also required here.

Key Takeway​

Start your Technical Documentation with a clear description of your software, including its specific intended purpose and the exact software versions covered by the document. This context is foundational for the entire compliance file.