Hello All,
I am fairly new to the world of business analysis. I majored in finance and have 5 years accounting/finance experience out of college. Just this past year I picked up a consulting gig at a bank as a BA primarily on production support for the general ledger. I was working on that for about 6 months, fielding any questions from users regarding system issues and general accounting issues related to mapping tables in the system. The group really liked my enthusiasm and decided to keep me on and put me on my very first project.
I am now learning about how the various systems integrate and allow the accounting to flow through each system , into the G/L and then on to Reporting modules for regulatory and management reporting, etc. Not having a systems background it makes it difficult for me to follow the system mapping and flow of information. Is there anything some of you seasoned veterans can recommend i do to get more accustomed to reading Functional Specs and making sense of them?
You said you are finding it difficult "to follow the system mapping and flow of information". How are you actually doing this? Is it documented or diagramed? What are you specifically finding challenging?
It may depend on the nature of the specs that you are reading. Are they laundry lists of the "system shall" variety? Or UML diagrams? Or models using a particular notation? Or maybe some kind of hybrid madeup by the original author?
brought to you by enabling practitioners & organizations to achieve their goals using: