This is the GitHub repo for the solution created by team L5. It contains a proposed architecture for Intelligent Flight Tracking Assistant.
Team members:
- Sanghoon Roh sanghoor@andrew.cmu.edu
- Dongkyu Kim dongkyu3@andrew.cmu.edu
- Hanmin Jo hanminj@andrew.cmu.edu
- Ukheon Jeong ujeong@andrew.cmu.edu
- Kyungjik Min kyungjim@andrew.cmu.edu
- Hyunjae Im hyunjaei@andrew.cmu.edu
This section contains the requirements, distilled from the provided document #1, provided document #2 and the interview with the SolveIt but also with some assumptions we made. These requirements were the main drivers for the design decisions in this proposal.
As a starting point, there's a context diagram that gives an overview of the external elements that interact with what we called the Intelligent Flight Tracking Assistant, which is the scope of this software architecture.
Context Diagram |
The main part of the software architecture is the set of four architecture views seen below. These views provide modules and runtime perspective of the system, that is, they show the components and connectors that have runtime presence and altogether correspond to the main capabilities provided by the Intelligent Flight Tracking Assistant system.
Finally, we have a deployment view that describes Windows UI program (RUI) and Linux server program (Flight Tracker).
Intelligent Flight Tracking Assistant - Deployment view |
Our architecture views were documented following a lightweight view template available here.
The linked ADRs below record the main architecture decisions regarding the proposed design, including their context and rationale. Each ADR may include links to relevant experiments from technical-experiment repository that supports the architectural decision.
- ADR 001 - Use VBO method
- ADR 002 - Use ping/echo tactic
- ADR 003 - Use C#/WPF envinronment
- ADR 004 - Use filter pattern
- ADR 005 - Use polling-based monitoring
Note: we used this ADR template.
Level5 represents the idea of a unified system formed by the collaboration of top experts across all domains.
