A specification should describe how an application does what?

A specification serves as a detailed document that outlines the intended behaviors and functionalities of an application. Describing how an application performs its defined tasks is crucial because it provides clarity on the expected operations and workflows within the system. This ensures that developers, testers, and stakeholders understand the specific tasks the application is designed to execute, which contributes to accurate implementation and validation.

By focusing on how tasks are performed, the specification enables teams to establish a common understanding of the application's operations, assess performance criteria, and identify any potential gaps in functionality during development. Additionally, addressing how an application performs its tasks allows for better planning for maintenance and enhancements in the future, as it provides a baseline for current capabilities.

The other options, while related, do not capture the primary essence of a specification in the same direct manner. For instance, processes for user feedback, business objectives, and functional requirements are important aspects of the overall development process but are secondary to the specific task execution that the specification primarily aims to describe.