How the operations research make the overall structure of the problem more comprehensible

It would be greatly appreciated if you could provide further clarification on the necessity of employing a request for proposal as a means of eliciting details pertaining to system requirements.

Provide an explanation of the major difference between the two typical methods to system development. Which of these strategies has the most positive and negative aspects, and why?

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