Brainscape's Knowledge GenomeTM

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


See full index

Semester 5 > WAABA > Flashcards

WAABA Flashcards

1
Q

What is the role of a business analyst and their primary job?

A

Their role is to be a mediator between the business (or user) and IT.

Their primary job is to understand the business’ (or the user’s) needs and translate it to something a developer can understand.

The different tools we use are different means to communicate the needs.

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

What are the 5 steps in the business analyst process?

A
  1. Collect information using documentations, interviews and observations.
  2. Start modelling processes and business rules.
  3. Understand the new processes and model them through interviews and workshops
  4. Document the final requirements.
  5. Talk to a developer how requirements should be implemented in a solution.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the sub processes to the 1. step in the BA process - collecting information?

A
  1. Identify relevant stakeholders.
  2. Look at current documentation of processes and existing systems.
  3. Do interviews with stakeholders and observations of users.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are the sub processes to the 2. step in the BA process - Analyze and modelling?

A
  1. Model as-is processes
  2. Get an overview over the current problems with the as-is situation.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are the sub processes to the 3. step in the BA process - to-be processes?

A
  1. Do interviews or workshops to understand the new processes.
  2. Model the new to-be processes.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are the sub processes to the 4. step in the BA process - writing final requirements?

A
  1. Identify the gap between the as-is and to-be processes.
  2. Write the requirement specification.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the sub processes to the 5. step in the BA process -

A
  1. Sparring with a developer how requirements should be understood and realised.
  2. Continuous sparring with the business and user, when unresolved issued comes up.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the 3 most common context a business analyst can work in?

A
  1. Organization got their own systems and develop their own systems.

In this context the BA work agile with the key stakeholders and the developers.

  1. Privat organization needs external system with external development and implementation.

The BA have to make very specific requirements with the business and user.

  1. Public organization need external system

The BA has to follow legal requirements and there is limited communication with supplier.

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

What is the output of the business analysis?

A

When a BA conduct a business analysis they will deliver a requirement specification.

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

What are key skills required by a business analyst?

A
  1. Stakeholder engagement and collaboration
  2. Analytical thinking
  3. Innovative thinking
  4. Technical literacy
  5. Business knowledge and process understanding
  6. Value creation
  7. Problem solving
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is a project charter and the purpose of it?

A

It’s a document that formally authorizes the existence of the project and provides a reference source for the future how the project is carried out.

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

What are the main components of a project charter.

A
  1. Goals
  2. Costs and benefits
  3. Scope
  4. Risks
  5. Stakeholders
  6. Dependencies
  7. Technical requirements
  8. Milestones
  9. Budget
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is a project scope?

A

It outlines the work that needs to be done to accomplish the project goals and establishes the project’s boundaries by specifying what is included and excluded from the project

Eksample:

The scope is to develop a program that automatically translates verbal sentences from English to Russian.

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

What are the 3 things you try to balance when working with scope?

A

The scope:
* features
* functionality
* performance
* quality

Cost:
* Ressources
* Budget

Time:
* Schedule
* Production rate

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

What is scope creep?

A

Scope creep refers to the uncontrolled expansion or addition of features, requirements, or tasks to a project beyond its original scope. It occurs when there is a continuous and unauthorized growth of project deliverables, objectives, or expectations, often without corresponding adjustments to the project’s timeline, budget, or resources.

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

What are different types of stakeholders?

A
  1. Partners
  2. Suppliers
  3. Regulators
  4. Employees
  5. Managers
  6. Owners
  7. Competitors
  8. Customers

Keep in mind the stakeholders has varying importants. A business owner is usually more important than a pizza man, but they might both be a stakeholder.

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

How do you rate how important a stakeholder is?

A

You do this with the power/interest matrix.

Low power/ Low interest:
You shouldn’t spend much effort on these stakeholders.

Low power/ High interest:
Show consideration in their interest and keep them informed.

High power/ Low interest:
Meet their needs and keep them satisfied.

High Power, High interest:
These are key players and you should engage closely with them.

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

What are the 4 different stakeholder responsibilities?

A
  1. Responsible - The one who is responsible for a task gets done
  2. Accountable - The one who gets in trouble if a task is not done
  3. Consulted - The one who should be consulted and helped in some way.
  4. Informed - The one who should just be informed about progress etc.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

What is the difference between direct and indirect risk?

A

Direct risk:

The project has a large degree of control

Indirect risk:

The project has a little or no control

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

How do you evaluate a risk?

A

You evaluate a risk based on what are the chances that the risk occurs and if it does occur how severe is the consequences?

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

What are 3 main ways to respond to a risk.

A
  1. Try to avoid it
  2. Try to mitigate it
  3. Just accept it.
22
Q

What steps are there in the information gathering process?

A
  1. Collect information
  2. Analyze documentation and models. You will find new questions.
  3. Collect more information and validate documentation and models.
  4. Repeat step 1,2 and 3 until you got sufficient information and validation.
23
Q

What techniques are there to collect information from relevant stakeholders?

A
  1. Interviews
  2. Observations
  3. Workshops
  4. Focus groups
24
Q

How do you document and model the things you’ve analyzed?

A

Experience map - Visualizes qualitative data. What actions to perform and what that actions makes that person think, feel and pain point.

25
Q

What is user centered design and the 4 steps in the method?

A

User centered design is a method that ensures that a solution is designed and developed with the user in focus.

  1. Understand context of use
  2. specify user requirements
  3. Design solution
  4. Evaluate solution against the requirements and it meets up to the things defined in step 1,2 and 3.
26
Q

What are you trying to understand in the 1. step of user centered design (understand context of use), and which modelling are appropriate to use?

A

You are trying to understand the user’s need and the task the user is performing in the context you’re working with.

methods:
* Persona
* as-is scenarios
* User scenarios
* Storyboards
* Context diagram

27
Q

What is a persona?

A

A persona is a way to model the different users. This includes their, need, tasks, challenges etc.

28
Q

What is a as-is scenario and user scenarios?

A

They are scenarios that describes a user and that users tasks and challenges in focus.

You usually will model as things are today with all the pain points and then a future to-be scenario how you want it to be.

29
Q

What is a storyboard?

A

In a storyboard you visualize the user and the context (usually as a cartoon), and not only use text.

30
Q

What is context diagram

A

The context diagram visualize how the new system interacts with stakeholders and new systems.

This is usually by drawing which entities produce which data and who interacts with this data.

31
Q

How can you model data and how it’s used?

A
  1. Context diagram
  2. Data flow diagram
  3. E/R diagram
32
Q

How do you visualize and model business processes, rules and de

A

BPMN

33
Q

What is a data dictionary?

A

A data dictionary is a collection of all the data that is used in the system. This includes:

  1. Data name
  2. Definition
  3. Purpose of the data
  4. Data type
  5. Relation to other data
34
Q

What is a state diagram

A

A state diagram shows different states an entity in an E/R diagram can be in. For instance and invoice be unpaid and paid.

35
Q

What is a sequence diagram?

A

In a sequence diagram you can show how different events tricker in a use case, and send messages in between different components like customers and the system.

36
Q

What are the 5 steps in the BPM lifecycle

A
  1. Process discovery
  2. Process analysis
  3. Process redesign
  4. Process implementation
  5. Process monitoring
37
Q

What is an Issue log?

A

An issue log is a way to track ongoing and closed issues.

It usually contains:
* Issue no.
* Issue name
* Type
* Priority
* Stakeholder
* Relevant comments.

38
Q

What is an value-added analysis, and the 3 different categories?

A

You go through each step in a process and ask the question “does this step contribute to the direct value for the customer or the business?

Categories:

Value adding: Gives direct value to the customer.

Business value adding: Gives direct value to the business.

Non-value adding: Doesn’t produce value for either customer or business. These steps should be removed if possible.

39
Q

What is a waste analysis, and the 3 different types of waste?

A

In a waste analysis you try to identify steps in the process, where waste occurs.

Types:

Move:
Waste that is related to transportation and motion.

Hold:
Waste coming from waiting and too much work-in-progress that is not being completed.

Overdo:
Waste coming form doing more than necessary to deliver value to customer/business. Defects, overprocessing and overproduction.

40
Q

What is a flow analysis?

A

You calculate the average cycle time for a whole process to complete. This is done by figure out how long each task and decision takes to complete in a process.

By improving the time you can improve both cost and average time to complete a process.

41
Q

What do you describe in the requirement specification?

A
  1. The functional requirements.
  2. non-functional requirements like usability and security.
42
Q

What is a gap analysis?

A

In a gap analysis you identify the difference between the current state (as-is) and the future state (to-be). The difference is the gap.

You look at the as-is and to-be processes, issue lux, data analysis and describe the gap.

You usually make user stories that describes functionality that eliminates the gap when solved.

43
Q

What is the most common way to describe functional requirements?

A

User stories and accept criteria.

44
Q

How is a user story structured?

A

As a <usertype> I want to < to perform an action> so that I can <purpose>.</purpose></usertype>

Keep in mind when you setup user stories you also specify the data needed for this user story.

45
Q

What is an accept criteria, and what elements are there in an accept criteria?

A

Accept criteria is a way to describe when a functional requirement is fulfilled. This is done by making sure the user story works as intended and satisfies the customer.

The criteria has to be testable and the test resultat has to be either the criteria is fulfilled or is not fulfilled.

There can be multiple criteria for one user story.

46
Q

What is an requirement analysis?

A

When you have described all user stories and the associated accept criteria you do a requirement analysis.

In a requirement analysis you analyze the identified requirements by asking following questions.

  • Are there any of the user stories, that is too large? Do they have too many accept criteria and can be split up in more user stores?
  • Are there any of the user stories that is more or less the same and has same accept criteria?
  • Are any of the user stories conflicting?
47
Q

What the different types of requirements?

A
  1. Business
  • General
  • Constraints
  • Policies
  • Branding
  • Cultural
  • Technical
  • Hardware
  • Software
  • Internet
  1. Solution
  • Functional
  • Data entry
  • Overview
  • Retrieval requirements
  • Non-functional
  • Security
  • Usability
  • Accessibility
  • Backup
48
Q

What is MOSCOW prioritization of requirements?

A

It’s a way to prioritize requirements based on 4 categories:

  1. Must have
  2. Should have
  3. Could have
  4. Won’t have
49
Q

What is an Epic?

A

An epic is a larger task that consist of multiple user stories.

An epic could be “Approval of project” and have user stories associated with budget, resources, descriptions, hiring etc.

50
Q

What is a prototype and how can you use it?

A

A prototype is a visualization and example of how the final version could look like.

You can use it to validate and visualize the requirements to a solution.

51
Q

What elements does a reading guide to a requirement specification contain?

A
  1. Introducing the reader for the project. Background, scope, goals and descriptions.
  2. Functional requirements.
  3. Data
  4. Non-functional requirements.
  5. Other things like methods used or description of terms
52
Q

What is usually in the Appendix of a requirement specification/reading guide.

A
  • models of processes (as-is and to-be)
    *Prototypes
  • Data models
  • Other illustrations.

Remember to reference requirements to the relevant appendix.

Semester 5 (2 decks)

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