China
Africa
Explore chapters and articles related to this topic
Static Testing the Logical Design
Published in William E. Lewis, David Dobbs, Gunasekaran Veerapillai, Software Testing and Continuous Quality Improvement, 2017
William E. Lewis, David Dobbs, Gunasekaran Veerapillai
System testing is a multifaceted test that evaluates the functionality, performance, and fit of the whole application. It demonstrates whether the system satisfies the original objectives. During the requirements phase, enough detail was not available to define these types of tests. The logical design provides a great deal more information with data and process models. The scope of testing and types of tests in the Test Approach and Strategy section (see Appendix E2, “System/Acceptance Test Plan”) can now be refined to include details concerning the types of system-level tests to be performed. Examples of system-level tests to measure the fitness of use include functional, performance, security, usability, and compatibility. The testing approach, logistics, and regression policy are refined in this section. The rest of the items in this section, such as the test facility, test procedures, test organization, test libraries, and test tools, are begun. Preliminary planning for the software configuration management elements, such as version and change control and configuration building, can begin. This includes acquiring a software configuration management tool if it does not already exist in the organization.
Software Reliability
Published in Jerry C. Whitaker, Electronic Systems Maintenance Handbook, 2017
System testing is defined as when the development team is in charge of testing the entire system from the point of view of the functions the software is supposed to fulfill. The validation process is completed when all tests required in the system test plan are satisfied. The development team will then produce a system description document.
Rough sets-based prediction model for increasing safety of thermal power plants
Published in Energy Sources, Part B: Economics, Planning, and Policy, 2019
Vladimir Brtka, Vesna Makitan, Ljiljana Radovanovic, Zoran Zivkovic, Oliver Momcilovic
FMEA is based on the analysis of errors and their importance in order to obtain preventive action. It is a qualitative method that identifies those system components whose failure can disrupt the operation of the system or cause accidents with significant consequences. Some short-term benefits are: it gives a list of potential failures, identifies the severity of their effects, and determines the priority of the correction actions. Long-term benefits are: it develops the criteria for system testing, provides documentation for future reliability analyzes in case of system design change, provides a basis for maintenance planning, and provides the basis for a qualitative and quantitative analysis of the system reliability. FMEA also focuses on individual component failures rather than on their combination which is important drawback of the method, it does not identify risks that are not related to failures, it requires certain type of expertise for the process or product analysis. Also, this method anticipates failure during the design stage by identifying all of the possible failures in a design or manufacturing process.