As stated above, the business analyst will act as a condoit between IT and the business. What this means is that the business analyst must successfully fully capture the requirements and make sure they are translated to understandable documentation for the full project team. The life-cycle documentation includes the following.
1. Assisting with the Business case
2. High level feasibility
3. Gathering of the requirements
4. Designing and/or reviewing test cases
5. Processing change requests
6. Tracing the requirements during implementation (traceability matrix)
7. Manage scope
8. Acceptance, Installation, deployment
Once the project is defined and feasibility established in sections 1 and 2, the business analyst ventures into the requirements gathering and requirements management phase. To adequately cover all areas of documentation could cover a full book, so the focus for this article will just be items 3 through 6 in the documentation steps above.
No comments:
Post a Comment