A software requirements specification $$(SRS)$$ document should avoid discussing which one of the following?

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

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

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