RAD Methodology
Quick start planning and analysis
Early development of Data Models
Early development of Business Process Models
Iterative coding with frequent releases
Coherence of Requirements and Deliverable
TRAILING EDGE, BLEEDING EDGE
Traditional software development assumes coding proceeds from one rigidly defined phase to the next. This approach, often called the Waterfall Method, is still in productive use decades after its invention. At the other end of the spectrum lies Agile development and its offshoot Extreme Programming where requirements are expressed as increasingly mature coded prototypes.
RAD BUT NOT RADICALCorraTech employs an approach known as Rapid Application Development. RAD for short. In essence, we give our analysts a week’s head start and then turn our developers loose to try to catch them. As the analysts work to keep ahead of the engineers, they document requirements as they go. The engineers release working code at least once a week. The client then tests and that deliverable as we move on to the next milestone.
RESULTS GURANTEEDAt each step of the way, the RAD methodology confirms that development is on track and meets client requirements. By its very nature, such iterative development allows for course corrections throughout the project lifecycle. The approach guarantees that the client receives a working system that meets their requirements. The end-result is the right solution, delivered at lower cost, with a faster time to launch.
I CAN SEE CLEARLY NOWClients have access to our complete online project management system throughout the lifecycle of the project. Our goal is to provide complete transparency into all phases of the project. They are able to submit bugs and communicate directly with our engineers as coding proceeds. In addition to source control and bug tracking, our system provides a project wiki in which all requirements, project plans, and comments are maintained.
Because every technology project should be a success.
