+44 7941 452860 © Copyright 2006 Domino Software Ltd. Mantis Conversion  Complicated & Thorough Process  Several issues need to be addressed in the analysis.

Slides:

Advertisements

Similar presentations

1 COMS 361 Computer Organization Title: Instructions Date: 9/28/2004 Lecture Number: 10.

Advertisements

Computers Are Your Future

1 Software Engineering Lecture 11 Software Testing.

Data Dictionary What does “Backordered item” mean? What does “New Customer info.” contain? How does the “account receivable report” look like?

3/5/2009Computer systems1 Analyzing System Using Data Dictionaries Computer System: 1. Data Dictionary 2. Data Dictionary Categories 3. Creating Data Dictionary.

Engineering Problem Solving With C++ An Object Based Approach Fundamental Concepts Chapter 1 Engineering Problem Solving.

If You Missed Last Week Go to Click on Syllabus, review lecture 01 notes, course schedule Contact your TA ( on website) Schedule.

Run time vs. Compile time

Screen guidelines For data entry. Screen Layout for Data Entry Identify screen (name and purpose). Keep number of screens to a minimum. Ensure that all.

1 Run time vs. Compile time The compiler must generate code to handle issues that arise at run time Representation of various data types Procedure linkage.

Chapter 8: I/O Streams and Data Files. In this chapter, you will learn about: – I/O file stream objects and functions – Reading and writing character-based.

CICS Basic Commands COBOL programming statements.

CICS-Dbg1 Testing and Debugging Programmers responsibility that program works correctly! Can write program incrementally You must test anything that the.

Project Execution & Termination Life Cycle Execution Presented by: Basker George.

Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.

Compiled by Benjamin Muganzi 3.2 Functions and Purposes of Translators Computing 9691 Paper 3 1.

Struts 2.0 an Overview ( )

Intro. to Game Programming Want to program a game?

CICS – Mainframe (LC) 2 Copyright © 2005, Infosys Technologies Ltd ER/CORP/CRS/TP01/003 Version No: 1.0 Course Schedule Day1 - Introduction to CICS Day2.

A Simple Two-Pass Assembler

Copyright © 2012 Pearson Education, Inc. Chapter 1: Introduction to Computers and Programming.

Designing and Debugging Batch and Interactive COBOL Programs Chapter 5.

Programming Languages and Paradigms Object-Oriented Programming (Part II)

1 3. Computing System Fundamentals 3.1 Language Translators.

S2008Final_part1.ppt CS11 Introduction to Programming Final Exam Part 1 S A computer is a mechanical or electrical device which stores, retrieves,

1 Software Construction and Evolution - CSSE 375 Exception Handling - Principles Steve Chenoweth, RHIT Above – Exception handling on the ENIAC. From

DEBUGGING. BUG A software bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected.

C++ History C++ was designed at AT&T Bell Labs by Bjarne Stroustrup in the early 80's Based on the ‘C’ programming language C++ language standardised in.

© Janice Regan, CMPT 300, May CMPT 300 Introduction to Operating Systems Memory: Relocation.

The Advanced Manufacturing System Advanced Dealer Training Version 3.0.

Microsoft Visual Basic 2005 BASICS Lesson 1 A First Look at Microsoft Visual Basic.

1 Pre-Exam Lecture 4 Final Examination is scheduled on Monday December 18th at 1:30PM in class 4 There are 8 questions with or without sub- parts and.

Application Program Design Day3. 2 Copyright © 2005, Infosys Technologies Ltd ER/CORP/CRS/TP01/003 Version No: 1.0 Objectives Basic CICS programming –Structure.

ECE 353 Lab 2 Pipeline Simulator. Aims Further experience in C programming Handling strings Further experience in the use of assertions Reinforce concepts.

Introduction to the new mainframe © Copyright IBM Corp., All rights reserved. Chapter 11 Understanding transaction managers on z/OS.

Introduction to programming Carl Smith National Certificate Year 2 – Unit 4.

Copyright 2003 Scott/Jones Publishing Standard Version of Starting Out with C++, 4th Edition Chapter 1 Introduction to Computers and Programming.

How to Program? -- Part 1 Part 1: Problem Solving –Analyze a problem –Decide what steps need to be taken to solve it. –Take into consideration any special.

Mr C Johnston ICT Teacher

Chapter 14 Programming and Languages McGraw-Hill/Irwin Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved.

How Are Computers Programmed? CPS120: Introduction to Computer Science Lecture 5.

Java Programming, Second Edition Chapter Twelve Advanced Inheritance Concepts.

GDT Tips and Tricks. GDT Tips and Tricks Doug Evans GDT 2004 International User Conference – Evolving the Legacy July  Tucson, Arizona GDT Tips.

Principles of Programming CSEB134 : BS/ CHAPTER Fundamentals of the C Programming Language.

Introduction to Computer Programming using Fortran 77.

Software Engineering Algorithms, Compilers, & Lifecycle.

Powerpoint Templates Page 1 Powerpoint Templates Unit Testing Ari Seppi

World of Wokcraft The very best in Single pan cooking themed fantasy gaming!

In today’s lesson we will be looking at: what we mean by the software development lifecycle the phases in the lifecycle We will focus particularly on testing:

Information Systems Development

Why don’t programmers have to program in machine code?

FHIRForms – Viewing and Editing FHIR Data

SLC/VER1.0/OS CONCEPTS/OCT'99

Programming Languages

Chapter 5- Assembling , Linking, and Executing Programs

Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.

The Pseudocode Programming Process

Separate Assembly allows a program to be built from modules rather than a single source file assembler linker source file.

Information Systems Development

Assembler, Compiler, Interpreter

and Executing Programs

Computer Organization & Compilation Process

Problem Solving Using C: Orientation & Lecture 1

Machine Independent Features

Assembler, Compiler, Interpreter

Problem Solving Using C: Orientation & Lecture 1

COMS 361 Computer Organization

Queries Training Module.

Computer Organization & Compilation Process

Presentation transcript:

© Copyright 2006 Domino Software Ltd. Mantis Conversion  Complicated & Thorough Process  Several issues need to be addressed in the analysis stage  These issues are discussed and resolved with the User

© Copyright 2006 Domino Software Ltd. Basic Conversion Issues  MANTIS is a robust and forgiving language –Define files, maps & routines that do not exist –Define datanames in the in-line code These are illegal in COBOL!

© Copyright 2006 Domino Software Ltd. Conversion - Analysis  Check for Redundant Code  Re-iterative Process  Run until no redundant code remains  Redundant code retained as comments

© Copyright 2006 Domino Software Ltd. Conversion - Analysis  Completeness check  Do all referenced components exist?  Files, Screens, Programs etc.  Passed back to user for resolution

© Copyright 2006 Domino Software Ltd.

© Copyright 2006 Domino Software Ltd. Conversion - Analysis  Component Name Resolution  MANTIS allows much longer names  MANTIS names can user Cobol reserved words? These must be resolved  Conversion has defined defaults, but user has option to override

© Copyright 2006 Domino Software Ltd.

© Copyright 2006 Domino Software Ltd. Conversion - Analysis  Check for code validity?  MANTIS allows programs to address data areas that are outside bounds?  Array of 10 MANTIS let’s you reference 11, COBOL doesn’t!  Field of 6 bytes, MANTIS let’s you reference byte 7, COBOL doesn’t! Must be resolved!

© Copyright 2006 Domino Software Ltd. Now the CONVERSION!  Only when all the analysis issues have been resolved are we ready to commence the actual conversion!

© Copyright 2006 Domino Software Ltd. CONVERSION  User Mantis Screens are converted to BMS MAPS  User is provided with source of BMS maps to assemble  User is provided with Cobol Copybooks for the maps

© Copyright 2006 Domino Software Ltd.

© Copyright 2006 Domino Software Ltd. CONVERSION  User Mantis File, Database and Interface layouts are converted to Cobol layouts  User is provided with appropriate Cobol Copybooks

© Copyright 2006 Domino Software Ltd. CONVERSION  User Mantis Programs are converted to CICS Cobol  User is provided with clean compiled Cobol source All code produced is 100% pseudo conversational

© Copyright 2006 Domino Software Ltd. Code Sample - CONVERSE

© Copyright 2006 Domino Software Ltd. Code Sample TXT function

© Copyright 2006 Domino Software Ltd. Code Sample - Logic

© Copyright 2006 Domino Software Ltd. Initial Code Impressions Taken from a small sample  Many long component names, but this is easily addressed  No “out of bounds” errors  No “DO” of missing routines  No “Dynamic Screen Placement” e.g. CONVERSE MAP1(XROW,10)

© Copyright 2006 Domino Software Ltd. Conversion - Testing  Good quality on-site engineers  Cobol & MANTIS knowledge  Business Knowledge  CICS expertise (CEDF skills)  Access to debugging software