Ch. 6 Agile Modeling & Prototyping SDLC vs. Prototyping "I’ve got the idea of the century!" proclaims Bea Kwicke, a new systems analyst with your systems group. "Let’s skip all this SDLC garbage and just prototype everything. Our projects will go a lot more quickly, we’ll save time and money, and all the users will feel as if we’re paying attention to them instead of going away for months on end and not talking to them." A) List the reasons and conditions , you, as a member of the same team as Bea, would give her to utilize an SDLC and not just prototype every project. That is, tell Bea when you would use an SDLC. B) Bea is pretty disappointed with what you have said. To encourage her, use a paragraph to explain the situations you think would lend themselves to prototyping.

Refer below.

Explanation:

A.The SDLC ought not be rejected for each venture since certain frameworks might be rashly molded before the issue or opportunity being tended to is altogether comprehended. Additionally, utilizing prototype as an option may bring about utilizing a framework that is acknowledged by explicit gathering of clients yet which is insufficient for in general framework needs. In numerous framework prototyping can be effectively incorporated with SDLC approach. For surely knew frameworks, a straight SDLC approach has demonstrated its value.

B.In epic or complex circumstance, prototyping is a perfect mechansim for better understanding client prerequisites, and for getting client input for improving framework viability. What's more, prototyping has demonstrated valuable when fused into SDLC. This combination is especially helpful in better learning client needs.

i've had the same problem. i generally just ignore it, as a ton of these "verified answers" are completely wrong.

answerenforce the organization's security policy;