...
The higher level of requirements include business, architectural and stakeholder/user requirements. There are also some transitional requirements that are only relevant during the implementation of the system. On the base of identified high-level features or requirements, the detailed requirements are defined. TheSome of them are the consequence of system's functions, services and operational constraints, while others are pertaining to the the application domain.
Functional requirement defines a specific behavior or function (what the system does; not how - in terms of implementation, quality, or performance).
...
- Performance, availability, stability, load capacity, efficiency, effectiveness, scalability, response time
- Reliability, robustness, fault tolerance, resilience, recoverability;
- Privacy, security, safety;
- Configuratability, supportability, operability, maintainability, modifiability, extensibility;
- Testability, compliance, certification;
- Usability, accessibility, localization, internationalization, documentation;
- Compatibility, deployability, interoperability, portability, deployability, reusability.
The requirements specification is an explicit set of requirements to be satisfied by the system, and is therefore usually produced quite early in its development. Such a specification may be a direct input for testing process, as it lays out all requirements that were, hopefully, addressed during the system development. Alternatively, the requirements that are directly associated with testing can be formulated, without the prior access to the requirements produced during development.
...
The relationship between the requirements/features and test cases is summarised in the Traceability Matrix, which is usually placed in a separate document that is updated with the evolution of the requirements and test design specification, but also refinement of individual test cases.
Feature Pass/Fail Criteria
This specifies the criteria to be used to determine whether the feature or a group of features has passed or failed, on the base of results of individual test cases.
Test Case Specification
It enables both forward and backward traceability, as it simplifies how the test cases need to be modified upon the change of requirements, and vice versa. It is used to verify whether all the requirements have corresponding test cases, and to identify for which requirement(s) a particular test case has been written for. The Traceability Matrix is a table where requirements and test cases are paired, thus ensuring their mutual association and coverage. Since there are always more test cases than requirements, the requirements are placed in columns, and tests cases in rows.
Feature Pass/Fail Criteria
This specifies the criteria to be used to determine whether the feature or a group of features has passed or failed, on the base of results of individual test cases.
Test Case Specification
The Test Case The Test Case is a specification of criteria that need to be met in order to consider some system feature, set of features or Use Case as working. It is the smallest unit of testing and is sometimes colloquially referred as Test. It should include a description of the functionality to be tested, and the preparation required to ensure that the test can be conducted. A single test case is sometimes associated with several requirements. It may be partially or fully automated.
...
The Test Script is a sequence for instructions that need to be carried out on the tested system in order to execute a test case, or test a part of system functionality. These instructions may be given in the form suitable for manual testing or, in automated testing, as short programs written in a scripting or general purpose programming language. For software systems or applications, there are test tools and frameworks that allow specification and continuous or repeatable execution of prepared automated tests.Traceability Matrix is a table or standalone document matching Requirements and Test Cases, thus ensuring their mutual association and coverage. It enables both forward and backward traceability, as it simplifies how the test cases need to be modified upon the change of requirements, and vice versa. It is used to verify whether all the requirements have corresponding test cases, and to identify for which requirement(s) a particular test case has been written for. Columns REQS, rows Tests Cases.
Test Data Requirements
Test Data Report
...