Our solutions are designed to meet client needs with the highest quality and professionalism. The most important responsibilities of an LS COMMUNICATIONS are to act as a communication conduit between the stakeholders and the team. To represent the stakeholder community to the development team if the developers themselves don't have direct access, and to translate the business needs for the team. L
Scom developed a list of eight activities that business systems analysts will usually perform on a traditional software development project:
1. Scope the system: At the outset of a project, business analysts may be the only software development staff assigned to the project. And at this point, they work with key project stakeholders and business people to formulate and communicate the business vision for the project, and map out initial requirements and the scope of the project. Their fundamental goal is to get the project focused early by translating the initial high-level vision into something realistic.
2. Interpret business needs. A critical responsibility of business analysts is to work with project stakeholders to translate their requirements into something that developers can understand as well as to translate the resulting questions that the developers have into something the stakeholders can understand. A key skill needed in this part of the process is the business analyst's ability to distill the differing messages and needs of project stakeholders into a single, consistent vision.
3. Translate technical issues: Business analysts also have the arduous task of breaking down technical and architectural complexities so that project stakeholders can easily understand any issues that crop up, such as why your Customized-based application can't have as slick of a user interface as a Visual Basic application. LScom often explains what the developers are doing and why they need to do it, including explanations of the basis of schedules and estimates.
4. Spell out the project details and requirements: LScom will often work with project stakeholders to identify, model, and then document their requirements and business domain details.
5. Put the development team in touch with the right people: LScom typically has very good connections within the business community and therefore is in a position to help development teams find the right people to work with.
6. Political guide: LScom often help project teams through the political minefields within their organizations, particularly when the LScom has worked within the same organization for several years.
7. Test and validation: Business analysts work with project stakeholders to validate their requirements and analysis models via techniques such as reviews, walkthroughs, and play-acting. LScom will often aid in writing user acceptance test (UAT) cases and will be a liaison between project stakeholders and your testing organization during UAT."
8. Represent project stakeholders throughout the process: If project teams don't have direct access to their project stakeholders, which is never a good situation, business analysts have to act as "stakeholder surrogates. Typically developers will treat an LScom as the 'customer' from which requirements, domain information, and business priorities are provided. The LScom, in turn, will work with the stakeholders to obtain information and verify decisions.
