adplus-dvertising
frame-decoration

Question

What are the seven sins listed by Meyer that may beset the analyst when using natural language in a requirements specification?

a.

Noise, Silence, Over-specification, Contradictions, Ambiguity, Forward references, Wishful thinking

b.

Noise, Redundancy, Regret, Over-specification, Contradictions, Ambiguity, Wishful thinking

c.

Noise, Silence, Over-specification, Contradictions, Ambiguity, Forward references, Realistic thinking

d.

Noise, Redundancy, Over-specification, Contradictions, Ambiguity, Forward references, Realistic thinking

Posted under Software Engineering

Answer: (a).Noise, Silence, Over-specification, Contradictions, Ambiguity, Forward references, Wishful thinking Explanation:Meyer lists seven sins that may beset the analyst when using natural language in a requirements specification: Noise, Silence, Over-specification, Contradictions, Ambiguity, Forward references, and Wishful thinking. These refer to issues that may arise in the requirements specification when using natural language, such as the presence of text elements that do not contain relevant information, the absence of important aspects, over-specification that limits the solution space, and more.

Engage with the Community - Add Your Comment

Confused About the Answer? Ask for Details Here.

Know the Explanation? Add it Here.

Q. What are the seven sins listed by Meyer that may beset the analyst when using natural language in a requirements specification?

Similar Questions

Discover Related MCQs

Q. What is the alternative given by Meyer to the use of natural language in the requirements specification?

Q. What does the natural language description obtained after using the alternative given by Meyer represent?

Q. What are the visual clues used to distinguish different types of nodes and links in semantic networks?

Q. What is Entity--Relationship Modeling used for?

Q. What can Finite State Machines be viewed as?

Q. What does UML owe tribute to?

Q. What are UML diagrams used for?

Q. What are non-functional requirements viewed as in the development process?

Q. What type of requirements are external interface requirements and design constraints generally phrased in?

Q. What type of requirements do external interface requirements and design constraints often concern?

Q. What are the two essential issues usually emphasized regarding quality requirements?

Q. What are quality requirements in the context of software development?

Q. What should be the form of quality requirements in a requirements specification?

Q. What is the impact of extreme levels of quality requirements in software development?

Q. When is the analysis of technical feasibility of quality requirements done in software development?

Q. What should be kept in mind while specifying quality requirements?

Q. Why might users ask for more in quality requirements?

Q. What is the role of an early and careful analysis of technical feasibility?

Q. What is the purpose of verification and validation in requirements engineering?

Q. How is the requirements specification validated during requirements engineering?