Understand the Business Function

--

Agenda
Business Definition and Requirements Analysis Determining Basic Business Functions Design Standards or Style Guides System Training and Documentation Needs

6/7/2012

Fakultas Informatika IT Telkom

Business Definition and Requirements Analysis

Information Collection Techniques Requirements Collection Guidelines Defining the Domain Considering the Environment

6/7/2012

Fakultas Informatika IT Telkom

Information Collection Techniques

Direct Methods
Individual Face-to-Face Interview Telephone Interview or Survey Traditional Focus Group Facilitated Team Workshop Observational Field Study Requirements Prototyping User-Interface Prototyping Usability Laboratory Testing Card Sorting for Web Sites

Indirect Methods
MIS Intermediary Paper Survey or Questionnaire Electronic Survey or Questionnaire Electronic Focus Group Marketing and Sales Support Line E-Mail, Bulletin Boards, or Guest Book User Group Competitor Analysis Trade Show Other Media Analysis System Testing

6/7/2012

Fakultas Informatika IT Telkom

Defining the Domain

The domain is the area of expertise and specialist knowledge for which a system is being developed. The domain provides the systems underlying concepts. For example an airline system requires reservations, flight scheduling, crew scheduling, and so forth. A court services system might require functions such as pre-trial monitoring, probation,

parole, and drug testing.

Specialized knowledge to perform the tasks and accomplish goals must be understood and defined

6/7/2012

Fakultas Informatika IT Telkom

Possible Problems in Requirements Collection

Not enough user, customer, and other interested party involvement in the process Lack of requirements management or coordination Communication problems among all participants Capturing the relevant information may be difficult People who do understand the problem may be constrained

Organizational and political factors and agendas may influence the

process Disparities in knowledge may exist Changing economic and business environments and personnel roles

6/7/2012

Fakultas Informatika IT Telkom

Considering the Environment

Where the work or task is performed is also important in establishing requirements. Important environmental considerations are physical, safety, social, organizational, and user support (Stone et al., 2005). The physical environment and conditions address issues like lighting, temperature, noise, and cleanliness. The safety environment addresses any existing hazards or health

and safety issues

The social environment addresses the relationships between people and how they interact or do not interact The organizational environment addresses how a system will be integrated within the existing networks of people and technology The user support environment involves the availability of documentation and training materials, and colleagues to provide help when necessary
6/7/2012 Fakultas Informatika IT Telkom 7

Determining Basic Business Functions

Understanding the Users Work

Mental Models Performing a Task Analysis

6/7/2012

Fakultas Informatika IT Telkom

Developing Conceptual Models

A conceptual model is the general conceptual framework through which the systems functions are presented A conceptual model is based on the users mental model. Because the term mental model refers to a persons current level of knowledge about something, people will always have them

6/7/2012

Fakultas Informatika IT Telkom

Guidelines for Designing Conceptual Models

Reflect the users mental model, not the designers. Draw physical analogies or present metaphors. Comply with expectancies, habits, routines, and stereotypes. Provide action-response compatibility. Make invisible parts and processes of a system visible. Provide proper and correct feedback.

Avoid anything unnecessary or irrelevant.

Provide design consistency. Provide documentation and a help system that will reinforce the conceptual model. Promote the development of both novice and expert mental models

6/7/2012

Fakultas Informatika IT Telkom

10

Defining Objects
Determine all objects that have to be manipulated to get work done. Describe:
The objects used in tasks. Object behavior and characteristics that differentiate each kind of object. The relationship of objects to each other and the people using them. The actions performed The objects to which actions apply. Information or attributes that each object in the task must preserve, display,or allow to be edited

Identify the objects and actions that appear most often in the workflow. Make the several most important objects very obvious and easy to manipulate

6/7/2012

Fakultas Informatika IT Telkom

11

Developing Metaphors
A metaphor is a concept where ones body of knowledge about one thing is used to understand something else. Metaphors act as building blocks of a system, aiding understanding of how a system works and is organized
Choose the analogy that works best for each object and its actions. Use real-world metaphors. Use simple metaphors. Use common metaphors. Multiple metaphors may coexist. Use major metaphors, even if you cant exactly replicate them visually. Test the selected metaphors

6/7/2012

Fakultas Informatika IT Telkom

12

The Users New Mental Model

When the system is implemented, and a person interacts with the new system and its interface, an attempt will be made by the person to understand the system based upon the existing mental model brought to the interaction. If the designer has correctly reflected the users mental model in design, the users mental model is reinforced and a feeling that the

interface is intuitive will likely develop.

if the new system does not accurately reflect the users existing mental model? The results include breakdowns in understanding, confusion, errors, loss of trust, and frustration. Another result is an inability to perform the task or job

6/7/2012

Fakultas Informatika IT Telkom

13

Design Standards or Style Guides

Value of Standards and Guidelines
Allow faster performance. Reduce errors.

Reduce training time.

Foster better system utilization. Improve satisfaction. Improve system acceptance.

Reduce development and support costs.

6/7/2012

Fakultas Informatika IT Telkom

14

User Interface Standards

ISO 9241: Ergonomic requirements for office work with visual display terminals. ISO 14915: Software ergonomics for multimedia user interfaces ISO 13407: Human-centered design processes for interactive systems. ISO/CD 20282: Ease of operation of everyday products these standards is available at the Web sites of ISO (www.ISO.org) and the American National Standards Institute (ANSI) (http://webstore.ansi.org).

6/7/2012

Fakultas Informatika IT Telkom

15

Web Guidelines and Style Guides

Web interface design issues have also unleashed a plethora of Webspecific design guidelines and style guides, many of which are found on the Web itself. These guidelines can be seen on the sites of the various computer companies and interface consulting firms, in newsletters, and even on personal Web sites. Although many of the traditional interface

guidelines are applicable in a Web environment, the Web imposes a

host of additional considerations.

6/7/2012

Fakultas Informatika IT Telkom

16

Customized Style Guides

Include checklists to present principles and guidelines. Provide a rationale for why the particular guidelines should be used. Provide a rationale describing the conditions under which various design alternatives are appropriate. Include concrete examples of correct design. Design the guideline document following recognized principles for

good document design.

Provide good access mechanisms such as a thorough index, a table of contents, glossaries, and checklists

6/7/2012

Fakultas Informatika IT Telkom

17

System Training and Documentation Needs

Training and documentation are also an integral part of any development effort. System training will be based on user needs, system conceptual design, system learning goals, and system performance goals. Training may include such tools as formal or video training, manuals, online tutorials, reference manuals, quick reference guides, and

online help
System documentation is a reference point, a form of communication, and a more concrete design words that can be seen and understood. It will also be based on user needs, system conceptual design, and system performance goals

6/7/2012

Fakultas Informatika IT Telkom

18

Fakultas Informatika IT Telkom

19