This document outlines 15 sprints over 8 months to develop a track augmentation system. Sprint 0 focuses on knowledge transfer and environment setup. Sprints 1-3 involve requirements, prototypes, and demos. Later sprints implement augmenters for various data sources, interfaces, a web portal, and testing with a goal of the system providing augmented data through web services by the final sprint.
4. • Sprint 4 :Design and Documentation
• 8 weeks (09-05 01-07)
• Handover to Vincenzo
• Review of SRS with Vincenzo
• Doc.Analysis and Design
• Doc.Training Analysis
• SRR
• Sprint 5 : Design and Documentation
• 2 weeks (01-07 11-07)
• Doc.ICD
• Doc.Test Plan
• Doc.HMI Mock-ups
• JTR & CDR
AMN-12 Track Augmentation
Timeline Sprints
27/06/14 NATO UNCLASSIFIED 4
5. • Sprint 6 : TARM Implementation
• 3 weeks (11-07 01-08)
• Demo: SMB and SMTP and FTP data ingestion to TARM
• Sprint 7 : UTT Augmenter
• 5 weeks (01-08 05-09)
• Database Implementation
• Implement Generic Track Augmenter
• Implement Excel – TDL FieldForwarders
• Implementation of Excel Document Adapter
• Demo:Augmentation from Excel (via DB)
• Demo:SOP Excel(UTT) is persisted in DB
AMN-12 Track Augmentation
Timeline Sprints
27/06/14 NATO UNCLASSIFIED 5
6. AMN-12 Track Augmentation
Timeline Sprints
27/06/14 NATO UNCLASSIFIED 6
• Sprint 8 : ATO & LogFAS Augmenter
• 4 weeks (05.09 03-10)
• Implement ATO – TDL FieldForwarders
• Implement LogFAS Message – TDL FieldForwarders
• Implementation of ATO Document Adapter
• Implementation of LOGFAS Web Interface
• Demo:Augmentation from ATO (via DB)
• Demo:Augmentation from LogFAS info.(if LogFAS provides req. info)
7. AMN-12 Track Augmentation
Timeline Sprints
27/06/14 NATO UNCLASSIFIED 7
• Sprint 9 : Int-Core & ICC Interfaces
• 5 weeks (03.10 07-11)
• Implementation of ICC Web Interface and ICC data persistence.
• Implement Int-Core Subscription Interface
• Implement Int-Core Specific ATO Document Adapter and data persistence.
• Implementation of BSO Adapter and data persistance.
• Demo:Augmentation from ICC info.(if ICC provides req. info) and Int-Core
Specific ATO Document or BSO.
8. AMN-12 Track Augmentation
Timeline Sprints
27/06/14 NATO UNCLASSIFIED 8
• Sprint 10 : TrAD Producer
• 3 weeks (07-11 28-11)
• Implementation of Track Augmentation Data Producer.
• Implementation of BSO generator.
• Demo:TARM can provide Augmentation data via Request/Response Web
Services.
• Sprint 11 : Web Portal & TA user management tool
• 3 weeks (28-11 19-12)
• Implementation of Web Portal.
• Implementation of TA user management tool.
• Demo:User will be able to enter, query and edit Augmentation Data through
Web Portal.
• Demo:Administrators will be able to create and manage authorised TA users.
9. AMN-12 Track Augmentation
Timeline Sprints
27/06/14 NATO UNCLASSIFIED 9
• Sprint 12 : NVG&KML service
• 2 weeks (19-12 09-01, 1 Week off)
• Implementation TIES Manager and TARM interface for LinkBack page table.
• Implementation of augmentation data details web page.
• Demo: NVG-KML clients will be able to receive augmented data through NVG or KML
messages.
• Demo:User will be able see augmentation data details when clicked on the NVG or KML link-
backpage button.
• Sprint 13 : ORBATLAND & LC2IS Augmenter
• 4 weeks (09-01 06-02)
• Implement ORBATLAND – TDL FieldForwarders
• Implement LC2IS Message – TDL FieldForwarders
• Implementation of ORBATLAND Document Adapter
• Implementation of LC2IS Web Interface
• Demo:Augmentation from ORBATLAND (via DB)
• Demo:ORBATLAND is persisted in DB (From File)
• Demo:LC2IS data is persisted in DB (Via Web Services)
• Demo:Augmentation from LC2IS info.(if LC2IS provides req. info)