Software Process Modeling With System Dynamics

Raymond J. Madachy

Language: English

Pages: 626

ISBN: 2:00011437

Format: PDF / Kindle (mobi) / ePub


Preview
This book is designed for professionals and students in software engineering or information technology who are interested in understanding the dynamics of software development in order to assess and optimize their own process strategies. It explains how simulation of interrelated technical and social factors can provide a means for organizations to vastly improve their processes. It is structured for readers to approach the subject from different perspectives, and includes descriptive summaries of the best research and applications.
---
Alt. ISBN:0471274550, 0471274550, 9780471274551

Uncovering African Agency: Angola's Management of China's Credit Lines

Professional Visual Studio 2012

PHP in a Nutshell

Pro PHP MVC

 

 

 

 

 

 

 

 

 

 

 

Goals are defined in terms of purpose, perspective, and environment using the generic templates as follows: Purpose. {To characterize, evaluate, predict, or motivate} {the process, product, model, or metric} in order to {understand, assess, manage, engineer, learn, or improve it}. Perspective. Examine the {cost, effectiveness, correctness, defects, changes, product metrics, or reliability} from the point of view of the {developer, manager, customer, or corporate perspective}. Environment. The environment consists of the following: process factors, people factors, problem factors, methods, tools, and constraints The questions quantify the goals as completely as possible within the context of the development environment.

10 Rayleigh Curve Generator 185 3. 4. 11 Attribute Tracking 186 3. 4. 12 Attribute Averaging 187 3. 4. 13 Effort Expenditure Instrumentation 187 3. 4. 14 Decision Structures 188 3. 5 Software Process Chain Infrastructures 192 3. 5. 1 Software Products 193 3. 5. 2 Defects 196 3. 5. 3 People 200 3. 6 Major References 203 3. 7 Chapter 3 Summary 204 3. 8 Exercises 204 PART 2 APPLICATIONS AND FUTURE DIRECTIONS Introduction to Applications Chapters 211 Chapter 4 People Applications 217 4.

Figure 2. 41 shows the model runs for step increases of 1 person for 10 days and 0. 5 persons for 20 days (anything shorter will largely resemble the pulse). The first trendline is the pulse of 10 people, the second is the 10 day step increase, and the third is the 20 day step increase. Another parameter to vary is the assimilation rate. Values of 20, 40, and 60 days will be used (these represent 1, 2, and 3 working months, respectively). Since the base run has no personnel allocation, these changes will have no impact to it.

The point of stopping is also tied to the question of model validity described in Section 2. 8. 1. 2. 10. 5 Example: Model Improvement Next Steps The Brooks’s Law model described so far is based on simplified assumptions and has certain limitations. The following enhancements would improve usage of the model: ț Add a stop to the simulation when all requirements are developed. This will prevent the model from running overtime. ț Make the model scalable for larger team sizes up to 60 people to overcome the current restriction on maximum team size.

44. Monte Carlo results: effort distribution. system that was gained during the modeling exercise iterations. The final result of policy analysis is identifying policies that are actually implemented on projects. The term policy analysis has long been used in the system dynamics community. In software process improvement, processes are typically defined by a combination of policies, procedures, guidelines, and standards. A policy in this context generally states what has to be done, and the rest of the artifacts provide details of how.

Download sample

Download

Rated 4.06 of 5 – based on 29 votes