There aren't any silver bullets in software development, and there probably never will be. However, Extreme Programming is a simple set of common-sense practices that, when used together, really can give you much of what you just read in the paragraph above. In this book, we tell you what the XP practices are, and how to install them in your project.

Introduction The natural evolution of any new area of consulting includes the appearance of methodologies for problem-solving. If Knowledge Management (KM) is the answer to questions about how to capture tacit knowledge, or accelerate innovation, or share knowledge, or resolve cultural incompatibilities in business processes, then this answer is not really operative until we can apply KM knowledge in such a way as to provide practical, concrete solutions for specific business problems. This need naturally gives rise to the development of recipes, guidelines, and procedures for problem solving, called KM process methodologies, and even to particularly comprehensive methodologies called KM "Life Cycle Methodologies." (LCMs) Life Cycle methodologies are those that specify a linear sequential stepwise process composed of phases that are themselves composed of tasks and activities employing methods. Methods are procedures that detail the "how to's" of arriving at a valued result.

Abstract. The Pedagogical Patterns Project began at OOPSLA '95 and started holding workshops in 1996 at the ECOOP, TOOLS and OOPSLA conferences. The aim of the project has been to capture successful experiences in teaching and learning OT, from industry or academia, in a homogeneous, easily-accessible format. Patterns have been regarded as an effective method for achieving this. Since 1996, many other sessions have been held at numerous conferences in America and Europe, resulting in the collection of more than 50 teaching techniques written in pattern format. As this present collection is now being refined and expanded, educators are discovering the effectiveness of sharing their teaching experiences in the form of pedagogical patterns. Why Pedagogical Patterns are needed Most educators and trainers are not taught how to teach. Rather, they often find themselves teaching by accident. Typically, a person with a skill that is in demand, such as a particular programming language, will be asked to teach it. People assume that if the person is good in this programming language, she will be good at teaching it. But knowing the subject matter is very different than knowing how to teach it.

Current software projects have generally to deal with producing and managing large and complex software products. It is generally believed that applying software development methods are useful in coping with this complexity and for supporting quality. As such numerous object-oriented software development methods have been defined. Nevertheless, methods often provide a complexity by their own due to their large number of artifacts, method rules and their complicated processes. We think that automation of software development methods is a valuable support for the software engineer in coping with this complexity and for improving quality. This paper presents a summary and a discussion of the ideas that were raised during the workshop on automating object-oriented software development methods. 1.

In this study we trace the effects of applying the techniques of refactoring and aggressive unit testing in source code based on historical information. We show how their impact on the evolution of the architecture can be testified. The study comprises the analysis of a large number of indiv idual integration versions of a large framework. The method described here can help development teams find weaknesses in their application of the two traced techniques.

This paper describes a multi-year research and development effort for a knowledge management system. We first describe the need for communication support between Knowledge Acquisition (KA) and Software Development (SD), as motivated by our software engineering experiences, including the Rotorcraft Pilot's Associate and its utility of Cognitive Decision Aiding Systems (CDASs). Technology exists to capture knowledge; putting it into a useful, accessible format for requirements definition and later SD lags behind.

Extreme Programming (XP) is a new software development method (SDM) that claims to be superior to other methods in some situations that are characterised by vague requirements and rapid change. XP has quickly gained a remarkable degree of acceptance in parts of the software engineering community. Interestingly, it has provoked a vivid and often controversial exchange of opinions, ranging from enthusiastic support to vigorous criticism. In this paper we look at possible sources of such fundamental disagreement. We use general systems theory as an integrative theoretical framework to analyse SDMs and expose their underlying, often implicit assumptions. We discuss some examples where the assumptions made by XP are fundamentally different from the assumptions made by most other SDMs. These fundamentally different assumptions indicate fundamentally different mental models. Mental models are central to systems thinking because they have a strong influence on our perception of reality and our behaviour. If they act as unconscious filters that limit our perception to what we expect, they can seriously impede our ability to learn. We conclude that mental models play a crucial role in the introduction of XP. 1.

The literature on Object-Oriented software development processes has proposed a lifecycle which is often found to be at odds with the established software engineering processes of organizations. In particular, more established software engineering processes at higher CMM (Capability Maturity Model) levels often have deep roots in the ‘Waterfall ’ lifecycle Some of these mature processes might be evolving into legacy processes. The emerging Software Engineering Body of Knowledge (SWEBOK) is more appropriate than the Project Management Body of Knowledge (PMBOK) as a course of study for potential project managers of software projects. PMBOK has a tendency to emphasize scope management and task decomposition, while SWEBOK focus on requirements analysis and architectural design. Recent developments in Object-Oriented software engineering assert that an emphasis on requirements rather than scope, and on architecture rather than tasks leads to superior software development processes. Specifically, organizations should not demand detailed fixed scope, cost and schedule plans at the beginning of a significant software development effort. There is a lesson to be learn from the building industry, which allocates up to half of the overall development time to architectural design, and does not create a controlled project environment until the construction phase. When developing e-commerce applications, requirements analysis and system architecture remain critical, but they should be expanded to a broader context. The business plan replaces a project plan in e-commerce; marketing (and even sales) drive requirements analysis; and architectural design should be broadened to include infrastructure design. E-commerce system design encompasses system-wide issues, including hardware, networks, purchased components and partnerships, as well as interfaces with back-end fulfillment and collection capabilities.

Prior to the use of Agile Methodologies in software industry, the software projects were chaotic and unpredictable. As a result the processes which are best suited for well-defined problem domains cannot manage such software projects. It had been seen that with highly detailed user interface designs, specifications and plans, the software developed turned out different from its original intent because customer requirements change frequently. The crux of Agile Methodologies is that the changes in the requirement can be managed software even during the development cycle of the software development. A survey of 18 SMEs catering software market has been carried out for finding software development scenarios. Eight Agile Methodologies had been studied and surveyed which I found effective in current scenario of software development. These are Extreme