Traceability is an important requirements attribute. It’s one of the things that should be checked when performing V&V of the system requirements. Describe how you would manually check traceability for an existing system and list a few features of a CASE tool that you think would help you with the task.

Traceability is an important requirements attribute. It’s one of the things that should be checked when performing V&V of the system requirements. Describe how you would manually check traceability for an existing system and list a few features of a CASE tool that you think would help you with the task.

Principles of Information Systems (MindTap Course List)

12th Edition

ISBN:9781285867168

Author:Ralph Stair, George Reynolds

Publisher:Ralph Stair, George Reynolds

Chapter12: Systems Development: Investigation, Analysis, And Design

Section: Chapter Questions

Problem 13RQ

See similar textbooks

Similar questions

Explain the value of having a system requirements engineer keep track of the connections between functional and non-functional needs, and show how this may be done.
Discuss the concept of a use case and how it is used in requirement analysis. How do use cases help in understanding system functionality?
Examine several requirements engineering CASE tools and document how (if at all) they support automated consistency analysis for validating and verifying requirements.
Compare three methods for determining system requirements during analysis.In what situations do you believe each method is most useful?What are the disadvantages of each method?How would you choose a technique?
What are your opinions on the importance of requirements discovery for a system in development? Provide an example to back up your answer to the question.
Explain the procedures that a system requirements engineer could follow in order to maintain tabs on the connections that exist between the system's functional requirements and its non-functional requirements.
Please explain why it is so important for systems analysts to have a record of user requirements documents in their files at all times.
Demonstrate to a system requirements engineer how to keep an inventory of both functional and non-functional requirements, and explain why this is crucial.
In K. Wieger’s paper, “Validating Requirements”, he wrote: “On many projects, testing is a late-stage activity. Requirements-related problems linger in the product until they’re finally revealed through time-consuming system testing or by the customer.” Based on what we discussed recently in the peer reviews module, how can we address this problem and reduce requirements-related problems?
Give three guidelines for creating system requirements and quickly explain each of them.
Please explain why it is imperative that systems analysts always maintain a record of user requirements papers in their files.
Explain why it would be advantageous for a system requirements engineer to monitor the links between functional and non-functional needs.