Entity - relation modeling and transformation, Database Management System

Represent the following scenarios with E-R diagrams drawn using the ER Assistant software. The diagrams should indicate cardinality and optionality of relationships. Transform each diagram into a set of corresponding BCNF relations indicating primary and foreign keys.

1. The employee database stores data about employees and related information. There are three types of employees identified by employee number (EMPNO): salespeople, developers, and secretarial staff. Employees identified by employee number (EMPNO) work in departments identified by department number (DEPTNO). Each department must have at least one employee working in it; employees must belong to a single department. Employees may manage other employees; each employee (except the CEO) has a manager  identified by MGRNO. The following information requirements have been identified during analysis for the employee database:

EMPNO employee number

ENAME employee name

SAL employee salary

COM employee commission (applies only to salespeople)

DEPTNO department number of the department employee works in

DNAME name of the department employee works in

MGRNO employee number of the manager of the employee 2

2. Each client identified by a client number (CLIENTNO) who applies for a loan is assigned to one bank loan manager identified by employee number (EMPNO). Each bank loan manager may have many clients. The bank loan manager assists the client to complete a loan application identified by a unique application number (APPNO). Each loan application must have a single client who is a primary applicant, and may have one or more clients who are secondary applicants. The loan amount (LOANAMT), date of the application (APPDATE), income (INCOME) and expenses (EXPENSES) of the primary applicant are recorded on the application. Each application must have at least one (but may have several) guarantors, who must also be clients of the bank. The total assets (TOTALASSETS) are recorded for each guarantor. Clients who are applicants (primary or secondary) on one application may be guarantors on another application, and vice versa. But the same client cannot be both applicant and guarantor on one application. The following information requirements have been identified during analysis:

CLIENTNO client number

CLIENTNAME client name

CLIENTADDRESS client address

EMPNO bank loan manager employee number

EMPNAME bank loan manager employee name

APPLNO loan application number

APPDATE date of application

LOANAMT loan amount

INCOME income of the primary applicant

EXPENSES expenses of the primary applicant

TOTALASSETS total assets of a guarantor

Posted Date: 2/22/2013 12:59:04 AM | Location : United States







Related Discussions:- Entity - relation modeling and transformation, Assignment Help, Ask Question on Entity - relation modeling and transformation, Get Answer, Expert's Help, Entity - relation modeling and transformation Discussions

Write discussion on Entity - relation modeling and transformation
Your posts are moderated
Related Questions
1.  Based on the dependency diagram, create a database whose tables are in at least 2NF, showing the dependency diagram for each table (as shown in class).  Label the types of depe

create an e-r diagram usuing graphical dipicted software that could theoritically be used in resturant application

Consider the subsequent relations RENTER(rno, fname, lname, address, tel_no, pref_type, max_rent) VIEWING(rno, pno, date, comment) PROPERTY_FOR_RENT( pno, street, area ,city,

Single Valued Normalisation  Codd in the year 1972 formed three normal forms (1NF, 2NF, and 3NF). These were based on functional dependencies between the attributes of a relati

What are the two types of blocks in the fixed -length representation? Define them. Anchor block: Have the first record of a chain. Overflow block: Have the records other tha

QUESTION (a) Consider a car database consisting of car model, car make, car origin, Engine capacity, color, cost.

various techniques of hashing?

What is persistency? Persistency ensures which data is stored and that after the object is no longer available (program stops running) the data will be available to other users

What is a disjoint less constraint? Ans: It needs that an entity belongs to no much more than one level entity set.  Disjoint less constraint needs that an entity belongs to

A constraint named less_than_20 was defined on the field date_of_birth of table student. Delete this constraint. ALTER TABLE student DROP CONSTRAINT less_than_20;