planning  B: analysis

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

71. A system analyst does not need to consider a. technical feasibility b. economics feasibility c. operational feasibility d. none of these

Draw a PERT chart for the given scenario. Identify critical path. Use the correct notation, otherwise your answer will not be accepted.

4. Why is it not recommended to use every available UML model in planning a system for every aspect of system behavior? Would any benefit be provided from creating this documentation, and how is it detrimental?