KALİTEKsoftware analysis & measurement

kalitek

agenda

about introduction efficiency agility

productivity next steps q&a

kalitek

aboutwhat we do

assess complex, multi-tier applications to identify vulnerabilities

productivity measurement

outsourcing management

rapid portfolio analysis

quality improvement benchmarking security

kalitek

about CAST

Fact-based transparency into application development

Integral part of software delivery and maintenance

World leader in software analysis and measurement

Achieve insight

Deliver excellence

Automated approach to capture quality and size of applications

kalitek

Introduction

kalitek

software development

•Largely manual activity

•Software has not been applied to software itself

•Reusable materials available but custom development is dominant

•Intellectual difficulty; no human mind can keep track of complex transactions

kalitek

software development

•Error free coding is impossible

•Testing is difficult, % 100 coverage is impossible

•Defect prevention is a must

•Certified reusable materials are needed

kalitek

efficiencywhy %40 of projects are behind schedule?

rework unpredictable delivery dates

long time spent on testing

Major cost

drivers

high quality applications shorten testing schedules and reduce rework.

with low quality large software projects, %50 of the effort is devoted to finding and repairing bugs and performing rework.post-release

maintenance

kalitek

efficiencyDefect & Cost by SDLC Stage

Capers Jones, 1996

application quality check shall be done before functional testing in order to avoid high fixing costs.

source code analysis shall be applied during code development.

kalitek

productivity

- Software development is expensive

- Lagging software development productivity can have a significant impact on the organization’s ability to compete and survive

- There has to be a process that ensures quality software can be produced consistently and efficiently

why important?

kalitek

Either in-house or outsourced, Quality of any software deliverable:

•should be predictable before project starts

•should be measurable:

– while projects are underway

– BUT ALSO after deployment / during maintenance

quality driven development

kalitek

What are the goals?Reduce Cost

Develop more valuable products for lower cost

Support Estimation Process

Provide consolidated history data

Early Defect Correction

Assess Supplier

CapabilityBenchmark

ApplicationsIdentify

production bottlenecks

quality driven development

kalitek

solutions

kalitekenterprise-grade software quality analysis and measurement dashboard

application quality dashboard1

2

3

4

5

kalitek

provides information about;

•technical sizing

•QI_quality index (calculated based on ISO 9126)

•portfolio history

•critical violations

•detailed QI for robustness, performance, security

application quality dashboard

kalitek

vendor management 1

kalitek

clientvendor

service&app. proposal

request for health assessment

source code

NDA NDA

health report &

certification

procurement

- visibility into the technical state (stability, performance, security) of critical systems- specified metrics and guidelines to evaluate vendor performance- transparent effort estimation to de-risk the sourcing negotiation

vendor delivery assessment

kalitek

vendor management 2

kalitek

clientvendor

source code, v1,v2..vn

request for health assessment

effort&cost estimation, action lists

SDLC- shifting resources offshore introduces high risk in structure quality and productivity- baseline productivity of outsourcing programs is a mandatory first step of any strategic sourcing shift/transition- performance based contract management

control vendor performance 

source code

kalitek

sample vendor outputv1 v2

effort estimation

cost estimation

man/day change %

kalitek

developer talent managementteam A

app.size 1.000.000developer count 20USD 80.000 cost per FTEdelivered in 200 man/days

team B

app.size 1.000.000developer count 20USD 40.000 cost per FTEdelivered in 200 man/days

team B is more productive because they deliver same project with lower cost??

2 critical violations per FTEtotal of 40 critical violations USD 200 per fixcost for 40 fixes=8.000 USD

25 critical violations per FTEtotal of 500 critical violations USD 100 per fixcost for 500 fixes=50.000 USD

team A is more productive because they deliver same

project with lower bug fix cost

however, using CAST findings!

kalitek

LoCTotal number of lines of code / function points

added

Object Complexity

Number of H/VH Complex objects/

components added/updated

Defect Injection

Number of added critical violations per

version delivered

Release Productivity

(RP) Volume of code

developed / Effort spent on the release

QA Productivity

RP x f(Technical Debt)

how to calculate productivity using CAST

productivity

kalitek

questions and answers session

Q&A

kalitek

our contact detailsAdressbarbaros Mh. deluxia Palaceören Sokak no:5 | 454, ataşehir,istanbul 

Websitewww.kali-tek.com

Emailinfo@kali-tek.comPhone+90 216 510 57 27

kalitek

Addendum- CAST Dashboards

kalitek

1

2

3

4

5

kalitekView for ARCHITECT or PROJECT MANAGER

View for PROJECT DIRECTOR

View for OUTSOURCING MANAGER

View for CIO or VP APP. DEVELOPMENT

kalitek

kalitek

kalitek