Making earth little softerEarthsoft Foundation of GuidanceEdge-Aggressive-Reliable-Trust-Honesty-Soft-Obedient-Fun-Transpa...
Making earth little softerEarthsoft Foundation of Guidance (EFG) has uploaded followingpresentations at http://myefg.in/do...
Making earth little softer• Organisation• Quality• Quality management• Quality Assurance• Quality Control• Processes• Case...
Making earth little softerIndex
Making earth little softerQuality Control
Making earth little softerProject RAG StatusNOTE: Pl update the RAG status from spectrumfor last 4 weeks. If any of the pa...
Making earth little softer• Functionality related gap between expectationsof client and actual delivery• Defects are injec...
Making earth little softerReviews• Review helps• To confirm client’s requirements• To detect defects in early stages• To r...
Making earth little softerRA Design Coding UT IT ATDefectsinsystemVarious Phases of SDLCTo be at better quality after ever...
Making earth little softerTeam structure & reviewsPMOReviewsPMOReviewsReviews of deliverables of each member at everylevel...
Making earth little softerReviews• Assuring:-• Quality of design document impacts quality ofthe code & the test cases.• To...
Making earth little softerReviews• Deciding on review density before starting theactivity• Review comments expected to red...
Making earth little softerCode reviews• Build detailed code checks into the developmentprocess• Make it impossible to rele...
Making earth little softerPerformance testing• Execute to check performance of each query• Create database as appropriate•...
Making earth little softerIssue Management• Issues are restraints to accomplishing thedeliverables of the project.• Typica...
Making earth little softerIssues/Risks (non-financial)Highlight highest risks for management attention
Making earth little softerMetrics-Development & EnhancementNOTE: Pl highlight the summary from themetrics reportWorkPacket...
Making earth little softerMetrics-Maintenance & SupportProvide the SLA compliance summary If you useany tool provide the s...
Making earth little softer• The perceptions of the user determine thepurpose. Quality therefore is a user perception.• Cor...
Making earth little softerTesting Improvements• PM decides on type of testing - automated ormanual or both• 400% increase ...
Making earth little softerPrerequisites of TestingTest Cases• Latest & Completed test cases documents fromCVS (or any Conf...
Making earth little softerFlow of Testing• Test cases• Test Data• Unit Testing• Screen Layout, look & feel• Screen Validat...
Making earth little softerTesting GuidelinesWhy the testing guidelines?• “Test cases may not cover 100% aspects thusextend...
Making earth little softerWho should testThere are 2 possible actors• Developers to execute 100% unit testing• Reasons bei...
Making earth little softerUnit Testing - UITo use a check list & test for following• Consistency- Control sizes• Basic fun...
Making earth little softerUnit Testing - UI• Tab sequence & Text selection• Links (Check each link to ensure it works)• Cu...
Making earth little softerUnit Testing - Validations• Field type & Size (Numeric, Alphanumerical,Database field width)• Fo...
Making earth little softerUnit Testing - FunctionalityTo use matrix of screens & functionalitiese.g. File Upload/Download•...
Making earth little softerUnit Testing - FunctionalityTo use matrix of screens & functionalities•Test User login Case Sens...
Making earth little softerIntegration Testing• Refer Integration Matrix while testing• Enter boundary values (Min , Max, 0...
Making earth little softer• Testing Business Transactions• Refer Screen Flow Diagrams while identifyingBusiness Transactio...
Making earth little softer• Application Menu should be in sequence of thefunctionality• User Management->Master Data Mgt->...
Making earth little softer• Perform transaction using multiple instances ofapplication, Open other applications like (Word...
Making earth little softer• Copy Paste of the URLs• Copy URL after Logging in and paste it inanother instance of browser• ...
Making earth little softer• Reports printing• Print Multiple Pages• Try to print without installing any printer driver• Ve...
Making earth little softerHow Much Testing Is Enough?• There is always one more bug…• So how much testing is needed to fin...
Making earth little softerTypes of defects• Blocker• Severe/ Critical• Major• Normal• Minor• Trivial• To publish phase wis...
Making earth little softerUpdate defect passbook at end of day and checkstatus and trendDefect passbook
Making earth little softerConfidential 41QAG measures QualityQAG tracks and measures quality using followingtemplateOrgani...
Making earth little softerQuality measurementNo. of defects 1effort in manmonths 3Loc per hr 10Lines of code 4800no. of de...
Making earth little softerMeasure where are you• To set a quality baseline & remain determined• To seek feedback• To measu...
Making earth little softerAim for Defect Metrics (sample)Phase Metrics UnitLowerLimitAverageUpperLimitRequirementdefinitio...
Making earth little softerBug content analysisPhenomenon Action exampleModule havingmajor changeSuspend test workReview of...
Making earth little softerBug content analysisPhenomenon Action exampleBug causeProblem ofdefectivespecificationRe-check s...
Making earth little softerBug content analysisOccurrence type Action exampleOperational error,without reproduction,identif...
Making earth little softer• No. of pages/ characters of design document &LOC of the code• Check planned No. of test cases ...
Making earth little softer•Check the pending test cases on daily &cumulative basis – check if volume is apt•Bug fixing on ...
Making earth little softerQuantitative analysis# Category Details Type1 SpecificationInadequacyDescription Inadequacy Inte...
Making earth little softer• Root cause analysis – assign root cause toeach bug & conduct analysis (fishbone diagram)• Seve...
Making earth little softerProcess• This PCB is released as Organization PCB• This PCB should be referred to when providing...
Making earth little softerPCB Contents• Productivity Data• Phase wise effort distribution• Effort – Actual Vs. Estimated• ...
Making earth little softerProductivity DataLOC/ 1 MMProductivity LCL Target UCLJava 700 1000 1300VB.Net 800 1500 2200C# .n...
Making earth little softerPlan to Collect Data• PCB shall be updated every three months, Endof every quarter - Jun, Sep, D...
Making earth little softerProject ClosureTo conduct a meeting with all stake holdersTo share following information estimat...
Making earth little softerThank YouAuthor has worked at as Sr management professionalVertex Software, now NTTDataTech Mahi...
Upcoming SlideShare
Loading in …5
×

2 earthsoft-quality control in software organidation

487
-1

Published on

"Earthsoft Foundation of Guidance (EFG) is working as an NGO/NPO for students - Education & Career
guidance and for Professionals for soft skills enhancements. I am working on speading , sharing
knowledge; experience globally.It has uploaded important presentations at http://myefg.in/downloads.aspx.
Also https://dl.dropbox.com/u/83265908/Links-events.xls has links for all ppt files.

Read http://tl.gd/jm1gh5

Be mentor using your education, knowledge & experience to contribute for a social cause & do conduct
free training/ workshop seeking help of existing platforms like rotary,etc
Kindly spread to your friends.Thank you!
- Earthsoft Foundation of Guidance
Let us make earth little softer..
"

Published in: Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
487
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 04/22/13
  • Above processes remove the defects
  • Reviews at each phase during SDLC removes the defects and quality improves
  • Global Standards Compliance Checker - GSCC 250+ detailed code checks Built into the development process Impossible to release code that violates these checks Started with 11i6, previously, these errors were only discovered by code reviews or testing Many errors only occurred on specific datasets Automatic Generation of Patch Database (DB) Drivers DB driver is portion of patch that updates schema, seed data and pl/sql DB driver errors accounted for ~20% of patch install errors Started with 11i6, previously these were manually coded, which was extremely complex and error prone
  • Automated Performance Analyzer Every SQL statement (~280,000) is run against multiple (5) real world customer databases Worst case Explain plan is analyzed Bugs automatically logged for worst performing statements This activity performed every month Fixes consolidated into next release Critical issues fixed as one-off fixes ~1,500 issues fixed monthly Started with 11i5, previously these were only caught by performance testing Database group uses this on new versions of the database 100+ bugs fixed prior to release of 9iR2
  • Issues not easily resolved are escalated for resolution. Issues are typically identified throughout the project and logged and tracked through resolution. In this section of the plan the following processes are depicted: Where issues will be maintained and tracked The process for updating issues regularly The escalation process The vehicle by which team members can access documented issues Issue… already impacting the cost, time or quality   Risk… POTENTIAL negative impact to project
  • 04/22/13
  • 04/22/13
  • 04/22/13
  • Software Requirements: 8 Traps to Avoid
  • Software Requirements: 8 Traps to Avoid
  • Following factors make the quality software
  • 400% increase in automated regression tests, Tests created for all key business flows Created by dedicated product QA teams All products now have RTs Used for Ongoing maintenance/bug fixes Platform certification (e.g. Linux) Technology certifications (e.g. 9iR2) eBusiness Flows certified prior to release With 11i7, 60+ Oracle consultants worked for 2 months to pre certify Oracle implementation flows Progress measured daily, and reported to executive management
  • (By changing system dates) After server side validations such as "Duplicate ID Check", retry entering valid data and save Read only fields Test (press enter key or click to verify that no unexpected events are getting fired)
  • Business Transactions – HKK Topacs Screen Flow Diagrams Hakkai ERP Application Testing Hakkai ERP Application Testing
  • “ There is always one more bug.” The amount of testing needed to ensure quality is hard to quantify. Very few project teams are able – or are willing – to predict how many bugs there will be in a release. Testing and fixing until all bugs have been found would be a very expensive task, if it were possible. And is it reasonable? Most organizations prefer to deliver a product on time, with a few unimportant defects, rather than to deliver it six months late. Needless to say, each industry has a different level of acceptable quality, for instance, word processors versus aircraft systems. In order to provide correct budget and schedule estimates, QA managers need the means to predict fault levels.
  • For translation projects
  • 2 earthsoft-quality control in software organidation

    1. 1. Making earth little softerEarthsoft Foundation of GuidanceEdge-Aggressive-Reliable-Trust-Honesty-Soft-Obedient-Fun-Transparent
    2. 2. Making earth little softerEarthsoft Foundation of Guidance (EFG) has uploaded followingpresentations at http://myefg.in/downloads.aspxBe mentor using your education, knowledge & experience tocontribute for a social cause & do conduct free training seekinghelp of existing platforms. Kindly share with your friends•Motivation for higher study, Planning for study, Educationguidance, Career guidance, Career available after SSC & HSC•Personality development – 3 files•How to prepare resume, Tips to attend interview successfully•Religion related –To understand basic religion, Do & Don’t tips•Health related - Be vegetarian, Be healthy, Manage health•Corporate - Project management, Assertiveness, Ownership,Effective communication, Leadership, Be entrepreneur•Finance - To avoid speculation in stock market•Social - Women empowerment, Choosing life partner, conflictresolution, stop ragging, stop alcohol, snakebite treatmentAbout us
    3. 3. Making earth little softer• Organisation• Quality• Quality management• Quality Assurance• Quality Control• Processes• Case studies experience• Strategic Quality PlanningIndex
    4. 4. Making earth little softerIndex
    5. 5. Making earth little softerQuality Control
    6. 6. Making earth little softerProject RAG StatusNOTE: Pl update the RAG status from spectrumfor last 4 weeks. If any of the parameter is Red /Amber, pl update the action required and statusfor the current week.Parameter LastWeek -1LastWeekCurrentWeekActionRequiredStatus TargetDateBudgetScopeEffortScheduleResourceQuality
    7. 7. Making earth little softer• Functionality related gap between expectationsof client and actual delivery• Defects are injected during Requirementanalysis, High & Low level Design and codingphase.• Continuous reviews help to prevent/ removedefect injection• Rigorous testing during Unit level, Integrationand application level testing detect the defects.RA R DesignR Coding R UT IT ATAchieving Quality
    8. 8. Making earth little softerReviews• Review helps• To confirm client’s requirements• To detect defects in early stages• To reduce rework at later phases
    9. 9. Making earth little softerRA Design Coding UT IT ATDefectsinsystemVarious Phases of SDLCTo be at better quality after every phase• Removing defects by reviewing & testing• From each deliverable• At each phaseReviews & Testing
    10. 10. Making earth little softerTeam structure & reviewsPMOReviewsPMOReviewsReviews of deliverables of each member at everylevel by supervisor help improving qualityCreating proposal Project Plan, ReportsFollowing Process & best practicesReview of DD, Coding conventionsReviews of Proposal; Reports, EscalationsCompliances of the best practices, clientmanagement & business growthCreating DD, Design Framework, Codingconvention, Reviews of deliverables ofDevelopers & testersCreating Specification, Code, Unit& SI test cases, Testing, etcCompletion checklist, Self review
    11. 11. Making earth little softerReviews• Assuring:-• Quality of design document impacts quality ofthe code & the test cases.• To identify the right resource for the reviewsdepending on entity to be reviewed• Assuring incorporating review comments• Reviews are discontinued when progress isdelayed. To assure to have reviews as planned• Tracking review efforts & duration for eachentity (like code, unit test cases, etc) (e.g.review time per page)
    12. 12. Making earth little softerReviews• Deciding on review density before starting theactivity• Review comments expected to reduce onrepeat cycle• Cause for concerns• No. of review comments & No. of majorcomments are not decreasing on progress asexpected is indication of unstable quality• Volume change of entity (e.g. no of pages fordesign doc, no. of test cases, etc) pre & postreview
    13. 13. Making earth little softerCode reviews• Build detailed code checks into the developmentprocess• Make it impossible to release code that violatesthese checks• Few errors would only be discovered by codereviews or testing• Many errors only occurred on specific datasets
    14. 14. Making earth little softerPerformance testing• Execute to check performance of each query• Create database as appropriate• Compile & Check manually all the queriesindividually for performance time, keep record• Every SQL statement is run against multiple realworld customer databases• Improve/ optimise the queries• Log the bugs for worst performing statements
    15. 15. Making earth little softerIssue Management• Issues are restraints to accomplishing thedeliverables of the project.• Typically identified throughout the project andlogged and tracked through resolution.Issues impact cost, time, quality, mostimportant is reputation and branding!Types of issue – Minor, Normal, Major,Critical, BlockerMinor issue is dangerous!
    16. 16. Making earth little softerIssues/Risks (non-financial)Highlight highest risks for management attention
    17. 17. Making earth little softerMetrics-Development & EnhancementNOTE: Pl highlight the summary from themetrics reportWorkPacketsEffortVarianceOn-timeDeliveryDefectDensityFieldDefectDensityProductivity COQ ReviewEffectivenessGoal Actual G A G A G A G A G A G A
    18. 18. Making earth little softerMetrics-Maintenance & SupportProvide the SLA compliance summary If you useany tool provide the snap shot of the same.The number of tickets includes the new receivedin the reporting month as well as the backlogfrom previous monthsPriority Number ofTickets/FaultsResponse SLACompliance%Resolution SLACompliance%RemarksGoal Actual Goal ActualP1P2P3P4
    19. 19. Making earth little softer• The perceptions of the user determine thepurpose. Quality therefore is a user perception.• Correctness : Does it as per users agreed on?(Unit Level)• Integrity : Does it maintain accurate data?(Integration Level)• Reliability: Does it behave right all the time?(Application Level)• Efficiency : Does it run as well as it could?(Application Level)• Robustness: Does it handle invalid data?(Application Level)Quality & User perceptions
    20. 20. Making earth little softerTesting Improvements• PM decides on type of testing - automated ormanual or both• 400% increase in automated regression tests inthe same efforts• Tests created for all key business flows• Created by dedicated product QA teams• Used for• Ongoing maintenance/bug fixes• Platform certification (e.g. Linux)• Technology certifications• eBusiness Flows certified prior to release• Progress measured daily, and reported
    21. 21. Making earth little softerPrerequisites of TestingTest Cases• Latest & Completed test cases documents fromCVS (or any Configuration management tool)Test Environments• Document that gives the details of H/W and S/Wrequired to start testing• Identical environment which client would havewhile going live• Development environment• Testing environment
    22. 22. Making earth little softerFlow of Testing• Test cases• Test Data• Unit Testing• Screen Layout, look & feel• Screen Validations• Functionality• Integration Testing• Application Testing• Users Acceptance Testing
    23. 23. Making earth little softerTesting GuidelinesWhy the testing guidelines?• “Test cases may not cover 100% aspects thusextend your thoughts beyond the writtenstatement of the test case.”
    24. 24. Making earth little softerWho should testThere are 2 possible actors• Developers to execute 100% unit testing• Reasons being they take the entire ownership ofquality of the delivery• Second possibility is dedicated testing teamexecuting test cases• Testing being skill of expert!
    25. 25. Making earth little softerUnit Testing - UITo use a check list & test for following• Consistency- Control sizes• Basic functionalities• Tables, navigation to next page• Search listing result• Validation error message• Layout (as per Prototype)• Spelling Mistakes• Font (Type & Size)• Icons display• Color Scheme• Screen resolution
    26. 26. Making earth little softerUnit Testing - UI• Tab sequence & Text selection• Links (Check each link to ensure it works)• Current selection indication• Alignments (Text, Numbers, Row, Column)• Compatibility with various browsers• Duplicate display of information• Mention of Copyright
    27. 27. Making earth little softerUnit Testing - Validations• Field type & Size (Numeric, Alphanumerical,Database field width)• Formatted fields (e.g. Date, E-mail, PhoneNumbers, Security ID)• Mandatory Fields• Messaging (Alert, Warning, field message,message post submissions, sequence, etc)• Database Records verification• Verify the values stored in database for Radiobuttons & Checkboxes• Test spaces trimming (leading & trailing spaces)• Update By & Update on fields
    28. 28. Making earth little softerUnit Testing - FunctionalityTo use matrix of screens & functionalitiese.g. File Upload/Download•Try all types of files – image files, office files,animated GIF•Try downloading files – verify they don’t containgarbage•Search using special characters like (%,_,’ etc.)Sorting functionality - Check the number ofrecords before and after the sorting are same• In case of mailing functionality, check for non-existing e-mail address. (The mail should bereturned back to some preset mail address)
    29. 29. Making earth little softerUnit Testing - FunctionalityTo use matrix of screens & functionalities•Test User login Case Sensitivity•Test the dependant behaviors of the controls•Enabling / Disabling based on some actions•Data shown in Popup Screens based on someactions (Refreshing)•Language Support Test (Wherever applicableJapanese / German/ French, etc Input)•Test readability by changing encoding type in thebrowser
    30. 30. Making earth little softerIntegration Testing• Refer Integration Matrix while testing• Enter boundary values (Min , Max, 0 , negativeetc)• Errors occur when values passed by oncescreen are used in calculations on other screen
    31. 31. Making earth little softer• Testing Business Transactions• Refer Screen Flow Diagrams while identifyingBusiness Transactions• Identify the User Roles to perform testing (SalesPerson, Purchase Manager, Dispatch PersonOR User , Administrator)• Ensure Test Data Variety & Test data Volume• Roles & Rights testing (Test for access rights)• Logging Mechanism testing (Errors and UserActions)• Deployment Testing (Perform Deployment asper the Deployment Document)Application Testing
    32. 32. Making earth little softer• Application Menu should be in sequence of thefunctionality• User Management->Master Data Mgt-> OrderEntry->Purchase Mgt->Dispatch• Navigation• Using Browser ‘Back’ & ‘Forward’ buttons• Using ‘Back Button’ & ‘Links’ in the application• Browser dependency• Test for all the browsers as per client request(Min should be IE & Netscape)• Disable Cookies and try to login or performTransactionsApplication Testing
    33. 33. Making earth little softer• Perform transaction using multiple instances ofapplication, Open other applications like (Word,Excel, Access, Others)• Quick Actions in the Application• Click Submit button twice• Switch between the screens quickly• Enter data in one instance & try to see itimmediately in another instance• Random operations• Enter any number of characters and clickanywhere• Clicks on read only areaApplication Testing
    34. 34. Making earth little softer• Copy Paste of the URLs• Copy URL after Logging in and paste it inanother instance of browser• Same operation while in the middle of abusiness Transactions• Session Timeout verification (test for < / = / >defined timeout value)• Disconnection Test (to verify there is noinconsistent data generated)• Disconnect Net connection in the middle of atransaction• Stop Database service while transaction is inprocess on the clientApplication Testing
    35. 35. Making earth little softer• Reports printing• Print Multiple Pages• Try to print without installing any printer driver• Verify Report Margins for the printed copy• Status related tests (Display only ‘Active’ / ‘Live’records)• Multi-user Testing• Concurrent users (Different users / users withdifferent roles)• Concurrent Transactions (Add / Update /Delete / File Upload)• Locking Issues Test• Common Tests…ref fileApplication Testing
    36. 36. Making earth little softerHow Much Testing Is Enough?• There is always one more bug…• So how much testing is needed to find “all” ?• Cost• Time to market• Feasibility• Rate of detection of defects• Industry-specific standards• To predict how many bugs will be in a release?• In order to provide correct budget and scheduleestimates, QA managers need the means topredict fault levels.
    37. 37. Making earth little softerTypes of defects• Blocker• Severe/ Critical• Major• Normal• Minor• Trivial• To publish phase wise defect data for eachmodule for above types• Responsibility wiseSample statistics
    38. 38. Making earth little softerUpdate defect passbook at end of day and checkstatus and trendDefect passbook
    39. 39. Making earth little softerConfidential 41QAG measures QualityQAG tracks and measures quality using followingtemplateOrganisation
    40. 40. Making earth little softerQuality measurementNo. of defects 1effort in manmonths 3Loc per hr 10Lines of code 4800no. of defects 1% of defects to LoC 1*100/4800=2.1%Achieved quality 97.9167%• 1 defect detected by customer for 3 manmonths of efforts is said to be fairly good quality• Count each type of defect (minor, normal,major, critical or blocker) ; Minor defect is worst!
    41. 41. Making earth little softerMeasure where are you• To set a quality baseline & remain determined• To seek feedback• To measure and conclude current levels fromdesired level• To draw action plan to be at set goal012345678Vertex NTTDDesired levelCurrent LevelCurrent level Desired level
    42. 42. Making earth little softerAim for Defect Metrics (sample)Phase Metrics UnitLowerLimitAverageUpperLimitRequirementdefinitionRequirementdocumentsReviewcommentsPer 100pages9.8 15 24DesignDetail design(DD)ReviewcommentsPer 100pages7.6 13 21Program design(PD)ReviewcommentsPer 100pages4.9 12 30CodingUnit TestingTest CaseDensityKLOC 65 110 170Defect density KLOC 3 6.4 9.7IntegrationTesting (SI)Test CaseDensityKLOC 16 39 92Defect density KLOC 0.7 2.2 3.6TestingSystem Testing(PT)Testing density KLOC 2.3 9.5 39Bug detectiondensityKLOC 0 0.7 1.4Entity which is measured, can be managed well
    43. 43. Making earth little softerBug content analysisPhenomenon Action exampleModule havingmajor changeSuspend test workReview of design document, review of sourcecode with the designerEnhanced test according to test items, bugcontentsTest density <allowable rangeEnhanced test according to test items, bugcontentsBug detectiondensity is lessthan allowableEnhanced test according to test item, bugcontentsBug detectiondensity exceedsallowable rangeAs per 1 above
    44. 44. Making earth little softerBug content analysisPhenomenon Action exampleBug causeProblem ofdefectivespecificationRe-check specifications for client, businessDesign document review with an expertIndetermination of specifications of designdoc. ambiguous partBug causeProblem ofdevelopmentfrom specificationConfirmation of specification to designerReview of design document & source codewith the designerClarification of implementation,implementation methodBug - Other thanspecificationThoroughness of walk through and sourcecode reviewOccurrence typeEnvironmentSpecify reason according to occurrenceperiod, contentsRe-examination of test environment, system
    45. 45. Making earth little softerBug content analysisOccurrence type Action exampleOperational error,without reproduction,identificationmistake)Review of test item, processRe-adjustment of design document, testenvironmentEducational guidance to designerCoding/ modificationmistakeThoroughness of source code reviewOccurrence ofimportant bug thatimpacts testprogressSuspend test workReview of design document & review ofsource codeEnhanced test according to the test item,bug contentsoccurrence of similarbugsCheck the latency of a similar bug inanother module
    46. 46. Making earth little softer• No. of pages/ characters of design document &LOC of the code• Check planned No. of test cases (a statisticalindex page for test cases shows the progress)• Test cases planned & actually execution• To capture No. of test cases executed on dailybasis and cumulative basis• No. of defects detected on daily andcumulative basis – check if volume is apt• Calculate defect density–check if volume is apt• Check if any delay in execution, understand &remove the delayQuantitative analysis
    47. 47. Making earth little softer•Check the pending test cases on daily &cumulative basis – check if volume is apt•Bug fixing on daily and cumulative basis - checkif volume is less or more•Check if any delay in fixing, understand &remove the delayQuantitative analysisMatrix AnalysisTest density Low Target value Upper limitBug Density -Low Less BugsdetectionRetest adding fewmore test casesMember skill level?Target Value Write additionaltest casesJudge verification ofthe result qualitativelyJudge verification ofthe result qualitativelyUpper Limit Multiple bugsoccurredMultiple bugs occurred Suspend testing, getinto other measure likecode review, etc
    48. 48. Making earth little softerQuantitative analysis# Category Details Type1 SpecificationInadequacyDescription Inadequacy Interface ErrorLogical ErrorData definition errorTable definition errorFormat ErrorOthersWrong descriptionAmbiguousStandard ViolationDocument not correctedDocument not consistent2 Issue whiledeployingSlipping over the specificationLack of understanding theLack of confirming the specificationInsufficient investigation of specs3 Issuesexcept themattersrelated tospecificationLess knowledge for language usageHalfway publicize / communicationStandard violationNot checked while re-usingNot checked while modifyingUnforced mistake
    49. 49. Making earth little softer• Root cause analysis – assign root cause toeach bug & conduct analysis (fishbone diagram)• Severity wise• Developer wise• Tester wise• Defect injection phase v/s defect detection• Defect injection phase v/s root cause• Daily status (like a bank passbook)Quantitative analysisDefect detected RA-Review HLD, IT -Review LLD, UT-Review Code review UT IT ATDefect injectedRAHLDLLDCoding
    50. 50. Making earth little softerProcess• This PCB is released as Organization PCB• This PCB should be referred to when providingOrganizational Data to the customers• Each project depending on the size, complexityand customer requirement shall define themetrics for the project.• This would be done in Process Plan as part ofthe project initiation.• In case the project targets are outside the UCLor LCL limits an approval would be requiredfrom the respective VP.
    51. 51. Making earth little softerPCB Contents• Productivity Data• Phase wise effort distribution• Effort – Actual Vs. Estimated• Schedule – Actual Vs. Estimated• Defect Metrics
    52. 52. Making earth little softerProductivity DataLOC/ 1 MMProductivity LCL Target UCLJava 700 1000 1300VB.Net 800 1500 2200C# .net 700 950 1200C 700 1000 1300This data applies to all the efforts spent on allSDLC Phases – from RA to Acceptance testingTo finalise parameters for data to be capturedTo create PCB data for each projectThus organisational data will be createdAnalyse & use the data
    53. 53. Making earth little softerPlan to Collect Data• PCB shall be updated every three months, Endof every quarter - Jun, Sep, Dec, and Mar• For development, testing & maintenance project• Finalise project metrics during kickoff of project• The project metrics collection plan shall befinalized as part of the project initiation process(Process Plan)• The projects shall contribute Phase End data orMilestone data every six months• To share PCB data during project closure
    54. 54. Making earth little softerProject ClosureTo conduct a meeting with all stake holdersTo share following information estimated & actual• Efforts• Schedule• Defect Matrices• Profitability• Client happiness IndexDetailing• Key learning• Best performance• What next?Remember
    55. 55. Making earth little softerThank YouAuthor has worked at as Sr management professionalVertex Software, now NTTDataTech MahindraSoftBridge Solutions, India& extremely thankful to these organisation for offering excitingopportunity to work in related areas, gain experience & contribute& a gentleman having deep passion about quality..MukandBhagwat
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×