Information Technology Reference
In-Depth Information
The current maturity levels of the Technology and Business axis, as shown in the
figure above, have been established based on the professional experience and State-
of-the-Art studies [ 15] [16] [17] [18 ] from the authors. Nevertheless, the maturity levels
will be accordingly updated with new achievements.
These maturity values represented in each axis have the following meanings:
Technology axis
(0,0) Monolithic: interface logic, business logic, and data logic are in the same
machine.
(0,0.5) Client-server with a thick client (i.e. VB application), event driven. Code
tightly coupled to the interface. DB is in the local network or on a server outside
but all the logic remains in the same machine.
(0,1) Client-server with a thin client (i.e. j2EE application, 2-n tier), with no usage
of web services. Multiple DB instances.
(0,2) Client-server with a thin client such as mozilla, opera, chrome or Internet
explorer (i.e. J2EE application, 2-n tier), with usage of web services. A unique
instance of the DB. Multiple instances of the application.
(0,3) Client-server with a thin client, 1 DB instance, 1 DB application, n
appearance customizations.
Business axis
(0,0) License (instalment), support, updates, upgrades, maintenance are paid under
a different fee model than the license. No helpdesk. No SLA. No upgrade protocol
and procedures.
(0,0.5) Most revenues are obtained from sales of licenses. Even though, there exist
some sales (less than 10% of the total amount) that are made in a service form with
a flat rate model.
(1,0) Most revenues are obtained from sales of licenses. Between 10-20% are from
the product sale as service with pay per use, flat rate, hybrid pricing models. SLA
is being defined. Upgrade protocol and procedures are being defined.
(2,0) More than 60% of the sales are from the product as a service. Helpdesk is
institutionalized but not 24x7 and only in certain languages. Existence of SLA,
upgrade protocol but upgrades are still seldom, legal department.
(3,0) 100% of the sales are from the product as a service. Existence of a 24x7
helpdesk, multilingual, Marketing mostly done through the Internet (social media),
SLA, upgrade protocol and procedures, Long Tail business model.
B. Technical Feasibility Analysis
A possible way to discern whether the migration is possible or not, is a feasibility
analysis. Existing migration methods to SOA like SEI's SMART [5] propose doing it
mainly by means of questionnaires or interviews to key people leaving aside the use
of supporting tools.
Search WWH ::




Custom Search