A model of correlated team behaviour in a software development environment

Potok, Thomas E.; Vouk, Mladen A.

doi:10.1109/asset.1999.756781

Cited by 4 publications

(4 citation statements)

References 2 publications

(6 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Recently, a study [20] summarized the methods of measuring software development team productivity. Most of the authors ( [21], [22], [23], [24]) considered only very simplistic measures of outputs and inputs.…”

Section: Productivity In Engineering Applications: Software Project Mmentioning

confidence: 99%

Estimating Productivity of Software Development Using the Total Factor Productivity Approach

Machek

Hnilica

Hejda

2012

International Journal of Engineering Business Management

View full text Add to dashboard Cite

The design, control and optimization of software engineering processes generally require the determination of performance measures such as efficiency or productivity. However, the definition and measurement of productivity is often inaccurate and differs from one method to another. On the other hand, economic theory offers a well‐grounded tool of productivity measurement. In this article, we propose a model of process productivity measurement based on the total factor productivity (TFP) approach commonly used in economics. In the first part of the article, we define productivity and its measurement. We also discuss the major data issues which have to be taken into consideration. Consequently, we apply the TFP approach in the domain of software engineering and we propose a TFP model of productivity assessment

show abstract

Section: Productivity In Engineering Applications: Software Project Mmentioning

confidence: 99%

Estimating Productivity of Software Development Using the Total Factor Productivity Approach

Machek

Hnilica

Hejda

2012

International Journal of Engineering Business Management

View full text Add to dashboard Cite

show abstract

“…This is something that is contrary to the concept of reliability growth based on the "classical" reliability models. There is also the issue of situations where the business model of an organization overshadows the software engineering practices and appears to be the sole (and sometimes poor) guidance mechanism of software development (Potok and Vouk (1999a), Potok and Vouk (1999b), Potok and Vouk (1997)).…”

Section: Issuesmentioning

confidence: 99%

“…In a resource constrained environment, there is a tendency to compress software specification and development processes (including verification, validation, and testing) using either mostly business model directives or some form of "short-hand" technical solution, rather than a combination of sound technical directives and a sensible business model. The business models that often guide modern "internet-based" software development efforts advocate, directly or indirectly, a lot of "corner-cutting" without explicit insistence on software process and risk management procedures, and associated process tracking tools, appropriate to these new and changing environments, e.g., Extreme Programming (XP), use of Web-based delivery tools (Potok and Vouk (1999a), Potok and Vouk (1999b), Beck (2000)). There are also software development cultures, such as XP, specifically aimed at resource constrained development environments (Auer and Miller (2001), Beck (2000), Beck (2001)).…”

Section: Introductionmentioning

confidence: 99%

“…For example, consider testing in "web-year" (i.e., 3-month development cycle (Dougherty (1998)) environments. While having hard deadlines relatively often (say every 3 months) is an excellent idea since it may reduce the process variance, the decision to do so must mesh properly with both business and software engineering models being used or the results may not be satisfactory (Potok and Vouk (1997), Potok and Vouk (1999a), Potok and Vouk (1999b)). One frequent and undesirable effect of a business and software process mismatch is haste.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Construction of Reliable Software in Resource‐Constrained Environments

Vouk

Rivers²

2002

Wiley Series in Probability and Statistics

View full text Add to dashboard Cite

Current software development practices are often "business-driven" and therefore tend to encourage testing approaches that reduce verification and validation activities to shorten schedules. In this paper, we focus on efficiency of testing and resulting software quality (reliability) in such an environment.We use a resource constrained testing model to analyze data from several projects. Our results indicate that in a practical resource constrained environment there is little room for improving testing during the actual process. Furthermore, there is likely to be considerable variability in the quality of testing, within a testing phase, that may stem from a variety of sources such as the human element, software development practices and the structure of the software itself. However, it is interesting to note that there are experimental resultsshowing that testing efficiency can be improved over longer periods of time through process improvement, and that software quality does appear to be positively correlated with an increase in the average testing efficiency that stems from process improvements. metrics and models can then be used to guide the process (Musa, et al (1987)). When software development and testing is resource and schedule constrained, some traditional quality monitoring metrics and models may become unusable. For example, during non-operational profile based testing, failure intensity decay may be an impractical guiding and decision tool (Rivers (1998), Rivers and Vouk (1999)).End-product reliability can be assessed in several ways. The aspect of reliability that we are concerned with is efficient reduction of as many defects as possible in the software being shipped. In the next section we describe and discuss the notion of resource constrained software development and testing.In Section 3, we present a software reliability model that formalizes resource constrained development and testing with respect to its outcome. Empirical results, from several sources, that illustrate different constrained software development issues are presented in Section 4. CONSTRAINED DEVELOPMENTSoftware development always goes through some basic groups of tasks related to specification, design, implementation, and testing. Of course, there are always additional activities, such as deployment and maintenance phase activities, as well as general management, and verification and validation activities that occur in parallel with the above activities. How much emphasis is put into each phase, and how the phases overlap, is a strong function of the software process adopted (or not) by the software manufacturer, and of how resource constraints may impact its modification and implementation (Pressman (2001), Beck (2000, Potok and Vouk (1997)). A typical resource constraint is development time. However, "time" (or exposure of the product to usage, in its many forms and shapes) is only one of the resources that may be in short supply when it comes to software development and testing. Other resources may include available staff,...

show abstract

Workflow Development Effort Estimation as Applied to Web Human Resource Management

Raheem

2016

Glob J Flex Syst Manag

View full text Add to dashboard Cite

Over the past decade most of engineers, researchers, institutions, standard organizations and businessmen had been faced with challenges on how to represent productivity functions for effort estimation in information system workflow development. Despite the fact that workflows are everywhere, only few reports about its development effort are available. Accurate workflow sizing is a very difficult task at conceptual state. This paper proposes the proximity scoring measurement method to determine workflow size and to estimate workflow development effort with its knowledge retention effort. The approach is applied to the web publishing industry as a human resources case study. The approach of this paper is scalable and easy to apply to evaluate Web human resource workflow development effort. The implication of this work is that workflows can be estimated more precisely, helping to estimate the benefit of workflow reuse.

show abstract

A model of correlated team behaviour in a software development environment

Cited by 4 publications

References 2 publications

Estimating Productivity of Software Development Using the Total Factor Productivity Approach

Estimating Productivity of Software Development Using the Total Factor Productivity Approach

Construction of Reliable Software in Resource‐Constrained Environments

Workflow Development Effort Estimation as Applied to Web Human Resource Management

Contact Info

Product

Resources

About