Software Engineer Recuirments Questions

Software requirements often unfold in progressive levels of decail. Identify 3 diflerent levels of requiremet specificacion from the abstract to the specific Tim Vision, features, use cases Non-functional, constraints functional Specification, validation, change control DQuestion 2 1 pts s it acceptable for the development team or requirements analyst to suggest modifying the requirements to reuse existing components No, the development team or requirements analyst shouldn't iluence requirements Yes, smal dfferences in functionality may be worth the reduced cost of reusing exsting components Question 3 1 pts What, if anything, is wrong with using a statement like the following in a requirements document in order to document a usability requirement: The user interface should be easy to use? The requirements documment shouldn't specify user interface design requirersents The statement isn't testable Statements in the requirements document should be rreasurable and testable thing is wrong with the stalerent. It expresses a non-functional returement-usabilky. Nothing is wrong with the statement. It expresses a constraint on dgn and implementation options. Question 4 1 pts A desirable characteristic of a requirements document is that it be traceable. Requirements may have forward and backward traceability. Backward traceablity (from the perspective of the requirement) means that it is possible to trace a specific requirement back to its source (where it originated from), Forward traceablity means it's possible to trace a requirement to a design element, code and or test case True O False