## 3 The Framework
### Classification of Requirements Package  
In order to facilitate the requirements analysis, the proposal is to divide the requirements into three general packages representing different levels, as it is shown in Figure 3 and described below.  
1. Application essential requirements from the integrator. The requirements contained in the initial specification are classified into different non-functional groups, such as operability, serviceability, reliability, comfort, special, and standards/regulations/policies requirements packages. The satisfaction of these requirements ensures that the motor correct performance in the system application.
2. Technical derived requirements. These are derived or copied from the essential requirements into the different disciplines: mechanical, electrical, control, manufacturing engineering, also additional requirements and cross-domain objectives. The satisfaction of these requirements ensures the correct design and performance of the motor during the development process and the system application integration tests.
3. Specific-domain derived requirements. These are derived or copied from the technical derived requirements into the different domains that are involved in the motor development; herein emphasizing: structural, electromagnetic, vibro-acoustics, insulation, thermal, and electromagnetic compatibility (EMC). The satisfaction of these requirements ensures the correct design and performance of the motor during the development process.  
Figure 2: Use case diagram of stakeholders in the specification context.  
Table 1 shows examples of requirements that fit on each group. However, the developer (experts in their field) should decide this internal classification. The essential requirements may be found in compound form in the initial requirements specifications. If this is the case, to better define them, these ought to be decomposed into more requirements. Some may be implicit; nevertheless, if an analysis is carried out, these should be categorized as derived and put inside one of the technical derived disciplines group. Regarding the domain-specific requirements, these are the ones that each domain need to design its respective partition. Some requirements may only be copied from a higher-level group.  
\begin{table}
\begin{tabular}{p{113.8 pt} p{113.8 pt}} \hline
**Package** & **Requirements Examples** \\ \hline _Application Essential Requirements_ & \\ \hline \multirow{2}{*}{Operability} & Power sources, ratings, torque, speed, efficiency, service factor, duty cycle, environmental conditions, insulation, mounting, frame size. \\ \hline \multirow{2}{*}{Servicesability} & Requirements related to ease of maintenance, ease of recycling, monitoring sensors (e.g., resistance temperature detectors (RTDs)). \\ \hline \multirow{2}{*}{Comfort} & Noise and Vibrations, dynamic smoothness control, continuous operation smoothness. \\ \cline{2-2} Reliability & Life expectancy, permissible design or manufacturing tolerances, lead times, fault tolerances, tests. \\ \hline \multirow{2}{*}{Special} & Transportation, training, mounting, assembly (e.g., an stic), commissioning. \\ \cline{2-2} Regulations/standards/policies & Regulations, standards or policies that the motor must accomplish or follow. \\ \