30.10.2012 Views

A Proposal for a Standard With Innovation Management System

A Proposal for a Standard With Innovation Management System

A Proposal for a Standard With Innovation Management System

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Mohammed AlSudairi and TGK Vasista<br />

services in an organisation is a specification of a workflow structure modeling or Business Process<br />

Modeling, tasks, actions, flow of in<strong>for</strong>mation artifacts and messages between the communicating<br />

applications. To enable interoperability of possibly heterogeneous capabilities, knowledge and<br />

capacities of each of the alliance partners, a common shareable knowledge model is used <strong>for</strong><br />

enriching the defined business process with semantic in<strong>for</strong>mation (Bednar, Furdik, Lukac and Sabol<br />

2009). For this purpose, a cloud can be constituted by a Common Cloud <strong>Management</strong> Plat<strong>for</strong>m<br />

(CCMP) implementation and an arbitrary number of cloud services can be delivered and managed by<br />

it (IBM CCRA Team 2011). Thus the In<strong>for</strong>mation Technology has the capability to produce plug and<br />

play business process modules to achieve speed to market and strategic business agility-based<br />

business objective where the business process components are made reusable and manageable<br />

(Ross, Weill and Robertson 2006). Semantic extension makes it much more effective.<br />

7.5 Abstractions (domain abstract consolidations and development abstract<br />

specifications)<br />

7.5.1 Reverse engineering<br />

To create an innovation, a product might require undergoing reverse engineering process (Hentschel,<br />

C. 2009). It can cause the following two types of innovation<br />

� Incremental <strong>Innovation</strong>, and<br />

� Radical <strong>Innovation</strong>.<br />

Senior manager’s intentions and social context lead to the adoption of certain CASE tools, and<br />

influence the conditions under which these tools are used such as planned impact or contingent<br />

impact. Use of CASE tools in the context of reverse engineering can lead to certain changes to the<br />

existing social context and may even bring about changes in manager’s strategy (Orlikowski 1991).<br />

7.5.2 Model-driven engineering<br />

Model-Driven Engineering (MDE) is a software development methodology which focuses on creating<br />

models, or abstractions, closer to some particular domain concepts than algorithmic ones. It aims at<br />

increasing productivity by maximizing compatibility among systems, simplifying the process of design,<br />

and promoting communication among individuals and teams working on the system. One objective of<br />

MDE is to apply model trans<strong>for</strong>mation and composition automatically via supporting tools. In this<br />

context, "Models" are rigorously defined specifications. Some activities or steps of development<br />

process can be automated or semi-automated (Chen 2009).<br />

7.5.3 Enterprise modeling<br />

Strategy: The basic strategy that drives the model and helps it offer solutions consists of four essential<br />

steps:<br />

� Look-in-the-box <strong>for</strong> internal service design,<br />

� Look-out-of-the-box <strong>for</strong> environment design such as service distribution, interoperability,<br />

integration and deployment,<br />

� Look-above-the-box <strong>for</strong> best practices, governance, business imperatives and business<br />

requirements, and<br />

� Look-below-the-box <strong>for</strong> separation of concerns, granularity management, loose coupling<br />

(Methodologies Inc.).<br />

Architecture: Model Driven Architecture (MDA) is an open standard designed to facilitate rapid<br />

application development in a plat<strong>for</strong>m independent manner. Models can be built at a high level of<br />

abstraction by using MDA based tools, trans<strong>for</strong>med into models and code targeting a specific plat<strong>for</strong>m<br />

or domain. At the abstraction level of a plat<strong>for</strong>m-independent business component model, services<br />

are visible only at a very high level. When the model is mapped to a particular plat<strong>for</strong>m, code will be<br />

generated by dynamic invocation that makes calls to the native services of those plat<strong>for</strong>ms (Soley<br />

2000).<br />

12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!