In the specification phase, referring to the list of requirements, it is documented how the requirements in the system are met or implemented in concrete terms, with three different phases:
Functional Specification (FS)
For commercially available products, the product specification is the responsibility of the manufacturer and manufacturer documentation should be available. If there is no appropriate documentation because the specifications may consist of many individual documents (multiple software components, no accumulated capture of specifications on successive versions of the software), it may make sense to summarize them in a compact customer document, with reference to the individual documentation.
Configuration Specification (CS)
Here you define the configuration of the application required for your business purposes based on your requirements (for example, Audit Trail Settings, Electronic Signature, User Administration, Authorization Concept).
Design Specification (CS)
Here you define the design of the technical infrastructure for your system, i.e. computer hardware, software, network, data backup concept, but also authorizations in the network. This phase is ultimately the basis and prescription for installing the system.
Design Review (DR)
This phase is completed by a Design Review, in which a list and comparison of all specifications is compiled and reviewed with the project team.
After completion of these phases, the system should be set up and the test cases developed (valley point in the V model). For the beginning of the test phase, a test plan should be drawn up, which shows the procedure and strategy of the test phase. Measures in the form of test cases, procedures, technical controls or staff training should be established based on a risk analysis taking into account the risk to humans, product and data. Most of the time you will take into account business-related risks. All test cases are already specified in the test plan.