Scribd Logo
Upload

Welcome to Scribd!

  • 41 views

    Hci UNIT 4

    Uploaded by

    karuna reddy
    This document discusses various interface building tools used when developing applications. It describes how interface building tools allow prototypes to be rapidly created by non-programmers, separating the presentation layer from the logic. This improves collaboration between managers, architects, programmers and users. Specific benefits mentioned include user interface independence, developing design methodologies, and performing low-cost testing of multiple versions early in the design process. Transition diagrams and Backus-Naur Form are also introduced as ways to formally specify interfaces and grammars.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd

    Hci UNIT 4

    Uploaded by

    karuna reddy
    41 views6 pages
    This document discusses various interface building tools used when developing applications. It describes how interface building tools allow prototypes to be rapidly created by non-programmers, separating the presentation layer from the logic. This improves collaboration between managers, architects, programmers and users. Specific benefits mentioned include user interface independence, developing design methodologies, and performing low-cost testing of multiple versions early in the design process. Transition diagrams and Backus-Naur Form are also introduced as ways to formally specify interfaces and grammars.

    Original Title

    hci UNIT 4

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document discusses various interface building tools used when developing applications. It describes how interface building tools allow prototypes to be rapidly created by non-programmers, separating the presentation layer from the logic. This improves collaboration between managers, architects, programmers and users. Specific benefits mentioned include user interface independence, developing design methodologies, and performing low-cost testing of multiple versions early in the design process. Transition diagrams and Backus-Naur Form are also introduced as ways to formally specify interfaces and grammars.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    41 views6 pages

    Hci UNIT 4

    Uploaded by

    karuna reddy
    This document discusses various interface building tools used when developing applications. It describes how interface building tools allow prototypes to be rapidly created by non-programmers, separating the presentation layer from the logic. This improves collaboration between managers, architects, programmers and users. Specific benefits mentioned include user interface independence, developing design methodologies, and performing low-cost testing of multiple versions early in the design process. Transition diagrams and Backus-Naur Form are also introduced as ways to formally specify interfaces and grammars.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 6

    UNIT 4

    1. INTERFACE BUILDING TOOLS :

     Writing an application requires agreement of several parties on the UI

     managers need to approve the design

     UI architects need to build it

     programmers need to be aware what they are programming to

     users are asked for opinions on the interface

     Let an interface be prototyped rapidly

     Let an interface be built by a non-programmer

     Allow the application to be built using the prototyped interface

     Benefits of using interface building tools

     User-interface independence

     Separate presentation from logic

     Prototype multiple user interfaces

     Multiple-platform support

     Domain expert as user-interface architect

     Enforce standards

     Methodology and Notation

     Develop design methodology

     Talk about design

     Project management

     Rapid prototyping

     Build and use multiple versions up front

     Low cost test, revise, test

     Usable user interfaces for users, managers and customers to see and use early

     Software support

     Productivity

     Constraint and consistency checks

     Ease of maintenance
     Teams
    2. TRANSITION DIAGRAMS :

     More complete and general than selection trees

     general enough to show the complete interaction with an application

     Directed graph

     Nodes represent states

     Links between nodes represent actions and the application’s response

     NFA

     Becomes cumbersome as the represented interaction grows.

    3. BACKAUS NAUR FORM :

    Backus Normal Form (BNF) is a metasyntactic notation procedure used to specify


    the syntax of computer programming languages.
    BNF is also known as Backus-Naur form.

    A BNF specification is a derivation rule set that is usually written as follows:

     The <symbol>::_expression_where <symbol> is a non terminal


     The _expression_consists of one or more symbol sequences.
     A vertical bar (|) delineates other sequence options.
     Symbols not appearing on the left side are terminals.
     Symbols appearing on the left side are located within the symbol-expression
    pair and are non-terminals.

    4. GRAMMARS

    a. Multiparty Grammars: Used for showing interaction between more than one party

    Effective for text-oriented command sequences.

    b. BNF :

    5. SOFTWARE ENGINEERING TOOLS :

    A software tool is a programmatic software used to create, maintain, or otherwise


    support other programs and applications. Some of the commonly used software
    tools in HCI are as follows −
     Specification Methods − The methods used to specify the GUI. Even
    though these are lengthy and ambiguous methods, they are easy to
    understand.
     Grammars − Written Instructions or Expressions that a program would
    understand. They provide confirmations for completeness and correctness.
     Transition Diagram − Set of nodes and links that can be displayed in text,
    link frequency, state diagram, etc. They are difficult in evaluating usability,
    visibility, modularity and synchronization.
     Statecharts − Chart methods developed for simultaneous user activities and
    external actions. They provide link-specification with interface building tools.
     Interface Building Tools − Design methods that help in designing command
    languages, data-entry structures, and widgets.
     Interface Mockup Tools − Tools to develop a quick sketch of GUI. E.g.,
    Microsoft Visio, Visual Studio .Net, etc.
     Software Engineering Tools − Extensive programming tools to provide user
    interface management system.
     Evaluation Tools − Tools to evaluate the correctness and completeness of
    programs.

    You might also like