Reference No [13]: Extreme Programming explained: embrace change

This book does a great job of conveying the practices, principles and values of XP to its target audience. It all adds up to a very engaging book that acts as a great introduction to the Extreme Programming ethos. According to this book ,XP focuses particularly on the workgroup dynamics, and leaves out discussion of some surrounding bits that are none the less necessary (like "release planning"), which is why the most popular Agile style is widely quoted as "XP plus Scrum. This source provides an insight into the agile based development. Reference No [17]: Agile software development, Alistair Cockburn This book discusses about the basics of agile development. According to this source It's more of a process, than a strict set of rules .The goal of Agile is to make working software that meets customer specification as quickly as possible in tested iterative cycles, each cycle setting up the next cycle for a win-win game-play. There is a fine balancing act of keeping the procedures and methodologies pared back to get things done in a systematic way without getting in the way of getting software done. Cockburn explains the whys of Agile by blending his experiences, anecdotal evidence, cited references, interviews spanning years and analogies. He makes it very clear that people at the center of any project. And people need to communicate. A good deal of the book examines how to improve communication between everyone involved in the project. Reference No [23]: Agent-based simulation of open source evolution, Journal of Software Process Improvement and Practice This reference present an agent-based simulation model developed to study how size, complexity and effort relate to each other in the development of open source software (OSS). In the model, many developer agents generate, extend, and re-factor code modules independently and in parallel. These accords with empirical observations of OSS development. Validation of the model was done by comparing the simulated results against four measures of software evolution (system size, proportion of highly complex modules, level of complexity control work, and distribution of changes) for four large OSS systems. The simulated results resembled the observed data, except for system size: three of the OSS systems showed alternating patterns of superlinear and sublinear growth while the simulations only produced superlinear growth. Reference No [25]: Software complexity: Measures and methods This reference discusses about various issues related to Software complexity measure. The characterization of measure of McCabe as an ordinal scale and as a ratio scale has been described in this source. The use of McCabes cyclometric number has been explained and the researchers used the same as the measurement of complexity in their study.

Reference No [28]: Practical code inspection techniques for object-oriented systems: an experimental The author referred to this source for identifying the problems inspecting object oriented code. In this reference it is discussed that hierarchies. The inspection of OO code and an industrial survey3 have noticed that many hard to find defects in OO code share this same characteristic the information required to understand the defect is distributed throughout the system. They have termed this characteristic delocalization, after the description by Elliott Soloway and his colleagues of delocalized plans in program comprehension. The researchers used this reference to find out one of the threats to the validity of their study.