‘FAN IN’ of a component A is defined as
Count of the number of components that can call, or pass control, to a component A
Fan-in and fan-out are structural design metrics read from the calling hierarchy (structure chart) of a program.
Fan-in of a module A is the number of modules that call A, i.e. that pass control to A. A high fan-in means A is reused by many callers, which is generally desirable.
Fan-out of A is the opposite count: the number of modules that A itself calls (the modules A depends on).
“Components related to A” is too vague to be a metric, and “components dependent on A” does not describe the direction of control transfer that fan-in counts; since one statement gives the exact definition, “None of the above” does not apply.
Hence, the answer is Count of the number of components that can call, or pass control, to a component A.
Similar Questions
Temporal cohesion means
Adaptive maintenance is a maintenance which __________.
In Software configuration management, what is the primary purpose of version control ?
Match the software maintenance activities in List – I to its meaning in List – II.
List – I List – II I. Corrective (a) Concerned with performing activities to reduce the software complexity thereby improving program understandability and increasing software maintainability. II. Adaptive (b) Concerned with fixing errors that are observed when the software is in use. III. Perfective (c) Concerned with the change in the software that takes place to make the software adaptable to new environment (both hardware and software). IV. Preventive (d) Concerned with the change in the software that takes place to make the software adaptable to changing user requirements. Codes :
A server crashes on the average once in 30 days, that is, the Mean Time Between Failures (MTBF) is 30 days. When this happens, it takes 12 hours to reboot it, that is, the Mean Time to Repair (MTTR) is 12 hours. The availability of server with these reliability data values is approximately :
Match the terms related to Software Configuration Management (SCM) in List – I with the descriptions in List – II.
List – I List – II I. Version A. An instance of a system that is distributed to customers. II. Release B. An instance of a system which is functionally identical to other instances, but designed for different hardware/software configurations. III. Variant C. An instance of a system that differs, in some way, from other instances. Codes :
Important Questions from Software Maintenance
When a software application is modified to remain functional and compatible after its underlying operating system is upgraded, this activity falls under which category of software maintenance?
Size and complexity are a part of
Given below are two statements:
Statement I: Quality control involves the series of inspections, reviews and tests used throughout the software process. to ensure each work product meets the requirements placed upon it.
Statement II: Quality assurance consists of auditing and reporting functions of management. In the light of the above statements.
choose the correct answer from the options given below
Software re-engineering is concerned with:
In an activity-on-arrow PERT/CPM network, a merge event marks the ______ of all incoming activities before any outgoing activity may begin.
