1. Defense Business Systems (DBS) Acquisition (CLE077) KICK Off Meeting
26 October 2015
Dave Pearson
Bob Skertic
Joyce D. Williams

2. Agenda DAU Curriculum Development Overview ADDIE Process
DAU Course Development Process
DoD Software Domains and Acquisition
Systems Across DoD
Project Objectives / Scope
Initial Course Content Thoughts
The Project Team
Initial Roadmap/Schedule
Project Success Factors

3. DAU Curriculum Alignment
Stephanie Keith (DoD CIO)
Tom Hickok (CTR)
Competencies
Establishes & validates competencies & training requirements
FIPT*
Functional Leader
Working Group
Review/Validation
Learning Objectives
*DAU representation
on Functional Integrated
Process Teams (FIPTs)
Dave Pearson
(ENG & IT)
Change in requirements
DAU
Center Director
Content
DACM Reps Functional Reps
PLD
PLD**
PLD**
PLD**
Course Manager
Bob Skertic
PLD for IT
Development support
Centralized Design/Revision
Joyce D. Williams
DAU’s curriculum is owned by our stakeholders.

4. Analysis, Design, Development, Implement, Evaluate (ADDIE) Process

5. DAU Course Development Process Continuous Learning Module (CLM)
Course Advisory Group
RQT from IT Functional leader
Funding from WMG
DAU E&T Center
L/O
Design
Story
board
Program
Lessons
Pilot
Content from SMEs
Success!!
DAU IT Competency Papers
Contractor

6. DoD Software Domains and their Impacts on SW Acquisition
Cybersecurity Software Architecture
Infrastructure Systems
Modeling & Simulation (M&S) Systems
Not Real Time
Mix of COTS/GOTS HW/SW architecture
Example: High-Level Architecture (HLA)
Key SW Design is Portable Object Models
All Systems can use M&S prototypes to train our troops, discover requirements, design and save money.
CYBERSECURITY DESIGN
Real Time
Mix of COTS/GOTS HW/SW
Key SW Design is Network Performance
Cloud or Dedicated Servers and Processors
Transport Layer
Infrastructure Systems (e.g., Routing software, Enterprise Cloud Services (e.g., JIE))
Cybersecurity Design
Defense Business Systems
(DBS)
Not Real Time Data
SOTS HW/SW Architecture
Key SW Design is Privacy Focus
Real time transactions
Cybersecurity Design
State of the Shelf (SOTS)
M&S
Mission Systems
C4ISR Systems
Cybersecurity Systems
Real Time
Mix of COTS/GOTS HW/SW architecture
Defense in Depth SW Design
Design based on Required Controls as determined by NIST SP
Real Time Data
GOTS HW/SW Architecture
Key SW Design is Safety Focus
Special O/S
Cybersecurity Design
Near Real Time Data
Mix of COTS/GOTS HW/SW Architecture
Key SW Design is Cybersecurity
State of the Shelf (SOTS) refers to the current state of commercial products which includes COTS and Configurable COTS (ERPs); Configurable COTS has become an expensive, highly complex hybrid between COTS and GOTS. Configurable COTS is usually an Enterprise Resource Planning (ERP) COTS application that requires complex and costly configuration of RICEF-W objects: Reports (R), Interfaces (I), Conversions (C), Enhancements (E), Forms (F), and Workflow (W)
Note: Mission Systems include weapons and mission support equipment (e.g., aircraft); All software systems have embedded software/firmware today.

7. WMA vs DIMA vs BMA vs IEMA Systems

8. CLE 077 Objectives Develop an online, interactive, self-paced module:
DESIGN: Offered through the DAU’s learning management system
SCOPE: Focused on understanding the basics of Defense Business Systems (DBS), to include their unique:
acquisition model
solution architecture
relationships with the other DoD Software Domains
Estimated 5 hours to complete the module using “lunch-able” lessons
Targeted completion date of FY2017 (1st quarter)
Roadmap and tentative schedule will provide more detail
Target Audience: Defense acquisition field and across all acquisition career fields (Military officers (O-3 and above), Civilians (GS-9 and above), Industry equivalents)

9. Initial CLE077 Content Thoughts (DRAFT)
Recommended course should include:
DBS Governance (Laws, Policies, Regulations) on DBS Acquisition
DBS Program/Project Justifications, Approval and Compliance Processes
DBS Acquisition/Contracting/Funding/IP/Test Strategies
DBS software development (Agile, Incremental, Spiral) for rapid delivery
DBS life-cycle considerations
State of the Shelf (SOTS), COTS, Configurable COTS, ERPs
Service Development and Delivery Process (SDDP)
IT as a Service (ITaaS)
Requirements and Change Management Processes
Cybersecurity Architecture
Privacy as a main software design feature
Enterprise to Solution DBS Architectures
Data and Data Management
DBS Acquisition Measurement Program
DRAFT DAG Chapter on DBS
Other Lessons Learned, Evidence-based Best Practices, Rules of Thumb

10. CLE077 Project Team *Course Advisory Group Member CLE DBS Team NAME
ROLE
Responsibilities
Stephanie Keith
Sponsor
Jane Rathbun
AT&L*
WG Co-lead
Project Direction
David Pearson
DAU*
E&T Center Director
Execution Oversight
Bob Skertic
LCIC IT Performance Learning Director (PLD)
Overall accountable for fielding of the course
Joyce D. Williams DAU
Learning Asset Manager (LAM), CLE077
Project management of the course’s development
Scott Smith
Lead DBS SME
Lead Subject Matter Expert (SME)
Tom Hickok*
Functional Leader Representative
Project guidance, communications to FIPT
Contractor
Instructional Systems Designer (ISD)
Instructional design integrity of the course
Development Group Team Members
Content Development
Contribute and confirm learning objectives
Provide input on course design
Develop course content
*Course Advisory Group Member

11. CLE077 Acquisition Roadmap
Current Date
2015
2016 
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
RRR
PDR
Kick Off Mtg
CDR
PRR 1
PRR 2
DRR WG
Mtg WG
Mtg
Working Mgt Gp Mtg WG
Mtg
Develop Learning Objectives
Course
Design
Content
Development
Storyboarding
Programmed
Lessons
(PL) PL
Update
Prototype
Dev
Assessment Strategy
Dev
Deploy
Course
Provide
Gov
Feedback
SME Review
Government
Contractor
October 2015

12. Tentative Schedule March 2016 – October 2016 Contractor Activities
November to December 2015
Course manager/SME Team develop learning objectives
Requirements Readiness Review (RRR)
January 2016
Course Advisory Group (CAG) submit comments on learning objectives
WMG meets to approve revised learning objectives and discuss Preliminary Design
February 2016
Course manager/SME Team finalize initial course outline/design and Assessment Strategy
Preliminary Design Review (PDR)
February to March 2016
Course manager/SME Team develop course content
March 2016 – October 2016
Contractor Activities
April 2016
Critical Design Review (CDR)
May 2016
WG Meeting
July 2016
Production Readiness Review (PRR) 1
September 2016
Production Readiness Review (PRR) 2
November 2016 (Late)
Deployment Readiness Review (DRR)
SME Review

13. Project Success Factors
Stable and accessible project team throughout duration of project
Stay on schedule
Issues escalated and addressed in a timely fashion
Continuous and consistent communication
Work within the working group structure
Leverage as much provided content as possible material:
NEW DAG Chapter 12 (Need to Obtain DRAFT)
Other applicable content
Benchmark other course managers for Best Practices detailed upfront planning to include:
Applying SE principles to Curriculum Development
Get TLO’s/ELOs developed, coordinated, and approved using the working group.