Defining functional/non-functional requirements
Functional – defining what the system should do, defining features, etc.
Nonfunctional – defining how systems should perform (e.g. response time)
Solutioning: Looking at the functional requirements and deciding what is required.
E.g. deciding if a new system/application is required
Process Design/development – creating flow charts.
Optimization: streamlining processes, being the SME on how systems interact with each other
Must Haves
10+ years of experience
Combination of BA/BSA/Process Engineer skillset
Understanding of technology and the business side (e.g. APIs)
Understand waterfall requirements: BRDs, SRDs, etc.
Analytical, quick learner, detail-oriented, critical thinker, independent, can form good relationships.
Any Graduate