DEV-16: Leveraging the Power of Advanced GUI Power is nothing without control Erwin in ‘t VeldCCS Tony VertentenIntris Eric DebeijProgress Roland de PijperProgress

DEV-16: Leveraging the Power of Advanced GUI

Power is nothing without control

Erwin in ‘t Veld CCSTony Vertenten IntrisEric Debeij ProgressRoland de Pijper Progress

© 2008 Progress Software Corporation2 DEV-16: Leveraging the Power of Advanced GUI

D I S C L A I M E R

Under Development

This talk includes information about potential future products and/or product enhancements.

What I am going to say reflects our current thinking, but the information contained herein is preliminary and subject to change. Any future products we ultimately deliver may be materially different from what is described here.

D I S C L A I M E R


Agenda

Introduction CCS Intris Background: Architecture



Introduction

CCS and Intris both in transformation process Quite a different approach The need for a fancy UI in common And … the architecture and tools


Architecture = OERA

OpenEdge® Reference Architecture


Tool = iMo

iMo: based on best practices (Software Engineering Process) • Design in UML

• Generate skeletons

• Base Classes User interface based on MVC

Model View Controller Advanced GUI: only View has changed


Agenda




CCS

CCS application

Reason for change

Migration Challenge


CCS application

Financial application for insurance companies• CRM• Policy’s• Claims• Etc.

Rich functionality• 32000 function points

Origin 1992• Based on Progress® V8 / V9• Fat client


CCS

CCS application

Reason for change

Migration Challenge


Reason for change

Business• Flexible UI

• Workflow

• Individual user settings

• Microsoft standard Integration

• Service based integration with 3rd party app’s


CCS

CCS application

Reason for change

Migration Challenge


Migration challenge

3 year period

• Migrate all the existing functionality

• N-tier architecture

• Thin client .Net™ GUI

Develop new modules


Migration challenge

Focus on the business layer Introducing a business model as a gateway

between interfaces and datamodel Migration per module

• First completed module CRM

• 5 months Works seemless with the existing (non

transformed) modules


Migration challenge

Use of IMO• Modeling before building

• Generate skeleton

• Add business rules

• Re-generate models (roundtrip engeneering)


Migration challenge

IMO benefits• Enhances migration speed

– A strong framework for developpers to work with

– Reusable components

• OpenEdge Reference Architecture proof

• Support for UML base development

• Keep your technical documentation in sync with the actual code


Application screenshots


Agenda




Intris

Who is Intris Why .Net UI? Intris Case


1994 2008

Pu

t L

og

ic I

n Y

ou

r L

og

isti

csIntris Group

Offices: BE (HQ), NL +50 employees 250+ Customers, >4500 users Supply Chain Management Software


Intris



Why .Net UI?

Commercial Services provider (SOBA) Development


Commercial

Looks do matter Windows is the default GUI client UI is compared to Microsoft Office Frequently changes


Why .Net UI?


© 2008 Progress Software Corporation25 DEV-16: Leveraging the Power of Advanced GUI© Intris NV – 2007

Challenges in Logistics

Transparent part of the supply chain Business Process integration KPI SLA Connectivity Integrity Changing business requirements Quality of Service ...


Pu

t L

og

ic I

n Y

ou

r L

og

isti

cs

© Intris NV - 2007

Value Chain definition

Value Chain = A network of highly structured organizational processes and partners to create, produce, and deliver a product or service satisfying customer and market demands.

Companies are producing a constantly changing mix of increasingly complex products, while global competition demands ever shorter cycle times and shorter product life cycles. Market conditions and requirements change every day. This results in frequent new product introductions and constant adjustment of the value proposition of all products in the portfolio.

Value Chain responsiveness becomes a primary differentiator.


An incoming WHS processAn incoming WHS process

Pu

t L

og

ic I

n Y

ou

r L

og

isti

cs

© Intris NV - 2006

ad Inslag

Leverancier/Rederij Klant Dossierbeheer Magazijn Transport Koerier Boekhouding

Instructies (aankoop) Create Dossier

Shipping Instructions Update dossier

Planning Magazijn(verschepingslijst)

Planning transport

Afschrijvgegevens

Wegvervoer TransportOpdrachtTransport opdracht(spoor of lichter)

Aankomstbericht

Inslag

Cheque

Douane

Chequeopdracht

Afhalen Laatvolgen

Bellen Rederij

Start

Stockrapport

ActivityFinal

Facturatie

Aankoopvalidatie

Boeken verkoop

Boeken Aankoop

Registreer ontvangst

in SAP

YesNo


Pu

t L

og

ic I

n Y

ou

r L

og

isti

cs

© Intris NV - 2007

Challenges in a nutshell

Integration: Business process consists of several internal and external sub processes or services

The user experience has to be as if he is working with 1 application. The different business process must be presented in a consistent manner


Pu

t L

og

ic I

n Y

ou

r L

og

isti

cs

© Intris NV - 2007

What does it mean ?

Application is part of the business process of our customers

Evolve from software application to software solutions :• Software components

– Intris– Progress Software– Others

• Consultancy• Support


Why .Net UI?



Development

Use of .Net possibilities Use of commercial UI

components More possibilities and

properties means more complex


Intris



Intris case

Application Transformation iMo WorkFlow Management (WfM)


Application transformation


Requirements

Use Cases

Domain model

Use case realization

act Register Order

ActivityInitial

select principal

create empty order

check if principal valid

enter order data

select SLA

create tasks

Assign resources (UC 15)

create attachments

save order

ActivityFinal

prinipal selected

principal valid

SLA not selected

send alert

discard order

[true]

[false]

[true]

[false]

[true]

[false]

class Domain Objects

Task

Order SLA

End-user

Validation_Rule

Principal

CCTaskOwner

Serv ice

Resource

consistsconsists

executed according to

defines

guards

agreed withissues

interested inresponsible

Used in

derived from

executes

sd Register Order

Server::beOrder

Actor1

(from Client)

Server::bePrincipal Server::beSLA Server::beService Server::beTask

alt Principal is blocked

loop for each SLA get SLA specific information

[SLA are generic or from the current principal]

loop For each SLA get all serv ice

[Services are from the current SLA]

loop For each serv ice generate tasks

opt The user can add new tasks for the sav ed order

saveData()

Register Order(dsOrder) :LOGICAL

ValidatePrincipal(PrincipalID)

CheckPrincipalInformation (PrincipalID) :LOGICAL

Principal is Block

GetSLADetail(dsSla)

fetchData(phDataset,phContext)

GetServiceGenerateTask(auxdsService,piOrderNumber)

fetchData(phDataset,phContext)

GenerateTask(auxdsService,piOrderNumber)

storeData(phDataset,phContext)

Store complete successfully

storeData(phDataset,phContext)

class Manage Order

Presentation BusinessLogic DataAccess Persistence

ctdetailwin

Client::ctOrderDetail

ctsearchwin

Client::ctOrderSearch

model

Client::mdOrder

vwdetailwin

Client::vwOrderDetail

«property»- WindowTitle: CHARACTER = Order

vwframe

«instance»Client::vwOrderFrame1

«fil l in»- OrderID: INTEGER- Description: CHARACTER

«date»- OrderDate: DATE

«lookup»- OrderStatus: CHARACTER- PrincipalID: INTEGER

vwsearchwin

Client::vwOrderSearch

vwpage

«instance»Client::vwOrderTab1

- Label: CHARACTER = Detail- Page: INTEGER = 1

BusinessEntity

Server::beOrder

+ Register Order(DATASET) : LOGICAL+ ValidatePrincipal(INTEGER) : void+ GetSLADetail(DATASET) : void+ GetServiceGenerateTask(DATASET, INTEGER) : void+ GenerateTask(DATASET, INTEGER) : void

DATASET

Server::dsOrder

TEMP-TABLE

Server::ttOrder

«column»*PK OrderID: INTEGER(8) Description: CHARACTER(64) OrderDate: DATE OrderStatus: CHARACTER(8) FK PrincipalID: INTEGER(8) PrincipalName: CHARACTER(32)

«FK»+ FK_PrincipalID(INTEGER)

«PK»+ PK_Order(INTEGER)

«unique»+ UQ_Order_OrderID(INTEGER)

DataAccess

Server::daOrder

WFM Model::Order

«column»*PK OrderID: INTEGER(8) Description: CHARACTER(64) OrderDate: DATE OrderStatus: CHARACTER(8) FK PrincipalID: INTEGER(8) PrincipalName: CHARACTER(32)

«FK»+ FK_PrincipalID(INTEGER)

«PK»+ PK_Order(INTEGER)

«unique»+ UQ_Order_OrderID(INTEGER)

The window will hold all the order in the system. The user can filter orders using the search windowby: Principal or by OderStatus.Using the detail window user can fil l a description, or can change the status.For the moment the status can be: -NotRegister -Register -Cancel

ctsearchwin

Client::ctCodeSearch

ctsearchwin

Client::ctPrincipalSearch

vwlookup

Client::SlaFieldLookup

+ CreateLookup() : void+ AddFilter(CHARACTER, CHARACTER, CHARACTER) : void

OrderStatus

«call»

DataSource

dataAccess

viewer

DetailWindow

PrincipalID

«call»

viewer

businessEntity

«proxy»

«instantiate»

modelmodel

uc Manage Tasks

UC01 Define taskUC02 Ov erv iew tasks UC07 Define Serv ice

UC08 Ov erv iew Serv ice

Task Owner

(from Actors)

Account Mgr

(from Actors)

UC16 Manage attachment

«include»

«include»

«include» «include»

Pu

t L

og

ic I

n Y

ou

r L

og

isti

cs

© Intris NV - 2007

iMO Pilot


iMo benefits

Services Components Classes Design Standard Intris UI Hide complexity



Agenda




Imo View

Current view of iMo is based on codejock-ocx User interface pattern used is:

MVC - Model View Control Generic behavior of Model View and Control

is in iMo base classes


Progress inheritance model


Implementation: Desktopclass Desktop

Form

Imo.Windows.Forms::Form

Imo.Windows.Desktop::Desktop

Infragistics.Win.UltraWinExplorerBar::.UltraExplorerBar

Infragistics.Win.UltraWinDock::WindowDockingArea

UltraGrid

«instance»Imo.Windows.Desktop::

ErrorGrid


Desktop objects

Desktop = the VIEW part of MVC Only knows about the Form and the

Infragistics controls A model supplies the data (e.g. menu) A controller starts the model and view Same mechanism goes for all types of forms

(e.g. search window, detail window)


Advantages

Don’t interfere with the communication between .Net controls!

Subclass or replace a form, no need to change the model or controller.

Already moved from ocx’s to .Net without need to change the model and controller code. In the future: Rich Web UI, Ajax, ….


Demo, CCS current desktop


Demo, CCS current search window


Demo, Intris desktop with WorkListHandler


In Summary

What are your business requirements?

iMo / OERA really makes future development simpler

Architect your user interface with MVC (MVP)

Are you ready for the .Net user interface?


For More Information, go to…

Relevant exchange sessions• DEV-6 Introduction to the OpenEdge Advanced GUI

• DEV-29 A Deep Dive into Developing with the Advanced GUI

• DEV-36 Composite MVP – Building Blocks in Presentation Layer

iMo• http://www.my-imo.com/

• Expo – iMo stand


Questions?


Thank You


Documents

DEV-16: Leveraging the Power of Advanced GUI Power is nothing without control Erwin in ‘t VeldCCS Tony VertentenIntris Eric DebeijProgress Roland de PijperProgress