Is effective when there is thorough design of data types and structures and careful consideration of fields used as primary keys for creating relationships.

Is gained by the following steps;

• Define the need for information
• Initiate the search strategy
• Locate the resources
• Assess and comprehend the information
• Interpret the information
• Evaluate the product and the process.

1. Selecting the person or people to interview
2. Designing your interview questions
3. Preparing for the interview
4. Conducting the interview
5. Following up after the interview

1. closed-ended questions
2. open-ended questions
3. Probing questions

1. Read the title, subtitles, and headings
2. Read the introduction or abstract or executive summary
3. Read the first sentence under each heading
4. Note typographical and graphical aids
5. Read the conclusion/final summary
6. Look through the bibliographic/reference section at the end of the resource
7. Defining your purposes for reading using Guide Questions

• Listen/Look for key words or phrases. 
• Find important points in source materials. 
• Use short sentences to record your own ideas while the lecture is in progress. 
• Use pre-published material as a guide to lecture structure and so on. 
• Keep your notes organised for easy retrieval and use later on. 
• Use ink in a standard size notebook, start each lecture/tutorial on a new page with the date clearly noted.

• Approach listening as a process similar to reading
• Focus on content, not delivery
• Listen carefully to the speaker’s opening comments
• Attempt to understand the lecturer’s purpose
• Fill the gap between rate of speech and the rate of thinking
• Approach listening as a challenging mental task

1. Primary Information
2. Secondary Information
3. Tertiary Information

·         Define the need for information

·         Initiate the search strategy

·         Locate the resources

·         Assess and comprehend the information

·         Interpret the information

·         Evaluate the product and the process

Relevance

Reliability

Bias

An entity is anything (a person, a place, a thing, or an event) about which data are to be collected and stored. It can be a physical object as well as an abstract concept, such as Appointment. There has to be more than 1 instance of an entity

 Rows: = records = instances of the entity

Cardinality expressess the maximum number of relationships

·         Cardinality: = one-to-one, one-to-many, many-to-many

How do you optimize the user’s interactions with a system, environment or product, so that they match the user’s activities that are being supported and extended?

·         Command line interface

·         Menus

·         Natural language

·         Question/answer and query dialog

·         Form-fills and spreadsheets

·         WIMP Point and click

·         3-D interfaces

1.       Establishing the goal

2.       Forming the intention

3.       Specifying the action sequence

4.       Executing the action

5.       Perceiving the system state

6.       Interpreting the system state

7.       Evaluating the system state with respect to the goals and intentions

User interface guidelines for most of the popular operating systems encourage the use of metaphors in interface design. They suggest that applications should build on the user's real-world experience by exploiting concrete metaphors thereby making applications easier to use.

Metaphors connect the user with a familiar mental model and method of interaction.

1.       Increase the familiarity with Interface

2.       Motivates the user to explore

3.       Maintain Consistency in Interface

4.       Contain a naturalness and pervasiveness of metaphor in human thought and language

5.       Coherence: all elements of the metaphor naturally belong together

6.       Help novices to quickly learn how to use a computer system through the application of a source domain to the target domain

1.       Restrictive for design decisions

2.       A mismatch between source and target domains can mislead users

3.       Can be expensive and time consuming

4.       Slight mismatches between the real-world and the representation on the computer are inevitable

Accessable

Accurate

Complete

Economical

Flexible

Relevant

Reliable

Secure

Simple

Timely

Verifiable

(An Ant Can't Eat From Rob's Roast Still She Tries Violently)

1. Knowledge
2. Control
3. Notice 
4. Consent

1. Logical design (view)
   The logical design of a data base shows an abstract model of how the data should be structured and arranged to meet an organizations information needs. The logical design of a database involves identifying relationships among the different data items and grouping them in an orderly fashion.
2.  Physical design (view)
   Physical database design starts from the logical database design and fine-tunes it for performance and cost consideration [eg. Improved response time, reduced storage space, lower operating costs, etc.

·         Data and structural independence—structural independence: change in database structure does not require changes to programs e.g. inserting a new table; data independence: change to field characteristics does not require changes to programs e.g. field change from char to numeric. Independence allows us to view data logically rather than physically

·         Easy to design and manage data

• RDBMS requires substantial hardware and operating system overhead
• Slower than other database systems

“Optionality” expresses whether the relationship is optional or mandatory.

“Cardinality” expresses the maximum number of relationships.

When an instance of an entity may be related to multiple instances of another entity and vice versa, that is called a “many-to-many relationship.”  In the example below, a supplier may provide many different products, and each type of product may be offered by many suppliers: