Since last four to five years the buzz of continuous growing of agile development has been spread all around the world, specially Extreme Programming as the most important methodology of this kind. From the other side, ISO 9001:2000-TickIT Guide 5.0 has been established mainly in Europe as one of the well-known Quality Management Systems, in order to create a continuous software process improvement throughout software organizations that is mainly related to a certi¯cation process. This thesis is developed to mainly answer the question of how Extreme Programming and the standard ISO 9001:2000 with its interpretation for software development as TickIT Guide 5.0 can be used together, in order to have a continuous software process improvement with the agility to respond quickly to environment changes and satisfy the customer needs and expectations.

Litteratur inom systemutvecklingsområdet visar behov av nya snabbare systemutvecklingsmetoder. Orsaken är komplexiteten både i systemutvecklingsprojekten och i organisationer, där systemutveckling sker. Nu föredras små projekt, som omfattar färre än tio deltagare och genomförs på mindre än ett år. De traditionella systemutvecklingsmetoder anses vara lämpliga för stora projekt. Det finns nya systemutvecklingsmetoder, som får benämningen dynamiska metoder, för små projekt. I detta examensarbete studeras faktorer för två dynamiska metoder som gör dem lämpliga för små projekt. De två dynamiska metoderna som kommer att studeras är Extreme Programming och en specifik dokumenterad anpassning av RUP. Syftet med detta examensarbete är att studera metoddokumentationen för två dynamiska metoder för att reda ut i vilken utsträckning de passar för små projekt. Ett ytterligare syfte är att genom analys av andras erfarenheter om tillämpningar av de två metoderna redogöra för det som styrker argumenten om deras lämplighet för små projekt. För att besvara frågeställningen studerades litteratur och ett antal artiklar. Två telefonintervjuer genomfördes också för att besvara en av de två delfrågorna, som tillsammans utgör frågeställningen för denna studie. Resultatet visar att den specifikt dokumenterade anpassade RUP inte följer alla aspekter för små projekt. Däremot följer Extreme Programming alla de aspekterna.

With the advent of shorter time to market of software products there an increasing requirement for techniques and methods to improve the productivity levels in software development together with a requirement for increased flexibility and the introduction of late changes. This in turn has lead to the introduction of a set of techniques known as ―Agile methods which include one methodology known as ―eXtreme Programming. This is a collection of values, principles, and practices. Since these methods are becoming more common in industry, is has become more important to introduce these ideas in the undergraduate curriculum. This case study analysed whether or not it is possible to teach eXtreme Programming at a university by means of a course that presents a mixture of theory and practice within eXtreme programming. In this context, a case study was carried out to determine which of the practices of eXtreme Programming are more appropriate to university projects. The case study indicates that it is worth investing the effort to teach eXtreme Programming to students to enable them to apply eXtreme Programming or at least some of its practices in future business and university projects.

In this thesis, we tried to solve those problems by adapting agile development methods with Non-functional requirements-framework (NFR-Framework). In this thesis, we have inspected many research papers, and we have met industrial experts for feedback regarding our theoretical results. As a result of the inspection, we have been able to adapt agile development methods (extreme programming (XP)) with NFR-framework. We use XP since it is more practically oriented process than other agile development methods. In the first try for this process model, we got three alternatives for applying it. The first one is based on collecting all NFRs from the beginning of the development process. The second one is based on updating the SIG (software interdependency graph) every time we have new functional requirements (FR) and the third one is based on the incremental nature of agile development methods. Each one of these alternatives has it is own advantages and disadvantages. We tried to extract those advantages and disadvantages by brainstorming and reading research papers. The most important issue in all of the three alternatives is the applicability. Finally we got industrial feedback regarding all of them. As a result of the industrial feedback, we were able to find another alternative of how to apply the process model which is presented in 7.2.

This master thesis deals with choice of appropriate approach to software development. The thesis specifies currently used approaches of project management. Current project status and approaches are analysed. The thesis focuses on choice of method and its application in the project.

This study set out to determine various aspects of the agile approaches to software development. These included an investigation into the principles and practices driving these methodologies; determining the applicability of these approaches to the current software development needs; determining whether these methodologies can comply with software engineering standards (as set out for example by ISO); investigating the feasibility of these approaches for the telecommunication industry; establishing whether practitioners are reaping the benefits that are advertised by agile proponents; and attempting to discover short-comings of the agile paradigm. This dissertation examines the aforementioned issues and tries to provide answers to them. It is argued that: Agile software development is suited to projects where the system evolves over the life cycle of the project. These methodologies are intended to seamlessly handle changing requirements. Thus, using an agile approach might provide a competitive advantage in developing e-business solutions which are tightly coupled with the business strategy and needs. It is shown that agile methodologies can comply with software engineering standards such as ISO 12207:1995 and ISO 15288:2002. Furthermore diligent application of certain agile methodologies may result in a level 3 Capability Maturity Model (CMM) grading. Evidence from the feedback of a case study conducted on an XP project team, supports the view that XP, and agile in general, does indeed live up to its 'promises'. However, some potential problem areas were identified that should be kept in mind when implementing these methodologies. Finally, an in situ investigation suggests that there are a number of projects in the telecommunication industry that will benefit from the agile approach and its practices. / Dissertation (MSc)--University of Pretoria, 2005. / Computer Science / unrestricted

Refactoring is the process of transforming the internal structure of existing code while keeping the integrity of the code's functional requirements. Refactoring is proven to increase program maintainability, flexibility, and understandability and is recognized as a best practice in the software development community. However, with the exception of courses or lectures on extreme programming, refactoring is overlooked in the computer science curriculum. This paper helps demystify refactoring by introducing an incremental approach for teaching refactoring on the college level. Through this hands-on approach, refactoring can become an integral component in the computer science curriculum and an innovative means of reinforcing software engineering principles and good development practices. The approach and three introductory lessons are presented in this paper.

Refactoring is the process of transforming the internal structure of existing code while keeping the integrity of the code's functional requirements. Refactoring is proven to increase program maintainability, flexibility, and understandability and is recognized as a best practice in the software development community. However, with the exception of courses or lectures on extreme programming, refactoring is overlooked in the computer science curriculum. This paper presents the fourth lesson of an innovative pedagogical approach to teaching refactoring on the college level. This lesson covers the creation of well formed object-oriented methods including characteristics for evaluating such methods. Through this hands-on approach, building well formed object-oriented methods through refactoring can be better understood and integrated into the computer science curriculum.

No description available.

[pt] O trabalho a seguir apresenta uma proposta de metodologia de gerência de projetos de software aderente a pequenos projetos e fortemente inspirada em metodologias já consagradas como Unified Process e eXtreme Programming. O objetivo é prover um processo ágil, adaptável porém prescritivo. Chegaremos a um processo de fácil implantação e controle e menos dependente da qualidade técnica da equipe de desenvolvimento. A seguir, será apresentado um estudo de caso conduzido em ambiente real, por uma equipe de um pequeno empreendimento que consiste no relato do processo de amadurecimento e implantação do processo proposto, com uma análise do trabalho de implantação de processos de desenvolvimento em empreendimentos emergentes na área de TI. / [en] The following work presents a proposal of software project management methodology applicable to small projects and strongly inspired by already well established methodologies such as the Unified Process and eXtreme Programming. The objective of this proposal is to provide an agile process that is adaptable yet prescriptive. Through this one plans to arrive at a process of easy implementation and control, and less dependent on the technical quality of the development team. Subsequently, a case study will be presented that was conducted in a real environment, on a small enterprise development team. It consists of a report on the maturing and implementation of the proposed process and an analysis of the work of implementing development procedures in emerging enterprises in the IT area.