Dicsys Cobol Migrator · Plant management · From system to change
Back to the landing page
Cobol MigratorReal screenshot
Read the walkthrough as text

Guided demo · Cobol Migrator

  1. First, we gather what your system uses.

    System file list

    “60 files to review”

    The starting point for this example

    What you're seeing

    This list gathers the files the system works with. It helps you know what to review before changing it.

    What your team decides

    Confirm the right files are there and that no important part is missing.

    Scope of this view: Example taken from the application. This walkthrough explains the work; it does not modify any system.

    See which files could be analyzed ↗

  2. What happens when you save a change?

    How a change is saved

    “From request to record”

    A walkthrough to discuss with the people who use it

    What you're seeing

    The example follows plant management: create a plant, change its data or delete it. The system asks for confirmation and logs what happened.

    What your team decides

    Ask the people who use it whether these steps match their daily work.

    Scope of this view: Example taken from the application. This walkthrough explains the work; it does not modify any system.

    See the AC-001 screen ↗

    Read the simplified flow

  3. If you don't confirm, the change isn't saved.

    The third rule: only an affirmative confirmation lets you continue

    “Yes: continue · No: stop”

    A rule the new version must keep

    What you're seeing

    The third card says only Yes allows saving or deleting. A negative answer or cancel stops the operation.

    What your team decides

    Verify that the new version also honors every answer.

    Scope of this view: Example taken from the application. This walkthrough explains the work; it does not modify any system.

    See the on-screen confirmation ↗

  4. You don't need to change everything at once.

    What changes first and what waits for later

    “First: two parts”

    Plants and Postal Codes

    What you're seeing

    In this case, the work starts with Plants and Postal Codes. Configuration and the change log are left for a later stage.

    What your team decides

    Agree on where to start and how the parts not yet changed will keep working.

    Scope of this view: Example taken from the application. This walkthrough explains the work; it does not modify any system.

  5. One part is ready. The screens are still missing.

    Build status: progress and pending screens

    “9 screens pending”

    The panel shows 0 of 9 screens with code

    What you're seeing

    The right panel shows nine pending screens. The left one shows that one of the two internal parts is already prepared.

    What your team decides

    Complete the pending parts and test the flow end to end before calling it done.

    Scope of this view: A part that compiles has passed a technical check. It does not prove the whole system works correctly.

    See overall progress ↗

    See the part that already compiles ↗

Back to the solution: Cobol Migrator