系统介绍课程
需要记忆每个领域包含的任务名称,及输入输出
领域的相关方/技巧等重在理解
需求分析的旧版定义:一组任务和技术如何应用到工作中的组织架构/流程/运作方式等分析,在分析中发现问题,提供解决方案解决问题,为组织带来价值 。
系统介绍课程
需要记忆每个领域包含的任务名称,及输入输出
领域的相关方/技巧等重在理解
需求分析的旧版定义:一组任务和技术如何应用到工作中的组织架构/流程/运作方式等分析,在分析中发现问题,提供解决方案解决问题,为组织带来价值 。
课程分成12个单元,基本参考BABOK书籍
第一单元对应第一章
介绍背景/结构/重要概念
第二单元对应第二章
介绍重要概念:需求/干系人
第三到第八章
需求分析的六大领域,每个领域有任务,任务的输入输出是什么
第九章
基本能力:沟通/协调
第十章
六大领域工作中需要的方式方法:interview
考试实际占了比重
第十一章 视角
在特别行业的应用:IT 敏捷 业务流程管理 商业智能 商业架构
第十二单元
不是BABOK书内容,是考试指导
Agile-iteration-just enough, just in time
Prective-requirement are define at a rather early stage-deliverables at the final stage
Interfaces-departmental
Roles and permission matrix
use case
Crud: create read update delete
Variance-root cause analysis
Data mining
Define, validate
focus group: qualitative measures
current
Acceptance (one solution, pass/fail) and evaluation (multiple solutions, assign different weights, ranking) criteria
The previous chapters about requirements: elicitation, analysis.
In use-existing, in varying stages of development: proto, beta, operational release
Opportunity cost--by opting A you can't enjoy the benefits from choosing B and C
constraints on solutions: time, budget
Dependencies on other initiatives-about consideration
Sponsor: usually important decision maker
prioritisation: Must Could Should What
Identify improvement opportunities
better access to information
identify additional capabilities
Requirement allocation-solution components / release
Determing solution approach-understanding of requirements , solution architecture
Design options: personnel, section, operational structures, policy, rules, relationships, aapplications
Mind mapping
RFI-information, RFQ-quotation, RFT-Tender, RFP-Prposal
Can adopt various formality based on differing needs of the stkhldrs
audit and security-non functional requirements
more than one viewpoints, interrelated with each other-tracing requirements
User stories or use case--functional requirements
Elicitstion results-business analysis
Assumption
Alignment with solution scope
Tracing requirements-new requirements, change requirements
Review
Walkthrough-predictive-group
single issue review
ad hoc-temporary
Atomic
Verify-quality check
Use case
Main success flow
Alternative and exception flow
1 sprint (1-4wks)
Synchronous
asynchronous _signal
Metadata repository
Primitive data elements
Composite data elements
business policy, directive, broadly
business rule specific, testable directive
Definition rules (can only be misapplied)
Behavioral rules (can be violated)
override by authorised actor, with explanation, with no active enforcement
Business Rules Catalogue
Model
Mactrices
Diagram
People & roles
Rationale (scope model, root cause analysis)
Activity flow (use case, user stores, processes)
Capability (functions)
Data & information (Data dictionary, Glossary, interface)
attributes: prioritisation, value, source
Notations (UML, informal)