Fault detection is a process of detecting the faults before the software is put into operation.

Software reliability is a function of the number of failures experienced by a particular user of the software.

Software reuse involves reusing existing components rather than developing them especially for an application.

Fault tolerance strategy assumes that residual faults remain in the system. Facilities are provided in the software to allow operation to continue when these faults cause system failures.

Operation generalization involve adding operations to a component or removing operations, which are very specific to some application domain.

Exception generalization may involve checking each component to see which exception it might generate and including these exceptions in the component interface.

Abstract machine model organizes a system into a series of layers each of which provides a set of services.  

Data-flow model is a way of showing how data is processed by a system. The notation used in this model represents functional processing, data stores and data movements between functions.

White-box testing is also called as glass-box testing.

Object-oriented analysis is concerned with developing an object-oriented model of the application domain.

Top-down testing tests the high levels of a system before testing its detailed components.

A system model based on a shared database is called as repository model.

Object-oriented design is concerned with developing an object-oriented model of a software system to implement the identified requirements.

Weather station collects information and communicates it for processing.

Back-to-back testing is used when more than one version of a system is avaliable for testing.

A map is an outline of areas with super imposed weather information.

Data-flow design is concerned with designing a sequence of functional transformations that convert system inputs into the required.

The process of changing a system after it has been delivered and is in use is called software maintenance.

Function oriented design strategy relies on decomposing the system into a set of interacting functions with a centralized system state shared by these functions.  

Configuration management is the process, which controls the changes made to a system and manages the different versions of the evolving software product.

Software re-engineering is concerned with taking existing legacy systems and re-implementating them to make it more maintainable.

An entity-relation model is used to describe the logical data structures being used.

Adaptive maintenance means changing the software to some new environment such as different hardware platform or for use with a different operating system.

Chain management procedure is designed to ensure that the costs and benefits of change are properly analyzed and changes to the system are made in a controlled way.

Client-server model is a distributed system model, which shows how data and processing is distributed across a range of processors.

Perfective maintenance involves implementing new functional or non-functional system requirements.