Navy Data Environment NDE

1
Navy Data Environment (NDE) Navy Modernization
(NM) SHIPMAIN Entitled Process Program Review
7 January 2005
2
NDE NM Entitled Process Time Line
Business Rule Initiation
General Availability Release
November
September
September
December
February
February
October
January
January
August
August
March
March
April
April
May
June
May
June
July
July
2nd Q 2004
3rd Q 2004
1st Q 2005
4th Q 2004
2nd Q 2005
3rd Q 2005
4th Q 2005
Inception Phase
Construction Phase
Elaboration Phase
Life Cycle PPI
-
Transition Phase
3
Ship Change Document (1 of 3)

• ORIG PR6 ACTUAL
• SCD Release 1.6.8
• SCD Main Form modified to only allow New
  11/30/04
• to select one of the following HME, C4I, CS
• The View/Edit screen is modified to New
  11/30/04
• accommodate above
• NMCI Work-around on RCP New 11/30/04
• SCD movement to next Phase after
  Approval New 12/06/04
• RCP modifications to 06 Vote Criteria New 12/10/
  04
• CBA update of Inflation Factor Value New 12/10/0
  4
• CBA modifications to the ROI Payback
  Period New 12/10/04 12/10/04
• Release to test/testing 12/14/04 12/14/04
• Release to production 12/16/04 12/16/04

4
Ship Change Document (2 of 3)

• ORIG PR7 ACTUAL
• SCD Release 1.6.9
• Modified RCP to make TOC always positive New
  12/17/04
• value on RCP
• Modification to re-title column on RCP Export
  New 12/17/04
• parallel status
• Corrected displayed TOC Value on SOME RCPs
  New 12/20/04
• Modification to allow global recalculation of CBA
  New 12/21/04
• summary data on existing SCDs
• Added Points of Contacts file to Support
  Menu New 12/21/04
• Release to Testing New 12/22/04
• Release to Production New 12/27/04
• Recalculation of CBA Summary Information on all
  SCDs New 12/27/04

5
Ship Change Document (3 of 3)

• PR5 PR6 PR7 ACTUAL
• SCD Release 1.7
• AFOM Mouse Over 3 Left Columns New/TBD 1/07/05
• CBA Add Claimant to CBA New/TBD 1/10/05
• Mods to Distributed Systems (II, IIa,
  III) New/TBD 1/12/05
• Develop ADMIN Module 1/14/05
• Mods to make POC Info avail in
• Phases II, IIa, III 1/14/05
• Mod to input Legacy Alt Identifier 1/19/05
• AFOM Add additional Comment fields New/TBD 1/21
  /05
• SCD Split by Carriers PEO Ships
• (multiple POCs, AFOMs, CBAs, etc.) New/TBD TBD 1/
  28/05
• SCD Split by multiple classes
• (subset Phase III Indiv. SCD
  data) New/TBD TBD 2/11/05
• Update Help Pages (Reflect changes) New/TBD TBD 2/
  11/05
• SCD Update Export (Reflect changes) New/TBD TBD 2/
  11/05
• Release to test/testing TBD TBD 2/16/05
• Release to production TBD TBD 2/23/05

6
SHIP CHANGE DOCUMENT

• Business Process Changes
• SCD is Prototype Requirements change on a
  needed basis
• Resources
• Resources sufficient for approved SCD
  requirements development
• Funding to Complete
• Funding provided upon Sponsor approval of tasking
• Risks
• Detailed requirements and associated
  documentation, still evolving
• Critical Path
• Approved evolving requirements to assist user
  community
• Risk Mitigation
• Working with SHIPMAIN Team Leads weekly on
  changing requirements

7
Secure NDE-NM Environment Establish Secure
Operations

• Notes
• 1. SIPRNet connection requires coordination
  with DISA and Port Hueneme personnel for COMSEC
  equipment calibration (week of 24 January). Final
  H/W and encryption testing dependent on
  connection date.
• 2. DISA interim approval to connect (IATC)
  received 22 Dec.
• 3. AMPS-NTIRA interface SPAWAR unable to
  support interface requirements definition
• 4. Cross Domain Capability Air Gap method to be
  used interim due to DISA limitations for new
  customers.
• .

8
Secure NDE-NM Environment

• Business Process Changes
• None
• Resources
• Programmers in place
• HW awaiting final configuration/connectivity
• Funding to Complete
• Funding provided
• Risks
• Coordination required between multiple
  organizations (DISA, SPAWAR, NAVSEA CIO-IA, etc.)
• Sequential series of events impacted on other
  event accomplishment
• Cannot start operations until DISA approval are
  in place.
• Critical Path
• DISA approval received 12/22/04, working with
  DISA to schedule. This will determine when
  SIPRNet Encryption testing can take place.
• Final integration and HW configuration awaiting
  SIPRNet connectivity
• Risk Mitigation
• Air Gap will be used initially for Cross Domain
  transfer (Low High)
• Apply sufficient/focused project management
  attention to facilitate movement through DISA
  process
• Increased communications with DISA POCs for
  status/urgency
• Circuit reliability with Beale unknown until
  connected/tested

9
Software Development

• Orig PR2 PR3 PR 5 PR 6 PR7 Actual
• Inception Phase
• Navy Approval of Inception Products 9/1/04
  9/1/04 9/1/04 9/1/04 9/1/04 9/1/04 9/1/04
• Elaboration Phase
• Alpha 1 SME Inputs to ASC 9/27/04
  10/01/04 10/01/04 10/01/04 10/01/04 10/01/04
• Alpha 1 Requirements to NSLC 10/04/04
  10/08/04 10/08/04 10/08/04 10/08/04
  10/8/04 10/8/04
• Alpha 1 Software Release 11/08/04 11/08/04 11/08
  /04 12/30/04 12/30/04 12/30/04 12/30/04
• Alpha 2 SME Inputs to ASC 11/23/04
  1/21/05 1/21/05 1/21/05 1/13/05 On Target
• Alpha 2 Requirements to NSLC 12/4/04
  1/28/05 1/28/05 1/28/05 1/28/05 1/28/05
  Caution
• Alpha 2 Software Release 1/10/05 1/10/05 2/25/05
  2/25/05 2/25/05 4/15/05 At Risk
• Elaboration Product Delivery 11/29/04 11/29/04 2/
  27/05 2/27/05 2/27/05 2/27/05 On Target
• Process Business Rule Update 11/29/04 11/29/04 2/
  27/05 2/27/05 2/27/05 2/27/05 On Target
• Navy Approval Elaboration Products 12/13/04 12/13/
  04 3/20/05 3/20/05 3/20/05 3/20/05 On Target
• Construction Phase
• Beta SME Inputs to ASC 2/14/05
  3/23/05 3/23/05 3/23/05 4/12/05 Caution
• Beta Requirements to NSLC 2/21/05
  4/1/05 4/1/05 4/1/05 4/1/05 4/25/05 Caution
• Beta Software Release 3/21/05 3/21/05 4/29/05 4
  /29/05 4/29/05 6/8/05 At Risk
• Construction Product Delivery 3/17/05 3/17/05 5/6
  /05 5/6/05 5/6/05 5/6/05 On Target
• Navy Approval Construction Products 3/24/05 3/24/0
  5 5/27/05 5/27/05 5/27/05 5/27/05 On Target

Note Red dates indicate any change form
previous months PR Briefing.
10
Alpha 1 Development Status

• Schedule Orig PR5 Actual
• Alpha 1 SW Release 11/08/04
  12/30/04 12/30/04
• Development environment procured and implemented
  _at_ NSLC PAC
• Preliminary design and initial database
  established.
• Use Cases Developed
• Vote on Change
• Tally Vote
• Calculate Secondary Voting Options
• Issue - Use Cases still evolving
• Functionality addressed by these Use Cases is in
  the middle of the Entitled Process
• Many holes (missing business rules/actions
  needed) existed in documentation
• These use cases still being refined
• Testing Dec 20-30, 2004
• Unit Testing conducted by NSLC
• System Testing (Basically a black box at this
  point) conducted by NSLC
• Acceptance Testing not conducted (only limited
  functional capabilities exist)

11
Alpha 2 Development Status

• Schedule Orig Current Actual
• Alpha 2 SW Release 1/10/05 4/15/05
• Use Cases being provided in Blocks
• Block 2 (Development) 1/14/05
• Initiate Idea (Received 12/22/04)
• Submit Ship Change (Received 12/22/04)
• Find Ship Change (Received 12/22/04)
• Block 3 (Development) 2/04/05
• Assign Responsibility
• View Ship Change
• Edit Ship Change
• Block 4 (Development) 2/28/05
• Perform Technical Assessment
• Block 5 (Development) 3/21/05
• Perform AFOM Review
• Perform CBA Review
• System Testing 4/05/05

12
Alpha 2 Development Status (cont.)

• Issues
• Use Cases being received are out of order (for
  development/testing continuity) as to sequence of
  Entitled Process (e.g. Assign Responsibility
  after Initiate Idea Submit Ship Change)
• Results in
• Missing pieces in the Use Cases being developed
  and need to revisit code at a later date to
  complete
• Missing data for testing (not self generating)
• No valid entry point (Login Use Case is in Beta
  (Block 6)) process depends upon
  roles/privileges Need to revisit previous code
  development.
• Working with ASC to review use case delivery to
  ensure sequence is modified to facilitate most
  efficient and effective schedule
• Alpha 2 Design Model not received yet
• GUI/SCD Mock-ups not received (Block 2
  development due to be completed by 1/14/05)

13
Use Case General Venn Diagram
Future Enhancements to Entitled Process Software
Expert Tool Functionality (3)
Advanced Automated Support (12)
Advanced Reporting (3)
Advanced Admin Reporting (11)
Post DP 3 Functionality (1)
Baseline Entitled Process Software
Alpha 1 Software Release (3 Use Cases)
Alpha 2 Software Release (9 Use Cases)
Beta Software Release (16 Use Cases)
14
Use Case Detailed Venn Diagram
Future Enhancements to Entitled Process Software
CBA Calculation Tool
TA Determination Tool
AFOM Decision Tool
Handle Conjunctive Alterations
Handle Trade Off Funding
Modify Ship Change (Post DP 3)
Raise for Vote
Modify Funding Level (budget line up/down)
Expert Level SCD Search
Handle Capability Alteration
Display Dashboard
Auto Notification of Action
Advanced Admin Reporting (14)
Auto Populate FMP
Request Ship Change Withdrawal
Rework
Baseline Entitled Process Software
Perform AFOM
Adjudicate Funding
Assign Responsibility
Admin Reporting (9)
Initiate Idea
Perform CBA
Prioritize FMP
Tally Vote
Find Ship Change
Edit Ship Change
Vote on Change
Perform Technical Assessment
Refactor Funding
Submit Ship Change
View Ship Change
Calculate Secondary Voting Options
Linked Ship Change
Login
Notification of Action
Endorse Funding Line
Raise for Vote
15
Entitled Process Use Case Descriptions Alpha 1
16
Entitled Process Use Case Descriptions Alpha 2
17
Entitled Process Use Case Descriptions Beta
18
Entitled Process Activity Use Cases
Note1 Finalize Assessment SCD has been removed
and its functionality has been distributed to
other use cases.
19
Admin Reporting Use Cases

Note 1 Administrator Adjust SCD and Create
Ad Hoc Report Use Case functionality will be
used to implement future automation opportunities
within the Baseline software. Note 2 Assign
Voting Board Members, Implement Pick Lists, and
Save Ad Hoc Reports Use Case functionality have
been absorbed into other Use Cases Note 3
Administrator Adjust SCD has been moved from
Alpha 2 to Beta Release to facilitate meeting
Alpha 2 schedule and New Find NDE User use case
has been added
20
Software Development
Note 1 Number of Use Cases indicates total
number of Use Cases identified as part of
Baseline Entitled Process Software. Second
number of Use Cases indicates number of Use Cases
that are currently fully populated (i.e. Baseline
will have 28 Use Cases and 15 are currently
populated or 28/15). Note 2 Current Values
reflect actual values at the time of the brief
while values for various phases will not change
from the initial Inception Phase estimates. Note
3 December Estimates based on end of January
rather than 14 January.
21
Software Development

• The following Risks are currently being managed

E D C B A
PROBABILITY

• 2 3 4 5
• IMPACT

22
Software Development

• All identified risks

Note Assumes Software Development and Testing
IAW Current Schedule Estimates
23
Software Development

• Entitled Process Definition
• Need to establish baseline and configuration
  control on Business Rules
• Created Topical Business Rule outline and
  populated with 6 July BRs plus embedded Alpha 1
  Block 3/4 BRs
• BRTs establishing rules outside Business Rule
  Baseline Need to obtain BRT Outbriefs
• Business Rules Backward Compatibility Remains
  an Issue
• Populating All Business Rules which drive
  software to be developed in topical outline
• Need to promptly adjudicate Business Rule Issues
  SMEs are working to do so
• Need to validate automation estimates comply with
  Stakeholders expectations
• SCD Submitter will check if SCD could be
  re-submitted or combined with current SCD How
  much automation?
• Degrees of Automation by Business Rule activity
• Resources
• Current Resources sufficient to provide robust
  architecture and baseline functionality
  Requirements, Design, and Test Model Artifacts
• Funding to Complete
• Funding provided or in process
• Additional funding requirements dependent upon
  potential functionality requirements
• Risks
• Need to Lock Down Iterative Requirements and
  Design Products
• Managing Expectations
• Requirements Creep

24
Software Development

• Critical Path
• Entitled Process Definition
• Still in flux, coming into better focus and
  under configuration control but still not there
• Inception Phase Product Completion / Acceptance
• Delivered on August 13, Inception Phase products
  are approved
• Elaboration Phase Product Completion / Acceptance
  (Alpha 1 and 2)
• Need overall SHIPMAIN, Entitled Process, and
  software Scope defined
• Alpha 1 Requirements, Design, and Test Model
  Delivered and Accepted (10/11)
• Elaboration Phase activities may be re-directed
  based on functionality requirements
• Robust Architecture Needs to be Instantiated and
  Validated
• Part of Alpha 1 Functionality Coded and Validated
• Need Alpha 2 Functionality instantiated and
  associated information integrated
• Construction Phase Product Completion /
  Acceptance (Beta and GAR)
• Beta Functionality will complete system usability
• User testing to validate system acceptance
• Transition Phase Product Completion / Acceptance
  - General Availability Release
• Integration into existing operational user
  Information Infrastructure

25
Software Development

• Critical Path (cont) - Risk Mitigation
• Locking Down Requirements and Design Products
• Put Interim Process, Block Requirements and
  Design Products Under CM Completed and working
• Exercise Business Rules and Use Cases via
  multiple scenarios before approval and delivery -
  Progressing
• Managing Expectations
• Honest communications, including Bad news -
  Progressing
• Develop Detailed ShipMain Software Transition
  Plan
• Expected Automation Table listed by Business
  Activity Completed and working
• Develop Detailed POAM for design and development
  activities - Progressing
• Requirements Creep
• Requirements Management ensures change impact
  understood prior to including in scope.
• Process plan approved, methods are being used,
  but consuming resources - Progressing
• Use CM Process -
• Process approved, methods in use, baselines are
  established Completed and working
• Incomplete business model and rules
• Clearly define Scope and determine iterative
  software development approach.
• Business Rule definitions and issue adjudication
  are progressing, although slowly - Progressing
• Automation Table is serving as basis for scope
  and baseline functionality Completed and
  working
• Decisions may be needed to accommodate scope,
  functionality, and re-work issues - Progressing

26
Entitled Process Cost Total
Pre-Inception
Inception
Elaboration
Construction
Transition
27
NDE-NM Entitled Process Summary

• Functional Area Level of
  Confidence
• Short Term Entitled Process
• Ship Change Document
• Release 1.1 July 22, 2004 Complete
• Release 1.2 August 26, 2004 Complete
• Release 1.3 Sept 3, 2004 Complete
• Release 1.4 Oct 10, 2004 Complete
• Release 1.5 Oct 26, 2004 Complete
• Release 1.6 Nov 4, 2004 Complete
• Release 1.6.5 Nov 23, 2004 Complete
• Release 1.6.8 Dec 16,2004 Complete
• Release 1.6.9 Dec 27, 2004 Complete
• Release 1.7 Feb 23, 2005 High
• Short Term Entitled Process
• Secure NDE-NM Environment
• Operational Feb 22, 2005 MEDIUM
• Secure AMPS NITRA (2-way) TBD MEDIUM
• Long Term Entitled Process
• Software Development

28
NDE NM Entitled Process Action Items
NAVY DATA ENVIRONMENT- NAVY MODERNIZATION
(NDE-NM) PROGRAM REVIEW MEETING ACTION
ITEMS, What, Who, When (W3s)
W3s from 14 Dec 2004
W3s from 18 Nov 2004
W3s from 18 Nov 2004