ANMS v2.0 DDR
- Agenda
- Review Board
- Software Overview
- Work Product Status
- Requirements
- List of Software Change
- Test Status Summary
- Test Case Explanation(s)
- Unverified Requirements
- Unverified Improvements
- Unverified Defect Corrections
- Software Status
- Open Defect Summary
- Open CRIT 1 & 2 Defects
- Action Item Status
- Deviation Summary
- Deviations
| Review Board Chair | Jamie Shin |
| MGSS Chief Engineer | Michele Vogt |
| ANMS Task Lead | David Linko (for Brian Sipos) |
| ANMS CogE | Madeline Farina |
| MGSS Software Quality Assurance Engineer | Lila Baez (for Korwin Anderson) |
| MGSS MCS AEM | Erik Monson |
| MGSS System Test Lead | Madonna Ryan |
| MGSS Cybersecurity Engineer | Mike Pajevski |
| MGSS Customer Support Lead | Scott Markham |
| Customer | Kathy Rockwell |
Protocols:
- The Asynchronous Management Protocol (AMP) allows managing remote devices over delayed or disrupted transports
- The Bundle Protocol (BP) is a datagram (self-contained) transport layer which can operate over delayed or disrupted links and paths with arbitrary hop-lengths
- A Convergence Layer (CL) is how BP bundles are transported over a single hop of an end-to-end path
- The Internet Protocol (IP) is for terrestrial/wide-area internetworking
Terms:
- An Application Data Model (ADM) defines fixed structural objects, similar to a YANG or SMI model
- Runtime managed objects are part of the Operational Data Model (ODM)
- Both ADM and ODM objects have a Uniform Resource Identifier (URI) form of naming which is called its Asynchronous Resource Identifier (ARI), similar in function to an SMI Object Identifier (OID) but with parameters
- The Asynchronous Network Management System (ANMS) is a toolset to integrate a DTN Management Architecture (DTNMA) Manager with a Bundle Protocol (BP) Agent and provide user-facing tools to construct controls to remote Agents, as well as process and aggregate reports from Agents
- Requirements were removed and in terms of capability, the tools ANMS v2.0 uses (ACE, CAMP) were updated via the latest IETF drafts
- The scope of the ANMS is on the Manager side
- The test configuration contains a pre-existing set of ADMs related to agent management
- The test environment contains several Agents with pre-planned states
Version 2 of ANMS is a refinement of capability and a synchronization with the latest IETF and CCSDS drafts. This release removes JPL ION as a direct deployment dependency. Because of this, the ANMS does not configure or depend upon BP security or any particular convergence layers. This removes the need to configure ION or any other BPA for the developer. The v2.0 update includes defect fixes, usability enhancements, and sustainment updates.
- The logical diagram found in the ANMS Product guide found here includes 5 primary types of host
- The User Agent and Managed Device can have any number of instances (simultaneous use is resource-limited but in the thousands for modest resources)
In addition to the JPL-managed MGSS Controlling and Reference Documents (specifically v1.2, for SDR rev10 compliance), the following documents are being used for this release:
| Document Title | DMS Doc and Revision ID | DMS Document Status |
|---|---|---|
| ANMS TIP | DOC-002847 | Released |
| ANMS Release Plan | DOC-005851 rev A | In review |
| ANMS Concept of Operations for V0.1 | DOC-005437 | Released |
| ANMS Requirements (SRD) | DOC-005083 rev B | In signature |
| ANMS Architecture Design Document (ADD) | DOC-005089 | Released |
| ANMS Interface Specification (SIS) | DOC-005446 rev A | In review |
| ANMS Test Plan | DOC-005925 | In review |
| ANMS Test Specification | DOC-005926 | In review |
| ANMS Test Report for v2.0 | DOC-005442 | In review |
| ANMS Release Description (RDD) | DOC-005447 rev A | In review |
| ANMS Product Guide | DOC-005444 rev B | In review |
| ANMS User Guide | DOC-005443 rev B | In review |
| ANMS Software Design Document (SDD) | DOC-005445 | Released |
We removed the following untestable requirements, once listed (and now removed) from the Software Requirements Document rev B:
• 4.2.1.2
• 4.2.4.1
• 4.3.2.1
• 4.3.2.3
• 4.4.2.4
• 4.5.1.2
• 4.5.2.2
• 4.5.3
• 4.6.3.5
Total: 9
There are no new requirements.
Data collected on 10/14/2025.
The description of "new" in the Deviation column below for any of the tables implies that this RLI was either not listed in the original v2.0 release plan or not mentioned in TRR.
Specific issues with enhancement label:
Total number of new improvements: 18
Specific issues with bug label:
| Ticket | Criticality | Deviation |
|---|---|---|
| #12 Valid Message Conversion: Transcoder log display | CRIT-4 | new |
| #13 Valid Message Conversion: Pending | CRIT-4 | new |
| #16 Manage Agents: Invalid TBR entries | CRIT-4 | new |
| #17 Received Reports: Report Title | CRIT-4 | new |
| #27 Navigation: Page refresh | CRIT-4 | new |
| #31 ADM Listing: Missing controls | CRIT-4 | new |
| #39 EDDs: EDDs with REF | CRIT-4 | unchanged from v1.2 RP |
| #46 Generate Reports: Source report input | CRIT-4 | new |
| #47 Upload New, Valid ADM: Missing operation | CRIT-4 | new |
| #50 Known package issues | CRIT-4 | new |
| #87 Invalid Modifications to Existing ADM: Original ADM removed | CRIT-4 | new |
| #91 Received Reports – Report displays | CRIT-4 | new |
| #104 Agent Information – Agent address | CRIT-4 | new |
| #112 Generate Reports – BP full report | CRIT-4 | unchanged from v1.2 RP |
| #140 Investigate purpose of Docker socket API | CRIT-3 | unchanged from v1.2 RP |
Defects introduced and fixed during testing cycle:
Total number of defect repairs: 25
| Defect Criticality | Defect Count |
|---|---|
| CRIT-1 | 0 |
| CRIT-2 | 0 |
| CRIT-3 | 5 |
| CRIT-4 | 20 |
Specific issues with sustainment label:
Total number of sustaining activities: 23
| Metric | Count |
|---|---|
| Total Number of Tests | 35 |
| Passed | 23 |
| Passed with Comments | 9 |
| Passed with Known Issues | 1 |
| Partial pass | 2 |
| Deferred | 0 |
| Not executed | 0 |
| Failed | 0 |
- Description: Received Reports
- Result: Passed with Comments
- Reason: Test case executed as specified in the test specification. It would be useful to be able to see the entire 'report-list' column in the Received Reports panel. It is awkward to scroll through the field to review its contents. Adding an option to hover over the entire field or to export the selection would help.
- Description: ARIs
- Result: Passed with Known Issue
- Reason: Test case executed as specified in the test specification, with known issue for missing panel information icon, previously submitted.
- Description: Variables
- Result: Partial
- Reason: Variables were successfully generated and used in reports, but results were not obtained when submitted to an agent. It is the responsibility of the agent to evaluate the expression, making this issue out of the purview of ANMS.
- Description: Multiple Controls
- Result: Partial
- Reason: Expected resullts for TBRs with multiple controls sent to two agents did not consistently produce the expected results.
There are none. Note that "unverified" means our tester could not come up with a procedure for them.
| Requirement ID | Requirement Stagement | Rational for Not Verifying Requirement |
|---|---|---|
| n/a | n/a | n/a |
There are none.
There are none.
| Component | Lines of Code | Lines added | Comment Lines | Code Coverage |
|---|---|---|---|---|
| ANMS | 10.3k | 1.6k | 2.9k | TBD |
Code Coverage is TBD because we do not have an built-in mechanism to collect code coverage from ANMS as a deployed system.
-
CM Tool: Github, CM Repository: https://github.com/NASA-AMMOS/anms
-
Package: ICA for v2.0 release is ICA-48271: https://jira.jpl.nasa.gov/browse/ICA-48271
| Metric | Prior DDR (v1.1) | This DDR (v2.0) |
|---|---|---|
| Defects Opened in Cycle | 20 | 15 |
| Defects Closed in Cycle | 12 | 25 |
| Open Criticality 1 Defects | 0 | 0 |
| Open Criticality 2 Defects | 0 | 0 |
| Open Criticality 3 Defects | 1 | 2 |
| Open Criticality 4 Defects | 26 | 13 |
| Open Unassigned Criticality Defects | 0 | 0 |
Note that Defects opened in cycle does not equal all Open defects because some defects pre-existed this cycle.
This release has no CRIT-1 or 2 defects.
- Action Item MGSSAITS-1819 : opened at the v1.1 DDR (now closed)
| Deviation Category | Planned | Realized | Added |
|---|---|---|---|
| Requirements | 0 | 0 | 0 |
| Improvements | 14 | 19 | 5 |
| Defect Repairs | 4 | 25 | 21 |
| Sustaining Activities | 10 | 23 | 13 |
The only deviations to note are that the following RLIs were added after finalization and approval of the original v2.0 Release Plan and had to be added to the revised Release Plan on 10/22/2025:
In other words, there are more tickets closed at DDR than what was in the original v2.0 release plan. This is due to ongoing efforts to integrate ANMS v2.0 with internal software and/or projects (using internal funding).