[Solved] The SRS is said to be consistent if and only if

Q.	The SRS is said to be consistent if and only if
A.	its structure and style are such that any changes to the requirements can be made easily while retaining the style and structure
B.	every requirement stated therein is one that the software shall meet
C.	every requirement stated therein is verifiable
D.	no subset of individual requirements described in it conflict with each other
Answer» D. no subset of individual requirements described in it conflict with each other

819

Do you find this helpful?

View all MCQs in

Software Engineering

Discussion

No comments yet

Related MCQs

SRS stands for
SRS document is for
Which is not a characteristic of a good SRS?
IEEE standard for SRS is:
After the finalization of SRS, we may like to estimate
What methods can be followed if designers are out of good SRS or engineering design?
Match the following: A- Formal mathematical transformation: B- Formal process model: C-Formal Specifications: D-Formal System development: 1- Here the formal mathema- tical representation of the system takes place. 2- It is a starting point for process analysis. It is abstract and only defines the principal process activities and deliverables. 3-Specifications expressed in a language whose vocabulary, syntax and semantics are formally defined. 4-It is more common to waterfall model, but here the development process is based on formal mathematical transformation of a system specification to an exactable program.
The software life cycle can be said to consist of a series of phases. The classical model is referred to as the waterfall model. Which phase may be defined as “The concept is explored and refined, and the client’s requirements are elicited?”
If all the application processing and data management is carried out on the server and client is only responsible for running the system then this is referred as
Match the following : A- Maintenance control: B- Maintenance prediction: C- Maintenance process: 1-Cost of planning and scheduling hardware preventive maintenance, and software maintenance and upgrades, managing the hardware and software baselines, and providing response for hardware corrective maintenance. 2- Predicting the number of change requires a system understanding and the relationship between the system and external environment. 3- It is triggered by a set of change requests from system users, management or customers.