Henninger, S., Haynes, K., Reith, M. W. "A Framework for Developing Experience-Based Usability Guidelines," Proceeding of the Symposium on Designing Interactive Systems (DIS `95), Ann Arbor MI, pp. 43-53.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....are used to support work practices. This paper considers organizational learning in the context of software design. An organizational learning approach to software development uses an organization s accumulated knowledge of the development process and application domains as the basis for design [Henninger 1995]. This perspective of software design highlights the relationship between the knowledge needs and products of a specific project, and the accumulated products of past projects that are stored in a group memory. When a group or organization works in the same domain for a while, organizational ....

S. Henninger, K. Haynes and M. Reith, "A Framework for Developing Experience-Based Usability Guidelines," Symposium on Designing Interactive Systems (DIS'95), ACM Press, 1995, pp. 43-53.

No context found.

Henninger, S., Haynes, K., Reith, M. W. "A Framework for Developing Experience-Based Usability Guidelines," Proceeding of the Symposium on Designing Interactive Systems (DIS `95), Ann Arbor MI, pp. 43-53.

No context found.

Henninger, S., Haynes, K., Reith, M. W. "A Framework for Developing Experience-Based Usability Guidelines," Proceeding of the Symposium on Designing Interactive Systems (DIS `95), Ann Arbor MI, pp. 43-53.

No context found.

Henninger, S., Haynes, K., Reith, M. W. "A Framework for Developing Experience-Based Usability Guidelines," Proceeding of the Symposium on Designing Interactive Systems (DIS `95), Ann Arbor MI, pp. 43-53.

No context found.

Henninger, S., Haynes, K., Reith, M. W. "A Framework for Developing Experience-Based Usability Guidelines," Proceeding of the Symposium on Designing Interactive Systems (DIS `95), Ann Arbor MI, pp. 43-53.

.... for accessing the guidelines [24 28] But these systems have done little to address the problems demonstrated in studies using guidelines, such as the time to find relevant guidelines, problems with interpreting guidelines for the task at hand, and generally being too abstract to directly apply [29 31]. While usability guideline have become voluminous to the point that it is difficult to determine which principles are applicable to a given design problem. And the continuing proliferation of technology only exacerbates the problem. Little thought has been given to defining when guidelines are ....

....as local terminology, organization and project specific conventions, lessons learned, policies and guidelines, individuals with expertise, and many others. The Mimir Guidelines system illustrated how organizational memory techniques could be used to collect and disseminate usability guidelines [31]. Project experiences were captured using case based decision support technology [42] where cases were attached to guidelines as examples of how the guideline had been applied. Dissemination of guidelines was supported through hypertext and searching techniques where users matched project ....

S. Henninger, K. Haynes, and M. W. Reith, "A Framework for Developing Experience-Based Usability Guidelines," Proc. Designing Interactive Systems (DIS `95), Ann Arbor MI, 1995, pp. 43-53.

....issues for a number of reasons. First, most software developers have little training in usability issues, making it critical to disseminate best practices to the average developer. Second, while defined processes are difficult to come by, user interface design techniques are beginning to mature [7, 17] and usability guidelines are beginning to appear that are being mandated by development organizations [5, 10] Therefore a dynamic process of the kind presented here is needed to disseminate what is known while continuously improving the processes based on experiences. Third, the usability of ....

S. Henninger, K. Haynes, M.W. Reith, "A Framework for Developing Experience-Based Usability Guidelines," Proceeding of the Symposium on Designing Interactive Systems (DIS `95), Ann Arbor MI, 1995pp. 43-53.

....This is meant to demonstrate the kinds of development infrastructure that needs to be created, and not to argue that tool knowledge is the only or most important form of knowledge needed by software developers. We have also been researching project specific knowledge [21] and interface guidelines [20] as other forms of knowledge needed in our approach. The paper concludes with a brief overview of related research and an assessment of our experiences thus far. Supporting the Domain Lifecycle Support for software development and reuse is needed for new and evolving domains as well as mature ....

....did not match the design problem, designers found them useful for understanding guidelines and how they could be applied. Augmenting generalized knowledge with concrete cases (examples) help designers interpret the information, making it easier to comprehend and apply to the current design problem [20]. Structure of the Case Based Repository The central element of a case based repository is the case. Figure 2 shows the user interface for a case in BORE. The case is titled Data Window Retrievals Functions Available and consists of nine fields describing the case. The Description field ....

S. Henninger, K. Haynes, M.W. Reith, "A Framework for Developing Experience-Based Usability Guidelines," Proceeding of the Symposium on Designing Interactive Systems (DIS `95), Ann Arbor MI, 1995, pp. 43-53.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC