1.7. 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 provide. a. Needed/feedback b. User/system. System/user d. Functionalon-functional e. Development/user 1.8. A project is a predictable outcome of an activity where some formal report of progress should be presented to management. s should occur regularly throughout a software project. A deliverable is a that is delivered to the project customer. a. milestone b. task list C. Gantt Chart d. network 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