Exam (elaborations)
Business Analyst questions & answer.
- Course
- Institution
Business Analyst questions & answer.
[Show more]
Seller
Follow
Content preview
Business Analyst questions & answer.Business Requirements ANS - refers to a capability that a solution must provide (such as the capability
to conduct online transactions) or a condition that it must meet (such as compliance with a set of
regulations).
Functional requirements ANS - denote externally visible behavior that a system must be able to perform
and include features and use cases written from the customer, user, and system perspective.
Non-functional requirements ANS - anything other than functional requirements.
Business Service ANS - mean a Service that is delivered to Business Customers by Business Units, for
example, delivery of financial services to Customers of a bank, or goods to the Customers of a retail
store.
Business Analyst vs Systems Analyst ANS - systems analyst refers to a role distinct from the business
analyst; the business analyst analyzes the business, whereas the systems analyst designs the software
solution.
Template ANS - is a standardized form used for textual documentation.
Description ANS - is something that tells you what something is like; it is the actual documentation and
may be in the form of text and/or diagrams.
Software Development Cycle ANS - Initiation, Discovery, Construction, Final, and Closeout
Initiation ANS - Make the business case for the project. Work also begins on the user experience and on
architectural proof of concepts.
,The objectives of the Initiation phase are to develop the business case for the project, establish project
and product scope, and to explore solutions, including the preliminary architecture. (The prototyping
effort during Initiation should be risk-driven and limited to
gaining confidence that a solution is possible.) The BA assists the project manager by identifying
stakeholders, business services and processes, and IT services impacted by the project.
By the end of this phase, key functionality is identified—such as key
user tasks and IT services.
Discovery ANS - Conduct investigation leading to an understanding of the solution's desired behavior.
Requirements analysis peaks during this phase but never disappears entirely. During this phase,
architectural proof of concepts are also constructed.
The main objective of the Discovery phase is to understand the solution's desired behav-iour and
baseline the architecture
Construction ANS - Complete the analysis and design, code, integrate, and test the soft-ware. (On
iterative projects, these activities are performed for each iteration within the phase.) Design and coding
appear in all phases, but peak during this phase.
Final V&V ANS - Perform final testing before the product or service is transitioned into production.
(While final testing occurs in this phase, testing activities may occur throughout the SDLC, for example,
before design or as a replacement for it.
Interview Questions ANS - - What are the major problems you are experiencing?
- How often do they occur?
- What opportunities are we missing?
- What are the costs and benefits of a change?
- What are the risks?
- Who will be affected by the success or failure of the solution?
- Who are the users?
,- Who is the customer?
- Who will sign off on the solution?
- What is each stakeholder's interest (an addressed need or
opportunity) in the solution?
- What new business services or processes will be introduced by this project?
- For each identified service or process, what is the expected
impact of the change on the business area and on other
services and components?
Which of the business process participants (business actors and workers) will be direct users of the
system?
- Which tasks involve the IT system?
- What is the best way to group the automated steps into tasks
that can be accomplished by one user in one session?
- What business services or processes (business use cases) does this user task support?
- What business goals does it support?
Requirements must be signed off ANS - Requirements may be signed off iteratively, as they are
developed
On waterfall projects, the following items are baselined and finalized; on iterative projects,
requirements are subject to change at any time as long as they are not being implemented.
Are the requirements complete, correct, realistic, testable, and within scope?
Waterfall Project ANS - The waterfall model is a sequential design process, often used in software
development processes, in which progress is seen as flowing steadily downwards (like a waterfall)
, through the phases of Conception, Initiation, Analysis, Design, Construction, Testing,
Production/Implementation, and Maintenance.
Closeout Phase ANS - The purpose of this phase is to manage and coordinate the processes, systems,
and functions required for the deployment of a release into production and end project activities.
SDLC Phase ANS - During the Plan stage, annual planning occurs; criteria for defining, categorizing, and
prioritizing a project are developed; and projects are approved. During the Initiate stage, a business
project is begun. During Execute, the proposed changes are realized. During Transition, the solution is
made operational. At some point during or after this time, Post-Implementation Review. As the project
closes, Early Life Support occurs—a period of time during which a team is on standby should problems
occur, after which the internal IT team signs off on the changes.
Types of Meetings That a BA May Be Asked to Participate In ANS - - Scope initiation: Brainstorm
opportuities, risks, features.
- Requirements definition.
- Problem Log (PLOG) Resolution: Resolve a problem or issue.
- Structured walkthrough: Review a project artifact, such as a section of the BRD.
- Process modeling, workflow analysis: Analyze the workflow of a business process.
- Design reviews: Review external design definitions, screen prototypes, etc.
- Business process management: Manage, improve a business process.
- Gate review: Review and sign off on deliverables at specified points in the project.
- Confirmation of agreements.
- Post-implementation review: Assess results of a change.
Stakeholders ANS - Customers - Provide insight into problems with current service offerings. Know what
new services or changes are desirable from the perspective of the person paying for the service.
Users - Ensure that requirements meet the needs of end users of the IT system. Ensure system supports
all user tasks (goals) and workflow requirements and is easy to use. Understand day-to-day problems
with current system.
The benefits of buying summaries with Stuvia:
Guaranteed quality through customer reviews
Stuvia customers have reviewed more than 700,000 summaries. This how you know that you are buying the best documents.
Quick and easy check-out
You can quickly pay through credit card or Stuvia-credit for the summaries. There is no membership needed.
Focus on what matters
Your fellow students write the study notes themselves, which is why the documents are always reliable and up-to-date. This ensures you quickly get to the core!
Frequently asked questions
What do I get when I buy this document?
You get a PDF, available immediately after your purchase. The purchased document is accessible anytime, anywhere and indefinitely through your profile.
Satisfaction guarantee: how does it work?
Our satisfaction guarantee ensures that you always find a study document that suits you well. You fill out a form, and our customer service team takes care of the rest.
Who am I buying these notes from?
Stuvia is a marketplace, so you are not buying this document from us, but from seller Professorkaylee. Stuvia facilitates payment to the seller.
Will I be stuck with a subscription?
No, you only buy these notes for $14.49. You're not tied to anything after your purchase.
Can Stuvia be trusted?
4.6 stars on Google & Trustpilot (+1000 reviews)
79223 documents were sold in the last 30 days
Founded in 2010, the go-to place to buy study notes for 14 years now