1 / 12

Harris JTRS Project

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.

hayden-fulton
Download Presentation

Harris JTRS Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. 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

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

  5. 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

  6. 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

  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

  8. 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/

  9. Schedules

  10. Schedules

  11. Schedules

  12. 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

More Related