XML Working Group Joan Ugljesa NDIA PMSC January 31, 2006 949-609-2999 [email protected].
-
Upload
rebecca-mcbride -
Category
Documents
-
view
220 -
download
0
Transcript of XML Working Group Joan Ugljesa NDIA PMSC January 31, 2006 949-609-2999 [email protected].
January, 2006 2
Topics
Review development steps and current plan
Current work product Introduce Business Requirements
Specification (BRS) content Current events List of URLs
January, 2006 3
UN/CEFACT Development Steps
1. Project definition*2. Use Case Description (participants, process)* 3. Use case as UML model (basis for data model), UML
activity diagram (sequence of events)*4. Business Requirements Specification with high level
data models**5. Requirements Mapping Specification (detailed data
description)***6. Add any missing core components (ISO standard)7. Harmonization8. Schemas generated based on CEFACT design rules
* - Complete ** - Draft ready for review *** - Draft in process
January, 2006 4
Development Plan
UN/CEFACT Project Proposal Complete – Presented 9/05
UN/CEFACT Business Process Use Cases First edition complete – Presented 9/05
DCMA/Boeing St. Louis Proof of Concept
Initial draft XML schema for trial use
Began 11/05 - Phase I complete in 1st quarter ‘06
UN/CEFACT Business Requirements Specification
Complete by 3/3/06
Present at 3/13-17/06 UN/CEFACT meetingUN/CEFACT Requirements Mapping Specification
Draft XML schema for trial use ready for distribution with implementation documentation
Preliminary – 1st quarter ’06
Updates – 2nd quarter ‘06
3 Implementation Verifications – Boeing, others to be determined
Begin 3/06
Complete by 9/06
UN/CEFACT Published Schemas 9/06 or 3/07 UN/CEFACT Meeting
January, 2006 5
Current Work Products
Items to be presented at interim January UN/CEFACT TBG6 (Architecture, Engineering and Construction) working group meeting Draft Business Requirements Specification
(BRS) US Delegation includes: GEFEG and
DCMA France, UK, and Japanese delegates are
active participants in development work
January, 2006 6
Business Requirements Specification
1 2
3 4 5 6
Business Requirements Specification 7
(BRS) 8
9 10 11 12 13 14
Business Domain: Contract Management 15
16 Business Process: Project Schedule and Cost Performance 17
Management 18
19 Document Identification: 20
21 22 23
Title: Project Schedule and Cost Performance Management 24 International Standard 25
26
Trade Facilitation and Business Working Group: 27
TBG6 – Architecture, Engineering and Construction Domain 28
29 30 31 32 33 34
Version: 0 35
Release: 1 36
37 Date: January 19, 2006 38
39 40 41 42 43 44
January, 2006 7
BRS - ContentsBusiness Requirements Specification 1
Table of Contents 2 3
1. PREAMBLE........................................................................................................................................1 4
2. REFERENCES...................................................................................................................................1 5
3. OBJECTIVE........................................................................................................................................1 6
4. SCOPE ...............................................................................................................................................1 7
5. BUSINESS REQUIREMENTS ...........................................................................................................3 8
5.1. BUSINESS PROCESS ELABORATION....................................................................................................4 9 5.1.1. The Actors ............................................................................................................................... 4 10 5.1.2. Project Initiation Business Use Case ...................................................................................... 6 11
5.1.2.1. Create Project .................................................................................................................. 6 12 5.1.3. Project Reporting Business Use Cases .................................................................................. 8 13
5.1.3.1. Report Project Performance............................................................................................. 8 14 5.1.3.2. Provide Error Notice .......................................................................................................10 15 5.1.3.3. Provide Update Notice ...................................................................................................11 16
5.1.4. Project Modification Business Use Cases.............................................................................12 17 5.1.4.1. Reset Project Baseline ...................................................................................................12 18 5.1.4.2. Update Project Within Baseline...................................................................................... 14 19
5.1.5. Project Close Out Business Use Cases ................................................................................15 20 5.1.5.1. Cancel Project ................................................................................................................15 21 5.1.5.2. Complete Project............................................................................................................16 22
5.2. BUSINESS INFORMATION FLOW DEFINITION ...................................................................................... 18 23 5.2.1. Provide Data.......................................................................................................................... 18 24 5.2.2. Provide Error Notice ..............................................................................................................19 25 5.2.3. Provide Update Notice...........................................................................................................20 26
5.3. BUSINESS INFORMATION MODEL DEFINITION .................................................................................... 21 27 5.3.1. List of Entities ........................................................................................................................ 21 28 5.3.2. Schedule Data ....................................................................................................................... 25 29 5.3.3. Cost Data............................................................................................................................... 26 30
5.3.3.1. Reporting Structure ........................................................................................................27 31 5.3.3.2. Control Account..............................................................................................................28 32 5.3.3.3. Work Package ................................................................................................................29 33
5.3.4. Contract and Project Summary Data..................................................................................... 30 34 5.3.5. Funding Data ......................................................................................................................... 31 35 5.3.6. Auxiliary Data ........................................................................................................................ 32 36
5.3.6.1. Reporting Calendar ........................................................................................................32 37 5.3.6.2. Schedule Calendar.........................................................................................................33 38 5.3.6.3. Reporting Structure ........................................................................................................33 39 5.3.6.4. Resources ...................................................................................................................... 34 40 5.3.6.5. Variance Thresholds ......................................................................................................34 41
5.4. BUSINESS RULES ............................................................................................................................ 35 42 5.5. DEFINITION OF TERMS ..................................................................................................................... 35 43
44 45 46
January, 2006 8
BRS – Business Operation Mapod Business Operation Map
«BusinessDomain»Contract Management
+ Contract Financial Execution
+ Project Schedule and Cost Performance Management
«BusinessArea»Contract Financial Execution
(from Contract Management)
«BusinessArea»Proj ect Schedule and Cost Performance Management
+ Project Close Out
+ Project Ini tiation
+ Project Modification
+ Project Reporting
(from Contract Management)
No description of this Business Area is present in this document because i t is out of scope of this project . It wi l l be covered in the Contract Financial Management project.
«ProcessArea»Proj ect Close Out
+ Cancel Project
+ Complete Project
(from Project Schedule and Cost Performance Management)
«ProcessArea»Proj ect Initiation
+ Create Project
(from Project Schedule and Cost Performance Management)
«ProcessArea»Proj ect Modification
+ Reset Project Basel ine
+ Update Project Within Basel ine
(from Project Schedule and Cost Performance Management)
«ProcessArea»Proj ect Reporting
+ Provide Error Notice
+ Provide Update Notice
+ Report Project Performance
(from Project Schedule and Cost Performance Management)
January, 2006 9
BRS – The Actors
ud Actors
Data Prov ider Data Consumer
Supplier Program or Proj ect Manager
Contractor Client
Priv ate Public Gov ernment Agency
Internal Management
January, 2006 10
BRS – Create Project Use Case
od Contract Initiation
«BusinessProcess»Create Proj ect
«InformationArea»
Schedule Data
(from Business Process Model)
«InformationArea»
Cost Data
(from Business Process Model)
«InformationArea»
Contract and Proj ect
Summary Data
(from Business Process Model)
«InformationArea»
Auxilliary Data
(from Business Process Model)
Data Consumer
(from Business Process Model)
Data Prov ider
(from Business Process Model)
«include»
«include»«include»
«include»
«use» «use»
January, 2006 11
BRS – Report Project Performance Use Case
cd Report Proj ect Performance
«BusinessProcess»Report Proj ect
Performance
«InformationArea»
Cost Data
(from Business Process Model)
«InformationArea»
Schedule Data
(from Business Process Model)
«InformationArea»
Funding Data
(from Business Process Model)
«InformationArea»
Contract and Proj ect
Summary Data
(from Business Process Model)
Data Prov ider
(from Business Process Model)
Data Consumer
(from Business Process Model)
«include» «include»
«include»«include»
«use» «use»
January, 2006 12
BRS – Provide Error Notice Use Case
cd Prov ide Error Notice
«BusinessProcess»Prov ide Error
Notice
Data Prov ider
(from Business Process Model)
Data Consumer
(from Business Process Model)
«use»«use»
January, 2006 13
BRS – Provide Update Notice Use Case
cd Prov ide Update Notice
«InformationArea»
Auxilliary Data
(from Business Process Model)
Data Prov ider
(from Business Process Model)
Data Consumer
(from Business Process Model)
«InformationArea»
Schedule Data
(from Business Process Model)
«InformationArea»
Funding Data
(from Business Process Model)
«InformationArea»
Cost Data
(from Business Process Model)
«InformationArea»
Contract and Proj ect
Summary Data
(from Business Process Model)
«BusinessProcess»Prov ide Update
Notice
«include»
«use» «use»
«include»
«include»
«include»«include»
January, 2006 14
BRS – Reset Project Baseline Use Case
ud Reset Proj ect Baseline
«BusinessProcess»Reset Proj ect
Baseline
«InformationArea»
Auxilliary Data
(from Business Process Model)
«InformationArea»
Contract and Proj ect
Summary Data
(from Business Process Model)
«InformationArea»
Cost Data
(from Business Process Model)
«InformationArea»
Schedule Data
(from Business Process Model)
Data Prov ider
(from Business Process Model)
Data Consumer
(from Business Process Model)
«include»
«include»«include»
«include»
«use» «use»
January, 2006 15
BRS – Update Project Within Baseline
ud Update Proj ect Within Baseline
«BusinessProcess»Update Proj ect Within Baseline
«InformationArea»
Auxilliary Data
(from Business Process Model)
«InformationArea»
Cost Data
(from Business Process Model)
«InformationArea»
Schedule Data
(from Business Process Model)
Data Prov ider
(from Business Process Model)
Data Consumer
(from Business Process Model)
«include» «include» «include»
«use» «use»
January, 2006 16
BRS – Cancel or Complete Project Use Case
ud Complete Proj ect
«BusinessProcess»Complete Proj ect
«InformationArea»
Contract and Proj ect
Summary Data
(from Business Process Model)
«InformationArea»
Cost Data
(from Business Process Model)
«InformationArea»
Funding Data
(from Business Process Model)«InformationArea»
Schedule Data
(from Business Process Model)
Data Prov ider
(from Business Process Model)
Data Consumer
(from Business Process Model)
«include»
«include»
«include»
«include»
January, 2006 17
BRS – Information Areas
Foundation for detail data model (requirements mapping specification)
Identifies data entities (class diagrams) Produce targeted schemas for specific data
exchange purpose Can be used alone or combined
Includes: Schedule data Cost data Contract and project summary data Funding data Auxiliary data
January, 2006 18
BRS – Schedule Data
January, 2006 19
BRS – Cost Data
January, 2006 20
BRS – Contract and Project Summary Data
January, 2006 21
BRS – Funding Data
January, 2006 22
BRS – Auxiliary Data
January, 2006 23
BRS – Auxiliary Data
January, 2006 24
Current Events XML.gov* Community of Practice (CoP) February 15
meeting hosted by Microsoft in Washington, D.C. Meeting is open to anyone who wishes to attend
DCMA has submitted project to the XMLCoP and will be presenting at the meeting
DCMA representatives: Mike Williams (CIO), John Van Dinther, Peter Amstutz
Likely results: NIST** will invite DCMA to participate in a federal Data
Reference Model test bed to include project management data
XML.gov will establish an EVM CoP as a result of OMB initiatives, DCMA activities, and UN/CEFACT standards development work
* Purpose of XML.gov is to support the directives in the E-Government Act of 2002** NIST is responsible for establishing the framework for information technology standards for the federal government
January, 2006 25
Resources
XML.gov xml.govxml.gov/cop.asp (community of practice)xml.gov/agenda/20060215.htm (February 15 meeting details)
UN/CEFACT www.unece.org/cefact/index.htm
UN/CEFACT TBG6 http://webster.disa.org/cefact-groups/tbg/wg/tbg6_main.cfm
Working group documents
Available on the DAU web site:
https://acc.dau.mil/ndiaxml
Note: you must be a member of the Earned Value Community of Practice to access the web site