Metric Wise (Analyze, Understand)

Size: px

Start display at page:

Download "Metric Wise (Analyze, Understand)"

Claribel Pearson
6 years ago
Views:

1 The Joint 13 th CSI/IFPUG International Software Measurement & Analysis (ISMA13) Conference Mumbai (India) March 6, 2017 [Sysmetry] [Integrated FPA & [Krupananda Babu M] Metric Wise (Analyze, Understand)

2 Goals of the presentation G1. Business need of Software Size G2. Sysmetry - Introduction & Overview G3. Sysmetry Measuring Data Functions G4. Sysmetry Measuring Transaction Functions G5. Sysmetry Measuring Application/Project DPs 2

3 [Basic Project Measurements] Four Basic Measurements: Size Effort Schedule/Duration Defects/Quality The later three are relatively easier to measure. But arriving at an appropriate software size in not a straight forward job. 3

[Software Sizing needs different approach] For

applicable to all physical products, nor is as

4 [Software Sizing needs different approach] For software development size there has been no established and accepted unit of measurement like there are for weight, length, volume among others, applicable to all physical products, nor is as intuitive as number of requests serviced in a period of time. 4

[Business Need for Softwar Size] Business need of Software Size: To know how much effort will be needed so that a duration/schedule can be agreed upon along with expected number of defects To compare

5 [Business Need for Softwar Size] Business need of Software Size: To know how much effort will be needed so that a duration/schedule can be agreed upon along with expected number of defects To compare project s (team s) performance vis-à-vis expected. Example: Vendor/Internal team evaluation To know the Total Cost of Ownership of software applications In above all the need is more to know what it takes to develop software than to know how it benefits the user. 5

6 [Non-Functional Sizing Need] Function points served this purpose but were found not to correlate well with effort required to develop software as they were more oriented towards measuring the value as seen by users. With the advent of SNAP those areas which were not covered by FPA have become measurable, but the two sizes FPs and SPs pose some challenges with respect to productivity analysis and metrics base-lining. 6

7 [Sysmetry Introduction] This methodology measures all the aspects of software development, so the entire set of requirements is measured to provide a holistic size measurement. In this methodology the term Functionality is understood in its common perception as that which works to accomplish some purpose (logical or technical) and non-functionality simply means that which does not work as something becoming non-functional in a system. Also it is viewed that all functionality is implemented by some technicality, and all technicalities exist to support some functionality. 7

8 [Sysmetry Overview] A software application is viewed as information processing management system. In rudimentary form, a software application is deemed to have two basic components: 1. Data and 2. Transactions We measure both data and transactions considering two aspects: 1. Logical 2. Technical The measurement unit is called Development Point (DP). 8

9 [Sysmetry Method Steps] The steps to be followed are: 1. Identify and document the Purpose and Scope 2. Identify and document the relevant Users 3. Identify and document Sources of Information 4. Draw or Re-draw the Boundar(ies)y 5. Measure Data DPs 6. Measure Transaction DPs 7. Measure Application/Project level DPs 8. Calculate Total DPs Note: All calculations have to be rounded off to the nearest natural number. 9

10 [Measuring Data DPs - Brief] Data is (are) the documented fact(s) about business entities that are needed to be stored and maintained in the software applications to address required business information needs. Examples: tables, text files, XMLs, FLists, and Spread sheets etc. called generically as Data Files (DFs). Only data files internal to the application are measured. External data used in the application s transactions are accounted for in the respective transactions that interface with other applications. Another aspect that is measured is the data loading (DLD) that is needed at the inception and enhancement of software applications. 10

11 [Measuring Data DPs - Classification] Data is further classified as: Logical Data File (LDF): This includes all the Business data and Reference data (dynamic and static) which are primary from the business perspective and this is the data for which the application exists, to store and process as required by the end user. Examples: Customer Data, Billing Information, Tax Rates etc. Technical Data File (TDF): This is the data that the end user usually is not aware of. This data is needed to support the execution of the application in storing and/or processing the logical data. Examples: Temporary data stores, Views, Indexes, Staging tables etc. 11

12 [Measuring Data DPs Technical Data Files] Technical files such as Views, Indexes draw data from some source data files, each such source file is called and counted as one Source Files (SOFs). Rule 1: Count at least one SOF for each Technical Data function. Rule 2: Count one additional SOF for each additional LDF or TDF from which data is retrieved. 12

13 [Measuring Data DPs Calculation of LDF] The formula for calculating Logical Data size is: LDF DPs = ((1/20) X DETs) + (2 X RETs) Example 1: LDF: Employee Data File No. of DETs: 155 No. of RETs: 8 DPs = ((1/20) X 156) + (2 X 8) = 8+16 =24 DPs Example 2: LDF: Trainee Details File No. of DETs: 3 No. of RETs: 1 DPs = ((1/20) X 3) + (2 X 1) = 1+2 = 3 DPs 13

14 [Measuring Data DPs Calculation of TDF] The formula for calculating Technical Data size is: TDF DPs = ((1/25) X DETs) + SOFs Example 1: TDF: Materialized View Employee Leave Info DETs: 64 SOFs: 2 Size of TDF = ((1/25) X 64) + 2 = 3+ 2 = 5 DPs Example 2: TDF: Materialized View Bundle Offer Info DETs: 11 SOFs: 1 Size of TDF = ((1/25) X 11) + 1 = 1+1 = 2 DPs 14

15 [Measuring Data DPs Calculation of DLD] The formula for calculating DLD DPs is: DLD DPs = ((1/25) X DETs) + (2 X SOLs) Example: Data from existing Payroll application and HR Info application are to be ported to a newly developed HR Management application. DETs: 235 SOLs: 3 DLD DPs = ((1/25) X 250) + (2 X 3) = = 16 DPs 15

16 [Measuring Data DPs Calculation of Total DFs] The formula for total data function DPs is: Total Data DPs = LDF DPs + TDF DPs + DLD DPs 16

17 [Measuring Transaction DPs - Brief] Transactions are the interactions that happen with software applications. They carry data in and out of the software application boundary and perform information processing to satisfy certain business information needs. Apart from data carried the transactions inherently have certain logical processing and technical processing which contribute to their complexity and software development teams spend significant effort in this regard. 17

18 [Measuring Transaction DPs Logical Processing Complexity (LPC) Part 1] S.no Processing Logic Complexity Parameters Logical Complexity formula 1 Data Receipt Number of DETs received 1/10 X DETs 2 Data Validation 1) Number of DETs validated (1/5) X DETs) 1) Number of DETs used for 3 Mathematical Calculations operations calculation (1/2) X DETs) + (2 X No.of 2) Number of mathematical Operations) 4 Data conversion 1) Number of DETs converted (1/30) X DETs 5 Criteria based data filtering Number of filter criterion (1/3) X No.of Filter Criterion 6 Condition Analysis 1) Number of DETs analyzed (1/5) X DETs + (2 X No.of 2) Number of conditions analyzed Conditions) 7 Data updated in LDF(s)/TDF(s) 1) Number of DETs updated ((1/10) X DETs) + (No.of LDFs 2) Number of LDFs/TDFs updated and TDFs updated) 8 Data retrieved from 1) Number of DETs retrieved ((1/10) X DETs) + (No.of LDFs LDF(s)/TDF(s) 2) Number of LDFs referenced and TDFs referenced) 18

19 [Measuring Transaction DPs Logical Processing Complexity (LPC) Part 2] S.no Processing Logic Complexity Parameters Logical Complexity formula 9 Derived Data creation Number of DETs used for derivation and the derived DETs (1/3) X DETs 10 Application behavior altered Not applicable 3 11 Data is sent out of the application 1) Number of DETs sent out ((1/5) X DETs) + No.of LDFs or 2) Number of LDFs/TDFs referenced TDFs referenced 12 Data is sorted or re-arranged Not applicable 2 13 Data is fetched from another 1) Number of DETs fetched ((1/3) X DETs) + (2 X No.of application 2) Number of applications interfaced applications interfaced) 14 Internal Data Movements Number of DETs internally moved ((1/10) X DETs) + (No.of Number of LDFs referenced LDFs/TDFs referenced) 15 Data configuration 1) Number of DETs configured ((1/10) X DETs) +( (1/10) X No.of 2) Number of records configured records) 16 Data Encryption/Decryption 1) Number 0f DETs encrypted/decrypted 1/15 x DETs Processing Logic Complexity (PLC) of a Transaction is the sum of all the applicable items listed above. 19

20 [Measuring Transaction DPs Technical Processing Complexity (TPC)] S.no Technical aspect Complexity Parameters Technical Complexity formula 1 1) Number of UI elements No.of UI elements X (1/10) + User Interface elements 2) Number of properties No.of properties 2 1) Number of DETs input ((1/3) X DETs) + No.of input Multiple Input methods 2) Number of input methods methods 3 1) Number of DETs input ((1/2) X DETs)) + No.of output Multiple Output methods 2) Number of output methods methods) Technical Processing Complexity of a Transaction is the sum of all the applicable items listed above. 20

21 [Measuring Transaction DPs - Calculation] The formula for calculating total transaction DPs is: Transaction DPs = ((1/3) X LPC) + ((1/10) X TPC) 21

22 [Measuring Transaction DPs Example 1] Example 1: A Transaction is developed to enter product details of 28 DETs into the Inventory Management System application via mobile device and through computer screen, inserts 25 DETs into Inventory Items Info LDF and 11 DETs into Purchase Details Info LDF having. Total UI elements on the screens involved are 42 and an average 5 properties are to be configured. No. of DETs: 28 LPC Calculation: Items 1 and 7 from LPC table are applicable. Data Receipt PL = ((1/10) X 28) = 3 Data Updated PL = ((1/10) X 28) + 2 = = 5 LPC = 8 TPC Calculation: Items 1 and 2 from table 2 are applicable User Interface elements TP = 42 X (1/10) + 5 = 9 Multiple Input Methods TP = (1/3) = 11 Technical Processing Complexity = =20 Transaction DPs = ((1/3) X 9) + ((1/10) X 20) = = 5 DPs 22

23 [Measuring Transaction DPs Example 2] Example 2: A Transaction is created in Order Provisioning application which accepts 13 DETs via 3 screens with 18 UI elements of 3 properties (the same data entry is also possible through an excel sheet and screen scraping from CRM application); validates 2 DETs from Resource Info LDF availability and 1 DET from CRM application; retrieves 8 DETs of cost details from Product Info LDF and Offers Info LDF; fetch billing details from CRM application; calculates the approximate cost using 4 mathematical operations; converts the cost from local currency into USD and round off; then chooses the appropriate delivery mechanism and route from available 3 options; update 17 DETS of delivery details in Delivery Info LDF after creating a unique delivery code from order number, customer and date; move 25 DETs from Order details LDF to Provisioned Details Info LDF, sends 47 DETs in Excel and PDF formats to Billing & Rating application from Product Info LDF and Order Info LDF and 22 DETs to Customer Loyalty application from Order Info LDF. 23

24 [Measuring Transaction DPs Example 2] No. of DETS: 82 LPC Calculation: Items 1, 2, 3, 4,6, 7, 8, 9, 11 and 14 from LPC table are applicable. Data Receipt LP = (1/10) X 13 = 1 Validation 1 LP = (1/5) X 2 =1 Validation 2 counted as Data fetch from other application LP = (1/5) X 1 =1 Data Retrieval LP = ((1/10) X 8) + (2) = = 3 Calculation LP = (1/2) X 8) + (2 X 4) = = 12 Data conversion LP = (1/30) X 1 = 1 Condition Analysis LP = (1/5) X 2 + (2 X 3) = = 7 Data Update LP = ((1/10) X 17) + (1) = Create Derived Data LP = (1/3) X 3 = 1 Data sent out 1 LP = ((1/5) X 47) + (2) = = 11 Data sent out 2 LP = ((1/5) X 22) + (1) = 4 +1 = 5 Internal data movements = ((1/10) X 25) + 2 = = 5 Total LPC = 49 TLC Calculation: UI Elements TP = (18 X (1/10)) + 3 = 5 Multiple Input Methods TP = ((1/3) X 13) + 3 = 7 Multiple Output Methods TP = ((1/2) X 47) + 2 = 26 Total TPC = 38 Transaction DPs = ((1/3) X49) + ((1/10) X 38) = = 20 DPs 24

25 [Application/Project (Common) DPs] Some requirements and project activities pertain to an entire software application or a project. S.No Aspect Parameter(s) Complexity Formula 1 Technology used 1) Number of Software Platforms 2) Number of Software families 2 Environment setup 1) Number of Roles 2) Number of Members (5 X No.of platforms) + (3 X No.of families) (3 X No. of Roles) + (1/25) X No.of Members 25

26 [Calculate Total DPs] The formula for calculating total DPs is:- Total DPs = Total Data DPs + Transactions DPs + Common DPs 26

27 Q & A 27

28 Thank You 28

E s timation of effort using F unction Points

E s timation of effort using F unction Points -Vijay S hankar Vijay Shankar Cognizant Technology Solutions, Feb 2003. All rights reserved. You may make one attributed copy of this material for your own