Dynamic mobility applications open source application development portal task 6.1a : architecture and high-level design task 6.1b : list of requirements included in initial architecture and high-level design.

2016PDFTech ReportFHWA-JPO-17-489ITS program applicationsIntelligent transportation systemsIntelligent vehiclesMobile communication systemsVehicle to roadside communicationsVehicle to vehicle communicationsSystem architectureOpen SourceApplication DevelopmentCloud HostingDynamic Mobility ApplicationsConnected vehiclesUnited StatesUnited States. Department of Transportation. Intelligent Transportation Systems Joint Program OfficeLe, StevenNewton, DianeSchaefer, RonLeidosUnited States. Department of Transportation. Intelligent Transportation Systems Joint Program OfficeFederal Highway AdministrationThis document offers a detailed discussion of the system\u2019s functionality that was planned to be implemented. However, following the Agile Development methodology, during the course of system development, diligent decisions were made based on the latest information received or on technical constraints at the time to postpone or not to implement a feature. For this reason, sometimes an envisioned feature is installed but, it is not enabled or not fully configured. For instance, the envisioned community subsystem\u2019s forum has the discussion via email is a feature but it is disabled for security reasons. In the future, if such features are deemed necessary, they can be enabled. Some features may not get implemented by the time the system in production and can be enhanced in the future releases of the system. Please refer to the latest Feature Backlog which keeps track of all discussed features and their development status.In the original OSDAP system concept, Application Development Environment (ADE) was envisioned to be a collaborative development workspace where multiple developers and collaborators can write source code and build executable applications directly online. Several system solutions were considered in earnest including CollabNet; however, this type of system was deemed to be not conducive to the type of development projects that OSADP would host. Besides, the license per-seat license costs was prohibitive and not the most cost effective model.USDOT related development projects are contract based. Project code developers in such projects would design and build the code in their own development environment and test the applications with their external systems and data which would not be easily integrated with an online development environment. The application source code, after testing, get upload into a collaborative source code hosting such as GitHub or SourceForge, etc. USDOT approved a shift in system concept for the discussed reasons. Current OSADP system uses an Application Staging Environment (ASE) for staging application, where the uploaded source code get peer reviewed, issue tracked, and changes can be made collaboratively by development team members. In other words, the revised system design will no longer allowing application development to take place directly on OSADP; and instead applications will be developed in various development team environment. The mature application source code are source controlled on a staging environment and be prepared for release on OSADPDue to this shift in OSADP system architecture, all previous notions of ADE have been replaced by ASE throughout this document