基于MVC模式的STRUTS框架的研究与应用

一个好的软件设计框架能有效的理清系统结构，降低系统复杂度。基于MVC模式的Struts框架，对复杂的Web应用系统开发是较为理想的系统构建方式。文章结合笔者开发大型国资管理系统的实践，介绍Struts框架的体系结构以及基本设计思想．同时给出一个用户登陆实例，介绍了如何利用Struts技术开发基于MVC的Web应用。进一步揭示了Struts是一个高度可配置、高度扩展性的框架，并特别指出Struts框架在开放大型Web应用方面发挥的优势。     

基于Struts框架的Web应用设计与实现

随着面向对象技术和Web技术的发展,软件框架技术在Web开发中得到了广泛应用。Struts作为一个开源的Web层框架,是MVC及J2EE若干核心模式的标准实现,方便了代码的编写和管理,适用于大型、复杂的Web应用开发。讨论了Struts框架的工作原理,提出了一种基于Struts框架的Web应用软件设计方法（Struts＋proxy＋DAO）,并结合具体开发实例对架构的实现过程进行了详细描述。实践证明,基于Struts＋proxy＋DAO的Web应用系统具有很好的灵活性和易维护性。     

Struts框架Web应用的国际化

一个好的框架对于软件的开发是至关重要的。Struts是当前Web应用开发中最为优秀的框架之一。简要介绍了本地化与国际化的概念，Java和Struts框架对web应用国际化的支持，并讲述了创建Struts的ResourceBundle和Struts应用中访问ResourceBundle的各种途径。     

基于MVC设计模式的Struts框架及其应用的研究

Struts是基于MVC设计模式的非常优秀的Web应用框架，在Web应用开发中很好地将显示和逻辑分离，提高了代码的可重用性和灵活性。文中首先分析了Struts框架结构及其对Model，View和Controller层的实现原理，并总结了Struts框架的优点，然后给出了采用Struts框架的一个应用实例的实现过程，在应用实例业务逻辑的实现过程中采用了Jbas技术，实现Java代码与数据库操作代码（SQL语句）的分离。     

利用Struts框架进行Web应用开发的研究

Struts是一个用于开发Web应用程序的概念框架,它是Apache软件基金会Jakarta项目的一部分.Struts已经成为了用Java创建Web应用的一个最流行的框架工具,它所实现的MVC模式给Web应用带来了良好的层次划分,同时也提供了一系列的工具来简化Web应用的开发.该文就Struts框架所涉及的技术要点进行了分析,并结合一个具体的应用程序对如何用Struts进行Web应用开发进行了探索研究.     

基于MVC模式和Struis框架的Web应用研究与实现

首先简要介绍MVC设计模式和Struts工作原理,然后通过一个Web公文管理系统实例论述了基于MVC模式Struts框架的Web应用系统的实现方法。通过实例论述基于Struts框架开发的大型Web信息管理系统可获得较好的可重用性、可扩展性和易维护性。     

Struts框架的研究与应用

Struts是当前Web应用开发中最为流行的框架之一。它提供了一个非常好的MVC框架，在Web应用开发中把界面和业务逻辑分离，提高了代码的可重用性和灵活性，便于组件式开发。文章简要介绍了MVC(Model／View／Controller)设计模式和Struts框架的体系结构和工作原理，然后结合一个实例，讲述了Struts实现MVC模式web应用的过程。结果显示Struts能够大大提高开发效率，同时提高系统的可维护性和可扩充性。     

利用Struts框架进行Web应用开发的研究

Struts是一个用于开发Web应用程序的概念框架,它是Apache软件基金会Jakarta项目的一部分。Struts已经成为了用Java创建Web应用的一个最流行的框架工具,它所实现的MVC模式给Web应用带来了良好的层次划分,同时也提供了一系列的工具来简化Web应用的开发。该文就Struts框架所涉及的技术要点进行了分析,并结合一个具体的应用程序对如何用Struts进行Web应用开发进行了探索研究。     

Struts框架Web应用的国际化

一个好的框架对于软件的开发是至关重要的。Struts是当前Web应用开发中最为优秀的框架之一。简要介绍了本地化与国际化的概念,Java和Struts框架对Web应用国际化的支持,并讲述了创建Struts的Resource Bundle和Struts应用中访问Resource Bundle的各种途径。     

基于MVC模式和Struts框架的Web应用研究与实现

首先简要介绍MVC设计模式和Struts工作原理,然后通过一个Web公文管理系统实例论述了基于MVC模式Struts框架的Web应用系统的实现方法。通过实例论述基于Struts框架开发的大型Web信息管理系统可获得较好的可重用性、可扩展性和易维护性。     

基于模板的重构

重构是对软件的一种调整,在不改变软件的行为的同时提高其可理解性,降低其修改成本。模板是标准C 语言中的一个重要特性,并激起了对于基于此的泛型程序设计的研究。文中研究了如何将C 模板特性应用到软件重构中。重构是提高软件内部质量的重要途径,通过结合C 语言的模板特性,可以让程序更为精练、更为容易重用和改进。通过一些具体的实例,论述和介绍了三个基于模板的重构手法,以及对原有的程序设计的改进。     

Refactoring OCL annotated UML class diagrams

Refactoring of UML class diagrams is an emerging research topic and heavily inspired by refactoring of program code written in object-oriented implementation languages. Current class diagram refactoring techniques concentrate on the diagrammatic part but neglect OCL constraints that might become syntactically incorrect by changing the underlying class diagram. This paper formalizes the most important refactoring rules for class diagrams and classifies them with respect to their impact on attached OCL constraints. For refactoring rules that have an impact on OCL constraints, we formalize the necessary changes of the attached constraints. Our refactoring rules are specified in a graph-grammar inspired formalism. They have been implemented as QVT transformation rules. We finally discuss for our refactoring rules the problem of syntax preservation and show, by using the KeY-system, how this can be resolved.     

Assessing refactorings for usability in e-commerce applications

Refactoring has been reported as a helpful technique to systematically improve non-functional attributes of software. This paper evaluates the relevance of refactoring for improving usability on web applications. We conducted an experiment with two replications at different locations, with subjects of different profiles. Objects chosen for the experiment were two e-commerce applications that exhibit common business processes in today’s web usage. Through the experiment we found that half of the studied refactorings cause a significant improvement in usability. The rest of the refactorings required a post-hoc analysis in which we considered aspects like user expertise in the interaction with web applications or type of application. We conclude that, when improving quality in use, the success of the refactoring process depends on several factors, including the type of software system, context and users. We have analyzed all these aspects, which developers must consider for a better decision support at the time of prioritizing improvements and outweighing effort.     

Test-Driven Development of Relational Databases

In test-first development, developers formulate and implement a detailed design iteratively, one test at a time. Test-driven development (also called test-driven design) combines TFD with refactoring, wherein developers make small changes (refactorings) to improve code design without changing the code's semantics. When developers decide to use TDD to implement a new feature, they must first ask whether the current design is the easiest possible design to enable the feature's addition. Implementing test-driven database design involves database refactoring, regression testing, and continuous integration. TDDD is an integrated part of the overall development process, not a standalone activity that data professionals perform in parallel with application TDD. Although from a technical view point, TDDD is relatively straightforward, we must overcome several challenges to its whole sale adoption throughout the IT community     

Dynamic profiling-based approach to identifying cost-effective refactorings

ContextObject-oriented software undergoes continuous changes—changes often made without consideration of the software’s overall structure and design rationale. Hence, over time, the design quality of the software degrades causing software aging or software decay. Refactoring offers a means of restructuring software design to improve maintainability. In practice, efforts to invest in refactoring are restricted; therefore, the problem calls for a method for identifying cost-effective refactorings that efficiently improve maintainability. Cost-effectiveness of applied refactorings can be explained as maintainability improvement over invested refactoring effort (cost). For the system, the more cost-effective refactorings are applied, the greater maintainability would be improved. There have been several studies of supporting the arguments that changes are more prone to occur in the pieces of codes more frequently utilized by users; hence, applying refactorings in these parts would fast improve maintainability of software. For this reason, dynamic information is needed for identifying the entities involved in given scenarios/functions of a system, and within these entities, refactoring candidates need to be extracted.ObjectiveThis paper provides an automated approach to identifying cost-effective refactorings using dynamic information in object-oriented software.MethodTo perform cost-effective refactoring, refactoring candidates are extracted in a way that reduces dependencies; these are referred to as the dynamic information. The dynamic profiling technique is used to obtain the dependencies of entities based on dynamic method calls. Based on those dynamic dependencies, refactoring-candidate extraction rules are defined, and a maintainability evaluation function is established. Then, refactoring candidates are extracted and assessed using the defined rules and the evaluation function, respectively. The best refactoring (i.e., that which most improves maintainability) is selected from among refactoring candidates, then refactoring candidate extraction and assessment are re-performed to select the next refactoring, and the refactoring identification process is iterated until no more refactoring candidates for improving maintainability are found.ResultsWe evaluate our proposed approach in three open-source projects. The first results show that dynamic information is helpful in identifying cost-effective refactorings that fast improve maintainability; and, considering dynamic information in addition to static information provides even more opportunities to identify cost-effective refactorings. The second results show that dynamic information is helpful in extracting refactoring candidates in the classes where real changes had occurred; in addition, the results also offer the promising support for the contention that using dynamic information helps to extracting refactoring candidates from highly-ranked frequently changed classes.ConclusionOur proposed approach helps to identify cost-effective refactorings and supports an automated refactoring identification process.     

设计模式和泛型技术在系统重构中的应用研究

重构是在不改变代码外在行为的前提下,对代码做出修改,以改进程序内部结构的过程.设计模式是对被用来在特定场景下解决一般设计问题的类和相互通信的对象的描述.泛型编程专注于将型别抽象化,形成功能需求方面的一个精细集合,并利用这些需求来实现算法.以一个应用系统的数据采集子系统的系统重构为例,将设计模式应用于系统重构中设计阶段,将泛型技术应用于系统重构实现阶段;讨论设计模式技术和泛型技术的结合对系统重构的作用与意义.     

A test case refactoring approach for pattern-based software development

In the current trend, Extreme Programing methodology is widely adopted by small and medium-sized projects for dealing with rapidly or indefinite changing requirements. Test-first strategy and code refactoring are the important practices of Extreme Programing for rapid development and quality support. The test-first strategy emphasizes that test cases are designed before system implementation to keep the correctness of artifacts during software development; whereas refactoring is the removal of “bad smell” code for improving quality without changing its semantics. However, the test-first strategy may conflict with code refactoring in the sense that the original test cases may be broken or inefficient for testing programs, which are revised by code refactoring. In general, the developers revise the test cases manually since it is not complicated. However, when the developers perform a pattern-based refactoring to improve the quality, the effort of revising the test cases is much more than that in simple code refactoring. In our observation, a pattern-based refactoring is composed of many simple and atomic code refactorings. If we have the composition relationship and the mapping rules between code refactoring and test case refactoring, we may infer a test case revision guideline in pattern-based refactoring. Based on this idea, in this research, we propose a four-phase approach to guide the construction of the test case refactoring for design patterns. We also introduce our approach by using some well-known design patterns and evaluate its feasibility by means of test coverage.     

Web应用浏览器兼容性的自动规范化方案

近年来万维嘲应用在中国正在飞速增长．但是在我国很多Web应用要求用户只能用IE浏览器．符合W3C组织制定的规范就能保证web应用跨浏览器的移植性．文中着眼于Web应用的特点,从遗留系统的角度来看待这个问题,提出了基于模型的自动规范化重构方法来解决这个问题．作为一个例子,构建了一个能够跨浏览器上访问小来只能用IE的中国银行的网上银行服务的实例,证明此方法能够有效解决国内现存Web应用的规范化问题．     

代码变更中抽取类重构模式的识别

在现代软件开发和维护中,重构是提高软件可维护性和软件质量的常用手段.而大量重构模式掺杂在日常的bug修复、功能增加等代码变更中,使得变更理解变得非常复杂.识别重构模式可以将重构与其它类型的代码变更隔离,利于变更理解.目前在识别重构模式的相关研究中,并没有结合变更类型和相似性比较的识别重构模式的方法及工具.为此,提出了一种基于细粒度变更类型和文本相似性比较识别重构模式的方法.将该方法应用于抽取类重构模式,并在4个开源项目中进行了实验,其平均准确率在82.6%左右.     

Automatic software refactoring: a systematic literature review

Refactoring a software artifact is an embedded task in the maintenance phase of the software life cycle. To reduce the time and effort required for this task, researchers proposed methods to automate the software refactoring process at the design and code levels. In this paper, we conducted a systematic literature review of papers that suggest, propose, or implement an automated refactoring process. Using different phases, setting several quality measures, and snowballing, only 41 papers passed to the last stage to be analyzed and reviewed. We observe an increase in the number of papers that propose automatic refactoring. The results show that while most of the papers discuss code refactoring, only a few recent papers are focused on model refactoring. Search-based refactoring is gaining more popularity, and several researchers have used it to perform refactoring in a quick and efficient manner.