Development ● Security ● Operations
What is ROADMAP from RBR-Technologies?
ROADMAP is the intersection of proprietary code and a unique development methodology. It combines a modified Agile development process with specialized coding techniques. Designed to scale with increased demand and produce enhanced situational awareness for our customers, ROADMAP rapidly provides customized views for Government stakeholders and leadership which increase productivity and decrease response time.
The RBR-Technologies ROADMAP Methodology
What is new with ROADMAP 2.0?
In addition to incorporating operations into the development lifecycle ROADMAP 2.0 takes this integration a step further by incorporating security as code across the entire project lifecycle, supporting team member security training and security professional integration from design to deployment. We accomplish this through a combination of industry best practices and a unified software platform. Through this process, we foster innovation, make security a consumable product across the development and operations teams, and actively identify and attack risks rather than relying on scans and reports.
This methodology is also referred to as DevSecOps.
Modified Agile Development Methodology / DevOps
The ROADMAP 2.0 methodology leverages best practices from Agile software development and combines them with a modified approach based upon experience working with our DoD customers and their mission partners to develop and deploy capabilities to production.
Like standard agile methodologies, ROADMAP 2.0 utilizes a “sprint” or “spin” delivery cycle, focuses on delivering capabilities in regular intervals and puts a premium on customer interaction through regular demos. This, unlike traditional waterfall development, allows the flexibility to adapt to the ever-changing DoD mission by incorporating operations into the development process.
Agile Development Operations (DevOps)
ROADMAP Presentation Layers and Portal / Dashboard Environment
The ROADMAP 2.0 presentation layer delivers integrated briefing views which target 1 of 3 broad customer categories:
Executives: Executive views cover a large amount of information at a very broad level. These views are concerned with overall impact. Common visuals on executive views are stoplight charts and maps.
Operators: Operators require the most detailed information and the ability to drill down to gain granularity about issues. These views contain a great deal of information and often require training for use.
Users / Other Stakeholders: These users have views tailored to their specific type of interaction with the data which are based upon the information requirements for the tasks they perform.
ROADMAP 2.0 Description and Pricing
The ROADMAP 2.0 methodology has a flexible pricing model. With that said our basic ROADMAP pricing is based on an analytic / capability complexity level. An example of the complexity model is listed below:
Level 0 - A level 0 analytic / capability consists of a general mock-up that allows RBR to leverage previously developed code with little to no refactoring and very low development cost built in to pricing.
Level 1 - A level 1 analytic / capability consists of a prototype that may consist of operational re-use of code, utilize existing customer data, low level analytic capability, with minimal refactoring and development cost built in to pricing.
Level 2 - A level 2 analytic / capability consists of creating a new visualization / web app front end, use of existing customer data, moderate level analytic capability, minor development cost built in to pricing.
Level 3 - A level 3 analytic / capability consists creating one or more new visualizations / web apps front end, new data set, moderate level analytic capability, with development cost built in to pricing.
Level 4 - A level 4 analytic / capability consists of one or more applications that may have multiple visualizations, one or more new data sets, requires analytic capabilities, and significant development cost is built into the pricing.
Level 5 - A level 5 analytic / capability requires a detailed analysis of cost and LOE and can consist of modifications to platforms as well as capability and analytic development.