Page History

↓ Prototype                     

RAMP-WIN001: Creating a Basic Prototype of the Modernized Application
RAMP-WIN005: Reviewing Design

↓ Set Standards

Create project standards.

↓ Decide on Security

Decide on security/authority policy.

↓ Name screens

RAMP-WIN002: Rapidly Modernizing Complete Application Segments
RAMP-WIN004: Naming and Classifying the Employee Screens

↓ Classify screens

RAMP-WIN002: Rapidly Modernizing Complete Application Segments
RAMP-WIN004: Naming and Classifying the Employee Screens

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-WIN009: Tracing Navigation
RAMP-WIN014: Understanding and Handling Screen Variations

RAMP Stage 2C

↓Add value
See What Adds 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-WIN013: Sending Instance List Data to Excel
RAMP-WINAD04: Redesigning the Screen Using aXes

RAMP Stage 3

↓Remove platform dependencies

Optionally remove any IBM i platform dependencies.

↓ Test

Test the finished application.

↓ Deploy

Deployment Check List for RAMP-TS

← 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.