RJB Architecture Review

An RJB Architecture Review is a service offering designed to help customers make decisions on how to fix, upgrade, or otherwise move forward with changes to existing systems. The process usually takes several weeks, and involves onsite data collection and offsite preparation of findings and recommendations. The results are presented to company management as a clear road map on how to remediate the issues at hand. The report includes recommendations for fixing existing issues such as scalability, performance, maintainability, or the ability to upgrade the software. Along with recommendations, a high level impact statement will reflect anticipated cost and schedule of implementation. RJB's Application Delivery service is available for follow on implementation, if the customer decides to proceed with the recommendations.

Our Background

RJB has performed numerous Architecture Reviews that have enabled our customers to make appropriate decisions on how to fix or upgrade their software systems. Software upgrades are inevitable over time. Make sure you have all the facts on hand to make reliable decisions, and don't hesitate to get in touch for your Architecture Review.

RJB Architecture Review FAQ

What is an Architecture Review?

An Architecture Review is an analysis process which involves:

  • Investigating the current implementation
  • Understanding the planned enhancements
  • Assessing the stability of the architecture
  • Evaluating the robustness of the architecture to handle planned changes
  • Recommending ways to improve the underlying infrastructure
  • Propose the project team composition for implementation
  • Providing a project implementation schedule and cost

Why Do I Need an Architecture Review?

An Architecture Review will help you:

  • Determine the ROBUSTNESS of the current system architecture
  • VALIDATE the underlying infrastructure
  • Understand how to IMPROVE the architecture of an existing application.

After an Architecture Review you will be able to:

  • Assess the stability of the current implementation
  • Determine what effects planned changes will have on the application
  • Take advantage of expertise in improving the application infrastructure
  • Identify the potential areas of re-use

When Would I Use an Architecture Review?

An Architecture Review is valid when:

  • Functional or operational problems exist with an application
  • Concerns exist over the effect of proposed application changes
  • Validation of an architecture for use in follow-on applications is desired
  • There is uncertainty about how best to complete an application implementation

Who Performs the Review?

The following people perform an Architecture Review:

  • Project Coordinator (part-time)
  • Architect (full-time)
  • Team Leader (part-time)
  • Technical Specialists (as required)

How is the Review Performed?

There are three phases to an Architecture Review. Onsite phases may be performed by a combination of meetings at the customer site, and/or video conferencing.

Phase I Information Collection

  • Initial planning meeting to discuss client requirements and objectives.
  • Delivery of existing project documents to RJB, including some or all of:
    • Environment Description
    • User Requirements
    • Functional Specifications
    • Systems Analysis
    • Architecture Description
    • Application Design
    • Database Descriptions
  • High level review of documentation with client to confirm RJB understanding and relation to objectives.
  • On-site or video conference interviews with key personnel responsible for the application, including some or all of:
    • Business Analysts
    • System Architect
    • Design Team
    • Users
    • Project Manager
    • Senior Management

Phase II Information Analysis

  • Offsite analysis of information collected and individual follow-up meetings, as required.
  • Application of industry metrics as appropriate.
  • Final analysis of the work reviewed and determination of final recommendations.

Phase III Presentation of Results

  • Present findings, including some or all of:
    • Architecture Analysis
    • Design and/or Code Analysis
    • Metrics as applicable
    • Recommended Changes
    • Proposed Project Schedule and Costs
  • Review findings and solicit client feedback
  • Confirm that client objectives have been met.