As I meet many clients and team members I realized one thing, and that is:
Mobile will not fix or bypass existing deficiencies
in the enterprise, on the contrary Mobility will bring these concerns front and
center to all Mobile discussions. So Mobility is NOT about an app running on a
mobile device, but have far deeper implications when it comes to enterprise
integration and mobilizing these services. I think our experience and out
platform can serve as our competitive advantage in surfacing and addressing
these in our Mobile Conversations. From a platform perspective competing products
also have to have the enterprise DNA in them. ( More on this in next post)
Mapping Enterprise design points to Technical design points:
In
the spirit of engaging with a purpose and deliberately, I wanted to discuss an
approach that will lay the foundation and provide a structure before we get
into product features. The approach I usually take is devising a “Enterprise
Design points” and mapping to “Technical Design Points”. The idea with this
approach is to ensure we capture
the LOB/Business design requirements and
use the tools at our disposal
to define a solution architecture to address the
enterprise design points.
Enterprise
Design Points:
a. Deliberate and Intentional engagement
b. Exposing back end services and data
c. Data transfer and data growth
considerations
d. Bandwidth and TCP Socket chatter
e. MEAP or MCAP?
f. Enterprise Integration
g. Security – enterprise and endpoint
security
h. Device and Platform support
i. Legal responsibilities – Application
store, client data and resulting exposure
Which
Maps to
Technical Design Points:
a. Enterprise application integration (tools
and libraries
b. Device integration and peripheral support
c. Application client runtime
d. Device/OS platform support
e. Packaged mobile
f. Hosting
g. Architectural flexibility
As always I love
to hear from you your critique and thoughts.
– Let us engage
Deliberately and not by accident!
Have a great week ahead.
;)
Nitin
No comments:
Post a Comment