共查询到19条相似文献,搜索用时 62 毫秒
1.
软件危机几乎一直伴随着软件开发的整个历史,对于大型软件项目,它造成的危害更大。正是在此背景下,软件工程和面向对象技术得以产生和发展。作为面向对象的基础,设计模式为可复用面向对象软件开发指明了一条道路。敏捷软件开发和极限编程则作为面向对象的进一步发展而出现,成为近年来软件开发方法学研究的热点。 相似文献
2.
设计模式思想在构建软件框架过程中应用的探讨 总被引:2,自引:0,他引:2
许多文章在谈及设计模式和框架的关系时,多讨论它们之间的区别。而文中在介绍它们的区别之外,更多地是从设计模式提炼出的四个思想这个角度,以框架的含义为基础,来论述它们在软件设计上的联系,并针对这四个思想,逐一探讨了在软件项目开发过程中如何应用来构建软件框架。虽然这四个思想不是构件框架的全部思想,但无疑它们也是构件框架思想中不可或缺的。很好地应用这四个思想,将会提高框架的设计水平,增强框架的重用性。 相似文献
3.
作为一种重要的敏捷软件开发方法,极限编程提供了一个周密严谨的软件开发流程。该文给出了XP软件开发方法的由来及主要特征,并通过软件项目实例指出XP是解决科研软件开发中诸多问题的很好的方法。 相似文献
4.
5.
关于极限编程理论的研究 总被引:1,自引:0,他引:1
极限编程(XP)是敏捷软件开发方法的代表。它在提高软件质量、确保开发进度等方面取得了显著的效果,为促进沟通、激发程序员在开发中的潜力提供了有力的手段。本文在学习和研究XP理论的基础上,分析了XP的各项核心的应用,提出几点建议。 相似文献
6.
敏捷方法是一种面临迅速变化的需求快速开发软件的新开发方法,这种方法以快捷、轻便的思维方式,迅速解决了一些传统软件开发企业的生产效率问题,得到了迅速的推广。介绍了敏捷软件过程与极限编程的主要内容,并以一个债权管理系统的开发为例,展示了其实际应用过程。 相似文献
7.
"极限编程"(eXtreme Programming,简称XP)是目前最流行的敏捷软件开发方法(Agile Software Development,ASD).通过XP在实际项目中的应用"实践",本文将对XP的理论和实践方法进行探讨,并衡量XP方法在项目中的应用效果,给出实际应用XP方法的一些建议. 相似文献
8.
“极限编程”(extreme Programming.简称XP)是目前最流行的敏捷软件开发方法(Agile Software Development,ASD)。通过XP在实际项目中的应用“实践”,本文将对XP的理论和实践方法进行探讨.并衡量XP方法在项目中的应用效果,给出实际应用XP方法的一些建议。 相似文献
9.
极限编程在软件项目开发中的应用已经十分普遍,并随着信息技术的不断发展而深入到了社会的各个行业之
中。如何通过极限编程来提高软件的开发效率,使软件更加贴合用户需求,是当前值得研发人员思考的问题。本文主要分析
了极限编程的概念和原则,并对软件开发中极限编程的过程和实践进行探讨,以期为软件开发行业的壮大提供一些有益的经
验。 相似文献
10.
11.
12.
《Information and Software Technology》2014,56(8):911-921
ContextAgile software development is an alternative software development methodology that originated from practice to encourage collaboration between developers and users, to leverage rapid development cycles, and to respond to changes in a dynamic environment. Although agile practices are widely used in organizations, academics call for more theoretical research to understand the value of agile software development methodologies.ObjectiveThis study uses shared mental models theory as a lens to examine practices from agile software methodologies to understand how agile practices enable software development teams to work together to complete tasks and work together effectively as a team.MethodA conceptual analysis of specific agile practices was conducted using the lens of shared mental models theory. Three agile practices from Xtreme Programming and Scrum are examined in detail, system metaphor, stand-up meeting, and on-site customer, using shared mental models theory.ResultsExamining agile practices using shared mental models theory elucidates how agile practices improve collaboration during the software development process. The results explain how agile practices contribute toward a shared understanding and enhanced collaboration within the software development team.ConclusionsThis conceptual analysis demonstrates the value of agile practices in developing shared mental models (i.e. shared understanding) among developers and customers in software development teams. Some agile practices are useful in developing a shared understanding about the tasks to be completed, while other agile practices create shared mental models about team processes and team interactions. To elicit the desired outcomes of agile software development methods, software development teams should consider whether or not agile practices are used in a manner that enhances the team’s shared understanding. Using three specific agile practices as examples, this research demonstrates how theory, such as shared mental models theory, can enhance our understanding regarding how agile practices are useful in enhancing collaboration in the workplace. 相似文献
13.
基于C/S的软件体系结构研究 总被引:2,自引:0,他引:2
面向对象的技术为人们带来了无限希望和与软件危机做斗争的工具。该文介绍了以面向对象的技术为基础,以软件体系结构为核心的软件开发过程,描述了如何从软件体系结构的观点去考虑C/S系统,以达到最大限度的设计复用。 相似文献
14.
Agile methods rapidly replacing traditional methods at Nokia: A survey of opinions on agile transformation 总被引:2,自引:0,他引:2
Context
Many organizations have started to deploy agile methods, but so far there exist only a few studies on organization-wide transformations. Are agile methods here to stay? Some claim that agile software development methods are in the mainstream adoption phase in the software industry, while others hope that those are a passing fad. The assumption here is that if agile would not provide real improvement, adopters would be eager at first but turn pessimistic after putting it into practice.Objective
Despite the growing amount of anecdotal evidence on the success of agile methods across a wide range of different real-life development settings, scientific studies remain scarce. Even less is known about the perception of the impacts of agile transformation when it is deployed in a very large software development environment, and whether agile methods are here to stay. This study aims to fill that gap by providing evidence from a large-scale agile transformation within Nokia. While we have yet to confirm these findings with solid quantitative data, we believe that the perception of the impacts already pinpoints the direction of the impacts of large-scale agile transformation.Method
The data were collected using a questionnaire. The population of the study contains more than 1000 respondents in seven different countries in Europe, North America, and Asia.Results
The results reveal that most respondents agree on all accounts with the generally claimed benefits of agile methods. These benefits include higher satisfaction, a feeling of effectiveness, increased quality and transparency, increased autonomy and happiness, and earlier detection of defects. Finally, 60% of respondents would not like to return to the old way of working.Conclusion
While the perception of the impact of agile methods is predominantly positive, several challenge areas were discovered. However, based on this study, agile methods are here to stay. 相似文献15.
16.
17.
Nien-Lin Hsueh Author Vitae Peng-Hua Chu Author Vitae 《Journal of Systems and Software》2008,81(8):1430-1439
In recent years, the influence of design patterns on software quality has attracted an increasing attention in the area of software engineering, as design patterns encapsulate valuable knowledge to resolve design problems, and more importantly to improve design quality. As the paradigm continues to increase in popularity, a systematic and objective approach to verify the design of a pattern is increasingly important. The intent session in a design pattern indicates the problem the design pattern wants to resolve, and the solution session describes the structural model for the problem. When the problem in the intent is a quality problem, the structure model should provide a solution to improve the relevant quality. In this work we provide an approach, based on object-oriented quality model, to validate if a design pattern is well-designed, i.e., it answers the question of the proposed structural model really resolves the quality problems described in the intent. We propose a validation approach to help pattern developers check if a design pattern is well-designed. In addition, a quantitative method is proposed to measure the effectiveness of the quality improvement of a design pattern that pattern users can determine which design patterns are applicable to meet their functional and quality requirements. 相似文献
18.
This paper describes an Essential Software Framework for Meshfree Methods (ESFM). Through thorough analyses of many existing meshfree methods, their common elements and procedures are identified, and a general procedure is formulated into ESFM that can facilitate their implementations and accelerate new developments in meshfree methods. ESFM also modulates performance-critical components such as neighbor-point searching, sparse-matrix storage, and sparse-matrix solver enabling developed meshfree analysis programs to achieve high-performance. ESFM currently consists of 21 groups of classes and 94 subclasses, and more algorithms can be easily incorporated into ESFM. Finally, ESFM provides a common ground to compare various meshfree methods, enabling detailed analyses of performance characteristics. 相似文献