Finally we would like to thank all our friends and class mates for their countless suggestions towards improving the overall look of this project.

• The EMPLOYEE entity maintains the personal details of every employee..

• The SKILLS table is used to store the employee skills,this will be used by the project manager to deploy employees on a specific project requiring people with some specific skillset.

• The PROJECTS table holds some general information about every project.

• The ATTRIBUTE table contains the 15 cost driver factors or project attributes which will be used to estimate the cost and time of the project using the COCOMO Model.

• The REQUIREMENTS table gives the requirements of the each project in terns of human skill sets.The Project Manager can go through the Project Requirements report and Employee Skill report and allocate employees to projects.

· Deploy applications on the Internet.

· Produce efficient, scalable applications.

· Build large, consistent, maintainable applications quickly.

· Use third-party tools and database servers.

· Form modules

· Menu modules

· Object library modules

· PL/SQL library modules

· Graphics Builder

· Project Builder

· Procedure Builder

· Schema Builder

· Query Builder

· Translation Builder

· Report Builder

· Reports Server

create table employee(
e_no number,
sk_no number,
f_name varchar2(20) not null,
l_name varchar2(20),
address varchar2(50),
phone_no varchar2(10),
email varchar2(20),
dob date,
sex char,
title varchar2(20)
);


create table skills(
sk_no number,
e_no number,
languages varchar2(30),
tools varchar2(30),
platform varchar2(30),
qualification varchar2(30) not null,
experience varchar2(30)
);


create table projects(
p_no number,
p_name varchar2(20) not null,
persondays number,
no_of_persons number
);


create table status(
st_no number,
phase varchar2(20),
startdate date,
deadline date,
extension date
);


create table attributes(
a_no number,
rely number(5,2),
data number(5,2),
cplx number(5,2),
time number(5,2),
stor number(5,2),
virt number(5,2),
turn number(5,2),
acap number(5,2),
aexp number(5,2),
pcap number(5,2),
lexp number(5,2),
modp number(5,2),
tool number(5,2),
sced number(5,2),
kdloc number(10),
cons_a number(5,2),
cons_b number(5,2)
,p_no number);


create table estimate(
est_no number,
effort number(9,2),
time number(9,2),
p_no number
);


create table requirements(
rq_no number,
languages varchar2(30),
tools varchar2(30),
platform varchar2(30),
qualification varchar2(30),
experience varchar2(30),
p_no number
);


create table works_on(
e_no number,
p_no number,
hours number(9,2)
);



create table password(
name varchar2(8),
password varchar2(8)
);



insert into password values('employee','employee');
insert into password values('manager','manager');

alter table employee
add constraint employeepk
primary key(e_no);


alter table skills
add constraint skillspk
primary key(sk_no);


alter table requirements
add constraint requirementspk
primary key(rq_no);


alter table status
add constraint statuspk
primary key(st_no);


alter table projects
add constraint projectspk
primary key(p_no); 


alter table attributes
add constraint attributespk
primary key(a_no);


alter table estimate
add constraint estimatepk
primary key(est_no);


alter table works_on
add constraint works_onpk
primary key(p_no,e_no);

alter table employee
add constraint employeefk
foreign key(sk_no) references skills(sk_no)
on delete cascade;


alter table skills
add constraint skillsfk
foreign key(e_no) references employee(e_no)
on delete cascade;


alter table works_on
add constraint works_onfk1
foreign key(p_no) references projects(p_no)
on delete cascade;


alter table works_on
add constraint works_onfk2
foreign key(e_no) references employee(e_no)
on delete cascade;



alter table attributes
add constraint attributesfk
foreign key(p_no) references projects(p_no)
on delete cascade;



alter table estimate
add constraint estimatefk
foreign key(p_no) references projects(p_no)
on delete cascade;



alter table requirements
add constraint requirementsfk
foreign key(p_no) references projects(p_no)
on delete cascade;

create view emp_view (Employee_No,First_Name,Title)
as select e_no,f_name,title
   from employee
   order by e_no;


create view prj_dtls
as select projects.p_no,projects.p_name,projects.no_of_persons,attributes.kdloc,
works_on.hours,estimate.effort
from projects,attributes,works_on,estimate
where projects.p_no=works_on.p_no 
and projects.p_no=attributes.p_no
and projects.p_no=estimate.p_no;

1. Fundamental of Database Systems (Second edition) - Ramez Elmasri and Shamkant B. Navathe

2. SQL & Relational Data Bases - Soren Vang

3.Commercial Application Development Using Oracle Developer 2000 Forms 5.0 - Ivan Bayross

4. Oracle - The Complete Reference

5. Oracle 7 The Application Development Handbook 2nd Edition - Alexis Leon

6. Mastering Oracle 7 & Client / Server Computing - Steven M. Bobrowski