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

Harris JTRS Project

Embed Size (px)

DESCRIPTION

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. - PowerPoint PPT Presentation

Citation preview

Page 1: Harris JTRS Project

Harris JTRS Project

The A-TeamGarrett WampoleBen LitchfieldJason OffordJason GillmanDavid Bryant

Page 2: Harris JTRS Project

Agenda

Introduction to JVMS Processes

Design, Development, and Delivery Process Support Tools

Schedules Planning update

Concerns Risk Assessment

Prototype Demonstration

Page 3: Harris JTRS Project

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

Page 4: Harris JTRS Project

Processes

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

1/16

Page 5: Harris JTRS Project

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

Page 6: Harris JTRS Project

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

Page 7: Harris JTRS Project

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

Page 8: Harris JTRS Project

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

http://jtrs.kelut.org/

Page 9: Harris JTRS Project

Schedules

Week 8 Human-Machine Interface (HMI)

Week 8 Draft Detailed Design (phase 1)

Week 8 Final Test Plan Document

Week 8 Review Detailed Design (phase 1)

Week 9 IPR 2

Week 9 Final Detailed Design (phase 1)

Week 9 Draft Test Cases Document

Week 9 Begin Implementation (phase 1)

Week 10 Review Test Cases Document

Week 11 Final Test Cases Document

Week 11 Completion of phase 1 requirements (Code Freeze)

Week 11 Testing & Bug Fixes complete on phase 1 requirements

Week 11 Gather Customer Feedback

Page 10: Harris JTRS Project

Schedules

Week 11 Update Requirements Document

Week 12 Update High Level Design (phase 2)

Week 12 Draft Detailed Design (phase 2)

Week 12 Review Detailed Design (phase 2)

Week 13 Final Detailed Design (phase 2)

Week 13 Begin Implementation (phase 2)

Week 13 Update Test Cases

Week 14 IPR 3

Week 15 Completion of phase 2 requirements (Code Freeze)

Week 15 Testing & Bug Fixes complete on phase 2 requirements

Week 15 Gather Customer Feedback

Page 11: Harris JTRS Project

Schedules

Week 16 Update Requirements Document

Week 16 Update High Level Design (phase 3)

Week 16 Draft Detailed Design (phase 3)

Week 16 Review Detailed Design (phase 3)

Week 17 Final Detailed Design (phase 3)

Week 17 Begin Implementation (phase 3)

Week 17 Update Test Cases

Week 18 Completion of phase 3 requirements

Week 18 Final Code Freeze

Week 19 Final Testing & Bug Fixes

Week 20 Deliver Product

Week 20 Product Training

Week 20 Post Mortem

Week 20 Presentation Preparation

Week 20 IPR 4

Page 12: Harris JTRS Project

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