Dasturiy ta’minot qurilmasi va evolyusiyasi” fanidan nazorat savollari

Modul ulanishi va birlashishi asosida murakkablikni baholashni tushuntirib bering.

Module coupling is a measure of the degree to which two or more modules are connected. It is a measure of the number of connections between the modules, and the strength of those connections. Coupling is a measure of the complexity of a system, and is used to estimate the complexity of a system. It is based on the idea that the more connections between modules, the more complex the system is likely to be. Coupling can be used to identify areas of the system that are more complex than others, and can be used to identify areas that need to be refactored or redesigned to reduce complexity.


The productivity, if measured only in terms of lines of code per unit of time, can vary a lot depending on the complexity of the system to be developed. A programmer will produce a lesser amount of code for highly complex system programs, as compared to a simple application program. Similarly, complexity has a great impact on the cost of maintaining a program.
A complexity measure is a cyclomatic complexity in which the complexity of a module is the number of independent cycles in the flow graph of the module. A number of metrics have been proposed for quantifying the complexity of a program, and studies have been done to correlate the complexity with maintenance effort.

51. 
    Dasturiy ta’minotni ishlab chiqishda o’zgarishlarni kutish tamoyilini tushuntirib bering.
    

Change is inevitable in all large software projects. The system requirements change as businesses respond to external pressures, competition, and changed management priorities. As new technologies become available, new approaches to design and implementation become possible. Therefore whatever software process model is used, it is essential that it can accommodate changes to the software being developed.
Change anticipation, where the software process includes activities that can anticipate or predict possible changes before significant rework is required. For example, a prototype system may be developed to show some key features of the system to customers. They can experiment with the prototype and refine their requirements before committing to high software production costs.

52.