Assignment Instructions: 1. Read the case provided in the assignment 2. Answer these questions: a. Provide a summary of the issue/initiative/change. (100 words) b. Identify which truths are applicable in the case (minimum three truths). c. Provide your insight/analysis/views. (100 to 150 words) CASE Review: Gerhard, a senior manager at Contoso Pharmaceuticals, was meeting with Cynthia, the new manager of Contoso's information systems (IS) development group. "We need to build a chemical-tracking information system for Contoso, " Gerhard began. "The system should let us keep track of all the chemical containers we already have in the stockroom and in individual laboratories. That way, maybe the chemists can get what they need from someone down the hall instead of buying a new container from a vendor. This should save us a lot of money. Also, the Health and Safety Department needs to generate some reports on chemical usage for the government. Can your group build this system in time for the first compliance audit five months from now?" "I see why this project is important, Gerhard," said Cynthia. "But before I can commit to a schedule, we'll need to collect some requirements for your system." Gerhard was confused. "What do you mean? I just told you the requirements." "Actually, you described a concept and some business objectives for the project," Cynthia explained. "Those high-level business requirements don't give me enough detail to know what software to build or how long it might take. I'd like to have a requirements analyst work with some of the users to understand their needs for the system. Then we can figure out what functionality will meet both your business objectives and the users' needs. You might not even need a new software system to meet your goal of saving money." Gerhard hadn't encountered this reaction before from an IS person. "The chemists are busy people," he protested. "They don't have time to nail down every detail before you can start programming. Can't your people figure out what to build?" Cynthia tried to explain her rationale for collecting requirements from the people who would use the new system. "If we just make our best guess at what the users need, we can't do a good job. We're software developers, not chemists. We don't really know what the chemists need to do with the chemical-tracking system. I've learned that if we don't take the time to understand the problem before we start writing code, nobody is happy with the results." "We don't have time for all that," Gerhard insisted. "I gave you my requirements. Now just build the system, please. Keep me posted on your progress