There are at least four levels, analysis of the company:

1. Strategic planning – Analysis of the organization’s strategic needs

2. Operation / analysis of the economic model – the definition and analysis of organizations, policies and strategies of the enterprise market

3. Process Definition and Design – Business Process Modeling (often the result of process modeling and design),

4. IT / Technology Business Analysis – Analysis of business rules and requirements for technical systems (usually)

In the field of life support systems development life cycle (SDLC), business analysts, usually a link between the commercial side of the enterprise and service provider for businesses. A common alternative role in the IT sector, business analyst, systems analyst, and analyst, although some organizations may differ between these titles and related skills.

The Australian Institute of Business Analysis, the role of business analyst defines more broadly than the analyst more focused technical analysis business systems “Business is the ability to take problems to be solved to achieve the strategy outcomes expected business to analyze. “

Typical benefits

Depending on the level of reflection on the business analysis, technical analysis of business topics are the role (the conversion system of work organization), the conversion of the return to shareholders and take risks in planning Strategic.

The next section focuses on the prospects for the analysis of business IT industry, where most services. BA must have some form of requirements management tool to record whether a simple spreadsheet or a complex issue.

Business Requirements

(Project Initiation Document), which are necessary services and quality measures. They are generally required to report results of department stores, but may not fulfill the specific functions of the system, he expressed. Specific design elements are usually outside the scope of this document, although design standards may be cited.

* Example: To improve the readability of project plans.

Functional Requirements to describe what is necessary for a system, process, product or service to meet business needs. Note that the business needs is often divided into sub-business requirements and many functional requirements. They are often referred to as system requirements, although some features could be based on non-manual system, as the collection of notes or work instructions.

* An example that follows from previous business requirement example:

1. The system must be associated in a position to provide guidance for planning a project.

2. The system allows the user to enter free text notes the project plan, up to 255 characters.

User (stakeholder) requirements are some very important services, the needs of stakeholders must be interpreted correctly. May This objective also reflect how the product is developed, developed to define and describe how test cases should be formulated.

Quality of Service (non-needs) Functional are requirements that can not be a specific function for the year of tax liability, but which are necessary to support the functionality. For example: performance, scalability, quality of service, security and usability. It is often the system requirements, including, where appropriate.

Implementation (Transition), requirements Skills or behaviors that are required to allow the passage of current business desired future state, but now longer needed.

Report Details This is the subject of the report, the rationale, features and columns, the owner and the run time parameters.

Traceability Matrix process is a cons-matrix for requirements capture through the stages of requirements gathering. High level concepts will be matched with elements of implementation, which will be based on individual needs, functions to display the map. This matrix should also take into account any changes in scope during the lifetime of the project. At the end of a project should, this matrix to show each function built into a system, its origin and why all the above conditions have not been delivered may be.

Benefits of participation of business analysts in software projects

The role of the BA is the key in software development projects. Communicate directly with a provision in organizations where there is no formal structure or process, the press and developers together. This can be a problem: the objective of the company owner is very quickly what they want, and the goal of developers is to tell the business owner what they want, when he / she can give him / her.

This led to the creation of changes in the void that will not necessarily take into account the needs of all users of the system. There is rarely a detailed definition of requirements, and many times, can make the real reason for the request is not business sense. There is a tendency not to value long-term strategic objectives for the company on information technology and communication to achieve. The business analyst can adjust the structure and formalizing the requirements of this process, may also require greater foresight in the press the most important.

In recent years there has been an increased use of analysts of all kinds: business analyst, analysts, business process, risk analysts, systems analysts were. Ultimately, a good project manager are the business analysts who refuse to communication barriers between stakeholders and developers.


By Anonymous
http://ezinearticles.com/?Role-of-a-Business-Analyst-For-a-Software-Project&id=3975308
Business process modelling