Which is NOT a requirements analysis strategy?
A) Understanding of the as-is system
B) Identifying improvements
C) Developing requirements for the to-be system
D) Root cause analysis
E) Understanding of screen design,layout and navigation
Correct Answer:
Verified
Q13: The line between analysis and design is
Q14: An example of a functional requirement is
Q15: When gathering requirements,the most commonly used technique
Q16: The authors suggest that an analyst is
Q17: Probably the first thing to do when
Q19: A technique where a set of written
Q20: A technique where the analyst watches how
Q21: An interview report is prepared in which
Q22: Michael,a systems analyst,is preparing a closed wiki
Q23: Some people have suggested that the 'analysis'
Unlock this Answer For Free Now!
View this answer and more for free by performing one of the following actions
Scan the QR code to install the App and get 2 free unlocks
Unlock quizzes for free by uploading documents