1.
PMBOK Six Edition Data flow diagram
by English with MS-Visio (A4 * 2* 2 ) Page
Change Control Boad
(CCB)
Project Management
Information System
(PMIS)
(Configuration Management system)
(Specific, situation, verification and audit)
· Closed Procurement
#
Process
documents
Companies or
organizations
· output
relation
pl#： aj：
Process
· component
o retreat
· Enterprise
Environmental
Factors
· Organizational
process
Assets
toBe updates
Project initiator,
Sponsor
12.2： 4.09
Conduct
Procurements.
4.1： 2.01
Develop
Project
Charter.
· Enterprise
Environmental
Factors
· Organizational
process
Assets[1]
?
o AGREEMENTS.
PROJECT
DOCUMENTS.[1]
· Assumption log.
BUSINESS
DOCUMENTS.
· Business case.
· Benefits management plan. PROJECT CHARTER. 13.1： 2.02
Identify
Stakeholders.
13.2 ： 3.24
Plan
Stakeholder
Engagement.
· Business case.
· Benefits management plan.
PROJECT
MANAGEMENT
PLAN.[1]
o Communications management plan.o Stakeholder engagement plan. o Change log.
o Issue log.
AGREEMENTS.AGREEMENTS.
?
o AGREEMENTS.
· Requirements management plan.
· Communications management plan.
· Risk management plan.
· Stakeholder engagement plan.
· Assumption log.
· Issue log.
· Risk register.
· Stakeholder register.
· Stakeholder register.
4.6： 5.02
Perform
Integrated
Change
Control.
· Change Requests.
PROJECT CHARTER.
o Risk management plan.
AGREEMENTS.
o Assumption log.
o Change log.
o Issue log.
o Risk register.
· Stakeholder engagement plan.
5.1： 3.02
Plan Scope
Management.
PROJECT CHARTER.
Organization's culture.
Infrastructure.
Personnel admiknistration.
Marketplace conditions.
Previous similar projects
Information in the industory,discipline, and application data.
o Quality management plan.
· Stakeholder engagement plan.
5.2： 3.03
Collect
Requirements
.
5.3： 3.04
Define
Scope..
o Assumption log.
Business case.
AGREEMENTS.
PROJECT CHARTER.
o ?Lessons learned register.
· Stakeholder engagement plan.
· Stakeholder register.
· Stakeholder register.
· Scope management plan.
· Requirements management plan.
· Scope management plan.
· Scope management plan.
PROJECT CHARTER.
?
o Assumption log.
o Risk register.
?
· Project Scope statement.
· Assumption log.
· Requirements documentation.
· Requirements traceability matrix.
· Stakeholder register.
5.4： 3.05
Create WBS.
· Scope management plan.
· Project Scope statement.
?
· Scope baseline.
· Assumption log.
· Requirments documentation.
6.1： 3.06
Plan
Schedule
Management.
· Scope management plan.
Organization cluture and structure.Team resource availabitily
and skills
and physical resource availability.Scheduling software.Guidelines and criteria
for tailoring the organization's
set of standard process
and procedures to satisfy
the specific needs of the project.Commercial database,such as standard estimating data.Historical information and
Lessons lerned respositories.Existing formal and informal schedule development,
management- andcontrol-related policies, procedures and
guidelines.Templates and formsMonitoring and reporting tools.
· Schedule management plan.
6.2： 3.07
Define
Activities.
o Development approach.
· Scope baseline.
?
· Activity list.
· Activity attributes.
· Milestone list.
· Change Requests.
· Schedule baseline.
· Cost baseline.
6.3： 3.08
Sequence
Activities.
· Activity list.
· Activity attributes.
o Assumption log.
?
6.4： 3.09
Estimate
Activity
Durations.
· Project schedule network diagram.
· Activity attributes.
· Activity list.
· Assumption log.
· Milestone list.
· Schedule management plan.
· Scope baseline.
Organizational culture and structure.
Organizational calendars.
Published commercial information from commercial databases.
Project management information system(PMIS)
lessons learned repository containg historical information regarding activity lists used by previous similar projects.
Standardized proceses.
Template that contain a standard activity list or portion of an activity list from previous projext.
Existing formal and information activity planning-related policies,procedures, and guidelines,such as the schewduling methodology , that considered in the activity definitions.
· Activity list.
· Activity attributes.
6.5： 3.10
Develop
Schedule.
o Assumption log.
o Project team assignments.
o Resource calendars.
?
· Duration estimates.
· Basis of estimates.
· Activity attributes.
· Assumption log.
· Lessons learned register.
· Schedule management plan.
· Scope baseline.
o Assumption log.
o Project team assignments.
o Resource calendars.
o Risk register.
AGREEMENTS.
· Activity list.
· Activity attributes.
· Duration estimates.
· Basis of estimates.
· Lessons learned register.
· Project schedule network diagram.
· Project schedule.
· Schedule data.
· Project calendars.
· Activity attributes.
· Assumption log.
· Duration estimates.
· Lessons learned register.
· Resource requirements.
· Risk register.
· Schedule management plan.
· Schedule baseline.
· Change Requests.
· Schedule management plan.
o Performance measurement baseline.
7.1： 3.11
Plan Cost
Management.
PROJECT CHARTER.
Organizational calture and structure can influence cost management;
Market conditions describe what products, services, and results are available in the regional and global market;
Currency exchange rates for project costs sourced from more than one country;
Published commercial information;
Project management information system;
Producttivity difference in different parts of the world can have a large influence on the cost of products;
Financial controls procedures
Historical information and lessons learned knowledge bases;
Financial databases;
Existing formal and informal cost estimating and budgeting-related policies, procedures, and guidelines.
o Risk management plan.
· Schedule management plan.
7.2： 3.12
Estimate
Costs.
7.3： 3.13
Determine
Budget.
· Cost management plan.
· Cost management plan. o Quality Management Plan.· Scope baseline.
o Risk register.
· Project schedule.
?
· Cost estimates.
· Basis of estimates.
· Assumption log.
· Lessons learned register.
· Risk register.
· Cost management plan.
· Project schedule.
?
Business case.Benefits
management plan.
AGREEMENTS.
· Risk register.· Cost baseline.
· Project funding requirements.
プロジェクト資金要求事項
7.4： 5.06
Control
Costs.
9.1： 3.15
Plan
Resource
managemtnt.
Organizational culture and structure.
Geographic distribution of facilities and resources.
Existing resources competencies and availability.
Marketplace conditions.
Human resource policies and procedures.
Physical resource management policies and procedures.
Safety policies.
Security policies.
Templates for the resource management plan.
Historical information for similar projects.
PROJECT CHARTER. · Scope baseline.
o Project schedule.
o Quality Management Plan.
o Risk register.
· Stakeholder register.
· Team charter.
· Assumption log.
· Risk register.
9.2： 3.16
Estimate
Activity
Resources.
Resource location.
Resource availablity.
team resource skils.
organization culture.
Published estimating data.
Marketplace conditions.
policies and procedures regarding staffing.
Policies and procedures relationg to supplies and equipment.
Historical information regarding typoe of resources used for similar work on previous projects.
· Resource managemt plan.
· Scope baseline.
· Activity list.
· Activity attributes.
· Resource requirements.
· Basis of estimates.
· Resource breakdown structure.
· Activity attributes.
· Assumption log.
· Lessons learned register.
· Resource managemt plan.
· Resource breakdown structure.
· Resource requirements.
· Lessons learned register.
· Requirements documentation.
· Requirements traceability matrix.
· Requirements documentation.
o Assumption log.
o Cost estimates.
o Resource calendars.
o Risk register.
o Requirements documentation.
· Communications management plan.
· Requirements management plan.
· Schedule baseline.
· Cost baseline.
· Lessons learned register.
· Scope baseline.
· Cost estimates.
· Basis of estimates.
o Risk register.· Resource managemt plan.
· Project funding requirements.
8.1： 3.14
Plan Quality
Management.
PROJECT CHARTER.
· Scope management plan.
· Stakeholder engagement plan.
o Risk management plan.
· Scope baseline.
o Assumption log.
o Risk register.
· Requirements documentation.
· Requirements traceability matrix.
· Requirements documentation.
· Requirements traceability matrix.· Stakeholder register.
Govemmental agency regulations.
Rules,standards, and guidelines specific to the application area.
geographic distribution.
Organizational structure.
Marketplace conditions.
Working or operating conditions of the project or its deliverables.
Cultural perceptions.
Organizational quality management system includeing policies,procedures, and guidelines.
Quality template sutch as check sheets, traceability matrix, and others.
Histlical databases and lessons learned repository.
· Quality metrics.
· Lessons learned register.
· Requirements traceability matrix.
· Risk register.
· Stakeholder register.
· Quality Management Plan.
· Risk management plan.
· Scope baseline.
： (Requirements of
Cost performance
： ： baseline)
o Project life cycle description.
o Development approach.
12.1： 3.23
Plan
Procurement
management.
· Scope management plan.
· Quality Management Plan.· Resource managemt plan.
· Scope baseline.
Preapproved seller lists.
Formal procurement policies,procedures, and guidelines.
Contract types.
Cost-reimburssable contracts.
Time and material contracts(T&M).
· Stakeholder register. o Project team assignments.
o Risk register.
· Procurement management plan.
PROCEDUREMENT
DOCUMENTATION[1].
· Procurement strategy.
· Procurement statement of work.
· Bid documents.
· Make-or-buy decisions.
· Independent cost estimates.
· Change Requests.
· Organizational
process
Assets[2]
· Information on qualified sellers.
· Source selection criteria.
· Lessons learned register.
· Milestone list.
· Requirements documentation.
· Requirements traceability matrix.
· Risk register.
PROJECT CHARTER.
Business case.
Benefits management plan.
· Lessons learned register.
· Requirements documentation.
· Requirements traceability matrix.
· Milestone list.
· Milestone list.
· Milestone list.
· Resource requirements.
· Resource requirements..
· Resource requirements..
· Milestone list.
o Project schedule.
o Lessons learned register.
o Resource managemt plan.
10.1： 3.17
Plan
Communications
Managrement.
PROJECT CHARTER.
· Resource managemt plan.
· Stakeholder engagement plan.
· Stakeholder register.
· Requirements documentation.
Organizational cluture,political climate, nad govermanance framework.
Personnel administration policies.
Stakeholder risk thresholds.
Established communication channels,tools, and systems.
Global,regional, or local trends,practices, or habits.
Geographic distribution of facilities and resources.
Organizational policies and procedures for social media,ethics, and security.
Organizational policies and procedures for issues, risk, change, and data management.
Organizational communication requirements.
Standardized guidelines for development, exchange,storage,and retrieval of information.
Historical information and lessons learned repository.
Stakeholder and commuincations data and information from previous projects.
· Communications management plan.
· Stakeholder engagement plan.
? Project schedule.
(Requirements for communication
accompanying progress)
· Stakeholder register.
· Project schedule.
11.1： 3.18
Plan Risk
Management.
11.2： 3.19
Identify Risks.
11.3： 3.20
Perform
Qualitative
Risk Analysis.
11.4： 3.21
Perform
Quantitative
Risk Analysis.
11.5： 3.22
Plan Risk
Responces.
PROJECT CHARTER.
The enterprize environment factors that can influence that can influence
the Plan Risk management process
Organizational risk policy.
Risk categories, possibly organized into a risk breakdown structure.
Common defintion of risk concepts and team.
Risk statement formats.
Template for the risk managemant plan, risk register, and risk report.
Roles and responsibilities.
Authority levels for decision making.
Lessons learned repository from previous similar projects.
· Stakeholder register.
· Requirements management plan.
PROJECT
MANAGEMENT
PLAN.[2]· Risk management plan.
· Schedule management plan.
· Cost management plan.
· Quality Management Plan.
· Lessons learned register.
· Resource managemt plan.
· Risk management plan.
· Scope baseline.
(WBS dictionary
(technical documents,
(quality requirements, etc.)) "
· Schedule baseline.
· Cost baseline.
· Stakeholder register.
Published material, includeing commercial risk database or checklists.
Academic studies.
benchmarking results.
Industry stdsies of similar projects.
Project files, including actual data.
Organizational and project process controls.
Risk statement formats.
Checklists from previous similar projects.
Business case.
AGREEMENTS.
· Resource requirements..
· Duration estimates.
· Basis of estimates.
· Lessons learned register.
· Risk register.
· Risk report.
· Assumption log.
· Issue log.
· Lessons learned register.
PROJECT
DOCUMENTS.[2]
· ： Risk report.
· Requirements documentation.
· Risk management plan.
· Stakeholder register.
· Risk register.
· Assumption log.
The organizational process assets that
can influence Perform Qualitative Risk Analysis include.
· Risk register.
· Risk report.
· Assumption log.
· Issue log.
· Assumption log.
· Cost forecasts.
· Lessons learned register.
· Project schedule.
· Project team assignments.
· Risk register.
· Risk report.
· Project schedule.
Industory studies of similar projects.
Published material, includeing commercial risk database or checklists.
Templates for the risk management plan, risk register, and risk report.
Historical database.
Lessons learned repositories from similar projects.
· Risk management plan.
· Risk management plan.
· Risk register.
· Risk register.
· Risk report.
· Schedule management plan.
· Cost management plan.
· Quality Management Plan.
· Resource managemt plan.
· Procurement management plan.
· Scope baseline.
· Schedule baseline.
· Cost baseline.
· Cost estimates.
· Basis of estimates.
PROCEDUREMENT DOCUMENTATION.
· Scope baseline.
· Schedule baseline.
· Cost baseline.
· Resource managemt plan.
· Cost baseline.
· Lessons learned register.
o Lessons learned register.
o Project team assignments.
o Resource calendars.
4.2： 3.01
Develop
Project
Management
Plan.
PROJECT
MANAGEMENT
PLAN.[3]
4.3： 4.01
Direct and
Manage
Project Work.
· Any baseline or component plan.
· Scope management plan.
· *Any component
· Scope management plan.
· *Any component
· Change log.
· Lessons learned register.
· Milestone list.
· Project communications.
· Project schedule.
· Requirements traceability matrix.
· Risk register.
· Risk report.
· Approved Change Requests.
· Any baseline or component plan.
· Organizational standard policies,process, and procedures.
· Issue and defect management procedures defining
issue and defect control,
issue and defect identification and resolution ,and action item tracking.
· Issue and defect management database(s)
containing historical issue and defect status,
issue and defect resoution , and action results.
· Performance measurement database used to collect
and make available measurement data on process and products.
· Change control and risk control procedures.
· Project information from previous projects.
(e.g. scope,cost,schedule,
performance measurement baseline,
project calendars,
project schedule network diagrams,
risk registers,risk reports,
and lessons learned repository).
· Document
reffer
5.6： 5.04
Control
Scope.
6.6： 5.05
Control
Schedule.
8.3： 5.07
Control
Quality.
5.5： 5.03
Validate
Scope.
13.3： 4.10
Manage
Stakeholder
Engagement..
13.4： 5.12
Monitor
Stakeholder
Engagement.
4.4： 4.02
Manage
Project
Knowage.
4.5： 5.01
Monitor and
Control
Project Work.
11.7： 5.10
Monitor
Risks.
12.3： 5.11
Control
Procurements.
10.2： 4.07
Manage
Communicatio
ns.
10.3： 5.09
Monitor
Communicatio
ns.
9.3： 4.04
Acquire
Resources.
9.4： 4.05
Develop
Team.
9.5： 4.06
Manage Team.
9.6： 5.08
Control
Resources.
4.7： 6.01
Close Project
or Phase.
Customer
· Enterprise
Environmental
Factors
· Organizational
process
Assets[1]
PROJECT
MANAGEMENT
PLAN.[4]
PROJECT
DOCUMENTS.[4]
Sellers
11.6： 4.08
Implement
Risk
Responces.
8.2： 4.03
Manage
Quality.
Seller proposales
· Bid ducuments.
· Procurement statement of work.
· Independent cost estimates.
· Source selection criteria.
· Scope management plan.
· Requirements management plan.
· Communications management plan.
· Risk management plan.
· Procurement management plan.
· Configuration management plan.
· Cost baseline.
· Lessons learned register.
· Project schedule.
· Requirements documentation.
· Risk register.
· Stakeholder register.
· Selected sellers.
· AGREEMENTS.
· Change Requests.
· Requirements management plan.
· Quality Management Plan.
· Communications management plan.
· Risk management plan.
· Procurement management plan.
· Scope baseline.
· Schedule baseline.
· Cost baseline.
· Lessons learned register.
· Requirements documentation.
· Requirements traceability matrix.
· Resource calendars.
· Risk register.
· Stakeholder register.
· AGREEMENTS.
o AGREEMENTS.
o AGREEMENTS.
o AGREEMENTS.
· AGREEMENTS.
o Approved Change Requests.
· Deliverables.
· Deliverables.
· Deliverables.
· Issue log
· Activity list.
· Assumption log.
· Lessons learned register.
· Requirements documentation.
· Risk register.
· Stakeholder register.
· Work Performance Data.
· Work Performance Data.
· Work Performance Data.
· Work Performance Data.
· Work Performance Data.
· Work Performance Data.
· Work Performance Data.
· Work Performance Data.
· Work Performance Data.· Work Performance Data.
· Lessons learned register.
· Project management plan updates
(Change based on the official procedure
Modified version of all auxiliary
management plan)
· Work Performance Information.
· Quality control measurements.
· Verified Deliverables.
· Quality control measurements.
· Test and evaluation documents.
· Lessons learned register.
· Risk register.
· Test and evaluation documents.
· Quality control measurements.
· Quality Management Plan.
· Work Performance Information.
· Cost forecasts.
· Work Performance Information.
· Schedule forecasts.
· Work Performance Information.
· Work Performance Information.
· Work Performance Information.
· Work Performance Information.
· Work Performance Information.
· Work Performance reports.
· Work Performance reports.
· Cost forecasts.
· Issue log.
· Lessons learned register.
· Risk register.
· Schedule forecasts.
· Work Performance Information.
o Approved Change Requests.
· PROCEDUREMENT DOCUMENTATION.
· Risk register.
· Milestone list.
· Quality reports.
· Assumption log.
· Stakeholder register.
· Lessons learned register.
· Requirements documentation.
· Requirements traceability matrix.
· Change Requests.
· AGREEMENTS.
· Resource managemt plan.
· Schedule baseline.
· Cost baseline.
· Assumption log.
· Issue log.
· Lessons learned register.
· Pysical resource assignment.
· Resource breakdown structure.
o Approved Change Requests.
· Change Requests.
· Lessons learned register.
· Requirements documentation.
· Requirements traceability matrix.
· Performance measurement baseline.
· Scope management plan.
· Schedule baseline.
· Scope baseline.
· Cost baseline.
· Change Requests.
· Quality reports.
· Test and evaluation documents.· Quality Management Plan. · Lessons learned register.
· Quality control measurements.
· Quality metrics.
· Risk report.
· Quality reports.
· Test and evaluation documents.
· Requirements management plan.
· Scope management plan.
· Scope baseline.
o Quality reports.
· Lessons learned register.
· Requirements documentation.
· Requirements traceability matrix.
· Performance measurement baseline.
· Requirements management plan.
· Change management plan.
· Scope management plan.
· Scope baseline.
· Lessons learned register.
· Requirements documentation.
· Requirments traceability matrix.
· Performance measurement baseline.
· Cost management plan.
· Cost baseline.
· Lessons learned register.
· Assumption log.
· Basis of estimates.
· Cost estimates.
· Lessons learned register.
· Risk register.
· Performance measurement baseline.
· Cost management plan.
· Cost baseline.
· Communications management plan.
· Stakeholder engagement plan.
· Resource managemt plan.
· Issue log.
· Risk register.
· Stakeholder register.
· Lessons learned register.
· Project communications.
· Lessons learned register.
· Requirements documentation.
· Requirements traceability matrix.
· Change Requests.
· Assumption log.
· Basis of estimates.
· Lessons learned register.
· Project schedule.
· Resource calendars.
· Risk register.
· Schedule data.
· Performance measurement baseline.
· Schedule management plan.
· Schedule baseline.
· Cost baseline.
· Issue log.
· Lessons learned register.
· Stakeholder register.
· Communications management plan.
· Stakeholder engagement plan.
· Change Requests.
· Project schedule.
· Resource calendars.
· Resource requirements.
· Stakeholder register.
· Procurement management plan.
· Resource managemt plan.
· Cost baseline.
· Change Requests.
· Resource managemt plan.
· Cost baseline.· Physical Resource Assignments.
· Project team assignments.
· Resource calendars.
· Requirements management plan.
· Procurement management plan.
· Change management plan.
· Risk management plan.
· Schedule baseline.
· Procurement management plan.
· Risk management plan.
· Schedule baseline.
· Cost baseline.
· Risk register.
· Stakeholder register.
· Resource requirements.
· Lessons learned register.
· Requirements traceability matrix.
· Change Requests.
PROCEDUREMENT
DOCUMENTATION[1].
· Assumption log.
· Issue log.
· Lessons learned register.
· Risk register.
· Risk report.
· Change Requests.
· Change Requests.
· Work Performance Information.
· Work Performance reports.
o Project team assignments.
o Resource calendars.
· Lessons learned register.
· Project schedule.
· Project team assignments.
· Resource calendars.
· Team charter.
· Project team assignments.
· Team Performance assessments.
· Team charter.
· Change Requests.
· Change Requests.
· Resource managemt plan.
Lessons learned register.
Project schedule.
Project team assignments.
Resource calendars.
Team charter.
· Resource managemt plan.
· Communications management plan.
· Stakeholder engagement plan.
· Change log.
· Issue log.
· Lessons learned register.
· Quality reports.
· Risk report.
· Stakeholder register.
· Project management plan updates
· Project communications.
*Any component plan.
*Any component.
· Resource managemt plan.
· Schedule baseline.
· Cost baseline.
· Issue log.
· Lessons learned register.
· Project team assignments.
· Quality reports.
o Quality reports.
· Issue log.
· Lessons learned register.
· Project team assignments.
· Team charter.
· Resource managemt plan.
o Project communications.
o Project communications.
· Lessons learned register.
· Risk register.
· Risk report.
· Risk management plan.
· Change Requests.
Issue log.
Lessons learned register.
Project team assignments.
Risk register.
Risk report.
· Change log.
· Issue log.
· Lessons learned register.
· Stakeholder register.
· Communications management plan.
· Risk management plan.
· Stakeholder engagement plan.
· Change management plan.
· Change Requests.
· Change log.
· Issue log.
· Lessons learned register.
· Stakeholder register.
· Communications management plan.
· Stakeholder engagement plan.
o Project team assignments.
· Project team assignments.· Project team assignments.
· Lessons learned register.
· Project team assignments.
· Resource breakdown structure.
· Source selection criteria.
· Stakeholder register.
*Any component
· Performance measurement baseline.
· Schedule management plan.
· Schedule baseline.
· Scope baseline.· Schedule data.
· Project schedule.
· Project calendars.
· Resource calendars.
· Lessons learned register.
· Quality Management Plan.
o Test and evaluation documents.
o Lessons learned register.
· Quality metrics.
· Resource managemt plan.
o Issue log.
o Lessons learned register.
o Pysical resource assignment.
· Project schedule.
· Resource breakdown structure.
· Resource requirements.
· Risk register.
· Communications management plan.
· Stakeholder engagement plan.
· Resource managemt plan.
· Issue log.
· Lessons learned register.
· Project communications.
· Risk management plan.
· Issue log.
· Risk report.
· Risk register.
· Lessons learned register.
· Configuration management plan.
· Change management plan.
· Schedule baseline.
· Scope baseline.
· Cost baseline.
· Risk report.
· Basis of estimates.
· Requirements traceability matrix.
· Accepted Deliverables.
·
·
· Final Report.
· Final Product,Service,
or Result Transition.
Companies or
organizations
·
o Test and evaluation documents.
o Quality reports.
· Physical Resource Assignments.
· *Any component· Assumption log.
· Basis of estimates.
· Cost forecasts.
· Issue log.
· Lessons learned register.
· Milestone list.
· Quality reports.
· Risk register.
· Risk report.
· Schedule forecasts.
· Resource managemt plan.
· ORGANIZATIONAL
PROCESS ASSETS.
updates
(Management of defect and issues)
（Causes of variances,
Corrective action chosen
and the reasons,lessons learned）
{Completed checklists}
· Risk report.
(Issue log)
o Risk report.
PROJECT CHARTER.
o Test and evaluation
documents.
Reference：
”A Guide to the Project Management Body of
Knowledge (PMBOK® Guide) – 4,5,6 Edition”
Copyright © 2012,2018,jumnichi Kose edited

2.
That is not only validated,
it has been reconstructed
by this cross-reference EXCEL-Data.
列 ラベル
I n pu t O u tpu t
行 ラベル 最 小 / プロ セ ス 番 号最 大 / プロ セ ス 番 号最 小 / プロ セ ス 番 号最 大 / プロ セ ス 番 号
AGREEMEN T S . 4 .1 1 3 .2 1 2 .2 1 2 .2
(空白) 4.1 13.2 12.2 12.2
B U S I N ES S D O C U MEN T S . 4 .1 1 3 .1
Benefits management plan. 4.1 13.1
Business case. 4.1 13.1
C h an g e Re qu e s ts . 4 .3 1 2 .3 4 .3 1 3 .4
Approved Change Requests. 4.3 12.3 4.6 4.6
(空白) 4.6 4.6 4.3 13.4
D e live rable s . 4 .4 8 .3 4 .3 8 .3
Final Product,Service,or Result Transition. 4.7 4.7
(空白) 4.4 8.3 4.3 4.3
Accepted Deliverables. 4.7 4.7 5.5 5.5
Verified Deliverables. 5.5 5.5 8.3 8.3
EN T ERPRI S E EN VI RO N MEN T AL FAC T O RS . 4 .1 1 3 .4 9 .3 9 .5
(空白) 4.1 13.4 9.3 9.5
Producttivity difference in different parts of the world can have a large influence on the cost of products;7.1 7.1
Project management information system; 7.1 7.1
Organizational calture and structure can influence cost management;7.1 7.1
Published commercial information; 7.1 7.1
Currency exchange rates for project costs sourced from more than one country;7.1 7.1
Market conditions describe what products, services, and results are available in the regional and global market;7.1 7.1
O RGAN I ZAT I O N AL PRO C ES S AS S ET S . 4 .1 1 3 .4 4 .3 1 2 .3
(空白) 4.1 13.4 4.3 12.3
Financial databases; 7.1 7.1
Historical information and lessons learned knowledge bases; 7.1 7.1
Existing formal and informal cost estimating and budgeting-related policies, procedures, and guidelines.7.1 7.1
Financial controls procedures 7.1 7.1
PRO C ED U REMEN T D O C U MEN T AT I O N . 4 .7 1 2 .3 1 2 .1 1 2 .3
Independent cost estimates. 12.1 12.1
Make-or-bur decisions. 12.1 12.1
Bid documents. 12.1 12.1
Procurement statement of work. 12.1 12.1
*Procurement Documentation 12.3 12.3
Procurement strategy. 12.1 12.1
Closed Procurement 12.3 12.3
(空白) 4.7 12.3
PRO JEC T C H ART ER. 4 .2 1 3 .2 4 .1 4 .1
(空白) 4.2 13.2 4.1 4.1
PRO JEC T D O C U MEN T S . 4 .3 1 3 .4 4 .1 1 3 .4
Physical Resource Assignments. 9.3 9.3
Requirments documentation. 5.4 5.4
Project communications. 4.3 13.4 10.2 10.2
Project schedule. 4.3 13.2 6.5 11.5
Milestone list. 4.3 12.3 6.2 12.1
Requirements traceability matrix. 4.3 12.3 5.2 12.3
Change log. 4.3 13.3 4.6 13.3
Lessons learned register. 4.3 13.4 4.3 13.4
Risk report. 4.3 11.7 11.2 11.7
Risk register. 4.3 13.4 4.3 13.4
Project team assignments. 4.4 12.1 9.3 11.6
Stakeholder register. 4.4 13.4 4.3 13.4
Source selection criteria. 4.4 4.4 12.1 12.1
Resource breakdown structure. 4.4 9.6 9.2 9.6
Issue log. 4.5 13.4 4.3 13.4
Cost forecasts. 4.5 11.4 4.5 11.5
Schedule forecasts. 4.5 11.4 4.5 6.6
Quality reports. 4.5 12.3 8.2 8.2
Basis of estimates. 4.5 11.4 6.4 9.2
Assumption log. 4.5 13.2 4.1 13.1
Quality control measurements. 4.7 8.2 8.3 8.3
Requirements documentation. 4.7 13.1 4.3 12.2
Project Scope statement. 5.4 5.4 5.3 5.3
Requirments traceability matrix. 5.6 5.6
Activity list. 6.3 9.2 4.3 6.3
Activity attributes. 6.3 9.2 6.2 9.2

3.
Six edition DFD structure
propagates “Program management”
Project-A 1St Week
Thease Information will be propagated
to same Program managements
Project-B somedays
Project-A 2St Week
 BUSINESS DOCUMENTS.
 Project life cycle description.
 Development approach.
 Project funding requirements.

4.
DIRKW model in DFD.
• Data -> Information -> Report -> Knowage.
D
a
t
a
I
n
f
o
r
m
a
t
i
o
n
R
e
p
o
r
t
Knowage.

5.
PMBOK six Edition ITTO is tangled.
Appendix Ajail process is a bit better.
→My DSF unraveled the thread.