The development of an iTV application can be organised using a classic approach (based on documents) or using an agile method (e.g. based on a backlog). The classic method fits often better to an iTV format for a single event with fixed time of broadcasting (e.g. live). The agile method could be beneficial for ongoing iTV formats (e.g. in relation to a TV series). The content of the specifications are comparable for both methods.

Within the classic framework of an iTV application, for instance, two important documents could be used alongside the project plan. The "Rough concept" and "functional specification" (or requirement specification).

Rough concept: This is the result of the initial planning phase and is the decision-making basis for implementing or cancelling the project. The heart of the rough concept is the performance specification with the following points:

• Project goal
• Classification in the overall concept
• Central functions
• Project duration and milestones
• Parameters of the platform used
• Participating partners

If necessary, a feasibility study is also conducted:

• Technical feasibility
• Cost/benefit analysis
• User acceptance (with prototypes)
• Framework conditions (patents, laws, licences)

Functional specification: This is the central document for the analysis phase following the planning phase. It can be used as the contractual basis and comprises the following points:

• Precise description of the functions
• Dialogue description
• Exception and error cases
• Dynamic data
• Precise description of the system architecture
• iTV programme plan (e.g. playout timeframe, updates, synchronisation)
• Requirements for external quality (e.g. stability, performance, product documentation, useability, support)
• Requirements for internal quality (e.g. documented source code, changeability)

Other documents: All other documents can be used as in the conventional software projects.

• Graphic specification with all stipulations for graphic realisation
• Images and A/V files
• Test plan and test report for the system test
• Description of software design and implementation for the programmed application
• Release notes