<A function specification (FS) must contain the following sections (1-9). If no text is provided under a given section, a dash '-' should be inserted to indicate that the section is empty. Additional subsections can be added to the mandatory sections.>
Use this section if you want to summarize the document in a few sentences. Otherwise, remove the header.
This section should contain:
Example:
Rev | Sign | Feature | Description |
---|---|---|---|
PA1 | EH | MyMAIL | The xx description that describes the xx. |
This section should:
Example:
The purpose of this document is to give a detailed description of the MyMAIL application.
The document describes the interface, signalling procedures, messages and messages contents according to RFCs.
Example:
Main window | The main main window in mymail where the user can select mail and mailboxes. |
Example:
AC | Application Context |
APDU | Application Protocol Data Unit |
DP | Dialogue Portion |
Example:
Parameter | Description | Default value | Value range | Run time Configurable |
---|---|---|---|---|
Timer check of mail | The time for autochecking mail. | 0 | 0-86400 | Yes |
HOME | Home path. (readed at program start) | Empty | (String) | No |
This section should clearly specify all the capacities and limitations for each of the functions specified. Each topic should be stated under a separate bullet or a table entry, e.g.
This section should describe how the function is affected by possible faulty situations in the node and the corresponding recovery procedures.
This section should be a list, in alphabetical order of all documents referred to within the FS as well as any pertinent standards or other relevant system documentation, e.g., related FS's.