GATE CSE 2015 Set 2 | Software Engineering Question 7 | Software Engineering

GATE CSE 2015 Set 2

MCQ (Single Correct Answer)

-0.3

Consider the basic $$COCOMO$$ model where $$E$$ is the effort applied in person-months, $$D$$ is the development time in chronological months, $$KLOC$$ is the estimated number of delivered lines of code (in thousands) and $${a_b},{b_b},{c_b},{d_b}$$ have their usual meanings. The basic $$COCOMO$$ equations are of the form

$$E = {a_b}\left( {KLOC} \right)\exp \left( {b{}_b} \right),\,D = {c_b}\left( E \right)\exp \left( {{d_b}} \right)$$

$$D = {a_b}\left( {KLOC} \right)\exp \left( {b{}_b} \right),\,D = {c_b}\left( E \right)\exp \left( {{d_b}} \right)$$

$$E = {a_b}\exp \left( {b{}_b} \right),\,D = {c_b}\left( {KLOC} \right)\exp \left( {{d_b}} \right)$$

$$E = {a_b}\exp \left( {d{}_b} \right),\,D = {c_b}\left( {KLOC} \right)\exp \left( {{b_b}} \right)$$

GATE CSE 2014 Set 3

MCQ (Single Correct Answer)

-0.3

In the context of modular software design, which one of the following combinations is desirable?

High cohesion and high coupling

High cohesion and low coupling

Low cohesion and high coupling

Low cohesion and low coupling

GATE CSE 2014 Set 1

MCQ (Single Correct Answer)

-0.3

Match the following:
$$1)$$ Waterfall model
$$2)$$ Evolutionary model
$$3)$$ Component-based software engineering
$$4)$$ Spiral development

$$a)$$ Specifications can be developed incrementally
$$b)$$ Requirements compromises are inevitable
$$c)$$ Explicit recognition of risk
$$d)$$ Inflexible partitioning of the project into

$$1 - a,\,\,2 - b,\,\,3 - c,\,\,4 - d$$

$$1 - d,\,\,2 - a,\,\,3 - b,\,\,4 - c$$

$$1 - d,\,\,2 - b,\,\,3 - a,\,\,4 - c$$

$$1 - c,\,\,2 - a,\,\,3 - b,\,\,4 - d$$

GATE CSE 2014 Set 2

MCQ (Single Correct Answer)

-0.3

Which one of the following is TRUE?

The requirements document also describes how the requirements that are listed in the document are implemented efficiently.

Consistency and completeness of functional requirements are always achieved in practice.

Prototyping is a method of requirements validation.

Requirements review is carried out to find the errors in system design.