Page History
These tutorials have been created with RAMP-TS (not RAMP-TS2).
A RAMP modernization project should progress like this. You will use an iterative release cycle, repeatedly improving your application as time and resources permit:
RAMP Stage 1 | ↓ Prototype | RAMP-WIN001: Creating a Basic Prototype of the Modernized Application |
↓ Set Standards | Create project standards. | |
↓ Decide on Security | Decide on security/authority policy. | |
↓ Name screens | RAMP-WIN002: Rapidly Modernizing Complete Application Segments | |
↓ Classify screens | RAMP-WIN002: Rapidly Modernizing Complete Application Segments | |
RAMP Stage 2A | ↓ Rapidly modernize | RAMP-WIN002: Rapidly Modernizing Complete Application Segments |
RAMP Stage 2B | ↓ Individually modernize | RAMP-WIN006: Snapping in a Basic Inquiry Screen RAMP-WIN007: Snapping in a Data Entry Function RAMP-WIN008: Changing Inquiry Screen to Update Mode |
RAMP Stage 2C | ↓Add value | RAMP-WIN003: Creating a Data Filter for Employees RAMP-WIN010: Using Special Field Handlers RAMP-WIN011: Snapping in Shipped Documents Command Handler RAMP-WIN012: Snapping in Shipped Notes Command Handler |
RAMP Stage 3 | ↓Remove platform dependencies | Optionally remove any IBM i platform dependencies. |
↓ Test | Test the finished application. | |
↓ Deploy | ||
← Repeat | In every cycle you will move more and more application components from stage 2A to 2B to 2C to 3. The mix/ratio of stages is critical because it impacts on how long your project will take, and it is dictated by how much time and resource you have available. |
|
Also see Advanced RAMP Windows Tutorials.