BCIS 4620 – Spring 2008

Assignment  #5.1 & 5.2 (continued)

NetExpress SQL

Semantic Object Models  & TableDesigner

===============================================================                 

HOMEWORK #5.2 (15 Points)

 

1.  SEMANTIC OBJECT DIAGRAMS   (9 POINTS)                                   

                                                                               

Identify the semantic objects in the Alameda case.  Create the Semantic Object diagrams that will meet the design specifications in the case.  I recommend that you use the TableDesigner software.  Also, create a "code" table, for example, Skill_Codes.        

                                                                                

Turn in 3 items:                                                               

                                                                               

a. The TableDesigner Object Model printout (include NOTE below)                

b. Tabledesigner Report (Objects list like homework 5)                        

c. Printout of SQL Generated by TableDesigner (SQLGen.txt)                    

                                             

NOTE: State any special database modeling assumptions clearly in the SOM tool.            

For example:  1) Is there a limit to the number of Next of Kin?                

2) Which many-to-many relationship will you attempt? You MUST have one.        

3) Which do you intend NOT to do? etc.  Include this with part a. above.       

                                          

2.  ENTITY-RELATIONSHIP DIAGRAMS (6 POINTS)                                               

                                                                                

a. Draw the E-R Diagram (normalized) for your database design.                 

You may use any CASE tool or drawing tool you are most familiar with. Given the variety we have available, all of these have acceptable ERD design tools:  Oracle, ACCESS, etc.  Recall TableDesigner can generate a Microscoft ACCESS database model with associated ERD.  Print a very professional looking copy of the ER Diagram to turn in.        

                                                                               

b. (2 Points) List the RELATIONS and include the KEY fields and ATTRIBUTE names.          

You will probably need to type this information in a separate one page report.  For example, the EMPLOYEE relation might look like:       

                                                                                

EMPLOYEE(ENO, FIRST_NAME, LAST_NAME, ADDR_FIELDS, foreign keys, etc.)       

                                                                               

RECALL:  Underline primary key, italicize foreign keys.                     

 

c. Turn in the Entity, Relationship, Attribute report that is produced by the ER modeling tool you are using.  ACCESS creates a very complete report. 

HINT:  Tools/Analyze/Documenter and print Relationship on File drop down menu.