can someone please answer question 2 i will be really apperate you lots i want 15 sentence for that paragaraph plzzs someone help me out i will really apperate you lots and plzz dont copy from internet plzz write it in your own word plzz help

The number one reason projects fail is bad business requirements. Business requirements de ered "bad" because of ambiguity or insufficient involvement of end users during analysis and tations by different participants will usually result in unmet expectations. Here is an exampled A requirement is unambiguous if it has the same interpretation for all parties. Differentie Chapter Seve Case Reducing Ambiguity in Business Requirements ambiguous requirement and an example of an unambiguous requirement: . Ambiguous requirement: The financial report must show profits in local and U.S. cutendes Unambiguous requirement: The financial report must show profits in local and U.S. Cuence using the exchange rate printed in The Wall Street Journal for the last business day of the per being reported Ambiguity is impossible to prevent completely because it is introduced into requirements in natu ral ways. For example: Requirements can contain technical implications that are obvious to the IT developers but not to the customers Requirements can contain business implications that are obvious to the customer but not to the IT developers . Requirements may contain everyday words whose meanings are obvious to everyone, yet dit ferent for everyone Requirements are reflections of detailed explanations that may have included multiple events. multiple perspectives, verbal rephrasing emotion, Ierative refinement, selective emphasis and boty leyguage--none of which are captured in the written statements Tips for viewing Business Requirements when in business requirements aways look for the following words to help dramatically reduce "And or have well-defined meanings and ought to be completely unambiguous, yet they are understood only informally and interpreted inconsistently Forecamie consider the Statem. The alarm must ring it button is pressed and if button Fis pressed." This statement may be headed to mean that to ring the alarm both buttons must be pressed or it may be intended mean that either one can be pressed. A statement this should never appear in a request because the potential for misinterpretation is too great. A preferable approach is to be very ect, for example, "The alarm must ring if both button and Fare pressed simultane ously. The alarm should not ring in any other circumstance." "Always" might really mean most of the time." in which case should be made more explicit For example, the statement "We always run reports A and B together could be challenged with "In other words, there is never any circumstance where you would run A without and without All you build a system with an "always requirement, then you are actually building the system to never run report A without report B. 1 user suddenly wants report without report A you will need to make significant system changes "Never" might mean "rarely." in which case it should be made more explict. For example, the statement "We never runt reports A and B in the same montcould be charged with "So that means that see that A has been run. I can be absolutely certain that no one will want to Again, if you build a system that supports a "never requirement then the system users can never perform that requirement. For example, the system would never low a user to run reports and Bin the same month, no matter what the circumstances Boundary conditions are statements about the line between true and lite and do and do not These statements may or may not be meant to include end points, for example, "We want to use method X when there are up to 10 pages, but method Yotherwise."you were building this tem, would you include page 10 in method X or in method Y? The answer to this question wory Casing an ambiguous business requirement. Questions are consid and design -nt interpre ample of an Why do the words and" and "or" tend to lead to ambiguous requirements trrencies 5. currencies pf the period