Assessment Flashcards
(195 cards)
1
Q
What are the two main settings that business analysis is performed in?
A
Project and Pre-Project
2
Q
What is necessary before a solution can be implemented to fix an enterprise problem?
A
The organisation must define the need in a detailed manner.
3
Q
What might be an element of the solution we recommend as Business Analysts?
A
Systems
System Features
Business Processes
Policies
Training
4
Q
What is one of the ways an organization can be hurt by not responding to change?
A
Costs can increase substantially if the organization doesn’t respond to change.
5
Q
True/False: It is important for an enterprise to understand all of the needs of its stakeholders, even if there is no solution that meets all those needs.
A
True, Unfortunately, sometimes a single solution will not satisfy all stakeholders. In those cases, Business Analysts must determine what the best solution is, keeping in mind the various needs.
6
Q
How might a Business Analyst learn about an organization’s problem?
A
Observing a single stakeholder to see how they perform a task
Interviewing a group of stakeholders to learn how a company process work
Surveying customers to learn about their preference and needs
Modelling an organisational process using a flowchart
7
Q
What is a requirement?
A
A usable representation of a need
Documentation of value that the solution must provide
A document (or set of documents) tat specify the solution in detail
Requirements server as the blueprint for moving from the current state to the future state.
8
Q
BABOK refers to requirements as being usable representations of needs. What does “usable” mean in this context?
A
That the team members who consume (or use) the requirements will consider them easy to use.
9
Q
True/False: Only people with the job title of Business Analyst are allowed to do business analysis work.
A
False
10
Q
Which of the following roles is least likely to perform business analysis?
A
A sales person
11
Q
True/False: Stakeholders are very important to the business analysis process.
A
Stakeholders are the primary source of requirements, and without them, nothing valuable will get done.
12
Q
What is the IIBA definition of Business Analysis?
A
The Practice of enabling change in an organisational context, by defining needs and recommending solutions that deliver value to stakeholders.
13
Q
What is a stakeholder?
A
Anyone impacted by your requirements in some way
14
Q
If you create an inventory system used by workers in a warehouse at your company, are you downstream or upstream from those workers?
A
Since you create the system, the warehouse workers depend on you. Therefore, you’re upstream from them.
15
Q
Why is it important to manage your upstream?
A
You are dependent on their work, and you can’t get yours done unless they do well with theirs.
16
Q
What is the role of the Project Manager?
A
Deliver the project. They get it done.
17
Q
What is not a typical project constraint?
A
Team. In project-speak, team members are “resources.”
18
Q
Why is the Project Manager an important requirements stakeholder?
A
The PM is responsible for the delivery of the project, and requirements are essential to successful delivery.
If requirements will be early or late, this can impact the project’s schedule and costs substantially( for good or bad)
If requirements are of poor quality, the project quality is likely to suffer.
19
Q
What is a good way for you, the Business Analyst, to help your Project Manager?
A
Let them know if you encounter a significant issues or risk. This is very important. And don’t worry about remembering – your PM will likely keep reminding y
20
Q
What is not a typical problem of a developer?
A
A lack of meetings is probably only a problem for salespeople, certainly not developers.
21
Q
When is a good time to meet with developers?
A
At the beginning of the day. It’s best to meet with them at the beginning or end of the day, so they have a block of time during the day that they can focus.
22
Q
What is a good way to let developers know that you expect a requirement to change?
A
Document the expectation of change alongside the requirement.
Mention the expectation of change in your e-mail to them
Verbally tell them
23
Q
What is the role of a QA Tester?
A
Quality Assurance - Make sure the project of high quality
24
Q
What is the definition of a defect?
A
Any difference between the product requirements and the project implementation.
25
What is a defect?
A bug
A problem with the project
Any difference between the product requirements and the project implementation
26
When is the best time to engage testing professionals on a project?
Early on in the project - this way the testers can familiarize themselves with the requirements and provide their feedback
27
Why is it important for BAs to devote time to ensuring testers understand the requirements?
They do not test with incorrect assumptions.
Can efficiently create their scripts.
Do not complain to BA that they don't have enough support
28
Why is it a good idea to get to know the bosses of the development and testing teams
Builds their trust, it is very important among project teams and their management.
29
Why is it important to build a solid working relationship with your project sponsor?
They will contribute the majority of the business requirements
To ensure the product meets the needs of all its stakeholders
30
What if you are an expert in the area you are building a product for… Do you still have to engage the product’s users?
You always have to engage the people who will use your product.
31
What if your end users complain a lot and annoy you… Do you still have to engage them?
You always have to engage the people who will use your product.
32
What if your end users are dumb and have a lot of stupid feedback… Do you still have to engage them?
You always have to engage the people who will use your product.
33
What is the most likely outcome if you build a product without adequately involving its users?
Users won't like the product and pay for it. They will complain and management will give you a hard time.
34
When stakeholders have conflicting needs, what is the best strategy with which to tackle the problem?
Try and find a solution that works for all stakeholders
35
When should you perform a Stakeholder Needs Analysis?
Whenever there is a conflict among stakeholder requirements
36
Why is it important for us to act as the voice of the customer in internal debates?
Often stakeholders have a narrow view of their own departments needs.
Customers don't have a representative.
Customers are the most important stakeholders, and must be represented by someone who understands them
37
What is PLC ?
Product
Life
Cycle
38
What is SDLC?
Service
Design
Life
Cycle
39
What are the stages of PLC?
Initiation
Planning
Execution / Control
Closing
40
What are the stages of SDLC?
Analysis
Design
Development
Testing
Implementation
41
What stage (sub process) of the PLC does the SDLC fit in?
Execution / control
42
During which phase of the (waterfall) SDLC is requirement gathering performed?
Analysis
43
What is not a phase of the SDLC?
Redevelopment doesn’t mean anything
44
During which phase of the (waterfall) SDLC is the product released to customers/users?
Implementation. The product is released either fully (wide release) or to a subset of customers/users (pilot) during the implementation phase.
45
What are the defining characteristics of a waterfall SDLC?
A Sequence of phases and requires one phase is completed before the next one starts.
46
What problems would be considered most impactful in a waterfall/V-model SDLC?
A missed business requirement found during project acceptance.
47
What is the defining characteristic of an iterative SDLC?
Multiple iterations of development and testing.
48
In your estimation, which category of SDLC will result in a product more in line with users’ expectations?
Iterative. Since users and/or their representatives see versions of the system before it is released, they have the opportunity to give input on it.
49
What is the Agile Manifesto?
Individuals and iterations over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
50
Approximately how many Agile Methodologies are there
24,
Scrum, Scrum XP Hybrid, custom hybrid, Kanban,Scrumban, feature-driven development, Extreme programming XP, Lean
Agile modeling, AgileUP (unified Process), Dynamic systems development method
51
What is the most common Agile Methodology?
Scrum, over 50% use it
52
What is the Ideation phase of the Product Life Cycle all about?
Coming up with high-level idea of what the product should be and making sure customers will buy it.
53
What is the Development phase of the Product Life Cycle all about?
Analysing, designing, developing, testing and implementing the new product
54
In which two phases do BAs do the most work?
Development and Ideation
55
What is the BABOK definition of a Requirement?
A requirement is a usable representation of a need. Requirements focus on understanding what kind of value could be delivered if a requirement is fulfilled. The nature of the representation may be a document (or set of documents), but can vary widely depending on the circumstances.
56
What is the Requirements life cycle?
Drafted
Validated
Baselined
Implemented
Managed
Retired
57
What does it mean when you say that a requirements document is “baselined?”
The requirements in the document are considered frozen. These can then be implemented and tested. Any changes to them will require significant review and approval.
58
What do you think will happen if requirements are not properly managed after the project is done?
Requirements Docs are lost so the users don't know how the system works
Requirements Docs are not updated
Management will be annoyed as you can't justify what has been delivered
59
What are the 3 phases of the Requirements Gathering Model?
Form
Transform
Finalise
60
What is the goal of the first phase of RDM?
To form a draft of your requirements
61
What are the three key elements of a documented requirement?
Description
Source
Rationale
62
What is a good reason to document the requirement source?
So you know who to approach for more information
63
What is a good reason to document the requirement rationale?
It is useful later to prioritise the requirements with project sponsor.
Help find additional missing requirements.
Identify incorrect stakeholder assumptions.
64
What might happen if a requirement isn’t clear?
Test team will write cases according to their misunderstanding of the requirements, leading to rework and project delays
65
What requirements is implementable?
one that is realistic and achievable.
66
How often should you conduct walk-throughs of your requirements with stakeholders?
At least once per project.
67
What are the 6 attributes of good requirements?
Clear
Complete
Applicable
Prioritised
Implementable
Testable
68
What are the 4 types of requirements?
Business
User
Functional
Non Functional
69
What requirement types is the highest level?
Business, all the other requirement types trace back to the user requirements in some way.
70
What is the source of most business requirements?
Business requirements are most often derived by some strategy of the organization.
71
72
Where do user requirements usually come from?
Users - Both internal & External
73
Why is it important to document the parent of a user requirement?
To understand what business requirement the user requirement belongs to in the requirements hierarchy.
74
What should you do if a user requirement doesn’t have a clear parent business requirement?
Make sure that you are not missing any business requirements. Tracing user requirements to business requirements helps you ensure you’re not missing anything higher up.
75
What do business and user requirements describe?
What the product will do.
76
What do Functional requirements describe?
How the product / system will do it / behave
77
Where are Functional requirements derived from?
Business and / or user requirements.
78
What are functional requirements?
Requirements that specify how the system / product should behave
Requirements that elaborate how higher-level requirements should be implemented.
The most detailed requirements that we deal with.
79
TRUE/FALSE: A functional requirement can have a business requirement as its parent.
True. A functional requirement can have either a business requirement or a user requirement as its parent.
80
THINK: Which of the requirement types that we have covered so far would have the MOST impact on the project if the BA fails to discover and document it?
Missing a business requirement means that you have missed a MAJOR priority of the organization.
81
What do Nonfunctional requirements describe?
The Qualities of the system. They cover the organisational needs that don't relate to functions.
82
Name some categories of Nonfunctional requirements.
Data Privacy
Disaster Recovery
Legal / Compliance
Security
System Availability
System Performance
Usability
83
What fields should you include on a requirements table?
Req ID (F - Functional, NF - NonFunctional, B - Business, UR - User)
Category
REquirement
Rational
Source
Parent
84
Why is it important for the Business Analyst to be very focused on finding nonfunctional requirements?
No one else usually looks for them. It is rare for stakeholders to think of the quality needs of the product, and it is up to us to make it happen.
85
What is wrong with the following nonfunctional requirement?
“System must act in accordance with FDA Rule US-FDA-2010-079.”
It is not complete as it doesn't state what the rule is.
86
When using resources what 3 things
Ensure the information is reliable and upto date
Bring in an expert when necessary.
Keep a stakeholder as your requirements source, this can be a BA from an old project.
87
What value does pre-existing requirements documentation provide?
It tells you how the system / product works
Tells you which projects your organisation has run and why.
Contains a list of useful stakeholders
Contains requirements that often should be leveraged in your project.
88
What are the challenges associated with pre-existing requirements documentation?
It can be be out of date.
It can be hard to understand if it relies heavily on industry or technical jargon
It maybe poorly written or structured.
89
What should you do before an interview?
Find the right stakeholders
Start with the sponsor
Define your goals for the interview
Setup the meeting
Choose the right
setting / environment
Learn about your stakeholder, name, title, responsibilities
90
Which stakeholder is the best to start your interviews with?
The project sponsor
91
Why do we use open-ended questions in interviewing?
We need them to do the vast majority of the talking, so we can understand them better as they can give you more input.
92
What is the best way to make sure you understand what your interviewee is saying?
Recap what they are saying, give them the opportunity to correct / confirm your understanding.
93
What is the main benefit of group interviewing?
Getting to speak with many stakeholders at once
The group dynamic of seeing stakeholders interact with each other
When one stakeholder proposes a point, other stakeholders will give their input.
94
Why is it important for you to bring someone to take notes in a group interview you are facilitating?
Facilitation takes alot of work, it's difficult to facilitate the decision and take notes at the same time.
You are likely to miss requirements.
You may lose control of the meeting.
95
Why is it best to have a single document that contains all requirements for a project?
It’s a bad idea to have requirements proliferate across multiple documents.
1) readers may miss requirements
2) less work to create and maintain
96
What are the 4 parts of a user story
Role
Requirement
Rationale
Acceptance Criteria
97
TRUE/FALSE: Requirements are important in agile projects.
Requirements are important in agile, just not as important as the working product.
98
What is a user story?
A common language expression of what the users needs and why
99
Who manages the Product Backlog?
Product owner
100
Who manages the Sprint backlog
Team
101
"Generally, all analysis gets beyond description and into examination and explaination."
102
Definition of analysis?
A careful study of something to learn about its parts, what they do, ad how they relate to each other
103
What two reason you need to analyse?
1) Understand the business need
2) make sure we are providing the best solution
104
What is decomposition?
Decomposition is breaking something down into its parts.
105
What is additive analysis?
Adding a component to a complex to understand its role
106
What is subtractive analysis?
Removing a a component to a complex (consisting of many different and connected parts)to understand its role
107
What is the definition of Gap Analysis
A component-wise analysis of a complex (consisting of many different and connected parts) to understand its difference from another complex.
Eg,
Current and future states
Organisation's needs and vendor needs
These are any two things that are not the same
108
Which of the following best describes a gap analysis?
A piece by piece comparison of two complex things to understand how they differ
109
What is Decision Analysis?
Determining which decisions need to be made.
Developing analytical frameworks to make them.
110
When is it best to use a simple decision table instead of a weighted decision table?
When each category has the same priority, simple decision tables are best.
111
Let’s say you are doing a Five Whys analysis of a problem, and you get a very good answer after asking “why” only three times. What do you think would be the best course of action?
Keep going. Even though it looks like you have a good answer, the next one might be even better.
112
If you suspect that a problem will have multiple contributing causes, which RCA approach will make the most sense?
Ishikawa diagrams tend to produce large numbers of contributing factors.
113
At the end of the lecture, you were advised to talk through your cause-and-effect logic to validate it.
What is the most likely to identify a problem in the logic?
Although the sales team’s lack of experience may be one factor, there are likely to be many other factors impacting the company’s profitability.
114
What are the 4 question approach for stakeholder needs analysis?
What do they say they want?
Why?
What is the priority in their mind?
What are their assumptions?
115
116
Why is it important to find a solution that meets the needs of all conflicting stakeholders?
Meeting the needs of all stakeholders is important if we are going to solve the overall problem.
Stake holders have varying positions and different valid view of the problem.
Requirements that don't meet the need of all stakeholders are not really that good,
117
What methods will be will be useful in finding solutions to stakeholder conflicts?
Additive analysis
Decomposition analysis
Decision Analysis
118
What is modeling
A depiction of a requirement or solution or process
119
what types of modeling are there?
illustrative - eg, prototypes
Predictive - eg, process simulators
General purpose - eg, flow charts
120
In flowcharts, what does a diamond represent?
A decision point
121
In flowcharts, what does a rectangle represent?
A step in the process
122
In flowcharts, what does a solid circle with a ring around it represent?
End of process
123
In flowcharts, what does a solid circle represent?
Beginning of process
124
What is wrong with this flow chart?
Without the text on the decision diamond , we have no way of knowing how the system will act.
125
Swim lane flowcharts are simply regular flowcharts with the activities broken down by _______.
Actor
126
What would not usually be considered an actor in a swim lane flowchart?
The project sponsor has an important role on the project, but is not typically considered an actor for modeling purposes.
127
If you have a process with three actors, which type of flowchart would you most likely use?
Swim lane flowcharts are recommended for processes with two to five actors.
128
In ER diagrams, which of the following shapes represents an entity?
Rectangle
129
What is the relationship?
Cardinality of 1…n indicates that a single employer can have any number of employees.
130
What is the relationship?
A book can have many number of persons
131
What is the minimum number of states a State-Transition Diagram can have (reasonably)?
Two. If the diagram has fewer than two states, then there cannot be any transitions between the states, and therefore they won’t make sense.
132
Which of the following is not a component of the data flow diagram?
Transitions are part of state-transition diagrams. The corresponding term in data flow diagrams is flow.
133
What flow is not permitted in data flow diagrams?
Direct flow from a data store to a data store. All flows must touch at least one Process.
134
What set of requirements would not likely require use case development?
The layout of a report would simply be specified, as it doesn’t contain any process to speak of.
135
What does the large rectangle signify in a use case diagram?
The boundary contains all the use cases handled by the system.
136
what is not considered an actor in a use case?
A "sub-use case" would never be considered an actor.
137
What is the definition of a business process?
A series of activities repeatedly and uniformly executed by an organisation to achieve some goal.
138
What are the 3 big goals of business process modeling
1) Reduce cost (make it cheaper)
2 )Reduce Cycle time (make it quicker)
3) Improve quality (make it better)
139
What are the 4 components of business modelling
Actors - People and systems
Activities - Steps in the business process
Tools - Equipment and other objects
Information - Data (electronic or paper)
140
What is not a typical goal of business process modeling?
To reduce throughput. If anything, a goal of increasing throughput could be a goal of business process modeling.
141
Which of the following types of diagram best suits modeling a business process?
If you are not familiar with BPMN, swim lane flowcharts are typically the best fit.
142
What is UML?
Unified Modeling Language
Used in object-oriented analysis
143
What is BPMN?
Business Process & Model Notation (looks like swim lane flowcharts but has a standard notation)
144
What are the 3 stages of finalizing requirements?
1) Stakeholders are bought into the solution - Socialization
2) The requirements are complete and of high quality - Presentation
3) We have the baselined the requirements - Change control
145
What is involved in Socialization?
Gaining support
Defusing tricky situations
146
What are the non-ideal aspects and who will they affect?
Are their any tricky stakeholders that are senior
Work with Boss / Sponsor to determine who has +ive / -ive impact
147
What stakeholder are you most likely to need to socialize your requirements with?
Customer Service teams often end up being penalized by resource-constricted projects, and when this happens, it’s important to socialize the requirements with the head of the department before the walk-through.
148
What questions to ask at a presentation?
Is there anything major that is missing or wrong?
Have we got the right approvers?
Are you able to approve the BRD by next week?
149
Which type of requirement does not need to be presented to stakeholders?
All types of requirements must be presented to stakeholders to make sure that we have documented things correctly and haven’t missed anything important.
150
Why is it important to “check back” with your stakeholders by asking them questions during your presentation?
Asking your audience questions serves many purposes – don’t miss out on the opportunities this technique gives you to make sure you have solid requirements documentation.
To make sure they understand the document
Give the a chance to think and catch up with the document
Encourage people to ask questions
Ensure nothing is missed
151
What should you consider when presenting?
It’s most important to adapt your presentation to your audience.
152
How can you figure out who should be the approvers for your requirements document?
Ask PM and boss, then check with project sponsor
153
Where is the best place to store requirements approvals?
In an accessible shared location
154
What are use cases?
Descriptions of interactions among users and systems and have the following properties:
1) They are process-driven
2) The have a goal
3) The are user focused
Use cases are descriptions of how users (or actors, as we will cover later) interact with systems. Although they can be used to describe processes, they are bigger than just that one area. It has become fairly common to use the term “use case” to describe scenarios. This is, strictly speaking, incorrect. Later in the course, we will look at use case diagrams which are visual models for system functionality. But here we’re just talking about single use cases.
155
What project would use cases be an effective requirements development method?
A custom developed e-ecommerce site.
The middleware project would probably not be a very good candidate for use cases. Since it sounds like there are no human actors involved, and messaging would likely be handled by data descriptions, another approach (e.g. data flow modeling) would be a better candidate. The ready-made system project, since it has already been built, would likely not require use cases either. The custom-developed e-commerce site, with all the various shopping options, would be the best candidate for use case modeling
156
What are the 1st 4 components of a use case?
1) Use case ID
2) Title - Verb followed by Noun phrase
3) Description
4) Actor - Someone who plays the role in your use case (Who or What)
157
What is an actor, in the context of use cases?
Any person or system involved in the execution of use case
Actors are all those people and systems involved in executing a given use case. People actors would be a subset of all actors, and users are a subset of people actors. We usually don’t talk about stakeholders of a use case, but when we do, it’s referring to anyone with an interest in the use case being executed. The majority aren’t actors.
158
Why is it a bad idea to document business rules within a use case?
Single business rules have an impact on many system and use cases, documenting them in a single use case makes the difficult to find and maintain.
If you document 50 business rules in 200 different use case documents, it will be a nightmare to maintain. Business rules are actually quite short; nonetheless, a business rule repository or separate document is better suited for maintaining them. Modern businesses are dynamic indeed. But it is important to document business rules.
159
What are the 3 types of flow?
1) Basic - Happy flow - nothing goes wrong.
2) Alternative flow - different paths the actors use.
3) Exception flow - The goal of use case is not met.
160
What would be valid content for the “Notes and References” portion of a basic flow step?
A reference to alternative of exception flow
A note cautioning developers and testers about some intricate detail of the step
A reference to a business step
161
Why do we usually have alternate flows branch out from steps where a system is the actor?
we are specifying how a system should respond to some previous action
We cannot control what human actors will do.
162
What is the last step of an alternate flow?
The last step in an alternate flow should direct the reader back to the appropriate step in the basic flow. This helps the reader have a clear idea of how the system will behave. The first answer is usually the first step of an alternate flow.
163
What are good strategies for finding possible exceptions that should be modeled as exception flows in your use cases?
Have developers review your draft use cases and provide input
Look for places in your basic flow where unexpected problems might pop up
Look for places in your alternative flow where unexpected problems might pop up
164
What does the last statement of an exception flow usually do?
Just as the last step of alternate flows direct the reader back to a place in the basic flow, the last step of an exception flow ends the use case.
165
What is a common outcome of missing an exception flow here and there?
Missed requirements
Poor user experience
Annoyed management
166
What are the 3 types of use case triggers?
1) Human
2) System
3) Time-related
167
What is the best strategy for finding use case preconditions?
Best strategy: examining the basic, alternate and exception flows (usually in that order).
168
Will use cases always have at least one postcondition? Why?
Use cases always have a goal, and the achievement of that goal is the first precondition. Cockburn and Cunningham probably agree that postconditions are a best practice, but this has (to my knowledge) never been expressed by them together. Use cases do have exception flows where the goal is not met, true. But postconditions reflect the state of the system after the use case has been successfully executed, so this statement doesn’t apply. The last answer is false. All use cases should have preconditions.
169
What are the roles of a BA in an agile team?
Elaborating user stories
Story-splitting
Defining acceptance criteria
Managing dependencies
Guiding Prioritzation
170
What writing a user story what 3 attributes must they have?
Clear
Attributed - Written from the users viewpoint
Able to Prioritize, understand their value
171
What should be the format of a user story?
As a ... (Actor /Role)
I want .. (Description of need)
So I .. (Rationale)
172
What are the 3 types of acceptance criteria?
1) Boolean - True / false, eg report is sorted by surname
2) Make sure - more colloquial
3) BDD - Behaviour-Driven Development
Given (Pre-conditions)
When (Trigger / Event)
Then (System behaviours)
173
Which of the following numbers is a likely number of acceptance criteria for a user story?
7, This is a typical number of acceptance criteria for a user story.
174
What are the 3 types of Decomposition?
1) Functional
2) Process
3) Structural
175
What is the product backlog?
A prioritised wish list of items for the team to develop, managed by the product owner
176
What is a PBI?
An item on the product backlog (has user story, acceptance criteria and other data)
A PBI represents a chunk of business value on the product backlog.
177
What is a sprint backlog?
The sprint backlog is everything the team is doing for a given sprint, and is managed by the team.
178
What are story points?
They are numbers that give relative sizing of user stories.
179
What is velocity?
The number of story points delivered by a team in a sprint.
180
Why does it make sense to use story maps?
Story maps provide a highly usable way of managing the product backlog work slate.
181
Consider the layout of story maps. What goes across the top and what goes down the left side?
Epics or functionality across top
left side going down - Sprints in chronical order with product backlog at bottom.
182
In which order should user stories be listed in the product backlog?
prioritization from high to low helps you to most easily assign stories to sprints.
183
What should your primary goal be when determining the contents of a sprint?
The goal of any sprint is to maximize the business/customer value of the product version it creates. All other goals are secondary to this.
184
What are roles of a BA in agile?
writing user stories
developing acceptance criteria
story-splitting
Prioritising stories
analysing gaps
helping the team understand everything
Plus usual research, interviewing stakeholders, analysis
modeling
185
Who is involved in the sprint retrospective?
Optionally, the Product Owner can attend as well, but it is usually just limited to the ScrumMaster and team.
186
Which of the following use case components is the first activity in a flowchart?
The trigger is usually the first activity (rectangle) in a flowchart. Alternatively, the first step of the basic flow is also acceptable. Preconditions and postconditions are states rather than activities, and they aren’t depicted in flowcharts.
187
If your flowchart becomes very complicated, what is the best strategy for handling it?
The best approach will be to reduce the flowchart’s complexity. Complexity is harder for stakeholders to understand. Complexity also breeds defects and lower testability. Just be sure to refactor your use case as well.
188
Why are swim lane flowcharts better than regular flowcharts when paired with use cases?
Swim lane flowcharts highlight the actors of a use case, making it more easily mappable to the use case. For this reason, we more commonly use swim lane flowcharts than regular ones.
189
Business Analysis is the practice of enabling _________ in an organizational context, by defining ________ and recommending solutions that deliver ________ to stakeholders.
Changes, Needs, Value
Business Analysts are challenged to identify problems and recommend solutions in order to create value for the business.
190
What is not a task of a Business Analyst?
.The Business Analyst does not generally complete any coding as part of their projects.
191
This Business Analyst role focuses on creating the interface that end users interact with.
User Experience analysst
192
While eliciting the needs of users is part of most Business Analyst roles, this one specializes in it.
Business requirements analyst
193
This Business Analyst role focuses primarily on creating the 'as-is' and 'to-be' models.
Business Process analyst
194
This Business Analyst role takes the business requirements and converts them into functional requirements. Ultimately, they focus on "how" a system will do the "what"
System Analyst
195
