This paper will discuss which information gathering methods can be used in analyzing requirements, identify which business process mapping methods should be used in analysis activities, discuss which business process mapping tools should be used in documenting analysis, indicate how the analyst would know if these methods and tools were effective in understanding the requirements, and explain how prototyping tools could be used to confirm these requirements.
Assessment of Enterprise Level Business Systems
Information gathering used in analyzing the requirements of a business are essential to ensure that the customer is getting the best possible product for their needs. It is important for the consulting team to know different methods of information gathering to obtain the best possible information they can as this will help to ensure a higher success rate for the overall implementation of the product.
In today’s world, it is very easy for a customer to comparison shop the different products available to them. Browsing online and clicking a mouse is all it takes to move from one company to the next. The process starts when a customer starts narrowing down what they are looking for and begins to choose a few systems to have personally demonstrated to the company. Best practices would state that the consultant in charge of providing the demonstration of the software would do some homework on the company to find out what they do, start speaking with some of the stake holders to see what they expect from a new system (HR may not have the same requirements as IT, who may not have the same requirements as management or production). Meeting with a number of stakeholders within the different departments of a business will help the consultant narrow down the needs of the organization. This gives the consultant an edge and can help the consultant provide a customized demonstration of the software...