## 1 Introduction
In this study, the failure mode and effects analysis (FMEA) risk-assessment method will be used. However, the FMEA method has some disadvantages. In the classical FMEA method, risks are expressed with net values, and uncertain values are not taken into account [8]. In addition, in classical FMEA, risks with various combinations of P, S, and D may give the same RPN value, but they may actually be risks that should be evaluated quite differently. For example, in a case where the P, S, and D values of two different risks are (4, 3, 1) and (1, 3, 4), respectively, the RPNs are the same, but they should actually be evaluated very differently [9]. This is only possible with a more detailed analysis of P, S, or D. In addition, another disadvantage is that the relative importance of the risk components is assumed to be the same in FMEA and does not take into account the assumption that risk components may have different importance for the experts performing the assessment [8; 9]. In this study, a new risk-assessment approach is proposed in which the severity component, which is one of the components of the classical FMEA method, is divided into five sub-severity components (severity on time, severity on quality, severity on cost, severity on solvability, and severity on usability) when evaluating possible project software risks. The new approach aims to avoid the disadvantage of classical risk-assessment methodologies in assessing the severity of all risks in the same way/type. In addition, since the sub-severity components used in the proposed model cannot have the same weight on the software project, the sub-severity components were weighted with the fuzzy SWARA (step-wise weight assessment ratio analysis) method, one of the multi-criteria decision-making (MCDM) techniques. The basic scientific contributions aimed to be provided by this study:* The severity component of the FMEA method is insufficient for evaluating different impact dimensions while evaluating the risks of projects. In this study, a model was developed to evaluate different types of severity on the project. * In addition, there are few studies that describe and evaluate software development test-process risks. The study also aimed to make significant contributions to the literature in terms of including a case study in which the risks of the defense industry project-development test process are evaluated. There are studies where MCDM techniques are used together with the FMEA technique. For example, [PERSON] et al. [10] weighted the FMEA risk-assessment components with SWARA in light of the opinions of different experts. [PERSON] et al. [11] accepted that the classical FMEA risk-assessment components cannot have the same weight and weighted the components with BMW. [PERSON] and [PERSON] [12] added two new components to the FMEA components, expected cost and time, in their study and weighted all the components with MCDM methods and fuzzy set help. Although there are relatively recent studies in the literature, no study has been found that analyzes the FMEA risk-assessment components in such detail. In this study, the severity component of the risk-assessment components was divided into five subcomponents, and the effect of the risk was analyzed in detail in every aspect. The study proposes a new weighted FMEA model in which the severity component is detailed to prioritize the most recurring errors in software testing processes according to their severity on the project-development testing process for the defense industry. Although defense-industry data were used as an application example in the study, the model can also be used to evaluate risks in different projects in different sectors. The weighted FMEA model can be used for a more precise analysis of the severity in all projects where risk assessment will be carried out with classical FMEA. Additionally, the remaining parts of the article are as follows. The literature survey is included in Section 2. The methodology used in the research is explained in Section 3.