Aw Esb Soa Estimation 09

Your company logoArchitecture World ‘09IT Architecture Firm

Estimation Model

SOA/ESB

Uday Kr. BhattPrincipal ArchitectBirlasoft India Ltd


Agenda

Objective Definition Estimation Framework ESB/SOA Decomposition

Business Factors Business Factor Segmentation Complexity & Weight Factors

Technical Factors Technical factor Segmentation Degrees of Influence

Derived Formula Template Sample Data Summary References Acknowledgement & Q/A


Objective

To calculate the SIZE of a given ESB/SOA project through derived empirical equation.*

In current scenario, merger and acquisitions are widely practiced. The amalgamated organization requires application/business process integration. This results in multiple projects under ESB/SOA which requires effective sizing.

Requirements

Objective

However the estimated effort would vary from Organization to Organization on their respective productivity figure baseline in

Organizational Capability Release.


Definition

According to Gartner:-

“An Enterprise Service Bus (ESB) is a new architecture that exploits Web services, messaging middleware, intelligent routing, and transformation. ESB’s act as a lightweight, ubiquitous integration backbone through which software

services and application components flow.”


The Estimation Framework


ESB/SOA Decomposition

SOA/ESB hierarchical decomposition can help in identifying the primary components and processes Functional Requirements termed as

Business Factors (BFCT) Non- Functional Requirements

termed as Technical factors (TF)


Business Factor (BFCT)

Definition: The components which represents the business requirements and transactions in terms of:- Process

Process consists of set of business processes workflows

Services ESB provides the routing and connectivity through

services, hence services are the real backbone and defined as business services

Integration ESB provides a comprehensive persistent framework

for integration of applications


Business Factor: Process (BFCT-P)

Process: The process factor is decomposed and are following:-

Business Service Workflow (BSW)

BSW can further be decomposed into Sequential (BSW-S) Parallel (BSW-P)

Implementation service Workflow (ISW)

ISW can further be decomposed into Sequential (ISW-S) Parallel (ISW-P)



Process Complexity:

Business Service Workflow

(BSW) Complexity BSW-S

0-10 Simple 11-20 Medium 21-30 Complex

BSW-P 2-4 Simple 5-8 Medium 8-12 Complex

Implementation Service Workflow

(ISW) Complexity ISW-S

0-8 Simple 9-14 Medium 15 -20 Complex

ISW-P 2-4 Simple 5-8 Medium 8-12 Complex



Every Workflow has START and END Decision box Input-Output Parameters or Program Control Process points

Each sub-bullets point mentioned above is referred to as atomic workflow points

These atomic points are related to either data or transaction.

Hence the consolidate number of atomic workflow points are taken to identify the complexity of workflow in either case


Business Factor: Service (BFCT-S)

Services: Services herein defined as business services relation among defined nodes in ESB point Provider (S-P)

Provider who provided the message/data/control Consumer (S-C)

Consumer who consumes the message/data/control Provider/Consumer Complexity : Number of P-C Points

0-5 Simple 5-10 Medium 10-15 Complex


Business Factor: Integration (BFCT-I)

Integration: Integration herein defined as relation among applications under consideration

Application Type Product based (IA-P)

Open Specification : Simple Proprietary : Medium Legacy : Complex

Customer developed (IA-C) Open specification : Simple Proprietary : Medium Legacy : Complex

Integration Type Adapter based or services already in place (IS-A)

0-5 : Simple 6-10 :Medium 10 + :Complex

Customized services to be developed (IS-D) Number of tables and fields define the complexity

» DET :RET Defines the complexityDET :RET Defines the complexity


Weight Factors (Normalization)

Serial No. Component Simple Medium Complex

1 Business Service Workflow-SequentialBSW-S

1 2 3

2 Business Service Workflow-ParallelBSW-P

2 3 5

3 Implementation Service Workflow-sequentialISW-S

1 2 3

4 Implementation Service Workflow-ParallelISW-P

2 3 5

5 Service ProviderS-P

.5 1 1.5

6 Service ConsumerS-C

.5 1 1.5

7 Integration Application – ProductIA-P

1 2 3

8 Integration Application – ConsumerIA-C

2 4 6

9 Integration Services –Adapter 3 6 9

10 Integration Services – DevelopmentIA-D

5 7 10


Technical Factors (TF)

Definition: These are Non-functional requirements of any ESB integration. Most of the time applications take control of these factors:-

Routing Versioning Transformation Messaging Response Time Distributed Orchestration Protocol Transactions AAA


Technical Factors (TF)

These technical factors have degrees of influence between (0-5) and this has to be set to 3 at abinitio to make degree of influence as a multiple of 1, which means no impact on size. As these are set to a max of 5 the maximum percentile impact would be 15 %

TF =(DI*.01)+0.70

Keeping DI at low impacted multiplier is due to the tools availability to cater these requirements.


Derived Formula

SOA/ESB Size= Adjusted BFCT Count=BFCT Count*TF Effort in Person Days =

(Adjusted BFCT Count*Productivity Figure)/8 Hours

Unadjusted BFCT Count= ΣElements Count for a give Complexity*Weight Factor

Σ [Σ(BSW-S)S *WF+(BSW-S)M *WF+(BSW-S)C *WF+Σ (BSW-P)S *WF+(BSW-P)M *WF+(BSW-P)C

*WF+Σ (ISW-S)S *WF+(ISW-S)M *WF+(ISW-S)C *WF+Σ (ISW-P)S *WF+(ISW-P)M *WF+(ISW-P)C

*WF+Σ (S-P)S *WF+(S-P)M *WF+(S-P)C *WF+Σ (S-C) S *WF+(S-C) M *WF+(S-C)C*WF+Σ (IA-P) S*WF+ (IA-P)M*WF+(IA-P)C*WF+ Σ (IA-C)S*WF+ (IA-C)M*WF+ (IA-C)C*WF+Σ (IS-A) S*WF+(IS-A)M*WF+(IS-A)C*WF+ Σ (IS-D) S*WF+ (IS-D)M*WF+(IS-D)C*WF]

Normalized Unadjusted BFCT Count= ΣNormalized Elements Count for a give Complexity*Weight Factor

Σ [Σ(BSW-S)S *WF+(BSW-S)M *WF+(BSW-S)C *WF+Σ (S-P)S *WF+(S-P)M *WF+(S-P)C*WF+Σ (S-C) S *WF+(S-C) M *WF+(S-C)C*WF+ Σ (IA-P) S*WF+ (IA-P)M*WF+(IA-P)C*WF+Σ (IS-A) S*WF+(IS-A)M*WF+(IS-A)C*WF+ Σ (IS-D) S*WF+ (IS-D)M*WF+(IS-D)C*WF]


Template

Microsoft Excel Worksheet


Sample Data

Sl. No Project Planned Effort in PM

%age Variance

1 Project-A 3.53 +12%

2 Project-B 21 -3%

3 Project-C 45.38 -7.28%

4 Project-D 9.21 +14.17%


Summary

UOMUOM

Effort (in UOM)

Estimate Dimensioning

Technical Factor (TF)Business Factors (BFCT)

Effort EstimateRequired

Non-Functional Requirement

Routing Protocol Versioning

Distributed AAA Messaging

Response time Orchestration

Reusability TransactionProcess

Service

Integration

Weight Factor

Adjustment Factors


References

Comparative Analysis of the Software Effort Estimation Models: Jaswinder Kaur, Satwinder Singh, and Karanjeet Singh Kahlon

The Study of the Intelligent Fuzzy Weighted Input Estimation Method Combined with the Experiment Verification :Ming-Hui Lee, Tsung-Chien Chen, Tsu-Ping Yu and Horng-Yuan Jang

Estimation of Commercially Off-The Shelf (COTS) Software:PUsha Divakarla, PJitin Khurana

Cosmic FFP Manual 2003

FPA IFPUG Version 2.0

Use Case Estimation & Weight Factor Considerartion

Applied Numerical Analysis


Acknowledgement

I am thankful to following contributors for preparation of the model.

Amit Bajaj - Sr. Architect

I am thankful to following contributors for review of the model.

Digant Singh Brij Mishra Swaroop Diwakar


Questions


Thanks!!

Aw Esb Soa Estimation 09

Documents

Transcript of Aw Esb Soa Estimation 09