A model of the software development process using both continuous and discrete models

Martin, Robert H.; Raffo, David

doi:10.1002/1099-1670(200006/09)5:2/3<147::aid-spip122>3.0.co;2-t

Cited by 75 publications

(42 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…They incorporate feedback loops by dividing the inputs by five, iterating five times, calculating product, process, and project factors, and passing the attributes on to the next activity. One of the advantages of this approach is that it is possible to explicitly analyze the performance of each discrete process, which is regarded as a difficult task in system dynamics simulation (Martin and Raffo 2000).…”

Section: Analysis Of the Published Hybrid Spsm Approachesmentioning

confidence: 99%

“…(1) Martin and Raffo (2000) have developed a hybrid simulation model, which ensures that the discrete activities are consistent with the implied activities of the continuous portion. This combined model would allow investigation of the effects of discrete resource changes on continuously varying productivity and the influences of the duration of discrete code inspection tasks on continuously changing error rates.…”

Section: Analysis Of the Published Hybrid Spsm Approachesmentioning

confidence: 99%

“…Rus et al (1999) and Lakey (2003) made it possible to explicitly analyze the performance of each discrete process while incorporating the feedback loop mechanism. Martin and Raffo (2000) analyzed the manpower utilization using a hybrid simulation model, which shows us how manpower levels vary on the basis of the changes in workforce, hiring delays, allocation decisions, and the point at which the available manpower is wasted. This analysis is not reproducible in the continuous or discrete model alone.…”

Section: Introductionmentioning

confidence: 99%

“…The feedback loops approximated by Rus et al (1999) and Lakey (2003) are too coarse to fully represent the dynamics of continuously interacting variables such as schedule, size, quality, manpower, overhead, skill level, etc. Martin and Raffo (2000) assumed that the workload for an activity is constant during its life-cycle, which prevents the model from calculating the activity duration dynamically. This affects all the dynamics of the combined model.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

An approach to a hybrid software process simulation using the DEVS formalism

Choi

Bae

Kim

2006

Softw. Process: Improve. Pract.

View full text Add to dashboard Cite

This article proposes an approach to a hybrid software process simulation modeling (SPSM) using discrete event system specification (DEVS) formalism, which implements the dynamic structure and discrete characteristics of the software development process. Many previous researchers on hybrid SPSM have described both discrete and continuous aspects of the software development process to provide more realistic simulation models. The existing hybrid models, however, have not fully implemented the feedback loop mechanism of the system dynamics.We define the DEVS Hybrid SPSM formalism by extending DEVS to the hybrid SPSM domain. Our hybrid SPSM approach uses system dynamics modeling to convey details concerning activity behaviors and managerial policies, while discrete event modeling controls activity start/completion and sequence. This approach also provides a clear specification, an explicit extension point to extend the simulation model, and a reuse mechanism. We will demonstrate a Waterfall-like hybrid software process simulation model using the DEVS Hybrid SPSM formalism.

show abstract

Section: Analysis Of the Published Hybrid Spsm Approachesmentioning

confidence: 99%

Section: Analysis Of the Published Hybrid Spsm Approachesmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

An approach to a hybrid software process simulation using the DEVS formalism

Choi

Bae

Kim

2006

Softw. Process: Improve. Pract.

View full text Add to dashboard Cite

show abstract

“…-discrete-event models [16]; -system dynamics models [17]; -state-based models [18]; -rule-based programs [19]; -standard programming constructs such as those used in Little-JIL [20].…”

Section: The Models: Cocomo and Coqualmomentioning

confidence: 99%

On the Relative Merits of Software Reuse

Orrego

El-Rawas

2009

Trustworthy Software Development Processes

View full text Add to dashboard Cite

Abstract. Using process simulation and AI search methods, we compare software reuse against other possible changes to a project. such as reducing functionality or improving the skills of the programmer population. In one case, two generations of reuse were as good or better than any other project change (but a third and fourth generation of reuse was not useful). In another case, applying reuse to a project was demonstrable worse than several other possible changes to a project. Our conclusion is that the general claims regarding the benefits of software reuse do not hold for specific projects. We argue that the merits of software reuse need to be evaluated in a project by project basis. AI search over process models is useful for such an assessment, particularly when there is not sufficient data for precisely tuning a simulation model.

show abstract

Combining Process Feedback with Discrete Event Simulation Models to Support Software Project Management

Raffo

Vandeville

2006

Software Evolution and Feedback

View full text Add to dashboard Cite

Process feedback is an essential ingredient in process change planning and software project management. In this paper, we discuss on-going work with an industrial partner to integrate feedback from the software development process with a discrete event simulation model to improve process performance predictions. A flexible metrics repository provides feedback that is used to generate updated simulation model parameters at predefined project milestones. Model predictions using updated parameters and current project data are compared to Outcome Based Control Limits (OBCLs) defined for the project. These predictions enable the program manager to take corrective action as necessary with the simulation model providing feedback and insight on potential performance impacts of the proposed corrective actions. This creates a feedback loop with the process enhancing model predictions supporting project management decisions.

show abstract

A model of the software development process using both continuous and discrete models

Cited by 75 publications

References 3 publications

An approach to a hybrid software process simulation using the DEVS formalism

An approach to a hybrid software process simulation using the DEVS formalism

On the Relative Merits of Software Reuse

Combining Process Feedback with Discrete Event Simulation Models to Support Software Project Management

Contact Info

Product

Resources

About