Auto code generation development tool - business benefits


Published on

The IBM Web Experience Factory (WEF): Develop a single source application (portlet) that will adapt itself to the device type and form factor. It is model based with auto code generation. See more info here:

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Auto code generation development tool - business benefits

  1. 1. Web Experience Factory Business Benefits Fast,Simple Development of Enterprise Multi-Channel Applications
  2. 2. Key Challenges facing Development teams? ■ How to do more with less? ■ How to maximize reach with minimal development? ■ Finding skilled resources? ■ How do I enable new team members quickly? ■ How do I ensure code quality?
  3. 3. 3 In this day and age, we need a more efficient development approach... Web Experience Factory Provides a 50+ percent increase in productivity vs traditional J2EE programming  Faster time-to-market and cheaper solution delivery  Improved end-user experience  Better alignment with business customers  Easier integration with existing technology investments  Increased solution flexibility
  4. 4. Single web experience works across multiple channels... Desktop Mobile Browser Hybrid (Web & Native) Websphere Portal Web Experience Factory Application/Portlet
  5. 5. Examples of customers/partners who have benefitted: ■ Some examples from a partner: – used to take 9 months to develop a solution, now a few days to develop a similar solution – Web Experience Factory for building a number of apps for large financial services org in months vs 2 -3 yrs with traditional tool – Created analytics tool that is multichannel, running on mobile devices for large supermarket chain. 4 weeks dev ■ Large insurance organization: – created several applications with no portlet level API skills – Rapidly consume web services and relational data using integration builders, without writing to an api such as the JDBC. ■ Large automotive manufacturer: – created multi channel applications in weeks, optimized for smartphone and tablets. – Minimal coding required – Handover to customer team, with minimal coding skills required, took beta to production easily ■ Large Bank: – Needed to customization integration between WebSphere Portal and IBM Connections using IBM Connections 3.0.1 Portlets Developer Pack
  6. 6. 6 What is Web Experience Factory? ■ A model based IDE development tool making it easier and faster than traditional coding to develop exceptional web experiences ■ Includes 150+ pre-built builders the accelerate development time. Examples include: – Standard based Back-end connectors including Rest APIs, Web Services, Databases – Proprietary back-end connectors to systems like SAP, Peoplesoft and Siebel – Pre-built business logic builders for transformation and manipulation of content – Pre-built Front-end builders for building sophisticated mult-channel applications like Ajax and Dojo Widgets – common user interface patterns for lists, tables, forms, etc. ■ Dynamic profiling allowing you to write once deploy on many platforms with minimal effort Fast Simple development Write once deploy many
  7. 7. WebSphere Portal + Web Experience Factory + IBM Worklight Effective Multi Channel Development ■ Best of all worlds with a single source application that : – –Maximizes Coverage. – –Maximize Re-use of code – –Minimize Time/Effort to train skill in multi-channel development
  8. 8. © 2010 IBM Corporation Web Experience Factory Traditional Java Portlet Development Tools Quick summary ● Model Based development – you chose and tweak mode ● Creates standards based portlets (eg JSR 286 & JSR168), iWidgets and web applications ● You write and edit code ● Creates standards based portlets (eg JSR 286) and web applications Key differentiators ●Model-based automation framework ●150+ builders ●Quick to learn without having to learn low level framework and APIs ●You write code ● Use low-level frameworks and tooling Sweet Spots ●Solution where integration required maps to pre—built builders (eg SAP, Peoplesoft). ●Solution that are well suited to pre-built builders ●Where teams do not have strong Java skills ●Enterprise development teams with deep Java Skills Skills Requirements ● Web Developers (like .NET, Ruby, PHP...), with good understanding of coding and web principles and technologies but do not necessarily need to be low level Java developers. ● Only require deep Java if there is a need to create custom builders ● Requires enterprise level Java development skills. ● Skills for low-level framwork, APIs and tooling
  9. 9. Side by side comparison Run Wizard Tweak/Edit Model Run Wizard Tweak/Edit (Generated) Code Choose existing builder Start Writing from scratch Model based Traditional Java coding Skill Set ● general development skills. ● Will learn how to use specific builders ● Will need Java skills if you want to write your own builders or extend beyond out of the box ● deep JavaSkills ● Deep skills on chosen frameworks and tooling: eg Spring, JSF, Dojo/jQuery/HTML 5 Learning Curve ● 3 – 5 day course for basics (no Java required) ● Recommend working with experienced developer to achieve best practices ● More time required if you wish to extend beyond out of the box with own builders and custom Java code. ● Steep ● Multiplied for each of chosen framework and tooling ● Recommend working alongside experienced developers who have skills with all chosen variables Ensuring code quality ● Easier as you never touch code ● Need to ensure best practices are followed ● Harder to manage as each developer gets more flexibility, as writing each snippet of code.
  10. 10. Key Best Practices ■ All your traditional best practices... – Training/Education: at the bare minimum we recommend that developers attend a formal 3 – 5 day Web Experience Factory course to learn the basics and importantly how to approach developing best practices solutions with Web Experience Factory – Mentoring: It's strongly recommended that teams that are new to Web Experience Factory are teamed with mentors to ensure analysis, design and development follow a best practices approach. – Supporting two core levels of developers: • Level 1 – developers with basic Web Experience Factory skills, who don't have deep Java skills • Level 2 – the core experienced Web Experience Factory developers on a project who a) understand how and when to extend the project and b) can create infrastructure (eg builders and models) that can be re-used by Level 1 developers – Design and Development: Just because you are using model based design, does not mean that you should not follow a formal analysis and design of solutions being delivered. Especially on larger teams/projects extra care should be taken with a strong encouragement for identifying common patterns and investing in a common infrastructure to increase the ROI across projects – Re-use/Looking for patterns: One of Web Experience Factory's strengths is being able to encapsulate re-usable patterns. When these repeatable patterns are identified, the possibility of creating re-usable assets (including builders) should be looked at carefully, with intent to support the two levels of developers.
  11. 11. Example of applying best practices (from real Customer) Customer profile: Large technology provider develops and sells a core banking solution to many SMB banks Requirement: for each new bank there is a need to integrate the banking solution with the bank's internal systems, requiring a fair level of customization. Key challenges: – The out of the box builders did not meet the requirement for the detailed transformations required for each bank's deployment. – There is a core highly skilled Web Experience Factory team (Level 2) who need to work with a larger pool of developers (Level 1) who are new to Web Experience Factory Options to address challenges: Pros Cons 1) Develop using Linked Java Objects Using Web Experience Factory out of the box, with minimal additional development ● Developers will require Java coding and skills which is time consuming ● More code: ● harder to control quality of code ● More maintenance effort 2) Can automate this with a Builder ● Reduced effort & time to develop solution using point and click ● Potentially reduced skill level of developer ● Better control of code quality Time, effort and skill required to invest in infrastructure Chosen approach: ■ The technology provider is investing in creating new builders to automate the development process, which will provide a better return on investment ■ Developers new to Web Experience Factory will be mentored by the technology provider's core Web Experience Factory team to apply best practices and use builders, favoring point and click vs hand coding
  12. 12. Best practices for addressing challenges with Model Based Development: ■ Reluctance of developers to try new approach: I can't touch code, I don't like it... – Need to approach from a clean slate, model based development is different. ■ Don't know which builder to use? – Use in IDE help and builder categories – IBM also provides a wealth of good samples and articles for customers and partners to understand which builders to use when. ■ It's hard to find folks with Web Experience Factory skills? – IBM and IBM partners can help organziations get up to speed. At the very least we recommend engaging with a skilled partner or IBM services team for mentoring and help orginations apply best practices and maximize chance of success. – Learning how to use model-based development tools is faster and easier than traditional coding tool, so it's not hard to enable folk. IBM and IBM partners offer standard and customized training options.
  13. 13. © 2010 IBM Corporation Mixing and Matching - When to use what? ■ It's fairly common that organizations have a mix of both skills and development tools for developing applications. Here are some guidelines that may help organizations decide which tool to apply to which project/solution and how they can work together. Web Experience Factory Traditional Java Development Tools Using both together Skills set: Do not require strong Java skills,applicable to a broader spectrum of web developers including Training is strongly recommended. Java and JEE skills are a must. When teams have a range of skills Application Requirements: If there is a close match to existing pre-builders vs using low-level APIs Web Experience Factory may be a better choice, regardless of skillset. For example, if there are strong requirements for SAP, Oracle/Siebel or Lotus Domino integration these builders exist with potential to speed up initial development effort and reduce ongoing maintenance costs. JEE standards based application development. In addition to skills set, if there is a strong set of custom J2EE based assets that can be re-used on a specific project. Ability to use SOA and loosely coupled APIs like REST APIs to allow teams to use tools of choice to create re-usable services that can be consumed by other developers using their tool of choice. Enterprise standards Web Experience Factory supports standard SCM and can provide a “lighter” development environment than a full-blown Java Dev installation For enterprise projects where there is a strong requirement and investment in Java EE industry standards, processes and education. Web Experience Factory can be installed into enterprise Java development environment RAD/RSA and Eclipse
  14. 14. 14 Backup
  15. 15. Additional Reference Materials Web Experience Factory Beta: Web Experience Factory Trial: Web Experience Factory Wiki: Web Experience Factory Zone on DeveloperWorks: Rapid Portlet Development with Web Experience Factory (via WebSphere Portlet Factory Redbook: WebSphere Portlet Factory Forums: WebSphere Portlet Factory External Site: WebSphere Portlet Factory Training US and Worldwide (Search for Keyword Portlet Factory):
  16. 16. IBM Lotus Connections 3.0 Portlet Developer Pack and IBM Industry Toolboxes for WebSphere Portal Out of the box Lotus Connections portlets built with Web Experience Factory and provided with full source code. Includes portlets for Blogs, Wikis, Tag Cloud, Profiles, Activities and Bookmarks IBM Industry Toolboxes for WebSphere Portal built with Web Experience Factory portlets.
  17. 17. 17 IBM Industry Templates for IBM WebSphere Portal Jump-Start Templates Speed Time to Value Product capabilities referenced in this document reflect planned capability and may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way.  Extensible, Configurable Software Templates   Accelerates solution construction for specific business needs  Delivers pre-built Portal sites, structure, and components commonly used in a target industry  Provides source code for easy customization by customers or partners   Reusable Web Experience Factory based software components available via Portal Solutions Catalog  Unified Task List  Checklist  Advanced Self- Registration  Sametime Chat  Tag Cloud  Content Teaser  eBanking portlets Government-to-Business Online Banking Retail Vendor On-Boarding Checklists, Universal Task List Sametime 8.5 Chat Advanced Self-Registration
  18. 18. 18 IBM® Healthcare Accelerator Patient Portal Package for Healthcare Providers Product capabilities referenced in this document reflect planned capability and may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way.  Increase Patient Loyalty Via easily accessed services & information   Improve Patient Satisfaction Via anytime access to appointments, payments, medical records, etc.   Increase Operational Efficiency By empowering the patient to perform transactions directly   Faster Time-to-Payment Online payments reduce mailed payments Can bypass a call center and manual handling   Reduce Cost-to-Collect Can eliminate paper invoices Fewer manual touch points   Single foundation investment (WebSphere Portal) to deliver multiple portals Start with a Patient Portal; add profiles and capabilities for Physicians, Nurses, Analysts, Employees, etc.
  19. 19. 19 Links to IBM apps/samples created with IBM Web Experience Factory Product Link on Catalog IBM WebSphere Portal Unified Task List Portlet version 5.0 action=editDocument&documentId=B83A591CD238D9AA85257706006AE752 IBM Websphere Portal Notifications action=editDocument&documentId=01CFC971382EAA6E8525775E00575AF3 IBM Healthcare Patient Portal Template for WebSphere Portal action=editDocument&documentId=125AA0175153315A852578B00060904C IBM Insurance Template for WebSphere Portal action=editDocument&documentId=971F32B2EFB5971A8525783E00585F0B IBM Government Self Service Template for WebSphere Portal action=editDocument&documentId=716AD6C25079CE98852578B0005DF209 IBM Retail Vendor Template for WebSphere Portal (v 2.0) action=editDocument&documentId=A102887A2F5EAE48852578B0006402EE IBM Retail Banking Template for WebSphere Portal 8 action=openDocument&documentId=D3C22AC6C8576C77852578AE0078C5A2 IBM WebSphere Portal Unified Task List Portlet - Developer Pack action=editDocument&documentId=9D3A741B10ACE980852577F400385312 IBM WebSphere Portal Self Registration portlet action=editDocument&documentId=8D03F98D3BB97579852576FF006AE798 IBM WebSphere Portal Sametime Chat portlet action=editDocument&documentId=9CE499C8A938AE238525770D006C6700&SessionID=D3JJ X8DRMQ
  20. 20. 20 IBM Software revolutionizes after-sales services by benefitting all parties IBM portal solution serves both consumers and businesses via an exceptional web experience The need: A new business model for providing online after-sales services required a portal capable of supporting both consumers and businesses around the world The solution: A portal solution based on IBM software components supports comprehensive services that pay for themselves while attracting additional new revenue sources for Yarraa and its business clients The benefit:  Customers benefit from a unique service that gives them a voice along with faster service and repairs  Businesses have access to better information that helps lower costs  Providing an exceptional web experience gives Yarraa rapid growth to 2 million product registrations “Everybody has a horror story about a lost warranty card, or something that broke down a week after the warranty ended, or a receipt they couldn’t find. Our goal is to put a stop to that.” —David Bede, Director of Marketing and Strategy, Yarraa, Inc. Solution components:  IBM® WebSphere® Portal  IBM Web Content Manager  IBM WebSphere Application Server  RigelSoft, Ltd WSP14421-USEN-00
  21. 21. 21 A Customer Reference: TransMontaigne  Company Profile:  Provides supply chain, distribution, sales and marketing services for the oil, gas, chemical industry  Challenges:  Provide immediate availability to shipment, status, terminal, product and billing information  Reduce the time and effort required by the staff to manually compile, prepare and distribute information  Access many different data sources (legacy custom applications, SAP, Excel spreadsheets)  Results:  Improved effectiveness with dashboards that provide immediate, real-time information  Increased staff productivity by eliminating hours of manual effort per day  Reduced costs by making the staff more productive and reducing the IT development time and costs
  22. 22. 22  Profile One of North America’s largest facilities outsourcing companies $650 million in annual sales 4  Challenges Programmers with minimal exposure to J2EE, Java languages and HTML Need to unite technology and leverage legacy systems Eliminate manual processes and meet technology needs for next 5 -10 years  Results Delivered Time Entry Application (T.E.A.) and Quality Inspection Portals - on time and on budget Established communication with AS400 and DB2 databases Leveraged LDAP groups for profiling T.E.A portal targets 200 sites, automates payroll process for 5000 employees Quality Inspection Portal added 100 new features to former quality inspection system 50% faster development UNICCO Service Company Enhancing Quality Assurance and Automating Labor Tracking
  23. 23. © 2010 IBM Corporation Web Experience Factory Traditional Java Development approach Quick summary Traditional IDE (Eclipse) model-based development for creating Multi-channel Portlets and Widgets that can be deployed anywhere on either WebSphere Portal Server, WebSphere Application Server and IBM Mashup Center Traditional Eclipse based IDE/Java development environment for creating Multi-Channel portlets, widgets and enterprise applications that can be deployed to WebSphere Portal and WebSphere Application Server. Key differentiators ●Model-based automation framework ●150+ builders ●creates standards based portlets and iWidgets ●automation ●Transformation ●Eclipse based - Integrates with traditional SCM and development tooling ●Standards based UI tooling (eg Dojo) ●Application require separate back-end/database ●Creates standards based portlets and iWidgets ●Tooling as part of broader Java EE development environment ●Support Java EE standard and frameworks like JSF ●Integrates with Web Services (JAX-RS, Apache Wink, REST) ●Provides tooling for SOA based development ●Out of the box editors to design HTML, JS and CSS pages ●Low level access to Java code ●Standards based UI tooling (eg Dojo) ●Application require separate back-end/database Sweet Spots ●Solution where integration required maps to pre—built builders (eg SAP, Peoplesoft). ●Solution that are well suited to pre-built builder ● Moderate Java skills ● Above Average JEE skills ●Add on for portlet development in an existing enterprise development environment. ●Ground up development required as rapid development solutions like WPF and Nitro do not cater well for the specific application/scenarios Skills Requirements ● Web Developers (like .NET, Ruby, PHP...), with good understanding of coding and web principles and technologies but do not necessarily need to be low level Java developers. ● Only require deep Java if there is a need to create custom builders ● Requires enterprise level Java development skills.