-
1-Facilitate creation of Business Requirements following a traditional approach, or using the Business Process and Analysis (BPA) methodology as determined by the project sponsor
-
2-Manage Scoring (approving) and Claiming processes with Business and Technology stakeholders to review and refine business requirements and use cases to ensure they are clear, concise and traceable; and to ensure business requirements will be satisfied by the appropriate teams / applications.
-
3-Identify project stakeholders, risks and benefits of alternate designs; document assumptions; assess project impact of system changes to users, internal and external customers
-
4-Develop System Requirements (SRQs), including process flows and use cases
-
5-Conduct SRQ reviews with project stakeholders and document consumers to ensure completeness and adherence to business requirements
-
6-Consult with internal customers, cross-functional team members and external vendors to capture agreed-upon business objectives and processes to define system requirements
-
7-Update and map SRQs to Business Requirements in the Requirements Traceability Matrix (RTM)
-
8-Review Architecture, Engineering and Application Development designs and QA / UAT test plans to ensure requirements are met and the RTM is updated as required
-
9-Provide BA support for software testing and debugging plans to ensure requirements are met
-
10-Provide status reporting for project progress, issues, dependencies and risks 11-Level I:
-
12-Typically performs smaller chunks of work or is one of many analysts on a project
-
13-Work is reviewed with frequent process checks during larger projects
-
14-Sphere of relationship and influence is primarily within the work team
-
15-Level II 16-Where knowledge may not be readily available, incumbents at this level know how & where to research and what information is necessary to document
-
17-Knowledge of the business may be deep in one functional area with surface understanding of other functional area.
-
18-Sphere of relationship and influence is primarily within the team & with key stakeholders