Recent Posts

Pages: 1 [2] 3 4 ... 10
11
Business Analyst Concepts Discussion / Re: Elicitation Techniques in Business Analysis
« Last post by 1200111407 on September 16, 2020, 02:18:29 pm »
Elicitation techniques are used to get most of the information about requirements from stakeholders, subject matter experts (SME).
These are proactive in nature as against requirements gathering. Elicitation is a technique which span across all the stages of project lifecycle.
Some techniques are-
1. Brainstorming (Brainstorming works by focusing on a topic or problem, and then coming up with many radical solutions to it. This technique is best applied in a group as it draws on the experience and creativity of all members of the group)

2. Document analysis (Document analysis is a means to elicit requirements of an existing system by studying available documentation and identifying relevant information. Document analysis is used if the objective is to gather details of the "As Is" environment such as existing business rules)

3. Focus groups (A focus group is composed of pre-qualified individuals whose purpose is to discuss and comment on a topic. This is an opportunity for individuals to share their own perspectives and discuss them in a group setting.)

4. Interface analysis (Interface analysis helps to clarify the boundaries of the system. It distinguishes which system provides specific functionality along with the input and output data needs.)

5. Interview (An interview is a systematic approach to elicit information from a person or group of people in an informal or formal setting by talking to the person. In an interview, a business analyst formally or informally directs his/her questions to: a stakeholder / a subject-matter-expert / a potential user to obtain answers that finally take the shape of requirements)

6. Observation (Observation is a means to elicit requirements by conducting an assessment of the subject matter expert's work environment.)

7. Prototyping (aims to uncover and visualize interface requirements before the application is designed or developed)

8. Survey / Questionnaire (A survey is a means of eliciting information from many people, anonymously, in a relatively short time. A survey can collect information about customers, products, work practices and attitudes. A survey is often referred to as a questionnaire.)
12
Business Analyst Concepts Discussion / Re: Types of Companies and Projects
« Last post by 1200111407 on September 16, 2020, 02:16:48 pm »
Types of  Companies: There are two types of companies
 Product based companies: These companies are used to develop products , for that they need IT department to make the product, there are some  companies that worked on the product based
                                                                            1. IBM
                                                                            2. SAP
                                                                         
 Service based  companies: These are the companies which is used to give the services to the products are called as service based companies
                                                                             1. Accenture
                                                                             2. TCS
Types of projects: There are two types of projects
                           a. Fixed bid projects: Budget and time will be fixed
                           b. Billing projects : Resources working in the project will be billed to the client on the hourly basis.
                                                       
13
Business Analyst Concepts Discussion / Re: What are the Non Functional Requirements
« Last post by 1200111407 on September 16, 2020, 02:13:50 pm »
Non - Functional requirements shows the Behaviour of the system.
Non-functional requirements are also known as quality or supplementary requirements. They capture conditions that do not directly relate to the behavior or functionality of the solution. These can include requirement related to capacity, security, speed, availability and the information architecture and presentation of the user interface. Non-functional requirements may also describe aspects of the system that don't relate to it's execution, but rather to it's evolution over time (e.g. maintainability, extensibility, documentation, etc).
 
14
Business Analyst Concepts Discussion / Re: What is Importance of flow chart
« Last post by 1200111407 on September 16, 2020, 02:10:45 pm »
Flowcharts are the Graphical representation of program.
Flow chart models the entire business case flow whereas activity diagram shows the system involved.
Flowcharts are a means to help design a program and figure
out what the program need to do how to do it before you sit
down to code.
15
Business Analyst Concepts Discussion / Re: What is Importance of flow chart
« Last post by 1202408606 on September 07, 2020, 09:49:35 pm »
a flow chart is a pictorial represtation of the documentation. flow chart gives the pictorial view which is more easy to understand the process  within less time
The flowchart lists each step necessary to perform a process. The flowchart helps a designer remove unnecessary steps in a process, as well as errors. The flowchart should only include the steps that are requirements to reach the endpoint of the process.
16
Business Analyst Concepts Discussion / Re: What are the Non Functional Requirements
« Last post by 1202408606 on September 07, 2020, 09:06:29 pm »
Nonfunctional Requirements (NFRs) define system attributes such as security, reliability, performance, maintainability, scalability, and usability. these describe the environmental conditions under which the solution must remain effective or qualities that the system must work
17
Business Analyst Concepts Discussion / Re: Scrum
« Last post by 1202408606 on September 07, 2020, 08:57:50 pm »
scrum is a development methodology used to manage the software projects. the team is self directed the major roles of scum are
1.scrum team
2.product owner
3. scrum master
18
Business Analyst Concepts Discussion / Re: BA Role
« Last post by 1202408606 on September 07, 2020, 08:49:59 pm »
BAs understand the functionality the system is supposed to deliver and as such, have the knowledge needed to validate the system. The fact that a system has been built to specification does not make it automatically acceptable. UAT helps stakeholders to determine whether the system can be put to use in real-life business scenarios or not.
19
Business Analyst Concepts Discussion / Re: Types of Companies and Projects
« Last post by 1202408606 on September 07, 2020, 08:45:06 pm »
IT companies are broadly classified into two categories
1. product based company-  is a company that makes products that might be/might not be related to software but they need IT deparment to make to make the product.example samsung ,adobe.
2. service based company-is a company that provides that provides software products and services to anyone who asks for it and have to pay for it. example TCS
PROJECT TYPES
1.fixed bid projects- both the budget and time will be fixed .
2.billing projects-resources working in the project are billed to the client on the hourly basis.
20
Business Analyst Concepts Discussion / GAP Analysis
« Last post by 1200407706 on August 24, 2020, 04:43:43 pm »
GAP Analysis:

BPM: Identifying the problem areas / Areas of limitation / Improvement
area
Pages: 1 [2] 3 4 ... 10