| Business Analysis |
|
| Written by Sergei Kostigoff | |||||||||||||||||
| Friday, 14 March 2008 | |||||||||||||||||
General
Glossary and Abbreviations
Business AnalysisThe following diagrams are shown and at certian level are commented below:
Applications:: Data FlowWhen you are doing Business Analysis, there are few key issues:
Figure 1 shows generic template of the Data Flow. The template should be adopted for the given situation as appropriate. Fig.1: Applications:: Data FlowAfter you will fill the template with names of the systems / applications used by the Company and show existing interfaces with the General Ledger you will create Data Flow Diagram for the Company you are working with. Based on the analysis of the Data Flows you may then set priorities, choose (or replace) applications for the functions, propose and implement controls and interfaces. Applications:: Applications MapTo simplify your work as a first step you can map all Business Applications to the following list:
Figure 2 shows the example of such applications mapping. You may change it according to you applications and/ or business units.
After you will list all the existing systems and document interfaces between them - you may show the resulting map to Company Management, and you will prove that you do understand Company Business Flows and Applications. As a side effect, you will really understand Company Business, and may explain it to Development Team. As another side effect, you will see which interfaces are missing or needs to be improved. Applications:: Business Function MappingIf you will map business functions to existing systems using a table similar to shown on Figure 3, you may find Primary and Derivative systems Company using. As well you will be able to show links including information transfer between business units and functions.
Again, such a map may serve as a tool for the analysis. You may discover that Business Application and/ or Accounting databases does not provide necessary analysis or/ and can not be customized as required, and users have to write their own macros on Excel or Access (or whatever generic office applications). As a next step you may find out that these macros are not documented nor maintained. As a next step you may discover that such approach may cause problems if user leaves Company. And finally you may explain why it is necessary to replace or upgrade existing Business Application or Accounting ssytem. You may discover a lot of interesting things using quite simple tools. Applications:: Inadequacies AssessmentTo estimate quality of the particular system, it is fashion at present time to use so-called "magic quadrant" (will not shown). "Magic Quadrant" is widely used in marketing slides, but its usage as a tool looks a bit inappropriate from my personal point of view. If you will instead use Red-Amber-Green (R-A-G) diagram shown on Figure 4 you get:
Downloads
Your Comments
|
|||||||||||||||||
| Last Updated ( Sunday, 16 March 2008 ) | |||||||||||||||||
| Next > |
|---|




