Recent Posts

Pages: [1] 2 3 ... 10
Product Development :-
1. IT company will have the concept and they invest time and money to build the Product
2. IT company initiates the development
3. IT company is the owner of the developed product
4. IT company will sell the same product to multiple clients or customers
5. Customizations are done if required for each customer
6. Installations are done at the client's place
Eg : Microsoft, Oracle, IBM, SAP, CRM

The role of the BA in Product development companies -
1. Understand the product features
2. Understand the product domain
3. Understand where this product fits in the domain
4. Understand the client's requirement
5. Understand what customizations are required for this product to fit in the client's requirements

Application Developement IT Companies
1. Client will have a requirement and will engage an IT company to develop an IT Application
2. Client initiates the development
3. Client is the owner of the developed application
4. Client will be the only customer for this application
5. Deployment will be done at the client's place
Eg : Infosys, TCS, Wipro, Satyam

The role of a BA in Application Based companies :
1. Understand the client industry
2. Understand the client requirements domain
Business Analyst Concepts Discussion / Re: Process re-engineering
« Last post by 111222333 on September 22, 2017, 02:41:08 pm »
Business process re-engineering (BPR) is a business management strategy focusing on the analysis and design of workflows and business processes within an organization. It is the practice of rethinking and redesigning the way work is done to better support an organization's mission and reduce costs.

The following are some of the reasons why a business analyst uses the Business Process Re-Engineering :
1. Align Operations with Business Strategy
2. Improve Process Communication
3. Increase Control and Consistency
4. Improve Operational Efficiencies
5. Gain Competitive Advantage
Business Analyst Concepts Discussion / Re: How does a BA model business processes?
« Last post by 111222333 on September 20, 2017, 01:33:22 pm »
There are few steps to be followed by the business analyst for modelling the processes :-

1. Modelling the dependencies

2. Process the execution logic rules
   The process/task specification defines the execution logic that the process implements.
3. Process the non-functional rules
   Every process/task will also have a set of defined non-functional requirements.

4. Process data requirements
   Essentially this is a CRUD (create, read, update, delete) matrix of tasks to data entities. The same argument about applying non-functional requirements to any level higher than the atomic applies to CRUDing.

5. Process the model management : This can be done by following the mentioned
   a. Process decomposition
   b. Identifying Business Processes
   c. Process Specification Management
A business analyst is not the only one held responsible when a project fails. But as he is responsible for gathering the requirements, communicating it to the technical team and is the only medium of all communications, hence he's the first one to be blamed.
So as a business analyst, its very important to gather the requirements correctly and model them so it is easier to find the actual flaw when a project fails.
Workflow is the series of activities that are necessary to complete a task.  The workflow model can be defined as "a visual representation of the flow of work in a business area. Workflow models are used to document how work processes are carried out, and to find opportunities for process improvement."

The construction of workflow models is an essential technique that the business analyst (BA) needs to master. For the past decade, the Unified Modeling Language (UML) has emerged as the  industry standard for the visual representation of analysis and design artifacts. Therefore, it is essential for the practicing BA to understand how workflow models can be represented in UML.
There are various certifications which one can take for business analysis :
1. IIBA cetifications
          -ECBA (Entry Certificate in Business Analysis)
          -CCBA (Certification of Capability in Business Analysis)
          -CBAP (Certified Business Analysis Professional)

2. IVY certifications
          -CITBA (Certified IT Business Analyst)
          -CITBAP (Certified IT Business Analyst Practitioner)
Business Analyst Concepts Discussion / Re: SME
« Last post by 111222333 on September 19, 2017, 05:26:11 pm »
SME : This stands for Subject Matter Expert. SME is a person who is an expert in a particular topic or area.

As SME is an expert in a particular area, he has a greater knowledge and can suggest the various things which can be overlooked while designing or development phase. SME may also have been aware of the problems and can help suggest more feasible solutions in less time thus increasing the performance.

Difference between a SPOC and SME
SME is a person who is an expert in a particular topic or area whereas, single point of contact (SPOC) is a person or a department serving as the coordinator or focal point of information concerning an activity or program.
Business Analyst Concepts Discussion / Re: SDLC Methodology
« Last post by 111222333 on September 19, 2017, 04:53:58 pm »
The type of project and project requirements plays an important role in selecting the type of SDLC methodology and model to be used :-

1. Sequential : When its a small project and all the requirements are very well known, one can use this methodology.

2. Iterative : When the requirements of the complete system are clearly defined and understood. When the project is big.

3. Evolutionary : It is good for large and critical projects where lot of risk is involved.

4. Agile : When the requirements are not clear initially and there is a high chance of Change requests, this methodology can be used.
Business Analyst Concepts Discussion / Re: What is Importance of flow chart
« Last post by 111222333 on September 19, 2017, 03:59:31 pm »
A Flowchart is a diagram that graphically represents the structure of the system, the process flow, algorithm, or the sequence of steps and decisions to be made. For easy depiction various symbols are used (specific shapes and graphic symbols) which are linked by lines and directional arrows. The most commonly known shapes are rectangle or box, rounded box, diamond, circle.
Flowchart is a convenient way to observe the follow the process from beginning to end, it lets improve the work of process, highlight the key elements and detach not essential or even excessive steps. The Flowcharts can represent different levels of detail: High-Level Flowchart, Detailed Flowchart, and Deployment or Matrix Flowchart. They are incredibly useful for programmers when developing the programs of any complexity and on any high level language.
Business Analyst Concepts Discussion / Re: Elicitation Techniques in Business Analysis
« Last post by 111222333 on September 19, 2017, 03:49:51 pm »
Elicitation Techniques in Business Analysis :-

1. Brainstorming : Brainstorming can be done either individually or in groups. The ideas collected can then be reviewed/analyzed and where relevant included within the system requirements.

2. Document Analysis : You may have documentation about your current system which could provide some of the input for the new system requirements. Such document could include interface details, user manuals and software vendor manuals

3. Reverse Engineering : In situations where the software for an existing system has little or outdated documentation and it is necessary to understand what the system actually does, reverse engineering is an elicitation technique that can extract process documents and also when driving the gap analysis for scoping of the migration projects.

4. Focus Groups : A focus group is a means to elicit ideas and attitudes about a specific product, service or oppurtunity in an interactive group environment. The participants share their impressions, preferences and needs, guided by a moderator.

5. Observation : Observing, shadowing users or even doing part of their job, can provide information of existing processes, inputs and outputs.

6. Workshop : Workshops can comprise 6-10 or more users/stakeholders, working together to identify requirements. Workshops tend to be of a defined duration, rather than outcome and may need to be briefly repeated in order to clarify or obtain further details.

7. JAD (Joint Application Document) : JAD technique is an extended, facilatated workshop. It involves collaboration between stakeholders and systems analysts to identify needs or requirements in a concentrated and focused effort.

8. Interview : Interviews of users and stakeholders are important in creating wonderful software. Without knowing the expectations and goal of the stakeholders and users, you are highly unlikely to satiate them.

9. Prototyping : Screen mockups can support the requirement gathering process when introduced at the right time.

10. Questionnaire(Survey) : Questionnaires can be usefu for obtaining limited system requirements details from users/stakeholders, who have a minor input or are geographically remote.
Pages: [1] 2 3 ... 10