Requirements

We have already provided some application-specific elaboration of the idea of functionality, the equivalent of a set of high-level requirements:

• The system should specify the grammatical errors made by the writer in such a way that the end-user is able to correct them;
• The system should not signal an error where no such error is present;
• The system should be able to handle combinations of errors to some extent.

We have also provided the outline of a task model that makes clearer the parameters along which detailed understanding of these requirements may vary. In this section, we bring the task model and the high-level requirements statement together to form a detailed statement of requirements that will form the direct basis for testing and reporting.

It should be understood that the following illustrative discussion is at an extremely preliminary stage.

 
• Functionality requirement - part I
• Functionality requirement - part II
• Functionality requirement - part III
• Discussion