7/7/2012 1
Layout
Introduction
Project Schedule
Summary of previous work done
Business Logic Design
E-R Model to Relational Model
Normalization
Physical Database Design
Future Work for 8th semester
docsity.com
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Business Logic Design and Relational Database Design for a Project, Slides of Applications of Computer Sciences
Information about the business logic design and relational database design tasks for a project. It includes the creation of an entity relationship model, the mapping of the model to a relational schema, and the normalization of the schema. The document also mentions the creation of tables using sql script and the creation of a database. References are made to catherine ricardo's database systems principles, design and implementation book.
Typology: Slides
2011/2012
1 / 52
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Business Logic Design and Relational Database Design for a Project and more Slides Applications of Computer Sciences in PDF only on Docsity!
Layout
Introduction
Project Schedule
Summary of previous work done
Business Logic Design
E-R Model to Relational Model
Normalization
Physical Database Design
Future Work for 8
th
semester
Introduction
VPC, an Internet-based
application intended to
manage and automate
the coordination process
of Seminar Project at
PIEAS, would provide the
Faculty Members and
Students, an easy to use
system that
automatically
coordinates their
projects and helps them
interact in a more
efficient and reliable
manner.
Figure VPC Architecture
Summary of work done
Following tasks were done in the period between
summer vacations and 7
th
semester midterm.
Logical Database Design
Proof of Concept Prototype
Pre-Mature Architectural Design
Following tasks were to be done in the period
between 7
th
semester midterm and 7
th
semester
final
Business Logic Design
Relational Database Modeling and Normalization
Physical Database Design
Pre-mature Architecture (previous work)
Pre-mature Architectural Design on basis of Proof of concept prototype
Business Logic Design
• Business Logic design incorporates the business logic
into the system
• Designed prior to the development of Physical
Database Design, Physical Database Implementation
and Application Software Design and Implementation.
• More than 50 business rules were identified.
• Some of the business rules are presented here
• Complete list present in Project Progress Report
User name to be case insensitive
Password to be case sensitive
Number of students not greater than 3 or as
specified by the department.
Business Logic Design
Should be
considered as
different
Password XYZ and xyz
Should be
considered as
same
ST0001 and
st
User Name
Business Logic Design
Marks Distribution for evaluation in 6
th
semester should
be:
Feature No.
Feature to Evaluate
Technical consultati on with supervisor
Literature Survey
Developm ent of SRS Document
Presentati on and Comprehe nsion of Project
Q/A
Session
Max. Marks
Business Logic Design
Marks Distribution for evaluation in 7
th
semester should
be:
Feature No.
Feature to Evaluate
Technical consultatio n with supervisor
Literature Survey
Developme nt of Design Description Document OR Research Findings Description
Project Progress Report
Presentati on and Comprehe nsion of Project
Q/A
Sess ion
Max. Marks
Administrator can delete unnecessary artifacts. Only
those Artifacts shall be available for deletion which
are more than a year old and whose projects are not
under execution.
Business Logic Design
Business Logic Design
When a user is changing his password, old password
must be confirmed twice before setting the proposed
new password as current password.
E-R Model to Relational Model
Relational Database Model
[1]
makes understanding of
the database easy on an intuitive level, in that it
allows separation of Logical and Physical levels, so
that logical design can be performed without
considering the storage structures.
The entity sets represented by rectangles become
relations represented by tables.
The attributes represented by ovals become
attributes of the relation, or column heading of the
table.
Relational Schema
STUDENT (STUID, STUFNAME, STULNAME, PASS, EMAIL, REGNO,
ADDRESS, PHONE, PROJTITLE)
PRIMARY KEY=STUID, FOREIGN KEY=PROJTITLE Referencing PROJECT
FACULTY (FACID, FACFNAME, FACLNAME, EMAIL, PASS, RANK) PRIMARY KEY=FACID
PROJECT (PROJTITLE, PROJDESC, PROJTYPE) PRIMARY KEY=PROJTITLE
ARTIFACT (ARTID, ARTTITLE, BASELINE, VERSION, CONTENTS,
DATE/TIME OF SUBMISSION, PROJTITLE, STUID)
PRIMARY KEY=ARTID, FOREIGN KEY=PROJTITLE Referencing PROJECT and STUID Referencing STUDENT
Initial Relational schema for VPC as obtained by mapping E-R Model to Relational Model
Relational Schema contd..
EVALUATION (FACID, STUID, SCHED, EVAID)
PRIMARY KEY=FACID, STUID, SCHED FOREIGN KEY=FACID Referencing FACULTY , STUID Referencing STUDENT and EVAID Referencing DETEVALUATION
DETEVALUATION (EVAID) PRIMARY KEY= EVAID
DET-EVA-6TH-SEM (EVAID, EVAREMARKS, TECH-CON-SUP, LISTSUR, SRS, PRE, Q/A)
PRIMARY KEY=EVAID
FOREIGN KEY = EVAID REFERENCES DETEVALUATION
DET-EVA-7TH-SEM (EVAID EVAREMARKS, , TECH-CON-SUP, LISTSUR, PRE, Q/A, DES/RES, PPR )
PRIMARY KEY=EVAID
FOREIGN KEY = EVAID Referencing DETEVALUATION
Normalization
Normalization involves techniques of identifying and
removing flaws in the Logical Database Design, which
result in redundancy and several insert, update and
delete anomalies
[2]