Dasturiy ta’minot qurilmasi va evolyusiyasi” fanidan nazorat savollari

Moslashuvchan xizmat ko’rsatish iborasi nimani anglatadi?

ENG: What is adaptive maintenance?
Adaptive maintenance is a type of software maintenance that modifies an application to keep it running efficiently on the current platform. It may update an application with new features or improve its performance to meet changing needs or changing business conditions. Examples of adaptive maintenance tasks include changing database or software library access methods, re-writing code for a new operating system, or adding new security measures.

101. 
     Profilaktik xizmat ko’rsatish iborasi nimani anglatadi?
     

ENG: What is preventive maintenance?
Preventive maintenance is a type of maintenance intended to prevent equipment failure, rather than remedying it after it has occurred. This type of maintenance is usually carried out on a regular or predetermined schedule using pre-defined procedures. Features of preventive maintenance include regularly scheduled inspections, inspections of critical systems, system adjustments or repairs to bring them back to peak or normal performance, and lubrication or other maintenance tasks. The goal of preventive maintenance is to reduce the likelihood of equipment breakdowns and unscheduled repairs.

102. 
     Dasturiy ta’minot evolyutsiyasining Lehman qonunlarini aytib bering.
     

ENG: Describe Lehman Laws of Software Evolution.
Lehman's Laws of Software Evolution are a set of principles co-developed by Dr. Meir M. Lehman and Dr. Paul W. Kaplan in 1980, which set out guidelines for software engineering and development.
The laws state:
1. The Law of Increasing Complexity: As software evolves, its complexity increases unless work is done to maintain or reduce it.
2. The Law of Continuing Change: As software evolves, it must be continually modified and maintained in order to keep up with changing requirements and technology.
3. The Law of Self Regulation: As software evolves, it will tend to regulate itself, so any changes to it should be kept within certain limits.
4. The Law of Conservation of Organizational Stability: As software evolves, changes must be made in accordance to existing organizational goals and existing structures.