Methodologies

Our Approach

The RA approach to software development is to visualise the finished product and then carefully plan the steps needed to get us there.

Technologies

We believe in ensuring the technologies we use are robust and stable and, most importantly, reliable for business. This ensures our solutions grow with our clients and is a key part of our 30 year success story. Discover more about our approach, and use of, technology.

Documentation

“If it’s not written down, it never happened”.

When developing computer systems we ensure every step is documented including all changes and/or modifications requested by the client.

To do this properly we rely on issue tracking software so nothing falls through the cracks.

Project Management

We use a methodology based on Microsoft’s Solutions Framework to manage all our projects. This approach splits a project’s cycle into four phases, with deliverables (or milestones) at the end of each phase.

Each project cycle can last for a few weeks, to a few months, depending on the size of the task. All development will pass through the four phases: Envisioning, Planning, Development and Stabilisation/Testing.

Phase 1: Envisioning

We work closely with the client to ensure we have a good understanding of their business, processes and requirements. We use this knowledge to develop a “Functional Specification” – detailing our understanding of their problem – which the client reviews and sign’s off.

The key to the Envisioning phase is to understand the business rules developed in this phase and how they affect the system currently in use or being built.

Phase 2: Planning

Planning involves preparing and providing the client with a detailed document listing all the work that needs to be carried out based on the Functional Specification created in Phase 1. This document is known as a “System Specification”.

Additional deliverables for this phase include:

  • Project Plan – an itemised list of tasks that create the basis for the proposal.
  • Risk Assessment – a document that lists, and categorises, the foreseeable risks in development and how likely those risks are. It includes actions to mitigate risks.

Phase 3: Development

This is when we roll up our sleeves and build whatever has been specified in the Envisioning and Planning phases.

Clients receive regular updates and demo versions are provided once significant functionality has been achieved. The deliverable to this phase is a completed product ready for client testing.

Phase 4: Stabilisation/Testing

We work with our client to test the final product, make changes as required, and sign off on the business rules and most importantly, the final product.