You are working on a project that is integrating code from multiple development groups. There have been numerous integration problems, particularly regarding reliability, error recovery and transactional integrity. You are now responsible for planning the performance efficiency testing for this product. There Is a strong feeling among the development managers that some parts of the code are weaker than others and will tend to exhibit problems during the performance efficiency testing. To identify these problematic areas as soon as possible, which type of testing should you do?

Subject to testing is a software system (COTS) for Project Administration and Control (PACS). PACS is a multi-project system for controlling the project time, e.g., in terms of scheduling and tracking, and managing the productivity of projects, e.g., in terms of effort and deliverables. During various interviews with stakeholders the following information was gathered: • Using PACS is not business critical. There is no impact such as high financial losses or problems to the operational continuity of an organization. Its application is not critical since the software package does not support directly the operational, or the primary, business processes of an organization. It supports (project) management in the project planning and tracking process. Of course, it will be highly annoying for users if the system “goes down” from time to time. Although this does not have a high impact for the business process as a whole, the Mean Time Between Failures (MTBF) still needs to be at a good level to be successful in the market. • Users of PACS typically have an academic educational level, but have no prior experience with this particular type of project management software. The system will be used by a large number of users within an organization. • The system will be used on a regular basis, e.g., several times per day by project managers and several times per week by project employees. This means that the system will not be used very intensively, often only for some data input or an information request. Its usage is not considered to be very time-critical. • The data is recorded on-line and real-time. The system is expected to run in multiple hardware environments in various network environments. It is also expected that changes in the operational environments will happen in the upcoming period that also need to be supported. Based on the information provided by the stakeholder, which combination of non-functional quality characteristics should you propose to test as part of your test approach?

At which test level would performance efficiency testing most likely be performed?

A new system is being built to handle the message handling of financial transactions - this system is critical to the organization's finances. The code includes loops and decisions with several multiple conditions. The nature of the system means that tests are quite time-consuming to execute. Which of the following would be the BEST white box testing option for the new software?