A Proposal for a Standard With Innovation Management System

Mohammed AlSudairi and TGK Vasista
7.5.4 Service metamorphosis
Service Metamorphosis is having the capability of service transformation into its various forms viz.,
environment, platform and software at various abstraction levels. Any service that transforms a
service must offer best practices, methodologies, disciplines, languages, tools, score card, time frame
and a process. It should support both forward and backward transformation.
7.5.5 Blue print
It is a modeling framework that encapsulates the abstractions and realizations of modeling practices,
modeling environments, modeling disciplines, modeling artifacts and solution entities (Methodologies
Inc).
One of the key service design principles is the metadata-based stateless service design (Erradi,
Kulkarni, Anand and Padmanabhuni 2005) which is used in order to minimize resource consumption
by differing the management of state information when necessary(SOA principles.com; Wiki,SOA). It
means that exchanged messages should be self-contained with sufficient information and metadata
(like links to persisted data) to allow the destination service to establish the message context (Erradi
et al. 2005).
7.6 Benchmarking of policies and rules with automated service bus (ASB)
The Automated Service Bus (ASB) Concept implementation can bring significant benefits such as (1)
simple aggregation of components and services according to the project needs based on a common
abstract infrastructure for communication between tools and systems (2) improved coordination
between tools that were not designed to work through access to data and relevant changes in other
tools (3) Legal recording and systematic closing of open loops in engineering team processes. In
advanced stages of an ASB implementation, global view on tools and systems in automation system
lifecycle for optimization of the engineering and operation processes like analysis of cross-linked data
from several sources; securing access to data in automation systems can be brought (Biffl, Schatten
and Zoitl 2009). Table 1 provides direction to design a development project type by adopting
appropriate web services type to different innovation customer types. The purpose of ASB in this
context is assumed to support all customer types.
Table 1: Matching projects and customers with web services design and development
Sl. No. Customer Type Project Type Web Services Type
1. Innovators - Greenfield
2. Early Adopters Break through Top Down
3. Early Majority Platform Bottom Up
4. Late Majority Derived Meet-in-the-Middle
5. Laggards - -
7.6.1 Bindings
The concept of binding deals with (a) technical aspects of binding and (b) economic, artistic and
cultural values of bindings. While technological aspect deals with the technical concept of static and
dynamic bindings, economy, arts and culture bindings take place through automation of economy
through web service abstractions and encapsulation based on service metamorphosis principle and
using SOA Meta-model (Wiki-SOA and the Linthicum Group 2007).
7.7 Realization and accountability management plug-in
7.7.1 Concretizations
Concretization approach allows modeling and developing large complex systems. Concretization is
the step of developing the system in a concrete environment by realizing its functionalities according
to the specification for a specific platform (Chen 2009). Transformations are expressed in
Collaborative Component Based Model (CCBM) Approach to transfer model expertise into concrete
applications. This approach achieves black-box reuse of models and pre-serves them. Every
collaboration model specifies requirements that other models must fulfill in order to participate in
collaboration in terms of collaboration operations (Stereotypes) and collaboration templates (a variant
13