Bài giảng Business analysis in practice

BUSINESS ANALYSIS IN PRACTICE  
Practical Training Course  
Author: Tran Cong Cao  
Phone: 0909 146 976  
Email: cao.trancong@gmail.com  
Fb: fb/cao.trancong (#caotran)  
1
Author: APEX Learning Content Development Team  
Introductions and Expectations  
Participant introductions  
v Name  
v Position and background  
v How long experience with Business Analysis or Requirement  
Engineering?  
v What do you want to get out of this course (expectation)?  
2
Author: APEX Learning Content Development Team  
Learning Objectives  
v Understand the concepts of software requirements  
v Understand and appreciate the requirements process  
v Describe the importance of requirements in software development life cycle  
v Describe how requirements are used to solve business problem, create  
products and solution that meet the stakeholders’ needs  
v Use the requirements practices in the highly competitive software world  
v Organize and facilitate communicate between stakeholders, users and  
developers  
v Plan and setting the stage for requirements development  
v Elicit and analyze requirements correctly and efficiently  
v Document and validate requirements in a quality manner  
v Manage changes to requirements during the development process  
3
Author: APEX Learning Content Development Team  
Logistics  
4
Author: APEX Learning Content Development Team  
Rules of Engagement  
Participate.  
One person speaks at any given  
time.  
Keep discussions and questions to  
the point.  
Turn on your cell phones and other  
communication devices to Silence  
mode.  
Be prompt returning from breaks.  
5
Author: APEX Learning Content Development Team  
Business Analysis In Practice Course Agenda  
v Module 1: Introduction to Requirement Engineering  
v Module 2: Requirements Elicitation  
v Module 3: Requirements Analysis  
v Module 4: Requirements Specification  
v Module 5: Requirements Validation  
v Module 6: Requirements Management  
6
Author: APEX Learning Content Development Team  
INTRODUCTION TO REQUIREMENT  
ENGINEERING  
Business Analysis In Practice – Module 01  
Learning Objectives  
v Understand the Requirement Engineering  
v Understand the role of Requirement Engineer  
v Understand the competencies needs to success the role  
v Understand the relationships of requirements in the IT projects  
v Understand reason why requirement is important support IT project  
success  
v Understand the requirement approach with new project  
v Understand the common techniques to identify stakeholders and prepare  
for the project  
v Transform to requirement engineer mindset  
8
Author: APEX Learning Content Development Team  
What is Requirement Engineering?  
v A method of obtaining a precise formal specification from the informal and often  
vague requirements with customers.  
v The science and discipline concerned with analyzing and documenting  
requirements. It comprises needs analysis, requirements analysis, and  
requirements specifications.  
Requirements  
Requirement  
Baseline  
Requirement  
Elicitation  
Analysis  
(Gathering)  
Requirements  
Traceability  
Requirements  
Requirement  
Requirement Change  
Verification &  
Management  
Specification  
Validation  
* Based on IEEE Standard Terminology  
9
Author: APEX Learning Content Development Team  
What is Requirement?  
v A condition or capability needed by a user or  
customer to solve a problem or achieve an  
objective.  
Customer  
Provider  
v A condition or capability that must be met by a  
system or system component to satisfy a contract,  
standard, specification, or other formally imposed  
document.  
v A document representation of a condition or  
capability.  
v Requirements are descriptions of the necessary  
and sufficient properties of a product or service  
that will satisfy the customer’s need.  
* Based on IEEE Standard Terminology  
10  
Author: APEX Learning Content Development Team  
Software Requirements  
v Requirements describe the behavior of the software as seen from the  
customer’s perspective.  
v Requirements serve as a communications channel between customers,  
users and project managers who are concerned with the development of  
software products or services.  
v If software people do NOT have well written requirements that users  
agree to, how can they develop software that satisfy those users?  
11  
Author: APEX Learning Content Development Team  
Software Requirements  
v The “TO DO” List of the Project Team.  
v The List of “WHAT” Customer’s need.  
v The List of “WHAT” the software must do to satisfy its Customers.  
v The List of “WHAT” components must be built.  
v The List of “WHAT” each component must “DO” and “HOW” they will  
“INTERACT”.  
12  
Author: APEX Learning Content Development Team  
Requirements Engineer Role  
v Requirements engineer: a software engineer who has the responsibility  
to gather, analyze, document and validate the needs of the project  
stakeholders.  
v This role in collecting and disseminating project information is critical and  
requires a lot of experience and training.  
13  
Author: APEX Learning Content Development Team  
Requirement Engineer – Job Titles  
Requirements Engineer  
Business Analyst  
System Analyst  
System Engineer  
Project Manager  
Data Analyst  
Product Owner  
Development Lead  
14  
Author: APEX Learning Content Development Team  
Three Levels of Business Analysis in the Enterprise  
Level 3  
v Focus to Business  
Problem Solving to define  
the strategy  
Level 2  
v Most time work with senior  
managers and SME  
v Most work products is  
Business Model, strategic  
plan  
v Focus to Business  
Problem Solving  
Level 1  
v Most time work with middle  
managers and SME  
v Most work products is  
business requirement as:  
Business case, project  
proposal  
v Focus to Requirement  
Engineering in detail  
v Most time work with end-  
user and technical team  
v Most work products is  
User requirement and  
software requirement  
15  
Author: APEX Learning Content Development Team  
Underlying Competencies  
v Underlying competencies reflect knowledge, skills, behaviors,  
characteristics, and personal qualities that help one successfully  
perform the role of the Requirement Engineer.  
16  
Author: APEX Learning Content Development Team  
Requirements Engineer’s Tasks  
1) Define business requirements  
2) Identify stakeholders & user classes  
3) Elicit requirements  
4) Analyze requirements  
5) Write requirements specifications  
6) Model the requirements  
7) Lead requirements validation  
8) Facilitate requirements prioritization  
9) Transfer requirement  
10) Manage requirements  
17  
Author: APEX Learning Content Development Team  
Where Do Requirements Come From?  
18  
Author: APEX Learning Content Development Team  
Relationships of Requirements  
Requirement  
Documents  
Business  
Requirements  
Vision & Scope  
User’s view  
User  
Requirements  
Use Case  
System  
Requirements  
Developer’s  
view  
Software  
Requirements  
Hardware  
Requirements  
Software Requirement  
Specification  
19  
Author: APEX Learning Content Development Team  
Relationships of Requirements  
Business Needs  
System  
Subsystem A  
Subsystem B  
Subsystem C  
Software  
Hardware  
Software  
Hardware  
Software  
Hardware  
20  
Author: APEX Learning Content Development Team  
Tải về để xem bản đầy đủ
pdf 61 trang Thùy Anh 18220 Free
Bạn đang xem 20 trang mẫu của tài liệu "Bài giảng Business analysis in practice", để tải tài liệu gốc về máy hãy click vào nút Download ở trên

File đính kèm:

  • pdfbai_giang_business_analysis_in_practice.pdf