Use case diagram, activity diagram, Collaboration diagram.
Use case diagram :
It describes the business environment. Its primary goal is to show the series of events and actions within any given process that will be performed by an actor.
The activity diagram is important because it gives an outline of the work flow within the business as well as the activities and action completed.
For instance with a company, there is likely to be more than one department. In such a case each department, will have different access levels to the system.
So if there’s a Medical, HR and Accounts team they will only have access to screens that relate to each.
The activity diagram will highlight the differences within the departments which will be very helpful for developers when they are designing and coding.
A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML). The concept is more than a decade old although it has been refined as modeling paradigms have evolved.
Traceability matrix is a cross matrix for recording the requirements through each stage of the requirements gathering process. This matrix should also take into account any changes in the scope during the life of the project.
At the end of the project this matrix should show each function built into a system, its source and the reason that any stated requirements may not have been delivered.
JAD (Joint Application Development) is a methodology that involves the client or end user in the design and development of an application, through a succession of collaborative workshops called JAD sessions.
The JAD approach, in comparison with the more traditional practice, is thought to lead to faster development times and greater client satisfaction, because the client is involved throughout the development process. In comparison, in the traditional approach to systems development, the developer investigates the system requirements and develops an application, with client input consisting of a series of interviews.
Generally a business analyst covers several stages in Software Development Life Cycle.
Like: Client Consulting, Client Requirement Study, Planning for business needs, Business Requirement Documenting, Work on functional requirement, Prepare test data with inputs from end users, Document use case scenarios, Help Testing team with test plan and testing, Help end users with user acceptance testing UAT, Go live and post production support tasks.
Change management is the biggest challenge in each and every industry. After requirements stage when development is started client will come-up with some new changes or enhancements.
Cross departmental or cross team management – like conflict management between teams. Also individuals. This requires soft skills and smartness.
Communication problems – In real time this can happen. You might be good in speaking and understanding the English language. BUT sometimes it happens like Different people across the globe speak different style of English. In USA itself Mexico people speak English differently. Romans speak different English. So at initial level to understand the accent can be a challenge but after some time you will become perfect.