Software productivity is the ratio between the amount of software produced to the labor and expense of producing it. There are two measures of software productivity:
Size related measures:
It measures the line of code delivered and measures no. of delivered object code instructions or no. of pages of system documentation.
For example: A system which might be coded in 5000 lines of assembly code. The development time for the various phases in 28 weeks :
Then productivity = (5000*28)/4
Productivity is expressed in terms of the amount of useful functionality produced in some given time. It is based on an estimate of the functionality of the delivered software. Function in a program is computed by measuring program features:
- External inputs and outputs
- User interactions
- External interfaces
- Files used by the system
A weight is associated with each of these and the function point count is computed by multiplying each raw count by the weight and summing all values.
Factors affecting productivity
Application domain experience
Knowledge of the application domain is essential for effective software development. Engineers who already understand a domain are likely to be the most productive.
The development process used can have a significant effect on productivity.
The larger a project, the more time required for team communications. Less time is available for development so individual productivity is reduced.
Good support technology such as CASE tools, configuration management systems, etc. can improve productivity.
A quiet working environment with private work areas contributes to improved productivity.
206 total views, 2 views today
A Soon-to-be Computer Engineer by profession, he has profound devotion to add Data Scientist as a prefix to his name. He’s been to the nooks of the web (at least of the surface web) and planning to add some real figures in his pocket!