XUS265309567file1_0

download XUS265309567file1_0

of 10

Transcript of XUS265309567file1_0

  • 8/3/2019 XUS265309567file1_0

    1/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 1

    UnderstandingTESTINGESTIMATIONusingUseCaseMetrics

    AloomfortestingEstimation

    Prepared By

    Sanjeev [email protected]

    Date:-08Sept, 2009

    Table of Content:-

    1. PURPOSE

    2. PREAMBLE

    3. Testing Size and Effort Estimation using UCP

    3.1 Size Estimation3.1.1 Actor Weight [AW]3.1.2 Use Case Weight [UCW]3.1.3 Unadjusted Use Case Points [UUCP]3.1.4 Technical Complexity Factor [TCF]3.1.5 Environmental Complexity Factor [ECF]3.1.6 Calculate Final Use Case Points [UCP]

    3.2 Effort Estimation3.2.1 Conversion Factor3.2.2 Calculating Final Effort

    4. BENEFITS

    5. CASE STUDY

    6. REFERENCES

  • 8/3/2019 XUS265309567file1_0

    2/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 2

    1.Purpose: ThepurposeofthispaperistoexplainanewapproachtotheestimationofsoftwaretestingeffortsbasedonUseCasePoints[UCP]asafundamentalprojectestimationmeasure.Object

    orientedapplicationsfrequentlyrelyonUseCasestodescribethebusinessprocessesofasoftware

    application.

    Thismethodologyforestimationisinfactmorereliablethanfunctionalpoint[FP].Itworksonthebasic

    principlethat

    more

    the

    complexity

    of

    the

    use

    case

    more

    is

    the

    time

    taken

    to

    design,

    develop,

    test

    and

    implement.ThecaveathereisthattheVmodelmustbeinuseandusecasegenerationmuststart

    becomingavailablerightattherequirementsgatheringphase.Thispaperprovidesthestepswisetesting

    estimationprocessusingtheUseCasePoint[UCP].

    2.Preamble: EstimationeffortforSoftwaretestingisoneofthemostimportantfacetsofthe

    entiretestinglifecycleasitisdirectlyproportionaltothecostoftheproject.Estimationhasgreat

    impactonallthemostimportantaspectsofacustomerexpectationTime,CostandQuality.Acorrect

    estimationhelps

    in

    delivering

    the

    products

    at

    right

    time.

    If

    estimation

    is

    wrong

    it

    might

    lead

    to

    unwanteddelayindeliverables,increasedcostandinappropriateresults.

    ThereareseveralmethodsavailablefortestingestimationlikeTestCasePoints,FunctionPointetc.Use

    Casemethodologyisgainingfarabovethegroundpopularityforestimatingsoftwareeffort.Itcouldbe

    veryusefulincaseofbiddingprojectsastheusecasesareoneofthefirstorsometimestheonly

    informationavailableinthebeginningofasoftwareproject.

    Whyestimate?

    Youcannotplanifyoucannotmeasure,andifyoufailtoplan,youhaveplannedtofail.Anomelet,promisedintwominutes,mayappeartobeprogressingnicely.Butwhenithasnotsetin

    twominutes,thecustomerhastwochoices

    Eitherwait&eat(or)eatitraw!Ifthecustomerdoesnotwanttoeatitrawaswellashedoesnotwanttowait,thenthecookhastoo

    hasachoice hecanturntheheatonand

    Gettheomeletburntinonepartandrawinanother!Insoftwareindustrycustomers&vendorshavealsothesamechoices.Onemostimportantfactor

    thatrequiresconsiderationissettingtheexpectationsrightupfront.Thiscanbedonefirstby

    gettingtheestimationright.

    3.EffortEstimationusingUCP:

    3.1 Size Estimation:-TheFirststepforeverytypeofestimationistocalculatethesizeofactivitytobeperformed.InUsecase

    methodology,thereare4majorcomponentswhichareimportantfordeterminingthesizeofaproject

  • 8/3/2019 XUS265309567file1_0

    3/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 3

    1.ActorWeight[AW]

    2.UseCaseWeight[UCW]

    3.TechnicalcomplexityFactors[TCF]

    4.EnvironmentalcomplexityFactors[ECF]

    3.1.1 Actor Weight [AW]:-

    TheActorWeight[AW]isclassifiedinto3differenttypes Simple,MediumandComplex.FigureAdescribesthecriteriaforeachtypeandalsothefactor(weightage)ornumericvalues.

    ThetotalActorweightcanbecalculatedbycategorizingalltheactorsassimple,mediumandcomplex

    andthenaddingupallthefactors(weightage).

    FigureA

    ActorWeight

    WeightageType Factor(Weightage) Criteria/Description

    Simple 1 Representsanothersystemwith

    definedapplicationprogramming

    interface(API)

    Medium 2 TheActorrepresentsanother

    systeminteractingthrougha

    protocol,likeTCP/IP.Oraperson

    interactingthroughatextbased

    interface.

    Complex

    3

    Canbe

    aperson

    interacting

    via

    an

    interface(GUI)

    3.1.2 Use Case Weight [UCW]:

    UsagecaseweightcanbecalculatedinthesamewayasActorweightiscalculated.Alltheusecasesneedtobecategorizedassimple,mediumandcomplex.Thefinalweightisthesumofthefactorsforall

    thecategorizedusecases(SeeFigureB).Keepinmindthenumberofstepsinascenarioaffectstheestimate.Alargenumberofstepsinause

    casescenariowillbiastheUCWtowardcomplexityandincreasetheUCPs.

  • 8/3/2019 XUS265309567file1_0

    4/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 4

    FigureB

    UseCaseWeight

    WeightageType Factor(Weightage) Criteria/Description

    Simple

    5

    Verysimple

    interface,

    which

    touchesasingledatabaseentity,

    having3orlessertransitions/steps

    Medium 10 Moreinterface,whichtouchestwo

    ormoredatabaseentities,having

    47transitions/steps

    Complex 15 Verycomplexinterface,which

    touchesthreeormoredatabase

    entities,havingmorethan7

    transactions/steps

    3.1.3 Unadjusted Use Case Points (UUCP):

    UUCP = Actor Weight [AW] + Use Case Weight [UCW]

    3.1.4 Technical Complexity Factor [TCF]:

    Therearemainly7standardswhichimpactstheoverallestimationforaproject.TheFigureCshowsthelistofallthefactorsfromtestingperspectivewiththeirWeightage.Theweightofatechnicalfactor

    indicatesitsimpactontheoverallestimation.Technicalfactorsareevaluatedbythedevelopmentteam

    andassigneda valuebetweenzeroandfive.Aweightof0indicatesthefactorisirrelevantandthe

    value5means

    that

    the

    factor

    has

    the

    most

    impact.

    Technicalcomplexityfactoriscalculatedasbelow

    TCF = C1 + C2*(Total TF)

    AspertheUseCasePointmethod,theimpactofTCFonusecasepointsshouldvaryfromrangeof0.6

    (40%reduction)to1.3(30%increase).InordertoachievethisrangethecoefficientC2needstobe

    modifiedfortheTestingEffort.

    C2fortesting=(1.30.6)/50=0.014

    Where50isthemaxvalueofTCFfortesting.

    Where,

    C1=Constantwithvalue0.6

    C2=Constantwithvalue0.014

    TotalEF=TotalTechnicalFactor

  • 8/3/2019 XUS265309567file1_0

    5/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 5

    FigureC

    TechnicalFactors

    S.No Value(Weightage) Criteria/Description

    1

    2

    Test

    Tools.

    2 2 DocumentInputs

    3 1 TestwareReuse

    4 2 DistributedSystem

    5 1 PerformanceObjectives

    6 1 SecurityFeatures

    7

    1

    ComplexInterfacing

    3.1.5 Environmental Complexity Factor [ECF]:

    Thereare7environmentalfactorswhichimpactstheoverallestimationforaproject.The

    FigureDshowsthelistofallthefactorsfromtestingperspectivewiththeirWeight.Aratingof0meanstheenvironmentalfactorisirrelevantforthisproject;3isaverage;5meanithasstronginfluence.The

    weightofatechnicalfactorindicatesitsimpactontheoverallestimation.

    Environmentalcomplexity

    factor

    is

    calculated

    as

    below

    ECF = C1 + C2*(Total EF)

    AspertheUseCasePointmethod,theimpactofECFonusecasepointsismorethanTCFanditshould

    varyfromrangeof0.0425(57.5%reduction)to1.4(40%increase).Inordertoachievethisrangethe

    coefficientC2needstobemodifiedfortheTestingEffort.

    C2fortesting=(1.40.0425)/37.5=0.0362

    Where37.5

    is

    the

    max

    value

    of

    ECF

    for

    testing

    Where,

    C1=Constantwithvalue1.4

    C2=Constantwithvalue(0.0362)

    TotalEF=TotalEnvironmentalFactor

  • 8/3/2019 XUS265309567file1_0

    6/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 6

    FigureD

    EnvironmentalComplexity Factors

    S.No

    Value(Weightage) Criteria/Description

    1 1 ApplicationKnowledge

    2 2 TestEnvironment

    3 1 TestData

    4 0.5 TestLeadCapability

    5 1 Motivation

    6

    2

    StableRequirements

    7 1 PartTimeWorkers

    3.1.6 Calculate Final Use Case Points (UCP):-

    UCP = UUCP*TCF*ECF

    3.2 Effort Estimation:-

    3.2.1 Conversion Factor (CF):-

    TheConversionFactor(CF)isaratioofthenumberofmanhoursperusecasepointbasedonpast

    projects.OncethesizeofaprojecthasbeencalculatedintermsofAdjustedUseCasePoints,thetotal

    sizeneedstobeconvertedtoeffortbymultiplyingitwithaConversionfactor.TheConversionfactor

    (Effort/Size)isdefinedasthetotaltestingtimerequiredtotestoneUseCasePoint.

    TheConversionfactorcanbederivedbyreverseengineeringtechniquei.e.byputtingthehistorical

    projectdataintheestimationtemplatefordifferenttechnologies.Itis20(hrs)forJavabased

    applications.Ifnohistoricaldatahasbeencollected,afigurebetween15and30issuggestedby

    industryexperts.

  • 8/3/2019 XUS265309567file1_0

    7/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 7

    3.2.2 Calculating Final Effort:-

    Final Effort = UCP * Conversion factor

    4. Benefits of Use Case Point methodology:-

    1.Thisscientificmethodgivesmoreaccurateandpreciseresultsoveranytraditionalmethodavailable

    foreffortestimation.

    2.Noanydetailrequirementsarerequiredforestimation.

    3.Thismethodisverywellsuitedforbiddingprojectsasmostofthetimeusecaseistheonly

    informationavailableatthebeginningofaproject.

    4.TheUseCasepointmethodconsidersthetechnicalandenvironmentalfactorswhichcanberefined

    furthertoachievemoreaccurateestimates.

    5.Thiscanbeusedtoillustrateproductivitybenchmarksacrossanorganizationsinceitisindependent

    oftestcases.

    5. Case Study:-

    5.1 Actor Weight [AW]:-

    ActorWeight

    S.No ActorName Weight ageType Factor

    1 Actor1 Simple 1

    2 Actor2 Medium 2

    3

    Actor3

    Complex

    3

    4 Actor4 Simple 1

    5 Actor5 Medium 2

    Total 9

  • 8/3/2019 XUS265309567file1_0

    8/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 8

    5.2 Use Case Weight [UCW]:-

    UseCase Weight

    S.No

    Use

    Case

    DescriptionWeight

    age

    Type Factor

    1 UseCase1 Simple 5

    2 UseCase2 Medium 10

    3 UseCase3 Complex 15

    4 UseCase4 Simple 5

    5 UseCase5 Medium 10

    Total 45

    5.3 Unadjusted Use Case Points (UUCP):-

    UUCP = AW + UCW= 9 + 45 = 54

    5.4 Technical Complexity Factor Calculation [TCF]:-

    TechnicalFactors

    S.No Description Weightage Perceived

    Complexity

    CalculatedFactor

    1 TestTools 2 1 2

    2 DocumentInputs 2 2 4

    3 Testwarereuse 1 3 3

    4 DistributedSystem 2 4 8

    5

    Performance

    Objectives

    1

    5

    5

    6 SecurityFeatures 1 1 1

    7 ComplexInterfacing 1 3 3

    Total Factor 26

  • 8/3/2019 XUS265309567file1_0

    9/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 9

    TCF = C1 + C2*Total TF= 0.6 + (0.014)*26= 0.96

    Aperceivedcomplexityof0meansthetechnicalfactorisirrelevantfortheproject;3isaverage;5

    meansithasstronginfluence.

    Eachfactorsweightismultipliedbyitsperceivedcomplexitytoproduceitscalculatedfactor.The

    calculatedfactorsaresummedtoproducetheTotalFactor.

    5.5 Environmental Complexity Factor Calculation [ECF]:-

    Environmental Factors

    S.No Description Weightage Perceived

    Complexity

    CalculatedFactor

    1 Application

    Knowledge

    1 5 5

    2 TestEnvironment 2 3 6

    3 TestData 1 1 1

    4 TestLeadCapability 0.5 1 0.5

    5 Motivation 1 5 5

    6 StableRequirements 2 2 4

    7 PartTimeWorkers 1 2 2

    Total Factor 19.5

    ECF = C1 + C2*Total EF= 1.14 + (-0.0362)*19.5= 0.43

  • 8/3/2019 XUS265309567file1_0

    10/10

    Understanding TESTING ESTIMATION using Use Case Metrics Page 10

    5.6 Calculate Final Use Case Points (UCP):-

    UCP = UUCP*TCF*ECF= 54*0.96*0.43= 22.29

    5.7 Calculating Final Effort:-

    Final Effort = UCP * Conversion factor

    Final Effort (Hrs) = UCP*20 = 22.29*20 = 445.8

    6. References:-

    http://www.codeproject.com/KB/architecture/usecasep.aspxhttp://www.stsc.hill.af.mil/crosstalk/2006/02/0602Clemmons.pdf

    astitchintimessavesnine