Successfully reported this slideshow.

Jerry Romanek series mobile development 2012 year end review


Published on

  • Be the first to comment

  • Be the first to like this

Jerry Romanek series mobile development 2012 year end review

  1. 1. IBM Rational WebCastMobile App Development Series 2012 Year End Review December 2012 Leigh Williamson
  2. 2. Mobile is a significant component of the evolution of computing Consumer experience and “bring your own device” are driving much new enterprise use.
  3. 3. Fundamentally changing industries Retail Financial Services DistributionMobile banking will be the most widely used banking channel by 2020, if not sooner Source: Mobile banking: A catalyst for improving bank performance, Deloitte, 2010
  4. 4. Augmented Reality, driven by mobile devices
  5. 5. 360° experiences arent just about retail ° and media… Sanofi AventisiBG Star Blood Glucose Meter
  6. 6. Rational Mobile Software StrategyRational’s goal is to offer value to teams that are developing mobile applications & software, regardless of the application architecture. Web Programming Model Hybrid Programming Model Cross-Platform Native Programming Model Single-Platform Native Programming Model SMS and Feature Phone SoftwareRational’s value spans the entire software development and delivery lifecycle. It leverages an integrated set of products that provide collaboration, linkage, and transparency across: Requirements Modeling & design Code development Build & packaging Testing & quality management Software delivery
  7. 7. IBM announces the intent to acquire Worklight to extend our enterprise mobile capabilitiesWorklight : a privately held company based in Tel Aviv and New York thatprovides a leading open standards based mobile application platform forsmartphones and tablets letting you build and iterate mobile apps quicklyIBM and Worklight Together: With the combination of existing portfoliocapabilities in Mobile Device Management, Mobile Web ApplicationDevelopment, Integration, Collaborative Tools and Mobile strategy,planning, implementation, and hosting services, with the acquisition ofWorklight, IBM can now offer a complete end-to-end solution to enterpriseslooking to capitalize on the rapidly expanding mobile market.
  8. 8. Worklight Overview Worklight Studio The most complete, extensible environment with maximum code reuse and per-device optimization Worklight Server Unified notifications, runtime skinning, version management, security, integration and delivery Worklight Runtime Components Extensive libraries and client APIs that expose and interface← with native device functionality Worklight Console A web-based console for real-time analytics and control of your mobile apps and infrastructure
  9. 9. IBM’s strategy addresses full range of mobile enterprise needsExtend & Transform Build & ConnectExtend existing business Build mobile applicationscapabilities to mobile devices Connect to, and runTransform the business by backend systems in supportcreating new opportunities of mobile Manage & Secure Manage mobile devices, services and applications Secure my mobile business
  10. 10. IBM Has Extensive Approach to Mobile Security Over the Network & At the Device For the Mobile App Enterprise Manage device Secure Access Develop Secure App Register; Set appropriate Properly identify mobile users & Develop secure apps; security policies; compliance; devices; allow or deny access. Utilize secure coding wipe; lock. Connectivity. practices. Secure Data Protect from threats Test for Vulnerabilities Data separation; Encryption. Protect from mobile and web Test and Identify application threats vulnerabilities Secure Application Monitor access Integrate Securely App security policies; Log network access, events. Secure connectivity to enterprise application level controls Monitor & gain intelligence applications and services Internet Corporate Intranet Safe usage of smartphones and tablets in the enterprise IBM Mobile Secure access to corporate data and supporting privacy Security Strategy Visibility and security of enterprise mobile platform
  11. 11. Tealeaf CX Mobile: Mobile dashboard Discover what’s working and what isn’t – and WHYAutomatic detection of Cross channelmobile customer analytics: web, app,struggle mobile site Complete experience capture: In screen visibility Complete experience capture: user actions, application, In screen visibility (orientation, swipe, user actions, application, environmental and network (orientation, swipe, form entry, clicks) to environmental and network data form usability issues track entry, clicks) to data track usability issues
  12. 12. IBM Worklight Studio New Worklight Native SDK Construct UI Preview Test inCreate Preview Debug in Build in simulatorProject Build browser App browser or device Code Business In Logic Studio In RTC
  13. 13. Unique mobile development project challenges Delivering high quality apps that engage users Developing for multiple mobile platforms and meet business objectivesHighly fragmented set of platforms, Poor quality can negativelydevices, languages, and tools impact brand imageincreases cost and complexity of Bad ratings and commentsdevelopment and test can cause other users toChoosing not to support one or more avoid trying an appplatforms reduces the reach of anapplication Integrating with enterprise systems Meeting accelerated time to market requirementsRecreating instead of leveraging Hand-off errors and delaysexisting business logic increases between teams slows progressmaintenance costs and risk of and responsiveness toinconsistent behavior features and fixesLack of ready back-end services Misalignment of stakeholdersslows front-end development results in late rework andand increases potential for last increased cycle timesminute integration issues
  14. 14. Mobile software development is a team sportSoftware development involves a team of peoplewith diverse skills using different tools – Design, development, test, operations, etc.Tools can make or break collaboration – Fragmented tools create silos – Integrated tools break down barriersEffective development depends on … – Defined goals – Transparency of progress and quality trends – Aligning teams across the entire application development lifecycle
  15. 15. For any team, silos create barriers to effective software delivery 1. Business2. Development 3. Operations*
  16. 16. Application lifecycle management (ALM) is the discipline of overcoming these silos to realize a whole-team, whole-view approach to the software delivery cycle. Mobile developmentALM manages the requires the adoption offlow of: Agile practices to 1. Business keep up with demand People for frequent releasesProcessInformation 2. Development 3. Operations*
  17. 17. IBM Mobile Development Lifecycle Solution V4.0a collaborative, multi-platform mobile development lifecycle A comprehensive mobile development solution combining: Enterprise-grade, standard-based mobile Design application platform, supporting native, hybrid and mobile web programming models Best-of-class collaborative mobile application App Design and IBM Worklight Mobile Testing Construction development lifecycle capabilities Distributed team build and test integrations with SCM and Mobile the IBM Mobile Platform Builds “Mobile device-cloud” service integration for on- IBM Rational Collaborative Lifecycle Management device testing Support for Agile methodologies for dealing with fast-paced development for mobile Mobile development best practice
  18. 18. 18 Agile ALM Usage Scenarios for Mobile development teams End-to-end process; highlighting capabilities relevant to mobile development and delivery Build and package for test • Build the app based on integrated changes from the team Deploy to Dev and Test environment • Build for each target platform • Build deploys to the mobile app server-side, and ‘app store’ Add requirement to the plan • Device under test retrieves app • Add item to sprint plan • Update test plan Manual testing Elaborate requirement and review • Launch emulator / device and • Review seeded artifacts; focus on perform manual integration test Fix bug and simulate linkage and UI sketching/storyboard • Find problem and fix • Perform final approval to close out a Construct and simulate • Preview using mobile simulator review • Review design from the IDE • Check in and deliver code • Code using visual editor • Preview using mobile simulator • Check in and deliver code
  19. 19. Lifecycle techniques to help optimize user experienceImprove collaboration and communications between line-of-business stakeholders and development team Ensure that development understands and will deliver an app that meets business objectives Engage non-technical stakeholders Improve collaboration to find a cheaper yet satisfying solutionPut more focus on the application design and conceptualization phase Iterate during the phase of the lifecycle when it is cheapest to make changes, not when the code is done and changes require drastic re-architectureUse UI sketching, storyboarding, and business process diagrams Improves communications – “a picture is worth a thousand words” Avoid over-elaboration with sketches; focus on high-level, big-picture issues Ensure proper application flow and interactions with business process diagrams
  20. 20. Communicate an outside-in user experience spec Collaborate as a team using comments and annotations Get feedback from non- technical stakeholders
  21. 21. Testing the end-to-end mobile solutionClient Tier Devices Middle Tier Server Back-end Data & Services Testing involves much more than just the mobile front-end
  22. 22. RTW supports isolating tiers of the app for focused mobile testing Test VirtualizationRational Test Workbench support for isolating mobile client tier For focused automated mobile client tier functional testing, use RTW Test Virtualization to simulate the mobile middle tier and back office systems.
  23. 23. Deep Application Instrumentation for Mobile Function Test Mobile Testing Tech PreviewApplication instrumentation libraries provide a transparent overlay for user interaction with the mobile app.Architecture adheres to adapter model followed by other Rational quality management products. Architecturally, our approach is to have an adapter that deals with all mobile devices. An extension specific to the mobile platform resides on the device. Event capture and playback services together with UI elements constitute each extension. Recorder Service iPhone Android Extn Extn Instrument Player Service Keyboard Service Logging Debugging Communication Layer Componentized View of ExtensionKey Goals for Mobile Test Automation Dynamic Instrumentation of Android Mobile Applications (without requiring source/static enablement) Adapter model with specific extensions for multiple mobile platforms Capture with high-fidelity replay of multi-touch events23
  24. 24. Integrating with existing systems IBM CONFIDENTIAL• Mobile applications need to connect to enterprise back-end data and services• Existing programs and services may need to be modified for the mobile app• Multiple skills will be involved, responsible for different parts of the mobile application
  25. 25. Rational IDEs with IBM Worklight Design, code, build, test, and deploy mobile apps that run on a wide variety of mobile platforms; extend existing back-end services and data to mobile apps Integrated multi-platform development environmentsConstruct, debug, and test mobile Refactor and extend existing logic on UIs enterprise platforms (System z, Power) as mobile-consumable services IBM Worklight 5.0 is now included in the following IDEs (for development purposes only): Rational Developer for zEnterprise v8.5 Rational Application Developer v8.5 Rational Developer for Power Systems v8.5 Rational Software Architect v8.5
  26. 26. Rational Software Architect v8.5.11 Worklight Support Model RESTFul Service in RSA 2 Generate JAX-RS based Web Service 3 Generate JAXB classes from Data Model* Deployed on Websphere Application Server 5 Generate Worklight Client Stub * 4 Generate Worklight Adapter * Deployed on Mobile Deployed on Worklight Device (Worklight Server Device Runtime) * new transformation in RSA
  27. 27. Solve mobile development challenges with IBM Mobile Development Lifecycle Solution V4.0 Delivering high quality apps that engageDeveloping for multiple mobile platforms users and meet business objectivesCross-platform mobile web and Linkage and traceability acrosshybrid app development, test, and all phases of developmentbuild UI sketching and storyboardingManage plans, tasks, code, builds Test plan optimization andfrom a common development management and integrationworkbench with mobile “Device-clouds”Agile planning Portfolio management Meeting accelerated time to market Integrating with enterprise systems requirementsIntegrate Worklight Studio with the Automate and manageRational IDEs to create a continuous, end-to-end build andcomprehensive IDE for all parts of deployment process with RTCthe app (UI, mid tier, back-end) Deploy to private dev/test appExtend enterprise assets as Reduce cycle times by aligningmobile-consumable services and dev and operations teamsconnect via Worklight adapters
  28. 28. IBM Mobile Development Lifecycle Solution Video
  29. 29. IBM Mobile Development ResourcesExternal developerWorks Mobile Frontier blog