Function points in the estimation and evaluation of the software process

Low, Graham; Jeffery, D. Ross

doi:10.1109/32.44364

Cited by 168 publications

(80 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This measure is not without its flaws, but it is the most common measure of size and complexity in software engineering (Boehm 1981;Scacchi 1995). Many of the traditional drawbacks of KLOC -such as defining what qualifies as a line of code and how to count thousands of lines of code -are mitigated in our case, as we consider only one organization that uses a consistent counting methodology (Jones 1986;Low and Jeffery 1990). Software development has been shown to exhibit scale effects, so we use the logarithm of KLOC (Banker and Kemerer 1989).…”

Section: Control Variablesmentioning

confidence: 99%

Team Familiarity, Role Experience, and Performance: Evidence from Indian Software Services

Huckman¹,

Staats²,

Upton³

2009

Management Science

382

254

View full text Add to dashboard Cite

Much of the literature on team learning views experience as a unidimensional concept captured by the cumulative production volume of, or the number of projects completed by, a team. Implicit in this approach is the assumption that teams are stable in their membership and internal organization. In practice, however, such stability is rare, as the composition and structure of teams often changes over time or between projects. In this paper, we use detailed data from an Indian software services firm to examine how such changes may affect the accumulation of experience within, and the performance of, teams. We find that the level of team familiarity (i.e., the average number of times that each member has worked with every other member of the team) has a significant positive effect on performance, but we observe that conventional measures of the experience of individual team members (e.g., years at the firm) are not consistently related to performance. We do find, however, that the role experience of individuals in a team (i.e., years in a given role within a team) is associated with better team performance. Our results offer an approach for capturing the experience held by fluid teams and highlight the need to study context-specific measures of experience, including role experience. In addition, our findings provide insight into how the interactions of team members may contribute to the development of broader firm capabilities.

show abstract

Section: Control Variablesmentioning

confidence: 99%

Team Familiarity, Role Experience, and Performance: Evidence from Indian Software Services

Huckman¹,

Staats²,

Upton³

2009

Management Science

382

254

View full text Add to dashboard Cite

show abstract

“…Additional work in defining standards has been done by Zwanzig (Zwanzig 1984) and Desharnais (Desharnais 1988 (Boehm 1981) (Jones 1986 (Rudolph 1983, p. 6) Aside from this description, the only other research documented study is by Low and Jeffery (Low and Jeffery 1990). Their research focused on the inter-rater reliability of FP counts using as their research methodology an experiment using professional systems developers as subjects, with the unit of analysis being a set of program level specifications.…”

mentioning

confidence: 99%

“…In planning, the task of estimating the final SLOC count for a proposed system has been shown to be difficult to do accurately in actual practice (Low and Jeffery 1990). And in control, SLOC measures for evaluating productivity have weaknesses as well, in particular, the problem of comparing systems written in different languages (Jones 1986).…”

mentioning

confidence: 99%

Improving the reliability of function point measurement: an empirical study

Kemerer

Porter

1992

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

“…• 는 언어에 종속되어 있다 [9]. QSM [24] David [25] Jones [27] Mcgilbon [28] Sifri [29] 4GL(44) Access/Access 8.0(43) Ada/Ada 95(3)…”

Section:  기반 소프트웨어 공식과 문제점unclassified

Software Equation Based on Function Points

Lee¹

2010

The KIPS Transactions:PartD

View full text Add to dashboard Cite

This paper proposed software equation that is relation with effort and duration based on function point (FP) software size. Existent software equation based on lines of code (LOC). LOC sees big difference according to development language and there are a lot of difficulties in software size estimation. First, considered method that change LOC to FP. But, this method is not decided definitely conversion ratio between LOC and FP by development language. Also, failed though the conversion ratio motives software formula because was not presented about specification development language. Therefore, we derived software formula directly to large project data that was developed by FP. Firstly, datas that reasonable development period is set among development projects. Secondly, FP through regression analysis about this data and effort, motived relation with FP and duration. Finally, software equation was derived from these relation.Proposed model solves application problems that LOC-based model has and has advantage that application is possible easily in business.

show abstract

Function points in the estimation and evaluation of the software process

Cited by 168 publications

References 6 publications

Team Familiarity, Role Experience, and Performance: Evidence from Indian Software Services

Team Familiarity, Role Experience, and Performance: Evidence from Indian Software Services

Improving the reliability of function point measurement: an empirical study

Software Equation Based on Function Points

Contact Info

Product

Resources

About