Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

BA > Overview > Flashcards

Overview Flashcards

1
Q

A business analyst real name should be what?

A

Business Systems Analyst

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Two types of systems BA works on:

A

External systems- customer access

Internal systems- employee access

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The three types of projects or systems a BA can work on:

A

New System, System Enhancement(90%), System Reengineering

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Skills needed to be a excellent BA

A 
Interpersonal skills
Communication
Listening skills
Ability to ask questions
Good note taker
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Two teams BA work with and their roles in the BA process:

A

Business Team: communicate the need &

IT team: execute the changes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

BA create document requirements. One of these three depending on business preference and which one dose NOT follow after a BRD:

A

FRD
Use Case
User Stories(No BRD)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

BA workflow once project sponsor communicates a new project(assuming not agile)

A
  1. BRD which defines scope of project
  2. Review BRD with business owner and get sign off
  3. Based on BRD, PM creates
    Project charter(timeframe & budget)
  4. Project kick of meeting
    which triggers SDLC
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Three types of environments

A 
Sandbox environment(test),
Staging environment(copy of production),
Production environment(live)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

What do you think the role of a BA is?

A

My role as a BA is to understand the business, understand the requirements and become a subject matter expert for the team. I see myself as power user of the system. In other words to know the system in and out since I wrote the requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

If given an opportunity to work with us, how would you get up to speed?
If introduced to a new business domain, what steps would you take to understand the domain?

A

I would start understanding the new business domain by reading existing process documents
so that I can familiarize myself with the “AS-is-business” processes. I would also make sure that I
understand all the business jargons associated with the project scope and lastly make sure I understand
the current system in a Sandbox Environment. While I do this, I would compile a list of questions that may
arise and would like to get them answered by talking to a designated mentor.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is the SDLC process? Stages

A

Requirements gathering(speak with SMEs- JAD)
Analysis(From JAD session we create FRD, Use Case, or User Stories(Based on Business Rules, Functional & UI requirements)
Design(System Design by Sys Arc)
Implementation(Developers write code and DBA develops database)
Testing(QA and BA testing)
Deployment(System goes live)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the characteristics of a good requirement?

A

A good requirement has the following three characteristics:

  1. Is documented using simple verbiage and is easy to understand.
  2. Is technically feasible and
  3. Is testable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

How would you define a use case?

A

A use case is a description of a functionality from an end users perspective. It identifies every scenario
that may arise while completing the functionality. For every scenario identified it documents the user action
as well as the received system response

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What exactly is requirements gathering in SDLC?

A

Requirements gathering is done during JAD sessions when a BA speaks with subject matter experts to understand how will the business scope with be executed

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

How would you conduct a JAD session?

A

I would begin by creating a JAD session agenda and send to JAD participants. Introduce the participants and discuss goals and objectives. Review any open questions from previous JAD sessions if any. Start brain storming session and identify the following for every business requirement:
business rules, functional requirements, and UI requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are business rules?

A

Business rules are business constraints that arise because of : operating procedures created by the business.

17
Q

What are functional requirements?

A

a function that can be done in a system (i.e edit pmts, download docs) that describes step by step functionality

18
Q

Non-Functional requirements include security, scalability, and performance requirements. There is one more. The only non Functional Requirement BA gather:

A

User Interface Requirements -the design of what the screen will look like and UI elements
(buttons, text box, radio button, check box, hyperlink, command button) - Screen mock-up/Wireframe

19
Q

How would you define a legacy system?

A

An old and outdate system that has all three environments(sandbox, staging, production)

20
Q

The role of a BA in Waterfall and RUP

A
  1. Define the scope of the project by creating a BRD
  2. Understand the As-Is Busines related to the scope of the project
  3. For every business requirement documented in the BRD, conduct JAD sessions to identify:
    a. Business Rules
    b. Functional Requirements
    c. UI requirements

Do one of the following two:

create FRD, add wireframes, activity diagrams & state diagrams
or
create use cases, add wireframes, use case diagrams, activity diagrams and state diagram

21
Q

The role of a BA in Agile Scrum (No BRD/NO FRD/No Use Case)

A
  1. Create Product Backlog (mainly done by SME’s)
  2. Understand As-Is Business
  3. Conduct Business Prioritization Meeting to define the scope for the next release
  4. Conduct JAD sessions to identify Business rules, functional requirements & UI requirements
  5. Document USER stories, and wireframes, activity diagrams, and state diagrams (if needed)
  6. Conduct ‘Sprint Planning meeting’ on 1st day of the sprint
  7. Conduct ‘Sprint Review Meeting’ also known as Spring Demo) on the last day of the sprint
  8. Conduct UAT during the last Sprint
  9. Document Release Notes for every Release
  10. Attend Scrum meetings on a daily basis
  11. Attend a retrospective meeting on the first day of a new release
22
Q

How do you manage requirement change?

A

In the event of a change of a requirement after the requirement has been signed off, I would turn
‘track changes’ on in my requirement document, update my requirements document with the proposed changes
and sent it across to the change control board ( composed of the PM, Sys Arch, a Sr.Dev, a Sr.DBA, and a Sr.QA)
the control board determines if changes are technically feasible and responds back with
time and budget for implementing the proposed change

23
Q

What is your knowledge or experience on Agile?

A
  • I am familiar with Agile scrum approach which would typically have a release on a monthly basis
  • A typical sprint would consist of two work weeks, which would make the release consist of two sprints
  • I would attend scrum meetings on a daily basis to provide a status update of what I did yesterday,
    what I plan to do today, and identify roadblocks
  • On the first day of a new release I would attend a retrospective meeting to identify the things
    we did well in the previous release, things we did not do well in the previous release, and
    identify action items to resolve them in this release.
    -On a monthly basis I would conduct business prioritization meetings with the SMEs to define the scope of the upcoming release
    -On the first day of a new sprint I would conduct a sprint planning meeting with the development team
    to review the user stories to be assigned that sprint
  • I would also assign story points to the user stories based on the backlog of the development team *
  • The last day of the sprint I would conduct a sprint review meeting with the SMEs to review User Stories
    that were delivered for that sprint
  • I would conduct a User Acceptance Testing (UAT) with SMEs toward the last sprint with the SMEs
  • For every release, I would document release notes, and provide a summary of changes to be introduced for
    that release
24
Q

Agile Scrum has several events. Name a few:

A 
1	Business Prioritization Meeting
2	Scrum Meeting
3	Retrospective Meeting
4	Sprint Planning Meeting
5	Sprint Review / Demo Meeting
25
Q

How do you conduct UAT?

A
  • Once I get a signoff from the QA team I shall schedule a date and time for conducting UAT
  • I shall confirm with SMEs if they want me to provide them with test cases or else they shall conduct
    ad hoc(random) testing. Still providing the test data.
    -During UAT would make myself available to the SMEs so that I can answer any questions that may arise during UAT
26
Q

What is traceability and its importance?

A

Traceability is mapping a business rule or a functional requirement or a use case to the business requirement is was derived from. Traceability helps identify the impacted business rule or a use case with a change in a business requirement
Its not as in important in Agile since its more flexible in making changes.

27
Q

What is the difference between a Use Case and a User story?

A

A use case is more like a description of a function from a user perspective. It would have the precondition, postcondition, a trigger, and three flows: the primary flow(which is a happy day scenario and defines the best way in completing the functionality), the alternate flow(any flow beside the primary flow, in which the scenario can be completed. and exception flow which is the failure scenario. The exception flow is a hard stop and the use case is not completed.
WHERE as, in Agile you define role, a goal, the benefit and acceptance criteria. A user story - is a tool used in Agile software development that captures a description of a software feature from the perspective of end-user goal
it is also referred as the smallest unit of work in an agile framework.

28
Q

How would you create your acceptance criteria?

A

I would write it in a format what are the things the tester would need to test the application and I would add wireframes for reference.

29
Q

Which software do you use to create your wireframes?

A

I use Axure. It’s so simple and straight forward. It’s like my canvas. Instead of paint selections, I have buttons, drop list, radio, and ability to lock my screen and create links between the different pages.

30
Q

Which UML diagrams have you used and what’s the purpose for them?

A

Helps developers better see the system they are trying to create. The purpose of visually representing a system along with its main actors. Reveal unforeseen scenarios that may not have been addressed during requirement gathering.

31
Q

RWhen you are creating an activity diagram, what symbol would you use to indicate a decision point?

A

A triangle called a decision box

32
Q

How would you differentiate a good BA from an excellent BA?

A

Someone who owns the requirements and understands the goals and fills the shoes of the SMEs themselves.

33
Q

What would you say are good JAD session questions?

A

Open-ended questions asked in a logical sequence (i.e. what comes next in the ordering steps of new user registration)

34
Q

What does UML stand for and used for?

A

Unified Modeling Language. One common language of drawing

35
Q

Activity Diagram also known as? And what is it exactly or what is it used for?

A

Swimlane diagram. Used to show business process workflow. Swimlane diagram documents activity and decision by actors by sections

36
Q

What are use case diagrams and activity diagrams used for?

A

both diagrams are for describing behaviors

37
Q

What is a use case diagram?

A

use case diagram shows the interaction between the actors, the use case and the relationship between use cases

38
Q

Recap of BA activities in QA:

A
  • Write Test Cases
  • Perform Manual Testing and create defects, if needed
  • Conduct weekly bug triage
  • Coordinate User Acceptance Test(UAT)
39
Q

Question to ask for UI elements(4)

A

Is this a required field?
What type of data is typed in by the user?
What is the minimum/maximum character length?
Is there a default selection?(except for Gender)

BA (1 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions