際際滷

際際滷Share a Scribd company logo

Aw Esb Soa Estimation 09

Download as PPT, PDF
Uday K Bhatt
Uday K Bhatt

This document presents a framework for estimating the effort required for Service Oriented Architecture (SOA) and Enterprise Service Bus (ESB) projects. It decomposes SOA/ESB projects into business factors and technical factors. Business factors include processes, services, and integration. Technical factors include non-functional requirements. It assigns complexity weights and degrees of influence to these factors. A derived formula is presented to calculate the adjusted size of the project based on these factors, which can then be used to estimate effort. Sample data from past projects is also shown.

1 of 23
Downloaded 27 times
Estimation Model SOA/ESB Uday Kr. Bhatt Principal Architect Birlasoft 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 Requirements Objective However the estimated effort would vary from Organization to Organization on their respective productivity figure baseline in Organizational Capability Release. 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.
Definition According to Gartner:- An Enterprise Service Bus (ESB) is a new architecture that exploits Web services, messaging middleware, intelligent routing, and transformation. ESBs 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)
Business Factor: Process (BFCT-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
Business Factor: Process (BFCT-P) 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 complexity
Weight Factors (Normalization) 10 7 5 Integration Services Development IA-D 10 9 6 3 Integration Services Adapter 9 6 4 2 Integration Application Consumer IA-C 8 3 2 1 Integration Application Product IA-P 7 1.5 1 .5 Service Consumer S-C 6 1.5 1 .5 Service Provider S-P 5 5 3 2 Implementation Service Workflow-Parallel ISW-P 4 3 2 1 Implementation Service Workflow-sequential ISW-S 3 5 3 2 Business Service Workflow-Parallel BSW-P 2 3 2 1 Business Service Workflow-Sequential BSW-S 1 Complex Medium Simple Component Serial No.
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
Sample Data +14.17% 9.21 Project-D 4 -7.28% 45.38 Project-C 3 -3% 21 Project-B 2 +12% 3.53 Project-A 1 %age Variance Planned Effort in PM Project Sl. No
Summary UOM Effort (in UOM) Estimate Dimensioning Technical Factor (TF) Business Factors (BFCT) Effort Estimate Required Non-Functional Requirement Routing Protocol Versioning Distributed AAA Messaging Response time Orchestration Reusability Transaction Process 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!!

More Related Content

Aw Esb Soa Estimation 09

  • 1. Estimation Model SOA/ESB Uday Kr. Bhatt Principal Architect Birlasoft India Ltd
  • 2. 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
  • 3. Objective Requirements Objective However the estimated effort would vary from Organization to Organization on their respective productivity figure baseline in Organizational Capability Release. 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.
  • 4. Definition According to Gartner:- An Enterprise Service Bus (ESB) is a new architecture that exploits Web services, messaging middleware, intelligent routing, and transformation. ESBs act as a lightweight, ubiquitous integration backbone through which software services and application components flow.
  • 6. 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)
  • 7. 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
  • 8. 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)
  • 9. Business Factor: Process (BFCT-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
  • 10. Business Factor: Process (BFCT-P) 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
  • 11. 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
  • 12. 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 complexity
  • 13. Weight Factors (Normalization) 10 7 5 Integration Services Development IA-D 10 9 6 3 Integration Services Adapter 9 6 4 2 Integration Application Consumer IA-C 8 3 2 1 Integration Application Product IA-P 7 1.5 1 .5 Service Consumer S-C 6 1.5 1 .5 Service Provider S-P 5 5 3 2 Implementation Service Workflow-Parallel ISW-P 4 3 2 1 Implementation Service Workflow-sequential ISW-S 3 5 3 2 Business Service Workflow-Parallel BSW-P 2 3 2 1 Business Service Workflow-Sequential BSW-S 1 Complex Medium Simple Component Serial No.
  • 14. 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
  • 15. 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.
  • 16. 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]
  • 18. Sample Data +14.17% 9.21 Project-D 4 -7.28% 45.38 Project-C 3 -3% 21 Project-B 2 +12% 3.53 Project-A 1 %age Variance Planned Effort in PM Project Sl. No
  • 19. Summary UOM Effort (in UOM) Estimate Dimensioning Technical Factor (TF) Business Factors (BFCT) Effort Estimate Required Non-Functional Requirement Routing Protocol Versioning Distributed AAA Messaging Response time Orchestration Reusability Transaction Process Service Integration Weight Factor Adjustment Factors
  • 20. 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
  • 21. 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