BUSINESS ANALYST Vs SYSTEM ANALYST - PowerPoint PPT Presentation
Title:
BUSINESS ANALYST Vs SYSTEM ANALYST
Description:
COEPD - Center of Excellence for Professional Development is a primarily a Business Analyst and PMP Training Institute in the IT industry of India head quartered at Hyderabad. COEPD is expert in PMP Training and Business Analyst Training in Hyderabad, Chennai, Pune , Mumbai & Vizag. We offer PMP and Business Analyst Training with affordable prices that fit your needs. COEPD conducts 4-day workshops throughout the year for all participants in various locations i.e. Hyderabad, Pune. The workshops are also conducted on Saturdays and Sundays for the convenience of working professionals. For More Details Please Contact us: Visit at or Center of Excellence for Professional Development 3rd Floor, Sahithi Arcade, S R Nagar, Hyderabad 500 038, India. Ph# +91 9000155700, helpdesk@coepd.com – PowerPoint PPT presentation
Number of Views:111
Title: BUSINESS ANALYST Vs SYSTEM ANALYST
1
BUSINESS ANALYST Vs
SYSTEM ANALYST
(Professional Business Analyst Training
organisation)
2
- A business analyst works as a liasion among
stakeholders in order to understand, - communicate the requirements for changes to
business processes,policies. - The business analyst understands problems
andopportunities in the context of requirements
that enable the organization to achieve its
goals.
3
- Responsibilities of a Business Analyst 1.
Interaction with client2. Ownership of
Responsibilities 3. Process re-engineering
4
- SYSTEM ANALYSTA systems analyst is an IT
professional who has knowledge on information
systems. - A systems analyst is a person who uses analysis
and design techniques to solve business problems
using information technology. - Although they may be familiar with a variety of
languages like C,C,JAVA and operating
systems(OS ) like MS OFFICE.
5
- Roles of a System Analyst 1.Plan a system flow
from the ground up.2. Interact with internal
users and customers to learn and document
requirements that are then used to produce
business requirements documents.3.Interact with
designers to understand software limitations.
Traditional BA (Waterfall) Agile BA
Requirements are documented in Use Cases,Business Requirements, Functional requirements, UI Specifications, Business Rules. Requirements are documented in Epics, User Stories and optionally Business (or Essential) Use cases.
Focuses on completeness of requirement and spends time in ensuring the requirement is unambiguous and has all the details. Focuses on understanding the problem and being the domain expert so that s/he can answer questions from the development team swiftly and decisively.
Focuses on getting a sign off on the requirements. Focuses on ensuring the requirements meet the currentbusiness needs, even if it requires updating them.
Often there is a wall between the BA/Business and the Development team. Agile BA (Often called as Product Owner) is part of the team.
Tends to dictate solutions. Has to remain in the problem domain, leaving the development team space to explore different solutions.
Long turnaround. Quick turnaround.
Focus on what the requirements document said. In other words, output (Artifact) is a well written thorough requirements document. Focus on the functionality of the developed software. In other words, output (Artifact) is the software that meets thebusiness needs.
6
(No Transcript)
