东北大学软件学院东北大学软件学院毕业设计（论文）外文参考资料毕业设计（论文）外文参考资料（原文与译文）（原文与译文）外文题目：外文题目：The Value of a Usability-Supporting Architectural Pattern in Software Architecture Design: A Controlled Experiment中文题目：中文题目：支持可用性架构模式在软件架构设计中的价支持可用性架构模式在软件架构设计中的价值可控制的实验值可控制的实验 作作 者：者：Elspeth Golden. Bonnie E. John. Len Bass专专 业：软件工程业：软件工程班班 级：级：08070807学学 号：号：2008XXXX2008XXXX 姓姓 名：名： XXXXXX20122012 年年 6 6 月月 9 9 日日第 1 页 共 21 页The Value of a Usability-Supporting Architectural Patternin Software Architecture Design: A Controlled ExperimentABSTRACT Design patterns have been claimed to facilitate modification and improve understanding in software design. A controlled experiment was performed to assess the usefulness of portions of a Usability-Supporting Architectural Pattern (USAP) in modifying the design of software architectures to support a specific usability concern. Software engineering and information technology graduate students received different subsets of a USAP supporting cancellation functionality. They then studied a software architecture design and made modifications to add the ability to cancel commands. Results showed that participants who received a usability scenario, a list of general responsibilities, and a sample solution thought of significantly more key issues than participants who saw only the scenario. Implications for software development are that usability concerns can be included at architecture design time, and that USAPs can significantly help software architects to consider responsibilities inherent from usability concerns. Categories and Subject Descriptors H.5.2 Information Interfaces and Presentations: User Interfaces evaluation/methodology, theory and methods. D.2.11 Software Engineering: Software Architectures domain-specific architectures, patterns. General Terms Design, Experimentation. Keywords Controlled experiment, usability, software architecture, design pattern, modification. 1. INTRODUCTION Usability is an important quality attribute of interactive software systems, but it has gotten little attention in the architecture design phase of software development. Since the 1980s, usability has been treated as a subset of modifiability, that is, architects commonly separate the user interface from the functionality of the system and assume that usability issues that arise during user testing can be handled with localized modifications. As recently as 1999, usability has been labeled not “discernable” at architecture design time 12. Unfortunately, simply separating the interface from the functionality does not support all usability concerns. In fact, many usability concerns reach deeply into a systems architecture design4. Therefore, when usability is not considered early in the design process and support for them is not designed into the architecture, usability problems found in user testing often require extensive and costly re-architecting of software systems. When this happens, projects often cannot afford the additional cost第 2 页 共 21 页and ship products that are not as usable as they could be. Our research on the relationship between usability and software architecture has lead to the development of Usability-Supporting Architecture Patterns (USAPs), each of which addresses a usability concern that is not addressed by separation alone 3.Each USAP consists of_ an architecturally sensitive usability scenario,_ a list of general responsibilities derived from forces inherent in the task and environment, human capabilities and desires, and software state, which must be considered by any software implementation for which the usability scenario is relevant, and_ a sample solution implemented in a larger separation-based design pattern such as J2EE MVC. An early version of USAPs were applied in the design of the architecture of the MER Board, a wall-sized tool that supports shoulder-to-shoulder collaboration of the engineers and scientists on NASAs Mars Exploration Rover mission 1. Tutorials on the application of USAPs to software architecture design have also been given at the ICSE and CHI conferences 6, 9, 10.These patterns could prove of great benefit to software architects responsible for developing large-scale software systems, and to the enterprises of all kinds for which these software systems are developed. Software architects may find it beneficial to have specific sets of responsibilities through which to address usability issues at architectural design time, both to avoid errors of omission, and to facilitate analysis of tradeoffs. However, USAPs are quite detailed and complex, which might make them difficult for software architects to apply to their own design problems. Since software architects are already burdened with complex tasks and extensive methodologies, it is important to determine whether all parts of a USAP are useful or necessary before widely disseminating USAPs to these pro