"Just be a little patient. I think we need to add a few more features before we turn it over them. Otherwise, this whole prototype will sink, not swim," says Ryan, a member of your systems analysis team. All four members of the team are sitting together in a hurriedly called meeting, and they are discussing the prototype that they are developing for an information system to help managers monitor and control water temperature, number of fish released, and other factors at a large, commercial fish hatchery. "They've got plenty to do already. Why, the system began with four features and we're already up to nine. I feel like we're swimming upstream on this one. They don't even want it," argues Mary, a second member of the systems analysis team. "I don't mean to carp, but just give them the basics. We've got enough to tackle as it is." "I think Ryan is more on target," volunteers Harris, a third member of the team, baiting Mary a little. We have to show them our very best, even if it means being a few weeks later in hatching our prototype than we promised." "Okay," Mary says warily, but I want the two of you to tell the managers at the hatchery why we aren't delivering the prototype. I don't want to. And I'm not sure they'll let you off the hook that easily." Ryan relies, "Well, I guess we could, but we probably shouldn't make a big deal out of being later than we wanted. I don't want to rock the boat." Harris chimes in, Yeah. Why point out our mistakes to everyone? Besides, when they see the prototype, they'll forget any complaints they had. They'll love it." Mary finds a memo in her notebook from their last meeting with the hatchery managers and reads it aloud. Agenda for meeting of October 25. Prototyping-the importance of rapid development, putting together the user analyst team, getting quick feedback for modification..." Mary's voice trails off, omitting the last few agenda items. In the wake of her comments, Ryan and Harris look unhappily at each other. Ryan speaks first: "I guess we did try to get everyone primed for receiving a prototype quickly and to be involved from day one." Noting your silence up until now, Ryan continuous, "But still waters run deep. What do you think we should do next ha asks you. Required: Assume you as the fourth member of the systems analysis team in the fish hatchery project. Prepare an email message to your teammates by addresses the following information. i. The actions that you should take in the project for the fish hatchery. ii. Decision whether should more features be added to the hatchery system prototype before giving it to the hatchery managers to experiment with. The important of the rapid development of the prototype. The trade-off involved in adding more features to the prototype versus getting a more basic prototype to client when it was promised. Recommendations whether the prototype should be delayed in order to add more features or delivered it on time with fewer features completed. (15 marks) (CLO2:PLO2:C6) iv