Confidently Practice Online with Free CTAL-TTA_v.4.0_UK_IE Exam Cram

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?

A product risk assessment has revealed the following product risks: • lack of usability requirements • security during on-line transactions • perceived performance of the system and response time from the user interface • a required availability of almost 100% To address the 4th risk, which of the following quality characteristics for technical testing should be part of the test approach?

Which of the following does NOT contribute to a more effective review preparation by the Technical Test Analyst?