In "Exploring Software project Effort versus Duration Trade-offs" (IEEE Software, July/Aug. 2012, pp. 67-74), Charles Symons proposed a process for exploring the trade-off between project duration and effort...
详细信息
In "Exploring Software project Effort versus Duration Trade-offs" (IEEE Software, July/Aug. 2012, pp. 67-74), Charles Symons proposed a process for exploring the trade-off between project duration and effort. However, the author of this comment argues that the process he described incorrectly estimates the strength of the relationship, finding a problem with the derivation. A Monte Carlo simulation demonstrates that the proposed process yields an incorrect result. A Web extra describes the mathematical results that showed this.
Estimates of effort and duration for a new software project often have to be adjusted to deal with an imposed target delivery date or a constraint on staffing. Estimating methods assume an effort/duration trade-off re...
详细信息
Estimates of effort and duration for a new software project often have to be adjusted to deal with an imposed target delivery date or a constraint on staffing. Estimating methods assume an effort/duration trade-off relationship based mostly on theory or expert judgment. This paper describes a process for analyzing actual project effort and duration data which is designed to explore the trade-off relationship. I assume a reference relationship of a simple power-curve with variable power ‘N’ and use this (a) as a means of comparing the trade-off relationships assumed by four well-known estimating methods, and (b) as the basis for a process to analyze actual project data. Results are presented of applying the process to 16 sub-sets of project data. These suggest, for example, that the value of ‘N’ differs between new development projects and enhancement projects. The Web Extra presents more results for each step in the effort-duration trade-off process described in the main article.
The goal of this paper is to propose a novel modeling framework to help project managers devise optimal workforce assignments that consider both short- and long-term aspects of projects that must be completed through ...
详细信息
The goal of this paper is to propose a novel modeling framework to help project managers devise optimal workforce assignments that consider both short- and long-term aspects of projects that must be completed through a multi-organizational social network. The proposed framework is comprised of an evaluation module and an assignment module. Each time a workforce assignment is performed, the Decision Evolution Procedure of the evaluation module first calculates the position value between each pair of currently available workforce members based on various social networking parameters such as trustworthiness, influence, reputation, and proximity. Second, by using these position values, the Extended Regular Equivalence Evaluation algorithm from the evaluation module computes the regular and structural equivalence values between each pair of workforce members. Finally, the assignment module selects an optimal workforce mix that maximizes both the short-term performance (productivity) as well as the long-term performance (workforce training, and robustness) of the project organizations. Agent-based simulation and multi-objective optimization techniques are leveraged for the evaluation module and the assignment module, respectively. The proposed framework is illustrated and successfully demonstrated using the software enhancement request process in Kuali, a multi-organizational alliance-based software development project involving 12 universities.
Much of modern software development consists of building on older changes. Older periods provide the structure (e.g., functions and data types) on which changes in future periods will build. Given a particular period ...
详细信息
ISBN:
(纸本)9780769538679
Much of modern software development consists of building on older changes. Older periods provide the structure (e.g., functions and data types) on which changes in future periods will build. Given a particular period in the lifetime of a project, one can determine prior periods on which it builds, and future periods which build on it. Using this knowledge, managers can identify foundational periods in the lifetime of a project, which provide the structural foundation for a large number of future periods. A good understanding and detailed documentation of events and decisions in such foundational periods is essential for the smooth evolution of a project. This paper examines how changes build on older changes by measuring the time dependence between code changes. Using our approach, we can create time dependence relations between periods and study the characteristics of such dependence relations. We apply our approach on two large open source projects, PostgreSQL and FreeBSD. We find that foundational periods are periods with huge restructurings, important new features or large imports of external source code. We also find that a project, as it ages, either progressively depends on older periods or cycles between depending on old and new periods.
Despite various industry reports about the failure rates of software projects, there\'\'s still uncertainty about the actual figures. Researchers performed a global Web survey of IT departments in 2005 and 200...
详细信息
Despite various industry reports about the failure rates of software projects, there\'\'s still uncertainty about the actual figures. Researchers performed a global Web survey of IT departments in 2005 and 2007. The results suggest that the software crisis is perhaps exaggerated and that most software projects deliver. However, the overall project failure rate, including cancelled and completed but poorly performing projects, remains arguably high for an applied discipline.
Traditional software engineering processes are composed of practices defined by roles, activities and artifacts. Software developers have their own understanding of practices and their own ways of implementing them, w...
详细信息
Traditional software engineering processes are composed of practices defined by roles, activities and artifacts. Software developers have their own understanding of practices and their own ways of implementing them, which could result in variations in software development practices. This paper presents an empirical study based on six teams of five students each, involving three different projects. Their process practices are monitored by time slips based on the effort expended on various process-related activities. This study introduces a new 3-pole graphical representation to represent the process patterns of effort expended on the various discipline activities. The purpose of this study is to quantify activity patterns in the actual process, which in turn demonstrates the variability of process performance. This empirical study provides three examples of patterns based on three empirical axes (engineering, coding and V&V). The idea behind this research is to make developers aware that there is wide variability in the actual process, and that process assessments might be weakly related to actual process activities. This study suggests that in-process monitoring is required to control the process activities. In-process monitoring is likely to provide causal information between the actual process activities and the quality of the implemented components. (C) 2007 Elsevier B.V. All rights reserved.
Flexible software development models, e. g., evolutionary and incremental models, have become increasingly popular. Advocates claim that among the benefits of using these models is reduced overruns, which is one of th...
详细信息
Flexible software development models, e. g., evolutionary and incremental models, have become increasingly popular. Advocates claim that among the benefits of using these models is reduced overruns, which is one of the main challenges of software project management. This paper describes an in-depth survey of software development projects. The results support the claim that projects which employ a flexible development model experience less effort overruns than do those which employ a sequential model. The reason for the difference is not obvious. We found, for example, no variation in project size, estimation process, or delivered proportion of planned functionality between projects applying different types of development model. When the managers were asked to provide reasons for software overruns and/or estimation accuracy, the largest difference was that more of flexible projects than sequential projects cited good requirement specifications and good collaboration/communication with clients as contributing to accurate estimates.
暂无评论