INTERNSHIP REPORT
Naval Science and Technological Laboratory (NSTL), DRDO
Visakhapatnam, Andhra Pradesh
Internship Duration: 1st August, 2025 – 30th January, 2026
Project Completion Date: 30th January, 2026
Submitted by:
Puskar Sarkar
Under the Guidance of:
Dr. R. Rajeswari Devi
Scientist-H, NSTL-DRDO
Project Supervision and Technical Mentorship:
Mr. Asish Mukherjee
Scientist-E, NSTL-DRDO
1
CERTIFICATE
This is to certify that Puskar Sarkar has successfully completed his internship at Naval
Science and Technological Laboratory (NSTL), Defence Research and Development
Organisation (DRDO), Visakhapatnam, from 1st August, 2025 to 30th January, 2026
under the guidance of Dr. R. Rajeswari Devi, Scientist-H, NSTL-DRDO. The assigned
project was completed on 30th January, 2026. During this period, he demonstrated good
technical knowledge and systematic working approach. His contributions to AIU
software enhancements, Plot Solution Window redesign, Target Motion Analysis (TMA)
restructuring and circular buffer implementation were carried out with discipline and
attention to system stability.
Dr. R. Rajeswari Devi
Scientist-H, NSTL-DRDO
Mr. Asish Mukherjee
Scientist-E, NSTL-DRDO
2
ACKNOWLEDGEMENT
I express my sincere gratitude to Naval Science and Technological Laboratory (NSTL),
Defence Research and Development Organisation (DRDO), Visakhapatnam, for
providing me with the opportunity to carry out my internship in a secure and professional
research environment. This internship gave me valuable exposure to software
development and system engineering.
I am deeply thankful to my guide Dr. R. Rajeswari Devi, Scientist-H, NSTL-DRDO, for
her continuous guidance, encouragement, and technical direction throughout the
internship.
I would like to express my sincere thanks to Mr. Asish Mukherjee, Scientist-E, NSTL-
DRDO, for his supervision and technical mentoring. His explanations and suggestions
were extremely helpful in understanding system behavior and implementing software
improvements effectively.
3
CONTENTS
Certificate .....................................................................................................2
Acknowledgement ............................................................................................3
List of Technical Terms and Abbreviations .....................................................6
Executive Summary ..........................................................................................7
1. INTRODUCTION............................................................................................ 8
1.1 Background.......................................................................................... 8
1.2 Motivation.......................................................................................... 8
1.3 Objectives of the Work............................................................................ 9
1.4 Scope of the Project............................................................................... 9
2. LITERATURE REVIEW...................................................................................... 10
2.1 Data Organization Using Container-Based Structures........................................... 10
2.2 Unified Data Access and Abstraction............................................................. 10
2.3 Bounded Data Storage and Circular Buffers..................................................... 11
2.4 User Interface Interaction and Visualization Design............................................ 11
2.5 Motivation for the Present Work................................................................. 11
3. METHODOLOGY............................................................................................ 13
3.1 Overview of the Approach......................................................................... 13
3.2 Study of Existing Implementation................................................................ 13
3.3 Unified Data Structure Design................................................................... 14
3.4 Controlled Mapping Mechanism................................................................... 14
3.5 Bounded Storage Using Circular Buffer.......................................................... 15
3.6 Data Retrieval Strategy.......................................................................... 16
3.7 Interface Enhancement and Visualization Improvements........................................ 16
3.8 Testing and Validation.......................................................................... 16
3.9 Tools and Development Environment............................................................. 17
4. FINDINGS.................................................................................................... 18
4.1 Overview of Results.............................................................................. 18
4.2 Improved Data Organization..................................................................... 18
4.3 Consistent and Reliable Data Retrieval........................................................ 18
4.4 Bounded Storage Behavior....................................................................... 19
4
4.5 System Stability During Continuous Input...................................................... 19
4.6 User Interface Improvements.................................................................... 19
4.7 Reduction in Maintenance Effort................................................................ 20
4.8 Summary of Key Findings........................................................................ 20
5. DISCUSSION............................................................................................ 21
5.1 Interpretation of Results........................................................................ 21
5.2 Impact of Data Structure Restructuring........................................................ 21
5.3 Significance of Bounded Storage................................................................ 22
5.4 Reliability of Data Retrieval................................................................... 22
5.5 User Interface Enhancements and Usability..................................................... 22
5.6 Design Trade-offs and Constraints............................................................. 23
5.7 Lessons Learned................................................................................... 23
5.8 Overall Discussion Summary..................................................................... 23
6. CONCLUSION AND FUTURE SCOPE........................................................... 24
6.1 Conclusion.......................................................................................... 24
6.2 Key Outcomes...................................................................................... 24
6.3 Future Scope....................................................................................... 24
6.4 Final Remarks...................................................................................... 25
7. REFERENCES............................................................................................ 26
8. APPENDICES............................................................................................ 27
Appendix A: System-Level Design Overview.......................................................... 27
Appendix B: Data Flow Overview...................................................................... 27
Appendix C: Circular Buffer Management............................................................ 28
Appendix D: Glossary of Technical Terms............................................................ 29
Appendix E: Confidentiality Statement............................................................... 29
5
LIST OF TECHNICAL TERMS AND ABBREVIATIONS
Abbreviation /
Full Form Description / Usage in This Project
Term
Core software module responsible for visualization
Article Interfacing and interaction with tracking and analysis outputs.
AIU
Unit Enhanced to support interactive vectors and
improved display behavior.
Analytical process used to compute and manage
Target Motion
TMA motion-related solution data from incoming sensor
Analysis
information.
Integrated
Qt Creator was used for development, debugging,
IDE Development
and testing of the software modules.
Environment
C++ framework used for GUI development and
Qt Qt Framework
event-driven programming in AIU modules.
Qt Vector Dynamic array container from the Qt framework
QVector
Container used to store solution data efficiently.
User defined type used to map solution categories to
Enum Enumeration
indices in the unified storage structure.
Application
Standard interface through which different software
API Programming
components interact with each other.
Interface
Graphical User Visual interface through which operators interact
GUI
Interface with displayed tracking and analysis data.
Constant Time Indicates that data access operations execute in
O(1)
Complexity constant time regardless of data size.
Display layer through which processed data is
UI User Interface
presented to the user.
6
EXECUTIVE SUMMARY
Modern tracking and visualization applications require efficient handling of continuously
generated solution data along with clear and responsive user interfaces. During this
internship, work was carried out to improve the structure, usability, and data management
mechanisms of an existing tracking and display software system.
The project focused on four major areas: integration of a movable and interactive vector
in the user interface, redesign of the Plot Solution Window to improve clarity and
stability, restructuring of solution data storage using a unified vector-of-vectors approach,
and implementation of a circular buffer mechanism to maintain bounded historical data.
These changes reduced data redundancy, improved maintainability, and ensured
consistent memory usage during continuous operation.
The redesigned architecture provides a structured approach for storing, retrieving, and
displaying solution data, while the improved interface components enhance user
interaction and visualization clarity. Overall, the work contributed to better software
organization, improved performance consistency, and easier future extension of the
system.
7
INTRODUCTION
1.1 Background
Modern software applications that handle continuous streams of data and graphical
visualization require well-structured internal architectures to ensure stability, clarity, and
ease of maintenance. As systems evolve, additional features and solution types are often
introduced, leading to increased complexity in both data handling and user interface
components.
Over time, such growth can result in scattered data storage, repeated logic, and tightly
coupled modules. These issues make the system difficult to extend, debug, and optimize.
Therefore, periodic restructuring and refinement of both data management and
visualization components are essential to maintain software quality and long-term
reliability.
Figure 1.1: Overview of the Software System
1.2 Motivation
The existing implementation relied on multiple independent data containers and separate
access functions for handling similar categories of information. This approach led to
repetitive logic, increased maintenance effort, and reduced flexibility when introducing
new features. Additionally, the visualization components required improvements to
support better interaction, clarity, and layout organization.
8
Another important implementation was the continuous accumulation of historical data.
Without a bounded storage mechanism, the system risked uncontrolled memory growth
and unpredictable behavior over extended execution periods. This highlighted the need
for a structured and capacity-controlled data management approach.
These factors motivated the redesign of both the internal data structures and the
associated interface components.
1.3 Objectives of the Work
The primary objective of this project was to improve the organization, maintainability,
and usability of the existing system through systematic restructuring and interface
enhancement. The specific goals of the work included:
• Redesigning data storage using a unified vector-of-vectors structure to reduce
redundancy.
• Implementing a bounded storage mechanism to manage historical data efficiently.
• Improving data retrieval through centralized and controlled access interfaces.
• Enhancing graphical components by introducing a movable and interactive vector.
• Redesigning the Plot Solution Window to improve clarity, stability, and user
interaction.
1.4 Scope of the Project
The scope of this project was limited to software-level restructuring and interface
improvements. It did not involve changes to external data sources or underlying hardware
components. All modifications were performed within the existing application framework
and followed predefined system constraints.
The work focused on improving internal logic, optimizing data flow, and enhancing
visualization behavior while preserving existing functionality and output consistency.
9
LITERATURE REVIEW
Software systems that deal with continuous data updates and graphical visualization often
face challenges related to data organization, performance stability, and user interaction.
Over time, several approaches have been proposed to improve data handling efficiency,
reduce redundancy, and enhance visualization clarity. This chapter reviews relevant
concepts and design practices that influenced the work carried out during this internship.
2.1 Data Organization Using Container-Based Structures
Dynamic data structures such as arrays, lists, and vectors are commonly used for storing
time-varying information in software applications. Among these, vector-based containers
are widely preferred due to their ease of access, memory locality, and flexibility.
However, when multiple categories of similar data are handled independently using
separate containers, the system often becomes difficult to maintain.
Previous studies and software design guidelines suggest consolidating related data into
hierarchical container structures such as vector-of-vectors or map-based storage. This
approach reduces duplication of logic and allows unified access patterns. By indexing
solution data through enumerations or identifiers, the complexity of managing multiple
independent data streams can be significantly reduced.
Figure 2.1: Legacy and Unified Data Storage Approaches
2.2 Unified Data Access and Abstraction
10
Large software systems often suffer from excessive conditional logic, such as long
switch-case or if-else chains, especially when handling multiple data types. Literature on
software refactoring emphasizes replacing such structures with unified interfaces and
abstraction layers. This improves code readability and minimizes the risk of errors when
extending the system.
Index-based access mechanisms, combined with centralized helper functions, provide a
clean way to retrieve and update data without repeatedly writing similar logic. This
concept formed the foundation for restructuring the solution storage mechanism in the
present work.
2.3 Bounded Data Storage and Circular Buffers
Continuous data generation can lead to unbounded memory growth if historical data is
stored indefinitely. To address this, bounded storage techniques such as circular buffers
have been widely adopted in software systems. A circular buffer maintains a fixed
maximum size and automatically removes the oldest data when new data is added beyond
the limit.
Unlike linear containers that require shifting elements during deletion, circular buffers
operate using index rotation, ensuring consistent memory usage and predictable
performance. Literature highlights circular buffers as an effective solution for
maintaining recent history while avoiding memory overflow, making them suitable for
long-running applications.
2.4 User Interface Interaction and Visualization Design
User interfaces that display dynamic data must balance information density with clarity.
Research in interface design emphasizes interactive elements such as movable vectors,
scalable plots, and responsive windows to improve user understanding. Poorly designed
visualization components can lead to cluttered displays and reduced usability.
Redesigning visualization windows to separate concerns, reduce overlap, and present data
in a structured manner improves user interaction. Allowing controlled movement and
interaction with graphical elements further enhances interpretability without
overwhelming the user.
2.5 Motivation for the Present Work
Based on the reviewed concepts, it is evident that efficient data management, bounded
storage, and clean visualization are essential for maintaining stable and maintainable
software systems. The existing implementation relied heavily on repetitive data structures
and scattered logic, which increased complexity and maintenance effort.
11
The work carried out during this internship applies established software design
principles—such as unified data structures, abstraction, bounded storage, and improved
visualization—to reorganize and enhance the existing system in a systematic and
maintainable manner.
12
METHODOLOGY
3.1 Overview of the Approach
The work carried out in this project followed a structured and step-by-step methodology
focused on improving data organization, controlled storage, and user interface behavior.
The approach emphasized understanding the existing system, identifying limitations,
designing improved structures, and validating the changes through testing.
Each modification was introduced in a controlled manner to ensure that existing
functionality remained unaffected while achieving better clarity, maintainability, and
performance.
Figure 3.1: Overall Methodology Workflow
3.2 Study of Existing Implementation
The first step involved a detailed analysis of the existing system to understand how data
was stored, accessed, and displayed. Multiple independent containers were being used to
store similar categories of information, each with its own access logic.
This design resulted in:
• Repetition of similar operations across different modules
• Increased dependency between data structures and interface components
13
• Difficulty in extending the system for additional solution types
The visualization layer was also examined to identify usability and layout-related issues,
particularly in the plot display and interactive elements.
3.3 Unified Data Structure Design
To address redundancy and scattered storage, a unified data organization approach was
designed. Instead of maintaining multiple independent containers, related data elements
were grouped under a single hierarchical structure.
Figure 3.2: Unified Vector-of-Vectors Data Structure
This was achieved by:
• Categorizing solution types using a controlled mapping mechanism
• Storing related data in a vector-of-vectors arrangement
• Ensuring uniform access patterns across all solution categories
This design reduced duplication and allowed future extensions without altering the
overall structure.
Figure 3.3: Unified Data Flow After Restructuring
3.4 Controlled Mapping Mechanism
14
A controlled mapping mechanism was introduced to translate incoming data types into
internal indices. This ensured consistent access to the unified storage structure and
eliminated the need for repetitive conditional logic.
By centralizing the mapping logic:
• Data access became predictable and easy to manage
• Errors due to incorrect indexing were minimized
• Maintenance effort was significantly reduced
Figure 3.4: Controlled Mapping and Unified Access Mechanism
3.5 Bounded Storage Using Circular Buffer
To prevent uncontrolled data growth, a bounded storage mechanism was implemented. A
circular buffer strategy was adopted to retain only the most recent set of data entries
while automatically discarding older records.
The circular buffer ensured:
• Fixed memory usage regardless of runtime duration
• Stable system behavior during prolonged execution
• Consistent availability of recent data for display and analysis
Figure 3.5: Circular Buffer Bounded Storage Workflow
15
3.6 Data Retrieval Strategy
A unified retrieval interface was designed to access stored data. This interface supported:
• Retrieval of the latest available data
• Retrieval based on time or sequence reference
• Consistent output formatting for downstream modules
Centralized retrieval logic improved reliability and reduced the risk of mismatched data
handling across different components.
Figure 3.6: Unified Data Retrieval Strategy
3.7 Interface Enhancement and Visualization Improvements
The user interface was enhanced by introducing an interactive and movable vector
element. This allowed users to adjust and analyze graphical information more intuitively.
Additionally, the Plot Solution Window was redesigned to:
• Improve layout alignment and readability
• Enhance stability during data updates
• Support smoother interaction without display flickering or overlap
These improvements resulted in a more user-friendly and visually consistent interface.
3.8 Testing and Validation
Testing was conducted after each major modification to ensure correctness and stability.
Validation involved:
16
• Verifying data integrity after restructuring
• Ensuring bounded storage behavior under continuous data input
• Observing interface response during interaction and updates
Test results confirmed that the redesigned components behaved consistently with
expected system behavior.
3.9 Tools and Development Environment
All work was performed using existing development tools and frameworks available
within the system environment. The methodology focused on logic refinement and
structural improvement rather than introducing external dependencies.
17
FINDINGS
4.1 Overview of Results
This chapter presents the outcomes observed after implementing the redesigned data
structures, bounded storage mechanism, and user interface enhancements. The results
demonstrate improvements in data organization, system stability, and interface usability.
The findings are based on functional testing, observation during execution, and
comparison with the earlier implementation.
4.2 Improved Data Organization
After restructuring the data storage mechanism, all related solution data was successfully
managed using a unified hierarchical structure. This eliminated the need for maintaining
multiple independent containers for similar data categories.
Key observations include:
• Reduced redundancy in data handling
• Uniform access pattern across all solution types
• Easier extension of the system for future solution categories
The centralized storage approach improved clarity and reduced complexity in data
management.
Figure 4.1: Improved Data Organization After Restructuring
4.3 Consistent and Reliable Data Retrieval
The unified retrieval interface provided consistent access to stored data across all
components. Retrieval based on recent data as well as reference-based selection was
verified during testing.
Findings indicate:
• Accurate retrieval of the most recent data
18
• Stable behavior during repeated access requests
• No mismatch between stored and displayed data
This consistency reduced logical errors and simplified downstream processing.
4.4 Bounded Storage Behavior
The bounded storage mechanism successfully restricted memory growth by maintaining a
fixed-size data history. Once the storage limit was reached, older entries were
automatically replaced by newer ones.
Observed results:
• Memory usage remained stable over extended execution
• Older data was removed in a predictable order
• Recent data was always available for analysis and display
This behavior ensured controlled memory usage without affecting data availability.
4.5 System Stability During Continuous Input
The system was tested under continuous data input conditions. Even during prolonged
operation, the storage and retrieval mechanisms remained stable.
Notable observations:
• No unexpected delays or failures
• Smooth data updates without interruption
• Consistent system behavior across long runtimes
This confirms the reliability of the implemented design.
4.6 User Interface Improvements
The integration of an interactive and movable vector improved user interaction with
graphical elements. Users were able to adjust and analyze visual data more intuitively.
The redesigned plot solution window showed:
• Improved layout clarity
• Better alignment of graphical elements
• Reduced visual clutter during updates
19
These improvements enhanced overall usability and presentation quality.
4.7 Reduction in Maintenance Effort
By consolidating data handling logic and eliminating redundant structures, the system
became easier to maintain.
Key outcomes:
• Fewer points of failure
• Simplified debugging and updates
• Improved readability of the internal structure
This makes future enhancements more manageable and less error-prone.
Figure 4.2: Reduction in Data Handling Complexity
4.8 Summary of Key Findings
The following key findings were derived from the implementation:
• Unified data structures improved consistency and scalability
• Bounded storage ensured stable memory usage
• Retrieval logic became simpler and more reliable
• Interface enhancements improved user interaction and clarity
• Overall system behavior became more stable and maintainable
20
DISCUSSION
5.1 Interpretation of Results
The results obtained from this work indicate that restructuring the data handling
mechanism and improving the interface design had a positive impact on overall system
behavior. The changes addressed long-standing issues related to data redundancy,
uncontrolled storage growth, and limited user interaction.
By organizing solution data in a unified structure, the system achieved better consistency
and predictability in both data storage and retrieval.
5.2 Impact of Data Structure Restructuring
Earlier, managing multiple independent containers for similar types of data increased
complexity and made the system difficult to extend or modify. After restructuring, all
solution data followed a common access pattern.
This approach:
• Simplified internal data flow
• Reduced dependency on multiple access functions
• Improved logical clarity across modules
The unified structure made the system easier to understand and maintain, especially for
new developers or future modifications.
Figure 5.1: Impact of Structural Improvements
21
5.3 Significance of Bounded Storage
Introducing a bounded storage mechanism played an important role in ensuring
controlled memory usage. Instead of allowing indefinite data accumulation, the system
now maintains only the most relevant recent data.
This design choice:
• Prevents performance degradation over time
• Ensures predictable behavior during long execution
• Eliminates the need for manual cleanup mechanisms
The bounded approach supports stable operation without sacrificing functional
requirements.
5.4 Reliability of Data Retrieval
The retrieval mechanism was designed to provide consistent access to stored data
regardless of solution type. The discussion of results confirms that retrieval operations
behaved reliably under different conditions.
This consistency is important because:
• It reduces chances of data mismatch
• It improves confidence in displayed outputs
• It supports accurate analysis and visualization
A single, unified retrieval approach simplifies logic and reduces error-prone handling.
5.5 User Interface Enhancements and Usability
The integration of interactive elements and redesign of the plotting window significantly
improved usability. Users were able to visually analyze data more effectively due to
clearer layouts and better interaction control.
These improvements:
• Made visual interpretation more intuitive
• Reduced confusion during dynamic updates
• Enhanced the overall user experience
22
Improved interface design complements backend improvements by making the system
easier to use and interpret.
5.6 Design Trade-offs and Constraints
While the implemented changes improved structure and stability, certain trade-offs were
considered. Limiting storage size means older data is no longer accessible beyond a fixed
history window. However, this was a necessary compromise to ensure stable operation.
Additionally:
• The focus was on structural improvement rather than feature expansion
• Design decisions prioritized clarity and predictability over complexity
These trade-offs were appropriate for the intended system behavior.
5.7 Lessons Learned
This work highlighted the importance of:
• Thoughtful data structure design
• Avoiding duplication in system architecture
• Planning for long-term stability and maintainability
It also reinforced the value of clear documentation and disciplined implementation when
working with structured systems.
5.8 Overall Discussion Summary
In summary, the implemented improvements successfully addressed key limitations of
the earlier design. The system became more structured, reliable, and easier to maintain,
while also offering better usability through interface enhancements.
The discussion confirms that the chosen design approaches were effective and suitable
for the intended application scope.
23
CONCLUSION AND FUTURE SCOPE
6.1 Conclusion
This project focused on improving data organization, system stability, and user
interaction through careful redesign and restructuring. The work addressed limitations in
the earlier implementation related to scattered data handling, uncontrolled storage
growth, and limited interface flexibility.
By restructuring solution data into a unified storage model, the system became easier to
understand and maintain. The introduction of a bounded storage mechanism ensured
controlled data retention and predictable behavior. In addition, interface improvements
enhanced visualization clarity and user interaction, making the system more intuitive to
operate.
The project successfully achieved its objectives by:
• Simplifying internal data structures
• Improving consistency in data access
• Enhancing stability through controlled buffering
• Improving usability through interface redesign
Overall, the implemented changes resulted in a more organized, stable, and maintainable
system architecture.
6.2 Key Outcomes
The major outcomes of this work include:
• Reduction in design complexity by consolidating multiple storage paths
• Improved reliability in data handling and retrieval
• Controlled memory usage through bounded storage
• Enhanced visualization and interaction within the interface
• Better alignment between backend data handling and frontend display
These outcomes demonstrate that structured design and careful planning can significantly
improve system behavior without increasing complexity.
6.3 Future Scope
24
The current work establishes a strong foundation for future enhancements. Possible future
directions include:
• Extending unified data handling to additional modules
• Improving visualization capabilities with advanced interaction tools
• Introducing configurable storage limits based on operational needs
• Expanding testing coverage for varied input scenarios
Figure 6.1: Possible Future Enhancements
6.4 Final Remarks
This internship project provided valuable experience in structured system design,
disciplined implementation, and practical problem-solving. The knowledge gained during
this work will be beneficial for future academic and professional endeavors involving
complex software systems and data-driven applications.
25
REFERENCES
1. Bjarne Stroustrup, The C++ Programming Language, 4th Edition, Addison-
Wesley Professional, 2013.
2. Scott Meyers, Effective C++: 55 Specific Ways to Improve Your Programs and
Designs, 3rd Edition, Addison-Wesley Professional, 2005.
3. Qt Group, Qt Documentation – Container Classes, Available online:
[Link]
4. Qt Group, QVector Class Reference, Available online:
[Link]
5. Herb Sutter, Exceptional C++: 47 Engineering Puzzles, Programming Problems,
and Solutions, Addison-Wesley Professional, 1999.
26
APPENDICES
Appendix A: System-Level Design Overview
This appendix explains the overall design approach followed during the project. The
system was designed in a structured and modular manner so that each functional part
works independently while still integrating smoothly with other parts.
The design follows a layered approach:
• Input data handling and validation
• Data mapping and storage
• Data retrieval and presentation
Such separation ensures better maintainability, easier debugging, and flexibility for future
improvements. Any change in one layer does not directly affect the other layers, which
makes the system more stable and reliable.
This design approach also helps in testing individual components separately before full
integration.
Appendix B: Data Flow Overview
This appendix describes how data flows through the system after restructuring.
Incoming data is first validated and mapped using predefined identifiers. After mapping,
the data is stored in a unified storage structure that holds all solution types together in an
organized manner. When required, the data is retrieved through a common interface and
passed to display or processing modules.
The unified flow eliminates repeated logic and ensures that all solution types follow the
same controlled processing path. This improves consistency and reduces errors caused by
independent handling.
27
Figure B.1: End-to-End Data Flow Through the System
Appendix C: Circular Buffer Management
This appendix explains the bounded storage mechanism implemented in the project.
To avoid uncontrolled memory usage, a fixed-size buffer is used. When new data arrives:
• The buffer size is checked
• If the buffer is full, the oldest data is removed
• The new data is added to the buffer
This ensures that only the most recent and relevant data is retained. The buffer always
remains stable in size, and older unnecessary data is automatically discarded. This
approach provides predictable memory usage and stable system behavior.
Figure C.1: Circular Buffer Logic
28
Appendix D: Glossary of Technical Terms
AIU
A software module responsible for visualization and interaction with processed data.
Vector-of-Vectors
A unified data structure where multiple solution histories are stored within a single
indexed container.
Mapping Function
Function that converts solution type identifiers into unified storage indices.
Validation
Process of verifying that system behavior matches expected outcomes under various test
conditions.
Circular Buffer
A fixed-size storage structure where old data is automatically replaced by new data once
capacity is reached.
Encapsulation
A design principle where internal data is protected and accessed only through controlled
interfaces.
Index-Based Mapping
Using predefined indices or identifiers to access data efficiently.
Refactoring
Improving the internal structure of code without changing its external behavior.
Appendix E: Confidentiality Statement
All technical descriptions provided in this report have been intentionally kept at a
generalized level. No proprietary algorithms, internal logic, source code, or restricted
implementation details have been disclosed. The information presented focuses only on
design decisions and workflow explanations. Any sensitive operational details, internal
mechanisms, or system-specific configurations have been intentionally omitted or
abstracted to ensure full compliance with organizational confidentiality and information
security requirements.
29