Harris JTRS Project The A-Team Garrett Wampole Ben Litchfield Jason Offord Jason Gillman David Bryant

Agenda Introduction to JVMS Processes  Design, Development, and Delivery  Process Support Tools Schedules  Planning update Concerns  Risk Assessment Prototype Demonstration

Introduction JTRS Visual Modeling Studio (JVMS)  “…provide a graphical “CAD-like” means of creating and managing configurations for JTRS radios…”  A set of XML files describe the available hardware communications facilities and software applications  The configuration also details how to create and install the applications and their relationships and dependencies on other facilities  JVMS allows designers to visually create JTRS configurations and generate the corresponding XML

Processes Requirements Elicitation  Major portion of project plan  Six weeks (+) to learn domain, gather requirements  Requirements Specification delivered and inspected 1/16

Processes Incremental Design  Three Phases Phase 1 High Level Design : 1/25 Phase 1 Detailed Design : 2/11  Implement features per phase and validate with client before beginning next phase  Feedback from previous cycle is incorporated into subsequent phases

Processes Development  Proceeds directly after each design phase  First Phase : High priority requirements  Second and Third Phases : Medium and low priority requirements  Implementation of Phase 1 requirements by 3/7

Processes Testing  Test plan completed : 1/25  Test cases will be developed and run against features implemented in each phase  Test Cases for Phase 1 by 2/21

Process Support Tools Kelut  Set of web-based process support tools  Features Discussion Forums Requirements Management  Coming soon Issue Tracking Task Management Test Case Repository 

Schedules Week 8Human-Machine Interface (HMI) Week 8Draft Detailed Design (phase 1) Week 8Final Test Plan Document Week 8Review Detailed Design (phase 1) Week 9IPR 2 Week 9Final Detailed Design (phase 1) Week 9Draft Test Cases Document Week 9Begin Implementation (phase 1) Week 10Review Test Cases Document Week 11Final Test Cases Document Week 11Completion of phase 1 requirements (Code Freeze) Week 11Testing & Bug Fixes complete on phase 1 requirements Week 11Gather Customer Feedback

Schedules Week 11Update Requirements Document Week 12Update High Level Design (phase 2) Week 12Draft Detailed Design (phase 2) Week 12Review Detailed Design (phase 2) Week 13Final Detailed Design (phase 2) Week 13Begin Implementation (phase 2) Week 13Update Test Cases Week 14IPR 3 Week 15Completion of phase 2 requirements (Code Freeze) Week 15Testing & Bug Fixes complete on phase 2 requirements Week 15Gather Customer Feedback

Schedules Week 16Update Requirements Document Week 16Update High Level Design (phase 3) Week 16Draft Detailed Design (phase 3) Week 16Review Detailed Design (phase 3) Week 17Final Detailed Design (phase 3) Week 17Begin Implementation (phase 3) Week 17Update Test Cases Week 18Completion of phase 3 requirements Week 18Final Code Freeze Week 19Final Testing & Bug Fixes Week 20Deliver Product Week 20Product Training Week 20Post Mortem Week 20Presentation Preparation Week 20IPR 4

Risks Identified in Project Plan  Inexperience with.NET and C# Marginalized – Team has a good handle on the technology  Too much domain knowledge Team has spent a good amount of time with domain expert Still may pose concerns as development continues  Rigid deadline Try to disseminate as much as possible on the state of the project, conduct IPRs, etc Have a fairly firm plan to conform to schedule