Showing posts with label MEAP. Show all posts
Showing posts with label MEAP. Show all posts

Tuesday, March 12, 2013

The Rules of Enterprise Mobility

During many mobile meetings, presentations, and discussions I've come across a collection of "Rules For Enterprise Mobility". These rules cover topics like selecting mobility tools, types of users and applications, mobility needs and a lot more. Let's start with three rules of three:

Rule of Three
Gartner coined the phrase "the rule of three" to help convey when it best makes sense to use a MEAP (Mobile Enterprise Application Platform). The idea is that you should consider a MEAP if you have any of the following needs:
  • 3 x mobile applications
  • 3 x device types
  • 3 x back end systems
Of course a platform helps with these by providing security, integration, and write-once deploy-many tools that you may have to develop yourself if you go it alone. So that's a rule number 1.

Three Mobile Groups
Coincidentally there are three user groups that we typically identify as the target of mobile applications:
  • B2E (Business to Employee/Enterprise)
  • B2B (Business to Business)
  • B2C (Business to Consumer)
Business to Employee/Enterprise applications are those which are used by employees of ones own company. Business to Business are used by partners or subcontractors and Business to Consumer are used by the general masses. Ok this is not really a rule per say but it's still mobility and involves the number 3.

Three Application Types
Thirdly there are 3 commonly recognised mobile application types:
  • Web
  • Native
  • Hybrid
Each of these application types have their place and various pros and cons (for example portability, performance, learning curve, cost) which I've discussed in my previous blogs. I don't know if that's now 9 or 27 rules or if it makes sense to try to or correlate them further. It would be great if there was one rule to bind them all but Tolkien didn't write enterprise mobility.

Four C's 
In the blog by Christopher Koch the concept of the four C's is discussed to explain the scope of a mobility platform:
  • Create
  • Consume
  • Connect
  • Control
As Christopher explains a mobility platform for enterprise that covers each of these areas will add value to business and IT. Suggest you have a look at the Gartner quadrants for some good information on the various mobile platforms.

Seven Steps
The 7 Steps for an Enterprise Mobility Strategy are covered nicely in Spider 21's Weblog these are:
  • Mobility Roadmap
  • User Workflow Analysis
  • Mobile Platform Selection
  • Device/OS Selection
  • Back-end integration
  • Mobile app development
  • Change Management.
Well worth a read to understand more about each of these important topics.

More Numbers?
I hope this selection of rules serves as a good reference for Enterprise Mobility and would love to hear some suggestions for more rules to include/update the article. If you are looking for detailed information on topics like Mobile Device Selection, Benefits of Mobility, or Mobile Testing then please follow the links or read through all the articles on this blog.

Friday, February 8, 2013

Testing Enterprise Mobility

One challenge for any IT project is to ensure that testing is performed efficiently and effectively. As with many things the goal is to try to find a happy balance. In this case ensuring quality without spending forever on the testing cycle. Before I go any further my intention here is not to dwell on V charts, and testing frameworks but rather to talk specifically about testing enterprise mobile applications.

Key Considerations
  • GUI
  • Screen flow/work-flows
  • Integration
  • Mobile device/s
  • Communications
  • Infrastructure
  • Security
  • Roll-out
GUI, Screens, & Integration
Certainly a lot of the focus when testing enterprise mobility should be the application, its screens, and integration. Involving end users early (when managed correctly) can really help to ensure that the screen flows work under real use scenarios. Often functions can be tested independently during the development cycle. Device Emulators/simulators on a desktop can help rapidly test while waiting for the infrastructure and comms to be put in place. If the mobile application works in an offline way then ensure to test for data conflicts, locks, and test the resolution process. How can the solution recover from an integration error?

Mobile Devices
An important consideration that is sometimes overlooked is the wide variety of Mobile devices, models, operating systems, screen sizes, peripherals, and input methods that are being used in the solution. Don't assume that everything that works on Model X will automatically work on Model Y.

Battery life - does your shiny new mobile application drain the battery flat in minutes? Is it using lots of CPU when decompressing or encrypting data? Does it constantly require communications or gps? Schedule some tests to simulate different levels of usage.

Communications
Communications (or lack there of) should be checked. What happens when halfway through a transaction the comms is lost. What happens if comms is slow or poor? I've seen some creative ways to test this. For example underground car parks, driving through dead spots, or using a Faraday chamber. When projects first move from simulators to devices they are often cradled or connected via wifi. Ensure at some point to factor in tests based on real world communication scenarios.

Infrastructure
With infrastructure it's often not possible to directly replicate the production environment. However it's definitely worth looking at simulating traffic. Try running functional tests while ramping up the load and find out at what point problems occur. MEAPs often come with tools for capturing, simulating, and amplifying traffic.

Authentication & Security
Its obviously important to test the authentication and security mechanisms. Consider carefully how the authentication works and schedule appropriate testing. What happens when passwords expire or the user enters it wrong too many times. Some companies hire in specialists to attempt to compromise the system.

Roll-out
As part of the overall strategy consider using a technical go-live where the mobile application is put into production and tested without being used for real business. This may require assistance from the business to run through some transactions and then back them out. Once the technical solution is confirmed then one or two key users can be introduced to the solution. At this stage monitor the system thoroughly and adapt any changes as necessary. Once proven expand the user base gradually and ensure that performance is managed. On some projects it's necessary to initially throttle the performance so that the first user group does not feel negatively impacted once the entire community is live.

Please let me know your thoughts and any additional lessons learnt from testing enterprise mobile applications...

Saturday, January 19, 2013

B2e mobile apps

Back again, this time I've got a blog on the Inside SAP website discussing the topic of HTML5 vs Native code for B2E apps. I suggest it's worth looking at the MEAP offerings MEAP blog on Inside SAP website