Database Management Systems Programming

2679 days ago, 1126 views
PowerPoint PPT Presentation
Database Administration Frameworks and Programming. LIS 558 - Week 10a Client Interface Outline. Workforce of Data and Media Studies Summer 2000. Diagram for Client Interface Outline. Basic database outline mistakes How is the nature of information influenced by every sort of blunder? UI segments

Presentation Transcript

Slide 1

´╗┐Database Management Systems & Programming LIS 558 - Week 10a User Interface Design Faculty of Information & Media Studies Summer 2000

Slide 2

Outline for User Interface Design Common database plan blunders How is the nature of information influenced by each sort of mistake? UI parts Interface Design Guidelines UI application plans with cases

Slide 3

The Well-Structured Database E-R displaying is beat down strategy for planning Transforming an E-R show does not ensure the best outline (e.g., E-R model could be off track) Best to change E-R model and afterward check the outline as indicated by the Cases of standardization Normalization is base up technique for planning a database Use both ways to deal with build up an all around organized database

Slide 4

Flat document database Too much information Compound fields Missing keys Bad keys Missing connections Unnecessary connections Incorrect connections Duplicate field names Cryptic field or table names Referential honesty Database Security Missing or off base business rules Missing or off base imperatives Common Errors in Database Design John Paul Ashenfelter, "Basic Database Mistakes", May 26, 1999, < > (Oct 10, 1999).

Slide 5

Database Application Development 1. Prepare perspectives of information: make, read, refresh, erase frames for keeping up information on a record by record premise question to attach, refresh, erase gatherings of records 2. Design or emerge sees make see with question or SQL articulation arrange see with report or shape 3. Implement requirements DBMS gives a few alternatives: e.g., MS Access gives referential uprightness and table properties, for example, approval rules, input veil, query records, default values different limitations must be modified with macros or VBA 4. Security and Control 5. Execute business rationale (Macros or VBA)

Slide 6

frames reports inquiries help mouse cursors symbols pictures content Components of Windows Interface toolbars summon catches quickening agent keys alternate way keys scroll bars menus setting delicate help general help

Slide 7

Anatomy of Event-Driven Applications Windows is occasion driven Messages passed upward/descending between working framework (OS) and application (and among modules) OS controls and courses messages and handles all low-level equipment/programming complexities Application based on Windows utilizes builtin institutionalized messages and occasions Each protest has set of properties and occasions Many properties intelligible and variable both at configuration time and run time Events can be caught at run time and related code is run

Slide 8

Interface Design Guidelines Create easy route (quickening agent) keys Define tab arrange Supply screen tips Create custom menus Create a startup shape Set startup properties See O'Brien's Microsoft Access Developer's Handbook (Chapter 5 - User Interface and Application Design) for an itemized depiction of parts, related properties, and utilization.

Slide 9

General Appearance of User Interface consistency - UI simpler to comprehend and utilize; interface components ought to look as though they have a place together course of action and stream arrangement gathering accentuation - attract regard for interface components to be seen to begin with, utilizing center, area, gathering, pecking order, empowering/handicapping, size, shading, or textual style qualities; outwardly show what client ought to do next visual pieces of information - utilize like measuring and dispersing to demonstrate UI components are comparable and diverse estimating and dividing to demonstrate UI components are distinctive white space utilize organization or item names and logos sparingly Adapted from: McKay, Everett N. (1999). Creating User Interfaces for Microsoft Windows . Redmond, Washington: Microsoft Press, Chapter 4.

Slide 10

Form Layout Acceptable: Better:

Slide 11

Visual Affordance Windows clients generally expect different conduct from an application (e.g., things with a white foundation and a glimmering vertical bar can be altered) Design your application reliably with expected traditions

Slide 12

Combo Box Format Properties

Slide 13

User's Interaction with the Application console access to all components mouse access to all elements activities with noteworthy outcomes require unequivocal choice from the (client should be completely mindful they are going to accomplish something unsafe or damaging) input for unsurpassed expending operations outwardly show modes single-clicking and double tapping are predictable right mouse catch just for setting menus don't utilize the center mouse catch (client doled out conduct) allot easy route keys reliably - as per tradition make alternate way keys excess maintain a strategic distance from even parchment bars

Slide 14

The cases that take after were taken from the "Interface Hall of Shame". The illustrations are all from "genuine" applications, some outlined by driving programming organizations.

Slide 15

Checkboxes are for Multiple Selections Option catches are utilized to permit the client to make a totally unrelated determination. Checkboxes are utilized to permit the client to make various choices. The very appearance of checkboxes tells the client that he or she can choose a few things. Never utilize checkboxes when you need the client to settle on a fundamentally unrelated decision.

Slide 16

More Checkboxes In the Font discourse box for Word 97 the client can set content qualities utilizing a variety of checkboxes; no issue there. In any case, there a 4 sets of fundamentally unrelated choices recorded: strikethrough/twofold strikethrough, subscript/superscript, decorate/etch, and all tops/little tops. the controls look like checkboxes however carry on like choice catches. Clearly, utilizing alternative catches would have ruined the feel of the control gather.

Slide 17

Radio catches are for Mutually Exclusive Options The exchange is proposed to permit the client to determine the fields on which to sort the information in a report. As can be deduced from the picture (and not without extensive trouble), the client can determine sorting on three fields. Really, the client must determine the sorting on three fields, since there is no real way to demonstrate that you need to sort on any less. As showed in the picture, sorting the outcomes by Part ID, then by Part ID, and after that by Part ID would be simply hunky-dory in the psyche of the designer.

Slide 18

Too numerous alternatives for radio catches The software engineer of this corporate application had evidently not yet perused the part on the utilization of drop-down controls. Makes you consider how the client is made a request to indicate his or her nation. Plans like this frequently result when the software engineer needs information of appropriate interface configuration, as well as needs involvement with the Windows condition. Such plans are wasteful for the client, and result in bigger, more drowsy applications that waste framework memory and assets.

Slide 19

Menus versus Toolbar Standards Use drop-down choices in menu bars. Symbols on instrument bars are best used to complete a quick activity. Constrain shocks for the client who is usual to outline gauges.

Slide 20

Drop-down boxes Displaying just 3 things in a listbox is out and out moronic. This exchange box is given by the Associate capacity in Microsoft's File Manager , as is shown when the client wishes to relate a specific document sort with an application. In this case, there are 133 passages in the rundown; tapping the page part of the scrollbar will show the documents 2 at any given moment. We are at a misfortune to clarify why the designer didn't utilize a greater amount of the accessible space on the frame to make the rundown bigger, or why he/she didn't simply make the shape bigger. The final product of the engineer's absence of believed is a control that is basically pointless for the job needing to be done.

Slide 21

Limit Drop-down box sections This kind of control is seen very frequently in corporate applica-tions: drop-down controls and records that contain a huge number of passages. Developers who erroneously utilize it for the most part get an indication that it may be unseemly when they discover that it requires a phenomenally long investment to stack the frame The reason for such cumbersome controls is frequently a misinformed understanding of the god-like invitation to battle, "We must guarantee information integrity." The software engineers need to ensure that the client determines a substantial section; in their view, the most ideal approach to do this is to compel the client to choose from a rundown. That would be fine in the event that you had, say 20, 60, or possibly 100 things in the rundown. Past that number, the way that the client can just look over a modest bunch of things at once causes the control to end up distinctly clumsy. All information can be sorted out in some important way that will permit the client to all the more quickly get to the particular data he or she is keen on. Records are sorted out into organizers or catalogs for instance. Representatives are regularly classified by division, work title, or pay review. Planning the interface to abuse the suitable association will permit the client to all the more quickly find the coveted data, while in the meantime, "ensuring information integrity."

Slide 22

Is this truly essential? In light of worry over the writing capacity of a portion of the 400,000 corporate clients, the venture supervisor of this specific application demanded that drop-down controls be utilized to gather data wherever conceivable.

Slide 23

Is this truly fundamental? Visual Labels requires right-snaps to perform essential capacities. It is the best way to get to vital capacities. Right-click setting menus are a valuable expansion to interfaces. They are proposed to be an option methods for getting to capacities; as alternate ways , essentially for cutting edge clients. They ought to never be required, and ought to dependably be utilized as a part of conjunction with traditional menus. Something else, new clients may never understand the capacities are accessible, and they will have no console access to the capacities once they discover them. At whatever point another client is observ