## 4 Evaluation
### Application Evaluation
#### 4.4.1 Input Success Criteria  
Success Criterion SC-1: Processability of Interdisciplinary Requirements  
Investigation as to whether requirements from different disciplines can be evaluated is based on the interdisciplinary requirements set of the articulated-arm robot (cf. Section 2), which also includes different specification levels. SC-1 is considered fulfilled if all steps of the workflow (cf. Section 3.4) can be carried out without restriction. Evaluation results: The application of the method for the requirement set of the articulated-arm robot was carried out by means of the software prototype without errors. This was also confirmed by pilot users from the industry. Since the dependency analysis is data-based, the performance parameters were used to proof correct execution. Here, it was shown that due to good performance (cf. Section 3.2.1 and SC-4) a correct execution between requirements of the same and different disciplines can be assumed. The performance parameters also lead to the assumption that the analysis is carried out correctly for the analysis of requirements of different specification levels. Validation result: SC-1 is fulfilled. Success Criterion SC-2: Processability of High Number of Requirements  
The processability of a high number of requirements is tested in two steps. First, it was determined for which step the number of requirements influences feasibility. In this case, required computing power for dependency analysis has to be tested. The other steps are performed manually or based on the PageRank, which is proven to work efficiently for large datasets [63; 64]. Therefore, no limitation of the feasibility is to be expected. The increasing application effort for manual activities is evaluated separately in the context of SC-12. In the second step, the dependency analysis was tested. For this purpose, the computation time for a pair of requirements was determined. This is the key parameter, since all requirement pairs are analyzed successively and computation time can be determined mathematically for each size of requirement sets. The validity of calculation was tested ex perimentally and confirmed for requirement sets with 150, 250, 500 and 1,500 requirements. The computation time for each pair of requirements was determined for two representative computing capacities: 16 GB RAM/i7 CPU (regular laptop; Lenovo ThinkPad) and 13 GB RAM/P100 GPU (high-performance cloud server; Google Colab) [75]. SC-2 is considered fulfilled if the computation time of the dependency analysis does not exceed a threshold of 5 h. The threshold was defined by asking industry experts at which runtime the feasibility is considered limited [workshop W6]. Evaluation results: The computing time for the dependency analysis is 2 s (regular laptop) or 0.001 s (high-performance cloud server) per pair of requirements. For a regular laptop, up to 95 requirements are within the time limit. Using a cloud server, up to 4250 requests can be processed within 5 h (cf. Figure 16). Since very large request sets can only be processed if sufficient computing power is available, the success criteria is rated as partly fulfilled. Validation result: SC-2 is partly fulfilled. Success Criterion SC-3: Processability of Regular Form of Documentation  
For investigation of processability of natural language documentation form the requirements set of the articulated robot arm is used. The requirements set is suitable as a data basis, since all requirements have a natural language description text in German. SC-3 is considered fulfilled if the requirement can be imported, processed and exported correctly. Evaluation results: Correct functionality of import and export was manually verified by analyzing the database storage of the software prototype (import) or correct representation in the output format (.csv) (export). With regard to processing, the focus is on the dependency analysis, since the requirement description is only used for this step. Correct functioning and plausibility of the results were manually checked in the program code.