Siri-on Setamanit

Using Simulation to Evaluate Global Software Development Task Allocation Strategies

We describe a hybrid computer simulation model of the software development process that is specifically architected to study alternative ways to configure global software development (GSD) projects, including phase-based, module-based, and follow-the-sun allocation strategies. The model is a hybrid system dynamics and discrete-event model. In this paper, test cases have been developed for each allocation strategy, and project duration is computed for each configuration under a range of plausible assumptions for key parameters. The primary finding is that although under ideal assumptions follow-the-sun is able to produce impressive reductions in time-to-market, under more realistic assumptions the reverse is true, thus corroborating findings by other researchers. We also conducted a factorial design to examine the impact of GSD factors including distance, culture, language, trust, and time zone on project duration under different task allocation strategies. The analysis reveals that different factors affected the performance of the selected allocation strategies in unique ways. These findings show how the unique ability of our GSD model to represent detailed development processes and work artifact transfer allows researchers to address challenging questions that are critical to GSD project success. Copyright

Planning and improving global software development process using simulation

Global software development poses a number of challenges and difficulties as well as significant potential benefits. In order to be successful, companies need to adapt and improve their processes to support this kind of development. Strong project planning and management is also required. Software process simulation modeling has been used to address a variety of issues in software development projects ranging from strategic management, project planning and control, process improvement, to training and understanding. We believe that a hybrid simulation model combining system dynamics and discrete-event models is needed to effectively model global software development projects. In this paper, we describe such a model, and focus on the use of the model to support project planning and process improvement in global software development. Example questions/issues that can be addressed by our GSD model are provided, along with an illustrative application.

Model-based tests of truisms

Software engineering (SE) truisms capture broadly-applicable principles of software construction. The trouble with truisms is that such general principles may not apply in specific cases. This paper tests the specificity of two SE truisms: (a) increasing software process level is a desirable goal; and (b) it is best to remove errors during the early parts of a software lifecycle. Our tests are based on two well-established SE models: (1) Boehm et.al.s COCOMO II cost estimation model; and (2) Raffos discrete event software process model of a software project life cycle. After extensive simulations of these models, the TAR2 treatment learner was applied to find the model parameters that most improved the potential performance of the real-world systems being modelled. The case studies presented here showed that these truisms are clearly sub-optimal for certain projects since other factors proved to be far more critical. Hence, we advise against truism-based process improvement. This paper offers a general alternative framework for model-based assessment of methods to improve software quality: modelling + validation + simulation + sensitivity. That is, after recording what is known in a model, that model should be validated, explored using simulations, then summarized to find the key factors that most improve model behavior.

Improving Global Software Development Project Performance Using Simulation

Global software development (GSD) has become a dominant paradigm in the software industry. Conducting development projects in multiple countries offers many potential benefits including reduction in development cost and reduction in time-to-market especially trough the use of follow-the-sun strategy. However, GSD also poses challenges and difficulties due to geographic dispersion, time-zone differences as well as cultural and language differences. Thus, few GSD projects have been able to realize the full benefits of follow-the-sun development. This raises the question whether follow-the-sun strategy is the best way to pursue in order to reduce development time. What need to be done to ensure that the full benefits of follow-the-sun are achieved? In this paper, we described a hybrid simulation model of the software development process that is specifically architected to examine GSD projects. Then, we illustrated how project managers can use such model to support project planning and process improvement. We found that, in general, one should avoid using follow-the-sun strategy since it requires too much communication and coordination between sites, which resulted in higher effort and longer duration. If one is determined to use a follow-the-sun strategy, three development sites working in 24- hour cycle are needed in order to reduce cycle time.

Identifying key success factors for globally distributed software development project using simulation: a case study

With the increased pressure to reduce cost, reduce development time,and improve quality, many software companies are moving toward using aGlobally Distributed Software Development (GSD) paradigm. Due to the challengesand difficulties with GSD, researchers and practitioners are attempting toidentify key success factors for GSD projects. Based on our previous work, wefound that the key success factors can be different depending upon specific projectcharacteristics. To ensure a successful outcome, project managers have tofocus on the right success factors for their particular project. In this paper, weillustrate how a GSD simulation model can be used to represent a specific projectand to identify key success factors for that project. We use a case studyfrom an actual software development firm. We also perform sensitivity analysisto assess the magnitude of the performance impact for the key factors for thespecific project. For the case study site, which uses a combination of phasebasedand module-based task allocation strategies, we found that team memberfamiliarity, frequency of team meetings, and communication frequency eachhave a strong impact on total project effort and duration.

Exploring the impact of task allocation strategies for global software development using simulation

We describe a hybrid computer simulation model of the software development process that is specifically architected to study alternative ways to configure global software development projects, including phased-based, module-based, and follow-the-sun allocation strategies. The model is a hybrid system dynamics and discrete event model. In this paper, test cases have been developed for each allocation strategy, and project duration under each configuration is computed under a range of plausible assumptions for key parameters. The primary finding is that although under ideal assumptions, follow-the-sun is able to produce impressive reductions in time-to-market, under more realistic assumptions the reverse is true, thus corroborating findings by other researchers. Further analysis reveals the presence of some interaction between the assumptions, but the results remain robust.

Evaluating the impact of the QuARS requirements analysis tool using simulation

Adopting new tools and technologies on a development process can be a risky endeavor. Will the project accept the new technology? What will be the impact? Far too often the project is asked to adopt the new technology without planning how it will be applied on the project or evaluating the technologys potential impact. In this paper we provide a case study evaluating one new technology. Specifically we assess the merits of an automated defect detection tool. Using process simulation, we find situations where the use of this new technology is useful and situations where the use of this new technology is useless for large-scale NASA projects that utilize a process similar to the IEEE 12207 systems development lifecycle. The method can be applied to assessing the impact (including Return on Investment), break even point and the overall value of applying any tool on a project.

Using simulation to evaluate global software development task allocation strategies: Research Sections

Workflows emphasize the partial order of activities, and the flow of data between activities. In contrast, cooperative processes emphasize the sharing of artefact, and its gradual evolution toward the final product, under the cooperative and concurrent activities of all the involved actors. This article contrasts workflow and cooperative processes and shows that they are more complementary than conflicting and that, provided some extensions, both approaches can fit into a single tool and formalism. This article presents Celine, a concurrent engineering tool that can also define and support classic workflows and software processes. We claim that the availability of both classes of features allows for the modeling and support of very flexible processes, closer to software engineering reality. Copyright

Exploring the effect of vendor managed inventory on the supply chain partner using simulation

To manage supply chain efficiently and effectively, the members of the supply chain should collaborate and cooperate. It is known that information sharing and visibility are important factors that contribute to supply chain coordination. The visibility in real customer demand can help reduce the bullwhip effect, improve customer service, and reduce costs. Vendor managed inventory (VMI) is an approach that allows suppliers/vendors to access to their customers inventory and demand information. The benefits of VMI have been reported in many studies. However, the gain that each member of the supply chain realized could be different. Some studies show that upstream members benefit more than the downstream ones, while some studies show the opposite results. Therefore, some members of the supply chain are still reluctant to adopt the VMI practice since they are not sure whether the benefits gain will justify the costs incurred. In this paper, simulation model is used to explore the effect of VMI implementation on supply chain costs both on system-wide level and on member level. It was found that VMI helps reduce total supply chain costs. However, the level of cost reduction differs significantly among members depending on the types of the implementation. As a result, it is important to establish the level of investment required and benefit shared for each member before implementing VMI. The members that may experience less cost reduction should be offered higher benefit share (or required less investment). Otherwise, the whole supply chain may lose the opportunity to gain additional benefits from implementing VMI. In addition, the benefits gained from VMI also vary depending on supply chain environment. Simulation model can be used as a guiding tool for establishing appropriate investment and benefits sharing structure for VMI implementation in different supply chain conditions.

Using Simulation to Evaluate the Impact of New Requirements Analysis Tools

Summary form only given. Adopting new tools and technologies on a development process can be a risky endeavor. Will the project accept the new technology? What will be the impact? Far too often the project is asked to adopt the new technology without planning how it will be applied on the project or evaluating the technologys potential impact. In this paper we provide a case study evaluating one new technology. Specifically we assess the merits of an automated defect detection tool. Using process simulation, we find situations where the use of this new technology is useful and situations where the use of this new technology is useless for large-scale NASA projects that utilize a process similar to the IEEE 12207 systems development lifecycle. We also calculate the value of the tool when implementing at different point in the process. This can help project manager to decide whether it would be worthwhile to invest in this new tool. The method can be applied to assessing the impact (including Return on Investment), break even point and the over-all value of applying any tool on a project.