As telecom carriers migrate their networks to a common IP Multimedia Subsystem (IMS) based infras... more As telecom carriers migrate their networks to a common IP Multimedia Subsystem (IMS) based infrastructure, they face a challenge of providing services to their customers based on the current need or situation of the customer. We have seen how Web 2.0 allows a user to build situational applications or mashups. We have used the concept of Context to provide a framework to service providers for providing such services. Context can be defined with attributes such as presence and location. A SOA based services infrastructure would help Telecom service providers to use context in providing composite services to their customers. This paper focuses on how to use context in defining call flows within a Telecom services infrastructure. We assume a Next Generation Network (NGN) infrastructure for the Telecom Services Provider, which would ensure a common IP backbone for all services. Based on our industry implementations, we will describe a generic call flow for one of the context attributes.
A goal-driven approach to enterprise component identification and specification
Communications of the ACM, 2002
... We are proposing a set of criteria for decomposing a business architecture into enterprise bu... more ... We are proposing a set of criteria for decomposing a business architecture into enterprise business components and mapping them onto a CBSA. ... It should capture business rules and conditions that will be important to defining the precise behavior of the components. ...
Service Oriented Architecture (SOA) is emerging to be the predominant architectural style of choi... more Service Oriented Architecture (SOA) is emerging to be the predominant architectural style of choice for many organizations due to the promised agility, flexibility and resilience benefits. However, there are currently few SOA metrics designed to evaluate complexity, effort estimates and health status of SOA solutions. This paper therefore proposes a SOA metrics framework which includes both service level and SOA-wide metrics to measure design and runtime qualities of a SOA solution. The SOA-wide metrics predict the overall complexity, agility and health status of SOA solutions, while service level metrics focus on the fundamental building blocks of SOA, i.e. services. The combined views deliver a compelling suite of SOA metrics that would benefit organizations as they consider adopting SOA. These metrics, which are based on observations of many SOA engagements, are illustrated through a case study that describes a recent ongoing project at IBM where SOA was utilized to build the solution assets.
Information as a Service: Modeling and Realization
Service oriented architecture is enabling a new approach to the design and assembly of service-ba... more Service oriented architecture is enabling a new approach to the design and assembly of service-based solutions and environments, which promises a more fundamental alignment of business and I/T organizations in the enterprise, greater agility of applications by the exploitation of loose coupling, and opportunities for effective reuse and governance of business and I/T activities. Current methods and tools that support SOA development activities, however, have focused primarily on supporting business process and business logic. We discuss the application of SOA principles to enable the utilization of information as a service (IaaS), the benefits in unifying information and process service approaches to SOA, and key research challenges in modeling and realization for IaaS in the context of SOA development.
This article will introduce the foundational concepts of Web services, levels of service integrat... more This article will introduce the foundational concepts of Web services, levels of service integration, discuss the real promise of intra-enterprise integration through an underlying component-based development and integration approach on which Web Services can be built, and then review the technical problems that any implementer or development manager should realize will be part of Web services for th e foreseeable future. Although much of the craze surrounding Web services revolves around inter-enterprise distributed computing, much of the initial power will come from integration within a single enterprise, either with existing legacy applications or with new business processes that span organizational silos. Enterprises will need organizational structures that support this new paradigm and its distribution of control and ownership of information. Finally, technical challenges will be paramount, as Web services are required to satisfy serious, demanding SLAs. When that is the environment, developers will need to confront the task of designing, building, configuring, deploying, and managing software that must meet, and continue to meet, constraints beyond functional correctness.
SOMA-ME: A platform for the model-driven design of SOA solutions
Ibm Systems Journal, 2008
... During domain decomposition, Domain model elements are created to represent each domain defin... more ... During domain decomposition, Domain model elements are created to represent each domain defined within the SOA solution. ,,Stereotype.. FunctionalArea represents a grouping of business functionality consistent with the business analysts' view of their business domain. ...
ADDRESSING THE LOGICAL Each of S3's nine layers has a logica... more ADDRESSING THE LOGICAL Each of S3's nine layers has a logical and phys-ical aspect. The logical aspect includes all the architectural building blocks, design decisions, options, key performance indicators, and so on; the physical aspect covers the realization of each logical aspect ...
Business flexibility requires IT flexibility. IT flexibility can not occur if the old ways contin... more Business flexibility requires IT flexibility. IT flexibility can not occur if the old ways continue to be followed. Transformation to SOA is the way forward. SIMM has proven to be an effective means to achieve that transformation to SOA through a successive set of adoption of states of maturity that is relevant to the enterprise
Service-oriented modeling and architecture (SOMA) has been used to conduct projects of varying sc... more Service-oriented modeling and architecture (SOMA) has been used to conduct projects of varying scope in multiple industries worldwide for the past five years. We report on the usage and structure of the method used to effectively analyze, design, implement, and deploy service-oriented architecture (SOA) projects as part of a fractal model of software development. We also assert that the construct of a service and service modeling, although introduced by SOA, is a software engineering best practice for which an SOA method aids both SOA usage and adoption. In this paper we present the latest updates to this method and share some of the lessons learned. The SOMA method incorporates the key aspects of overall SOA solution design and delivery and is integrated with existing software development methods through a set of placeholders for key activity areas, forming what we call solution templates. We also present a fractal model of software development that can enable the SOMA method to evolve in an approach that goes beyond the iterative and incremental and instead leverages method components and patterns in a recursive, self-similar manner opportunistically at points of variability in the life cycle. Ó
Variation-Oriented Analysis for SOA Solution Design
Many systems are built with very little foresight for incorporating changes resulting from new re... more Many systems are built with very little foresight for incorporating changes resulting from new requirements. This paper provides a systematic way and normative guidance to analyze the variations in SOA solution design. During SOA solution design, two types of change- oriented analysis patterns, variation-oriented analysis (VOA) and event-driven change analysis (EDCA), are proposed to create a resilient design that is adaptive to changes. Specifically, a meta-data model and associated assets for solution design are introduced first to capture the information context for SOA solution design. Then a new change propagation analysis process is presented to summarize the variation identification, variation impact assessment, variation impact path identification, variation analysis and decision making. Based on these two techniques, this paper creates a set of normative guidance for the variation oriented design. These guidelines include but not limited to the artifact type, variation description, variation type, variation artifacts, and impact analysis.
Focus of this paper is to highlight some of the key considerations in developing services in SOA ... more Focus of this paper is to highlight some of the key considerations in developing services in SOA environment. These are based on lessons learnt and experience gained through SOA engagements. High level view of IBM's Service Modeling Technique known as SOMA (Service Oriented Modeling Architecture) is provided here This technique consists of three key steps -Identification, Specification and Realization of Services, Components and Flows.
USING GRAMMAR-ORIENTED OBJECT DESIGN TO SEAMLESSLY MAP BUSINESS MODELS TO COMPONENT-BASED SOFTWARE ARCHITECTURES
... explores extensions to current methods to fully support CBDI across the life cycle starting f... more ... explores extensions to current methods to fully support CBDI across the life cycle starting from business modeling and throughout the software development lifecycle. ... They are, in order of increasing abstraction: base class, aggregation hierarchy, inheritance hierarchy, and ...
Using grammar-oriented object design to seamlessly map business models to software architectures
... explores extensions to current methods to fully support CBDI across the life cycle starting f... more ... explores extensions to current methods to fully support CBDI across the life cycle starting from business modeling and throughout the software development lifecycle. ... They are, in order of increasing abstraction: base class, aggregation hierarchy, inheritance hierarchy, and ...
As telecom carriers migrate their networks to a common IP Multimedia Subsystem (IMS) based infras... more As telecom carriers migrate their networks to a common IP Multimedia Subsystem (IMS) based infrastructure, they face a challenge of providing services to their customers based on the current need or situation of the customer. We have seen how Web 2.0 allows a user to build situational applications or mashups. We have used the concept of Context to provide a framework to service providers for providing such services. Context can be defined with attributes such as presence and location. A SOA based services infrastructure would help Telecom service providers to use context in providing composite services to their customers. This paper focuses on how to use context in defining call flows within a Telecom services infrastructure. We assume a Next Generation Network (NGN) infrastructure for the Telecom Services Provider, which would ensure a common IP backbone for all services. Based on our industry implementations, we will describe a generic call flow for one of the context attributes.
A goal-driven approach to enterprise component identification and specification
Communications of the ACM, 2002
... We are proposing a set of criteria for decomposing a business architecture into enterprise bu... more ... We are proposing a set of criteria for decomposing a business architecture into enterprise business components and mapping them onto a CBSA. ... It should capture business rules and conditions that will be important to defining the precise behavior of the components. ...
Service Oriented Architecture (SOA) is emerging to be the predominant architectural style of choi... more Service Oriented Architecture (SOA) is emerging to be the predominant architectural style of choice for many organizations due to the promised agility, flexibility and resilience benefits. However, there are currently few SOA metrics designed to evaluate complexity, effort estimates and health status of SOA solutions. This paper therefore proposes a SOA metrics framework which includes both service level and SOA-wide metrics to measure design and runtime qualities of a SOA solution. The SOA-wide metrics predict the overall complexity, agility and health status of SOA solutions, while service level metrics focus on the fundamental building blocks of SOA, i.e. services. The combined views deliver a compelling suite of SOA metrics that would benefit organizations as they consider adopting SOA. These metrics, which are based on observations of many SOA engagements, are illustrated through a case study that describes a recent ongoing project at IBM where SOA was utilized to build the solution assets.
Information as a Service: Modeling and Realization
Service oriented architecture is enabling a new approach to the design and assembly of service-ba... more Service oriented architecture is enabling a new approach to the design and assembly of service-based solutions and environments, which promises a more fundamental alignment of business and I/T organizations in the enterprise, greater agility of applications by the exploitation of loose coupling, and opportunities for effective reuse and governance of business and I/T activities. Current methods and tools that support SOA development activities, however, have focused primarily on supporting business process and business logic. We discuss the application of SOA principles to enable the utilization of information as a service (IaaS), the benefits in unifying information and process service approaches to SOA, and key research challenges in modeling and realization for IaaS in the context of SOA development.
This article will introduce the foundational concepts of Web services, levels of service integrat... more This article will introduce the foundational concepts of Web services, levels of service integration, discuss the real promise of intra-enterprise integration through an underlying component-based development and integration approach on which Web Services can be built, and then review the technical problems that any implementer or development manager should realize will be part of Web services for th e foreseeable future. Although much of the craze surrounding Web services revolves around inter-enterprise distributed computing, much of the initial power will come from integration within a single enterprise, either with existing legacy applications or with new business processes that span organizational silos. Enterprises will need organizational structures that support this new paradigm and its distribution of control and ownership of information. Finally, technical challenges will be paramount, as Web services are required to satisfy serious, demanding SLAs. When that is the environment, developers will need to confront the task of designing, building, configuring, deploying, and managing software that must meet, and continue to meet, constraints beyond functional correctness.
SOMA-ME: A platform for the model-driven design of SOA solutions
Ibm Systems Journal, 2008
... During domain decomposition, Domain model elements are created to represent each domain defin... more ... During domain decomposition, Domain model elements are created to represent each domain defined within the SOA solution. ,,Stereotype.. FunctionalArea represents a grouping of business functionality consistent with the business analysts' view of their business domain. ...
ADDRESSING THE LOGICAL Each of S3's nine layers has a logica... more ADDRESSING THE LOGICAL Each of S3's nine layers has a logical and phys-ical aspect. The logical aspect includes all the architectural building blocks, design decisions, options, key performance indicators, and so on; the physical aspect covers the realization of each logical aspect ...
Business flexibility requires IT flexibility. IT flexibility can not occur if the old ways contin... more Business flexibility requires IT flexibility. IT flexibility can not occur if the old ways continue to be followed. Transformation to SOA is the way forward. SIMM has proven to be an effective means to achieve that transformation to SOA through a successive set of adoption of states of maturity that is relevant to the enterprise
Service-oriented modeling and architecture (SOMA) has been used to conduct projects of varying sc... more Service-oriented modeling and architecture (SOMA) has been used to conduct projects of varying scope in multiple industries worldwide for the past five years. We report on the usage and structure of the method used to effectively analyze, design, implement, and deploy service-oriented architecture (SOA) projects as part of a fractal model of software development. We also assert that the construct of a service and service modeling, although introduced by SOA, is a software engineering best practice for which an SOA method aids both SOA usage and adoption. In this paper we present the latest updates to this method and share some of the lessons learned. The SOMA method incorporates the key aspects of overall SOA solution design and delivery and is integrated with existing software development methods through a set of placeholders for key activity areas, forming what we call solution templates. We also present a fractal model of software development that can enable the SOMA method to evolve in an approach that goes beyond the iterative and incremental and instead leverages method components and patterns in a recursive, self-similar manner opportunistically at points of variability in the life cycle. Ó
Variation-Oriented Analysis for SOA Solution Design
Many systems are built with very little foresight for incorporating changes resulting from new re... more Many systems are built with very little foresight for incorporating changes resulting from new requirements. This paper provides a systematic way and normative guidance to analyze the variations in SOA solution design. During SOA solution design, two types of change- oriented analysis patterns, variation-oriented analysis (VOA) and event-driven change analysis (EDCA), are proposed to create a resilient design that is adaptive to changes. Specifically, a meta-data model and associated assets for solution design are introduced first to capture the information context for SOA solution design. Then a new change propagation analysis process is presented to summarize the variation identification, variation impact assessment, variation impact path identification, variation analysis and decision making. Based on these two techniques, this paper creates a set of normative guidance for the variation oriented design. These guidelines include but not limited to the artifact type, variation description, variation type, variation artifacts, and impact analysis.
Focus of this paper is to highlight some of the key considerations in developing services in SOA ... more Focus of this paper is to highlight some of the key considerations in developing services in SOA environment. These are based on lessons learnt and experience gained through SOA engagements. High level view of IBM's Service Modeling Technique known as SOMA (Service Oriented Modeling Architecture) is provided here This technique consists of three key steps -Identification, Specification and Realization of Services, Components and Flows.
USING GRAMMAR-ORIENTED OBJECT DESIGN TO SEAMLESSLY MAP BUSINESS MODELS TO COMPONENT-BASED SOFTWARE ARCHITECTURES
... explores extensions to current methods to fully support CBDI across the life cycle starting f... more ... explores extensions to current methods to fully support CBDI across the life cycle starting from business modeling and throughout the software development lifecycle. ... They are, in order of increasing abstraction: base class, aggregation hierarchy, inheritance hierarchy, and ...
Using grammar-oriented object design to seamlessly map business models to software architectures
... explores extensions to current methods to fully support CBDI across the life cycle starting f... more ... explores extensions to current methods to fully support CBDI across the life cycle starting from business modeling and throughout the software development lifecycle. ... They are, in order of increasing abstraction: base class, aggregation hierarchy, inheritance hierarchy, and ...
Uploads
Papers by Ali Arsanjani