3、非功能性测试的软件测试生命周期
表二列出了非功能性测试的不同类型，并举出了属性的例子，同时简述了每一类的测试流程。参考一中有各类非功能性测试的定义。
在非功能性测试的生命周期中并没有引如新的阶段，但是每一个活动的范围都变广了以此来涵盖非功能性需求。并且，在相应的文档中也加进了刻画非功能性测试的特定章节。以下将说明为非功能性测试而在每个阶段中增加的活动：
测试计划：
| Category | Parameter | Criteria | Remarks |
| Performance | Traffic Capacity | X E | |
| Call setup time | X ms | ||
| CLI command acknowledge time | X s | ||
| Usability | Installation | Single command | |
| Portability | Target platform | X BTS | System testing will be completely done on the target platform |
| Volume | No. of subscribers | <= X | Minimum functionality testing to be done with 3000 subscribers |
| Call Duration | TBD | ||
| Call success rate | 99% with 1000 calls minimum | ||
| Stress | Call handling capacity | X BHCA | |
| Concurrent calls | X for 3 sector 1 carrier config. | Possible to simulate in the lab? | |
| X for 6 sector 1 carrier config. | |||
| Call rate growth | X calls per sec. | ||
| Efficiency | GLI2 Memory | <85% usage | Testing need to be done under stress. |
| MCC memory | <90% usage | ||
| GLI2 CPU | <80% usage | ||
| BCP | <90% usage | ||
| CMP | <95% usage | ||
| Recovery | System start-up time | <45 mins. With complete OMC download | |
| <30 mins. with no GLI code download | |||
| V5 comm. Switchover | X s | ||
| GLI Switch over | Time TBD |
Table 3: Non functional requirements for SCWiLL
X is used in place of actual values.
测试团队需要确定可应用于项目的非功能性需求的类型并把可测量的参数以及在SSTP中需要测试的需求文档化。它的输入可以来自需求说明书或者设计目标。测试团队则需要在复查过程中充当积极的角色，这样才能确保需求说明书中说清了非功能性需求并且它们能够通过测试，走查或者分析的方法来验证。在SSTP中，要确定那些可以被测试验证的需求。表三中列出Single Cell Will 项目的需求，下面的论述将以调用启动时间为例并且指出在测试的各个阶段要完成的工作。
