E-R Diagram Usability Part I: E-R Diagram Consider the following E-R diagram. Tr
ID: 3787166 • Letter: E
Question
E-R Diagram
Usability
Part I: E-R Diagram
Consider the following E-R diagram.
Transform this E-R diagram into a set of 3NF relations.
State and justify all referential integrity rules for the 3NF relations you created
Choose primary keys for the files that would hold the data for these relations. Did you use attributes from the relations for primary keys or did you design new fields? Why or why not?
PART I Usability Case Application (25 points)
Review the following General Design Guidelines for Usability of Forms and Reports
Consider an online form you might use to register a guest at a hotel.
For each usability factor, list two examples of how this form could be designed to achieve that dimension of usability. Use examples other than those mentioned below and apply it the specific case
Usability Factor Guidelines for Achievement of Usability Consistency Consistent use of terminology, abbreviations, formatting, titles, and navigation within and across outputs. Consistent response time each time a function is performed. Efficiency Formatting should be designed with an understanding of the task being performed and the intended user. Text and data should be aligned and sorted for efficient navigation and entry. Entry of data should be avoided where possible (e.g., computing rather than entering totals). Ease Outputs should be self-explanatory and not require users to remember information from prior outputs in order to complete tasks. Labels should be extensively used, and all scales and units of measure should be clearly indicated. Format Information format should be consistent between entry and display. Format should distinguish each piece of data and highlight, not bury, important data. Special symbols, such as decimal places, dollar signs, and ±signs, should be used as appropriate. Flexibility Information should be viewed and retrieved in a manner most convenient to the user. For example, users should be given options for the sequence in which to enter or view data and for use of shortcut keystrokes, and the system should remember where the user stopped during the last use of the system VENDOR Vendor ID Address PRICE QUOTE R Quote Quantity Price Priced at PART RECEIPT Order Number Date Order Quantity PART Item Number Description
Explanation / Answer
Anwer)
Steps)
1) Represent the entity.
2)Then represent the relationship
3) Then normalize the relations
4)Then merg them
when we do translation from relationship set to relation atributes we must include the primary key and foreign key.
Rules
Binary 1:N relationship
->Add the primary key atributes or atribute of entity at one side as the foreign key of entity on another side of relation
Like in Vendor table and price_quote table
Vendor(Vendor_id,Address)
and price_quote(quote_nuber,vender_id,item_number,quote_qty,price)
so in vendor table Vendor_id is primary key and in price_quote table Vendor_id is foreign key.
->For binary or unary one to one 1:1 relationship do following
Add the primary key of first entity as foreign key of second entity or add the primary key of second entity as foreign key of first entity or do both.
in above question there is not 1:1 relationship
->For M:N
First create the new relationship
Primary key of this new relation would be composite of two attributes that both take their values from the same primary key.
so final design without breaking the referential integrity would below:
VENDOR(vendor_ID , address)
PART(Item_No , descp)
PRICE QUOTE(quote_No, vendor_ID , Item_No, quote_qty, price)
PART RECEIPT(order_No, quote_No , vendor_ID, Item_No , date,order_qty)
In above underline atributes are primary keys
bold atributes are foreign keys.
Part 2)
1) consistency :Consistent use of terminology, abbreviations, formatting, titles, and navigation within and across outputs. Consistent response time each time a function is performed.
This can be achieved suppose gest registeform that we create form with fields First name,Last name,emailid,mobile no ,UId, permanent address. and the database should be consistence mean if you do transantion on one part it must show the change on another part too.
2)Efficiency:means you include the auto compelete in your form and spelling corrector and some formate like the formate for emailid or password or in dob using java script
3)Ease:We got to include the self explainatroy means for example if we submit the form is mustshow whether you have sucessfully regitered or not with proper massage.
4)Format: In form like that you want to make some of fields mandatory which are important some are not mandatory.
5)Flexibilty:Giving the user the to enter the information in any order and allowing copy and paste and other keystroke ans given the option as same as previouse in in many option like parmanent and coresspond addres.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.