agilesoftware development methodologies provide a significant improvement on the control and management of the software development process. Literature gives evidence of improvement in areas like development of softw...
ISBN:
(纸本)3540221379
agilesoftware development methodologies provide a significant improvement on the control and management of the software development process. Literature gives evidence of improvement in areas like development of softwarethat meets the user requirements, delivery of the product on time and within budget. Withthe growing number of agile methodologies the selection of a methodology that is suitable for a particular project becomes a nontrivial issue. this research work aims at devising a mechanism that can be used by practitioners to select the most suitable agile methodology for a given software development project. the literature survey done so far reveals that whilst those who have used agile methods have made significant benefits, there is a lot of apprehensiveness and uncertainty about the use of agile methods in the IT industry. this uncertainty is due to the lack of literature on the representation of agile methods and the lack of empirical data on the use of agile methods. the literature also shows that due to these gaps there is also a lack of ways of selecting the appropriate methodology for a given project.
this paper presents a solution for saving large systems from increasing entropy. the solution is proven on a large middleware platform giving good results. the method's objective is to rework the system so that re...
详细信息
ISBN:
(纸本)3540221379
this paper presents a solution for saving large systems from increasing entropy. the solution is proven on a large middleware platform giving good results. the method's objective is to rework the system so that reengineering investments pays off. Reaching agile practices is the methods basis. In order to reach the objective the method cynically relies on measurements to find unwanted characteristics of the system. Subjective opinions due to ownership and politics are ignored in the method. An extensive open source tool, the Cosmos Radar, is given to the community to make these measurements. Various symptoms and measurements are identified and approaches to solutions are discussed.
One of the main requirements of extremeprogramming (XP) is to do unit testing be a critical task of the daily development routine of a programmer. Our work aims at contributing to make easier the actual practice of t...
详细信息
ISBN:
(纸本)3540221379
One of the main requirements of extremeprogramming (XP) is to do unit testing be a critical task of the daily development routine of a programmer. Our work aims at contributing to make easier the actual practice of this requirement in the framework of distributed computer-supported cooperative work (CSCW) and in an education context. the proposed XP test environment is used as a basic mechanism for structuring the XP process in a distributed context. As an experimental prototype, we propose a Junit and JML based unit testing environment as an extension of the BlueJ Interactive Environment.
What is special about XP teams? Adopting XP involves social change as well as technical change, but what characterises a successful team? What happens when a team takes on the 12 practices and four underlying values? ...
详细信息
ISBN:
(纸本)3540221379
What is special about XP teams? Adopting XP involves social change as well as technical change, but what characterises a successful team? What happens when a team takes on the 12 practices and four underlying values? this paper contributes empirical findings that help answer such questions. We expand on previous work that suggested four characteristics of an XP team by analysing the data from boththe previous study and from a further study of another mature XP team. While there are clear differences between the two teams in terms of operating environment, their detailed implementation of the 12 practices and the team's overall character, we find that the four characteristics are present in both teams. the paper describes the characteristics in detail and discusses how those characteristics are embedded in the detail of the practices of XP as observed in the two particular settings.
None of the agile methods are claimed to fit all development situations. A team should attempt to adapt the methods and practices to fit their specific needs. For that reason agile principles call for self-reflection ...
详细信息
ISBN:
(纸本)3540221379
None of the agile methods are claimed to fit all development situations. A team should attempt to adapt the methods and practices to fit their specific needs. For that reason agile principles call for self-reflection on a regular basis in order to identify where and how to make improvements. While some systematic approaches on how to execute this self-reflection process effectively have already been proposed, little empirical evidence currently exists. this paper reports empirical results based on a study where a project team conducted a self-reflection process called "post-iteration workshop" in order to improve and optimize the adopted practices in an XP project. Both qualitative and quantitative data were collected from four 1-2 hour workshops. the results show that with less than 4% effort it is possible to hold post-iteration workshops that significantly help to improve and optimize practices and enhance the leaming and satisfaction of the project team.
Since the software crisis of the 1960’s, numerous methodologies have been developed to impose a disciplined process upon software development. Today, these methodologies are noted for being unsuccessful and ...
详细信息
ISBN:
(纸本)3540221379
Since the software crisis of the 1960’s, numerous methodologies have been developed to impose a disciplined process upon software development. Today, these methodologies are noted for being unsuccessful and unpopular due to their increasingly bureaucratic nature. Many researchers and academics are calling for these heavyweight methodologies to be replaced by agile methods. However, there is no consensus as to what constitutes an agile method. An agile Manifesto was put forward in 2001, but many variations, such as XP, SCRUM and Crystal exist. Each adheres to some principles of the agile Manifesto and disregards others. My research proposes that these principles lack grounding in theory, and lack a respect for the concept of agility outside the field of Information Systems Development (ISD). this study aims to develop a comprehensive framework of ISD agility, to determine if this framework is adhered to in practice and to determine if such adherence is rewarded. the framework proposes that it is insufficient to just accept agile methods as superior to all others. In actual fact, an ISD team have to identify whether they need to be agile, and to compare this to their agile capabilities before deciding how agiletheir eventual method should be. Furthermore this study proposes that an agile method is not just accepted and used. Rather it may be selected from a portfolio of methods, it may be constructed from parts of methods, or indeed it may be the product of the ISD team’s deviation from a different method altogether. Finally, this study recognises that agility does not simply come from a method. In actual fact, a cross-disciplinary literature review suggests that it is important to classify sources of agility, which could be the people on team, the way they are organised, the technology they use or the external environment with which they interact. A three phase research method is adopted, incorporating a set of pilot interviews, a large-scale survey and
Roles' playing is common in our lives. We play different roles with our family, at work as well as in other environments. Role allocation in software development projects is also accepted though it may be implemen...
详细信息
Roles' playing is common in our lives. We play different roles with our family, at work as well as in other environments. Role allocation in software development projects is also accepted though it may be implemented differently by different software development methods. In a previous work [Y. Dubinsky, O. Hazzan, Roles in agilesoftware development teams, in: 5th International conference on extremeprogramming and agileprocesses in softwareengineering, 2004, pp. 157-165] we have found that personal roles may raise teammates' personal accountability while maintaining the essence of the software development method. In this paper we present our role scheme, elaborate on its implementation and explain how it can be used to derive metrics. We illustrate our ideas by data gathered in student projects in the university. (C) 2006 Elsevier B.V. All rights reserved.
agile development and software reuse are both recognized as effective ways of improving time to market and quality in softwareengineering. However, they have traditionally been viewed as mutually exclusive technologi...
详细信息
ISBN:
(纸本)9783540731009
agile development and software reuse are both recognized as effective ways of improving time to market and quality in softwareengineering. However, they have traditionally been viewed as mutually exclusive technologies which are difficult if not impossible to use together. In this paper we show that, far from being incompatible, agile development and software reuse can be made to work together and, in fact, complement each other. the key is to tightly integrate reuse into the test-driven development cycles of agile methods and to use test cases - the agile measure of semantic acceptability - to influence the component search process. In this paper we discuss the issues involved in doing this in association withextremeprogramming, the most widely known agile development method, and extreme Harvesting, a prototype technique for the test-driven harvesting of components from the Web. When combined in the appropriate way we believe they provide a good foundation for the fledgling concept of agile reuse.
this research explored aspects of agile teamwork initiatives associated with positive socio-psychological phenomena, with a focus on phenomena outside the scope of traditional management, organizational, and software ...
详细信息
ISBN:
(纸本)9783540731009
this research explored aspects of agile teamwork initiatives associated with positive socio-psychological phenomena, with a focus on phenomena outside the scope of traditional management, organizational, and softwareengineering research. agile teams were viewed as complex adaptive socio-technical systems. Qualitative grounded theory was used to explore the socio-psychological characteristics of agile teams under the umbrella research question: What is the experience of being in an agilesoftware development team ? Results included a deeper understanding of the link between agile practices and positive team outcomes such as motivation and cohesion.
Current practice suggests that security is considered through all stages of the software development life cycle, and that a risk-based and plan-driven approach is best suited to establish security criteria. Based on e...
详细信息
ISBN:
(纸本)9783540731009
Current practice suggests that security is considered through all stages of the software development life cycle, and that a risk-based and plan-driven approach is best suited to establish security criteria. Based on experience in applying security practices, this paper proposes two new security practices, security training and a fundamental security architecture, for applying extremeprogramming.
暂无评论