Discussion
During the systems development life cycle (SDLC), certain key problems discovered in the later stages could be directly traced back to inadequate and/or poor efforts in the requirements phase and industry studies show that over 50% of systems problems belong to this case. In addition, as mentioned in lecture notes "the cost of errors in requirements that weren't discovered until later" may go up to 1,000 times. As a systems analyst, what should we do to minimize this problem? How might this be avoided?
Suppose you are explaining the concept of prototyping to your manager to persuade her to approve the prototype approach to a proposed system that you are working on. Her response to your explanation is that "prototyping is a waste of time and money". As a systems analyst, how could you respond to her?
The response should include a reference list. Double-space, using Times New Roman 12 pnt font, one-inch margins, and APA style of writing and citations.