Lecture Enterprise systems development (CSC447) - Lecture 30

One objective of this chapter is to compare the REA enterprise ontology with current developments in enterprise resource planning (ERP) systems and electronic commerce (e-commerce) in the context of the types of integration introduced in Chapter 1. The prospects for progress in using the REA enterprise ontology as a foundation for intra-enterprise systems (similar to ERP systems) and for inter-enterprise systems needed for seamless e-commerce are discussed. | Lecture 30 Enterprise Systems Development ( CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor College of Statistical and Acturial Science USER INTERFACE DESIGN GUIDELINES AND PRINCIPLES Guidelines Shared language Best practices Critics Too specific, incomplete, hard to apply, and sometimes wrong Proponents Encapsulate experience Navigating the interface Sample of the National Cancer Institutes guidelines: Standardize task sequences Ensure that embedded links are descriptive Use unique and descriptive headings Use check boxes for binary choices Develop pages that will print properly Use thumbnail images to preview larger images Accessibility guidelines Provide a text equivalent for every nontext element For any time-based multimedia presentation synchronize equivalent alternatives Information conveyed with color should also be conveyed without it Title each frame to facilitate identification and navigation Organizing the display Smith and Mosier (1986) offer five high-level goals Consistency of data display Efficient information assimilation by the user Minimal memory load on the user Compatibility of data display with data entry Flexibility for user control of data display Getting the user’s attention Intensity Marking Size Choice of fonts Inverse video Blinking Color Audio Principles More fundamental, widely applicable, and enduring than guidelines Need more clarification Fundamental principles Determine user’s skill levels Identify the tasks Five primary interaction styles Eight golden rules of interface design Prevent errors Automation and human control Determine user’s skill levels “Know thy user” Age, gender, physical and cognitive abilities, education, cultural or ethnic background, training, motivation, goals and personality Design goals based on skill level Novice or first-time users Knowledgeable intermittent users Expert frequent users Multi-layer designs Identify the tasks Task Analysis usually involve long hours observing and . | Lecture 30 Enterprise Systems Development ( CSC447) COMSATS Islamabad Muhammad Usman, Assistant Professor College of Statistical and Acturial Science USER INTERFACE DESIGN GUIDELINES AND PRINCIPLES Guidelines Shared language Best practices Critics Too specific, incomplete, hard to apply, and sometimes wrong Proponents Encapsulate experience Navigating the interface Sample of the National Cancer Institutes guidelines: Standardize task sequences Ensure that embedded links are descriptive Use unique and descriptive headings Use check boxes for binary choices Develop pages that will print properly Use thumbnail images to preview larger images Accessibility guidelines Provide a text equivalent for every nontext element For any time-based multimedia presentation synchronize equivalent alternatives Information conveyed with color should also be conveyed without it Title each frame to facilitate identification and navigation Organizing the display Smith and Mosier (1986) offer five .

Không thể tạo bản xem trước, hãy bấm tải xuống
TÀI LIỆU MỚI ĐĂNG
Đã phát hiện trình chặn quảng cáo AdBlock
Trang web này phụ thuộc vào doanh thu từ số lần hiển thị quảng cáo để tồn tại. Vui lòng tắt trình chặn quảng cáo của bạn hoặc tạm dừng tính năng chặn quảng cáo cho trang web này.