Please explain how an engineer who is responsible for developing a system requirements specification might maintain track of the relationships that exist between functional and non-functional demands.

Provide an example of how an engineer in charge of creating a system requirements specification could keep track of the connections between functional and non-functional needs.

Q-1 In your opinion, why for a system under- development the requirements discovery is needed? Justify your answer by giving an example. Q-2 If a system’s end- user stakeholders are not involved during its development or updation requirement engineering process then what type of functional requirements related problems are expected? Name and explain any two of them.

requirements are intended for use by people involved in using and procuring the system. They should be written using natural language with tables and diagrams that are easily understood. But, requirements are intended to communicate, in precise way, the functions that the system 1.7. provide. a. Needed/feedback b. User/system c. System/user d. Functional/non-functional e. Development/user 1.8. A project be presented to management. is a predictable outcome of an activity where some formal report of progress should _s should occur regularly throughout a software project. A that is delivered to the project customer. c. Gantt Chart d. network deliverable is a a. milestone b. task list e. management 1.9. The measures for the time to restart after failure, and/or percentage of events causing the failure, and/or probability of data corruption on failure are the property of for "specifying non-functional software requirements". a. size b. easy of use c. reliability d. robustness e. portability

Give an example of how an engineer in charge of generating a system requirements specification may keep track of the connections between functional and non-functional needs.

Give an example of how a system requirements specification may be maintained by an engineer who is in charge of keeping track of the links between functional and non-functional requirements.