Aversan's Delivery Approach

Aversan’s delivery approach is governed by aerospace industry standards, processes, best practices and guidelines defined in its Quality Management System. Adherence to these requirements-based process-driven methodologies ensures that our products and services are of the highest quality and are delivered on time, on scope and on budget. Our delivery model is built upon highly valued industry principles, a robust governance structure and continuous improvement.




Following Through Step by Step

The discipline to follow through on a design requires a staged approach that ensures all the pieces will fit together. It is the ability to look forward from the front end, backwards from the backend, which ensures the development will be executed successfully.


A requirements-based design approach uses validation and verification standards to qualify the requirements. This strategy would take into account the definition of requirements, designing strictly to those requirements, and performing accurate, complete and independent verification to a design. Within aerospace, this ensures compliance to DO-178B/C DAL ‘A’ and DO-254 DAL ‘A’.




v-chart-smaller
It Starts With Requirements

Meeting expectations is all about abiding by disciplined processes to identify and capture all of the requirements. Aversan uses IBM Rational DOORS as a complete end-to-end solution for requirements management. This ensures the traceability and bi-directional linkage of business, system and technical requirements to the test cases and the verification and validation of the development against those requirements. In addition, this process facilitates the assessment of scope change when conducting a change impact analysis as a result of changing business needs.


starts-with-requirements
Translating the Big Picture

The system requirements are captured from the customer’s defined need and recorded in DOORS and a preliminary design concept is created. This ensures complete traceability between requirements definition and verification. This traceability is valuable in all industries, and is an essential component within the aerospace industry, in achieving DO-178B/C and DO-254 certification. A safety assessment is performed to identify areas of concern and the design concept is modified accordingly.


A detailed set of system requirements is then established leading to a system design. The system design is sufficient to allow independent development of the hardware and software components and the system validation process.


Hardware and software design and implementation are performed in parallel with the verification process. As the hardware and software development progress towards mature verification processes are applied to determine readiness for system integration and eventual system validation. Data artifacts are retained throughout the process as required supporting regulatory approval.





chart
Development Process Excellence

The key to realizing a design is to use development processes than can simplify the complexities and churn out solid code.


Aversan’s incremental model to software development provided a structured and standardized process for all phases of the system development effort. These phases track the development of a system through several stages from initial analysis, system planning and concept development; to acquisition and requirements definition; design; development; integration and testing; deployment and acceptance; production; and finally to system delivery and acceptance. The key aspects of Aversan’s incremental model approach are:


Key Aspects of the Model:


Construct a partial implementation of a total system

Incrementally add additional functionality

The incremental model prioritizes requirements of the system

Each subsequent release of the system adds function to previous releases

Benefits of Using Approach:


Developing higher-risk or major functions first

Each release delivers operational product

Initial product delivery is faster

Risk of changing requirements is reduced

Aversan's Incremental Model (shown below) is a depiction of this development strategy. The agile approach embraces multiple rounds of unit testing, ensuring that as many defects are discovered and fixed as early as possible. The requirements can be modified during the development cycle, allowing a considerable amount of flexibility throughout the engagement. Aversan implements standard SDLC and ITIL development models. Development methodologies include Waterfall, Spiral, and Agile models, and implement Release Management (RM) strategies that best suit the needs of a project.


incremental-model
Real-Time Reporting

With many intertwined activities, project management tools need to highlight what matters, when it matters most. And what matters most is a moving target. Responding to the right issues at the right time is key.

test-planning-graph2

Aversan uses an in-house developed reporting engine, Aversan Reporting Engine (ARE), that grants visibility to management and stakeholders on project progress and delivery/team effectiveness. This is provided in an easy-to-read graphical depiction of budgetary and schedule related status of the development and testing effort in real-time. Each low-level task derived from the WBS is monitored and integrated into the ARE which calculates the metrics and KPI to generate powerful and easy-to-read reports based on Project Management Institute (PMI) principles.

Project Status Reporting

There is a project start date and a project end date. With a multitude of tasks, inter-dependencies and complexities, execution is heavily dependent on project status monitoring and reporting.

Aversan uses an integrated system of software tools to implement the Project and Risk Management processes and techniques that drive our daily operations. The technologies that drive this integrated system enable the automated enforcement of business process in accordance to industry standards, such as PMBOK and ITIL. Project status reports are provided to our clients on a regular basis, showing full details on the status of the engagement, any issues that have been encountered, details on costs, risks, schedule and solution quality.

We Know How to Make Decisions

Getting decisions made effectively keeps projects moving forward. And decisions need to be made at all levels and on a continuous basis.

Our governance model allows us to manage relationships, expectations, contractual dependencies and services in a comprehensive governance framework that is aligned with our customer’s strategies and goals.


1. Components of Governance
  • A clearly articulated decision framework
    • Decisions to be made
    • How decisions will be made and by whom
    • Responsibility for executing against decisions
  • Well formed governance structure
  • A shared vision for the type of relationship the parties aspire to have and of how they will manage the relationship

2. Results of Effective Governance
  • Clarity about decision making and executing roles and accountabilities
  • Efficient and effective decision making
  • A means for sharing important information on business objectives
  • A forum for addressing concerns and issues early and jointly
  • A strong working relationship

3. Value of Governance
  • Reduced coordination costs
  • Less time wasted due to poorly managed conflict
  • An ability to adapt effectively in a rapidly changing environment
  • Better management of scope
  • An ability to explore new avenues for innovation and improvement
  • More efficient resolution of problems addressing "grey areas" in the contract