State-of-the-Art in Programming Productivity Programming productivity

1 state-of-the-art in programming productivity

1.1 cocomo ii
1.2 jones s software productivity
1.3 function points
1.4 value-based software engineering
1.5 peopleware

state-of-the-art in programming productivity

in software development things more complicated in production of goods. software development engineering process.

cocomo ii

boehm 1 of first researchers systematically approached field of software productivity. cost estimation model cocomo – cocomo ii - standard software engineering knowledge. in model, defines set of factors influence productivity such required reliability or capability of analysts. these factors have been reused in other similar productivity approaches. rest of model based on function points , source lines of code (loc). limitations of loc productivity measure well-known.

jones s software productivity

jones author of series of books on software productivity. besides several theoretical considerations main contribution systematic provision , integration of large amount of data relevant productivity analyses. in @ least 2 of books, gives number of productivity factors points out each project different set of factors influential. these factors can form basis productivity assessments , comparison industrial averages.

this 1 such list:

the 20 factors quantified impacts on software projects have been determined historical data following:

programming language used
program size
the experience of programmers , design personnel
the novelty of requirements
the complexity of program , data
the use of structured programming methods
program class or distribution method
program type of application area
tools , environmental conditions
enhancing existing programs or systems
maintaining existing programs or systems
reusing existing modules , standard designs
program generators
fourth-generation languages
geographic separation of development locations
defect potentials , removal methods
(existing) documentation
prototyping before main development begins
project teams , organization structures
morale , compensation of staff


function points

function points proposed in 1977 albrecht better size measure software loc. in based on specification of software , thereby aims @ measuring size of functionality rather code itself. reason size of code not depends on size of functionality on capability of programmer: better programmers produce less code same functionality. function points have undergone several redesigns on years driven international function point user group (ifpug). group large on 1200 companies member shows rather strong acceptance of measure. however, in many domains still lacks practical application because conceived applicable business information systems.

value-based software engineering

several researchers proposed economic-driven or value-based software engineering important paradigm in future software engineering research. boehm , huang point out not important track costs in software project real earned value, i.e. value customer. explain important create software business case , keep date. in essence, value-based software engineering focuses on customer value, measured in monetary units.

peopleware

the famous book peopleware: productive projects , teams de marco , lister brought importance of people-related factors attention of broader audience. collected in many software projects experiences , bad management practice have influence on productivity of team. , others showed these decisive issues in software engineering able describe them anecdotally.