Cost Effective Rapid Application Development Tool

Designed and Developed by Aditya Prakash

Agenda
Introduction Concepts and Vision Key Aspects of Concepts Benefits FAQ

CERAD: Introduction
Configuration driven Capability Generate Application on fly. Incorporate new features to existing modules on fly

Business Entity and Process driven approach to generate all necessary code files

Limited or wider scope of use

Integrate the COTS product

No Hand Coding

Functional Defect Resolution - online

Low cost development

Stakeholders concerns
Costing, Delivery, Performance, Stability , Maintenance
Dependencies, Installation, Integration

Functionality Price

Usability, Modifiability, Testability

System Quality Attribute

Business Community view

End Users view Performance Availability Usability Security

Developers view Maintainability Portability Reusability Testability

Time To Market Cost and Benefits Projected life time Targeted Market Integration with Legacy System Roll back Schedule

CERAD Meeting all Expectations

CERAD: Vision

Phase 1

Phase 2

Phase 3

Phase 4

Requirement gathering

Service Solution Design OSS systems Design Business Entity and Attribute definition Business Rules definition

Tool Configuration Business Entity and Attribute Configuration Business Rules Configuration Execution to Launch Component Testing Automated

Functional Testing E2E Functional Testing ORT ORT Sign off

Deployment on Production

Overview of CERAD : Model

Business Capabilities (CERAD) Reconciliation Business Processes and Entities Reconciliation Services, Messages, Applications, Endpoints Configuration Execution Components, Workflow , XML, Database, Data Services App/DB Servers & Segments Logical /Rule Builder Data Center Constraints Manual change Manual Procedures Technology Architecture

Manual change

Constraints

Constraints

Deployment Units

Deployed on

Bundled into

Benefits: Time to market, Development Cost, Maintenance

Cost Vs New feature
C O S T S D e f e c t s
1 2

Defect Resolution

Subsequent Release

n -1

Time to resolve Defects

N e w P r o d u c t
1

Time to Market

CERAD Approach

Subsequent Release Time

n -1

Existing Approach

Major Benefits:
Time saving, Cost Saving, Agility, Modularity, Requirement Driven Well tested Components Ready to Use.

Cost Effective Rapid Application Development New Product and feature on fly 1 or 2 days E2E design driven component Ease for add-on requirement Version and source save control. Classical development style Reducing development cycle time line by 80%

Complete Agility Earlier Availability for Testing

Changes frequently incorporated Centralised Repository Ease to integrate

Custom Design & Configuration EAI Ticketing Discovery and Alarming Data Adopter

Authorization

Client Topology Configuration

Xml.config

CERAD Tool

Device Configuration KCI Notification Rules Work Flow Configuration

Java Plugin

Data Service

Web Service Work flow Module Data sync Agent Database

CERAD: Inputs /Outputs

Schema Contract Business Model Element and Attributes Product Model

Ordering modules

Inputs

Outputs

CERAD: Key Aspects

Single System concept

E2E Design Driven

Data Configuration Customization

Configuration Driven development

KEY CONCEPTS

No component CFT

Business Rule Configuration

No Manual Coding

Factory model

Template based UI

User Profile Instance Defect Fix Change to Implement any point of time

COTS product configuration files

Centralised Repository

CERAD
Order Handling/Sales Support Systems Product Model and Mastering

Data Service- Import and Export

Work Flow Management

Plugging rules and Configuration to activation of Device*

Monitoring of Device*

CERAD: Order Handling and Sale Support Systems

Rules classification and implementation Interaction with External Systems

UI Creating

Database Design and Scripts

EAI Transformation of Data to meet other systems Requirement

Source Code for all pages, Modularity of code, Business logic class Database Tables, Store Procedures- Add Update, delete and Retrieves Interaction with External Systems (xml, Web Service, Oracle API, file transfer) Web Service To Interact with other components to exchange the information EAI Transformation of Data to meet other systems Requirement Business rules ( Data driven, Custom, Service based) Customization- Transformation logic Consuming Services Adopter methods
Template based Web Pages

UI Source Code Database Adopter EAI Messaging

CERAD : Product Model and Mastering

Product Model
Product Library Integration Database Design and Scripts Database Adopters for import and Export User Friendly UI for Manual Operation

Interaction with External Systems Pull and Push

Web based Admin Module to add update records, Status update, Audit Database Script Tables, Constraints and Store Procedures Data loader : To import data from excel sheet, web service and .dat file Web Service to export the data to external systems Change Control: Versioning and change history Business rules ( Data driven, Custom, Service based)

Customization- Transformation logic

Consuming Services Adopter methods
Normalised Data base 3 NF

Database Tables Relations Store Procedure Web UI Data Loader Data Exporter

CERAD: Work flow Management

Work flow Task list Creation, configure Task Execution Dependencies, Configure KCI, Status Update, Task Triggering configurations, Task Rewinding Process, Separate Database conceptTask Management, Meta data Principles.

Work flow Manager

Database
Task Lists

E x t e r n a l G a t e w a y s

CERAD: Static Diagram Tool and Output components

FAQ
Does it support to access the remote database?
Yes, through API (DB Link), XML interaction, file transfer

How it invoke Web Services?

Capture Http path during configuration. Capture web Methods with input parameters. Request xml creation based on XSD. Parsing Response xml and populate respective place holder.

Does it support Event and Actions?

Yes

How it will support rules?

Providing the GUI to capture Rules based on Page fields, Database fields etc.

How it handle relational Database model

It would be having a capability to handle parent child relationship between objects.

What about performance of dynamically created Store Procedures, Does it impact performance of application?
It would be having B-Tree model of Library database to enhance the preformation of SQL Queries. Dependencies between object, smartly handle in BAL to avoid network latencies. SQL Queries would be written based on statistic of records, background automated job to check SQL and tune with every deployments.

You can write for more information or ask your Queries at prakasha@techmahindra.com