The key to successfully developing information systems is understanding the requirements of the system.

A. Case Study: Your client, APEX Hardware, specialises in Do It Yourself (DIY) supplies and products. They work with over 10,500 supplier companies and now require a new Supplier Management System. They would like to find out what impact the new systems functional requirements would have on their suppliers, particularly, the impact of the new flexible stock level management functionality. APEX Hardware is keen to get input from the majority of their 10,500 suppliers, as to whether, they would prefer to continue as it, or if they can comply with a new dynamic (changing) supply system, where they need to change the level of supply based on APEX Hardwares changing demand.

Name the data gathering technique most suitable to get this data. Briefly describe 2 reasons why you would choose this technique.

B. Case Study: You are the system analyst at a motorcycle manufacturing organisation, and have been called in to review work practices because there are constant problems on the factory floor. You have started by reviewing the process documentation, and from the documentation the work processes appear well structured and should not be causing any problems.

Name the data gathering technique most suitable to discover the cause of the problems. Briefly describe 2 reasons why you would choose this technique.

C. Interviews are often used to investigate the requirements of a system. Briefly describe 2 problems and 2 benefits that you need to consider when using interviews as a requirements gathering technique.