18

Description of information - miftakhurrizal.lecture.ub.ac.idmiftakhurrizal.lecture.ub.ac.id/files/2018/02/system-design.pdf · Determine the input needs of the system Specifies the

Embed Size (px)

Citation preview

Description of the information needs to the user

User

a complete and clear design picture

Programmer

General Design

System overview

Detailed design

Detailed design construction

Databasedesign

Process design

user interface

design

User interface design

User

Computer system

Command Language Interaction

Menu Interaction

Object – Based Interaction

Natural Language Interaction

Interface Design Section 1. Input Section

• Steps:

Determine the input needs of the system

Specifies the parameters of the input

input formbasic

documents

input input form (terminal screen dialog),

source,

tools used, volume period.

Interface Design Section2. Output Section

• Steps :

1. Needs the

output of the system

2. The output

parameters include the type of output, its format, the media and tools used, and the output period.

Layout design.

• The default format is the same

• Flexibility and consistency

• Users can move parts / tasks

• The data must remain stored until the user wants it.

• One key / command = one function

Data entry structure.

• The data entry structure must be considered well

• anticipate user error, be able to detect errors and justify them if necessary.

Provision of feedback.

• Feedback is valuable to users.

• Feedback informs what is going on in the system.

• The format in the feedback is consistent

• language or terms that are easy to understand

Help design.

• should not be abandoned

• Users find it helpful

• simple, well organized and demonstrative.

Form & Report

Form

• documents in an organization containing predefined data and other parts containing data to be completed.

• Usually the form corresponds to one record in a table in the database.

Report

• documents in an organization that contains only data / information that has been set previously.

• Report is a passive document that can only be read and not to be filled.

• Usually a report is the result of reading on more than one record or transaction.

Form & Report Design Process with Prototyping

1. System analysis creates initial prototype of form and report

2. Users assess prototype design and determine design decisions

3. If any changes are requested then the prototype is fixed