Assessment of Enterprise Level Business Systems
Assessment of Enterprise Level Business Systems
BSA/400
November 5, 2012
In corporate America projects are implemented on a regular basis. With implementing these projects there is a grave possibility that they may not be successful. In conducting any successful project it takes some type of organizational skills. Successfulness of a project can be jeopardized by a lack of planning, not enough funds to complete it, or the materials needed to complete it may not be readily available. In order for a project to be a success everything about the business must be evaluated to understand how well the system works. This paper will which information gathering methods can be used in analyzing the requirements, classifying which business process mapping methods should be used in analysis, discussing which business process mapping tools to use in documenting analysis, indicate how the analyst would know if these methods and tools were effecting in understanding requirements, and explaining how prototyping tools could be used to confirm these requirements.
Information Gathering Methods When completing an assessment of a business system a solution to a problem that may exist will not be fixed without knowing what the desired outcome needs to be. Gathering information correctly can be the difference between a projects success or failure. Gathering information allows a complete picture of the situation to be painted. Different techniques are available to perform this phase of the assessment. One technique is to conduct one-on-one interviews. Sitting down with the business execs and management to find out what the needs and expectations for the system are presents a productive start in the right direction. During this type of interview open-ended questions should be asked to get the person being interviewed talking. Probing questions can later be asked to understand their requirements as well. This means avoiding questions that can be answered using short answers
BSA/400
November 5, 2012
In corporate America projects are implemented on a regular basis. With implementing these projects there is a grave possibility that they may not be successful. In conducting any successful project it takes some type of organizational skills. Successfulness of a project can be jeopardized by a lack of planning, not enough funds to complete it, or the materials needed to complete it may not be readily available. In order for a project to be a success everything about the business must be evaluated to understand how well the system works. This paper will which information gathering methods can be used in analyzing the requirements, classifying which business process mapping methods should be used in analysis, discussing which business process mapping tools to use in documenting analysis, indicate how the analyst would know if these methods and tools were effecting in understanding requirements, and explaining how prototyping tools could be used to confirm these requirements.
Information Gathering Methods When completing an assessment of a business system a solution to a problem that may exist will not be fixed without knowing what the desired outcome needs to be. Gathering information correctly can be the difference between a projects success or failure. Gathering information allows a complete picture of the situation to be painted. Different techniques are available to perform this phase of the assessment. One technique is to conduct one-on-one interviews. Sitting down with the business execs and management to find out what the needs and expectations for the system are presents a productive start in the right direction. During this type of interview open-ended questions should be asked to get the person being interviewed talking. Probing questions can later be asked to understand their requirements as well. This means avoiding questions that can be answered using short answers