Drkraghavarao.files.wordpress.com



Project 1 : Management Information systems for Construction Companies

|Course |Database Management Systems |

|Project: |Management Information systems for construction |

| |companies |

|Document |Project Specification |

1.0 Project description

An organization dealing with civil constructions employs many employees with different expertise. The organization has many departments each concentrating on specific functions which include accounting, Billing and Purchasing, planning and monitoring, system administration of the Construction the department . Employees are recruited into theses department based on the need and the amount of work to be carried by the organization. The organization maintains project based accounting system. Employees are deployed to the projects. All the departments are functionally organized department wise. One employee can be assigned for different projects and one project will be undertaken by several employees. Every department is headed by a manager and the manager also works for one or more number of projects. Each department is responsible for certain number of functions.

2.0 Module Identification

|Serial | | | | |

|Number of |Name of the |Function |Functions to be discharged | |

|the |department |Number | | |

| | | | | |

|department | | | | |

| | |#1. |Design a database covering the functions of this Module | |

| | |#2. |Conduct Normalization | |

| | |#3. |Develop a DDL for creating the schema in the database | |

| | |#4. |Capture Quotations | |

| | |#5. |Issue quotations | |

| | |#6. |Make Comparative analysis of the Quotations | |

|1 |Billing and |#7. |Place orders for procurement of materials. The Tax and | |

| |purchasing | |duties must be computed automatically | |

| | | | | |

| | |#8. |Receive Materials | |

| | |#9. |Receive invoices | |

| | |#10. |Make Payments | |

| | |#11. |Capture work in progress | |

| | |#12. |Must be able to raise bills based on the quantum of work | |

| | | |done - project wise | |

| | |#1. |Design a database covering the functions of this Module | |

| | |#2. |Conduct Normalization | |

| | |#3. |Develop a DDL for creating the schema in the database | |

| | |#4. |Capture and maintain Work Content | |

| | |#5. |Capture and maintain work schedules | |

| |Planning |#6. |Report activities delayed – project wise | |

| | |#7. |Report on percentage of works completed – each project | |

|2 |and | | | |

| | | |wise | |

| |monitoring | | | |

| | |#8. |Raise alerts when abnormal delays are caused in | |

| | | | | |

| | | |executing certain tasks | |

| | |#9. |Capture and Maintain plans | |

| | |#10. |Display Project wise time and costing report | |

| | |#11. |Display Project wise milestones | |

| | |#12. |Display project wise Employee Allocations | |

|Serial |Name of the |Function |Functions to be discharged |

|Number |department |Number | |

|of the | | | |

|departmen | | | |

|t | | | |

| | |#1. |Design a database covering the functions of this Module |

| | |#2. |Conduct Normalization |

| | |#3. |Develop a DDL for creating the schema in the database |

| | |#4. |Prepare work schedules project wise and day wise |

| | |#5. |Asses the list of material on order project wise |

| | |#6. |Report completed works and the work in progress |

| | |#7. |Report details of blue prints being dealt as on date |

|3 |Construction |#8. |Display the employees associated with the projects |

| |Department |#9. |Display the list of projects awaiting the receipt of |

| | | |Material |

| | |#10. |Account for the list of materials received in respect of |

| | | |different project |

| | |#11. |Forecast of the delay in project execution due to lack of |

| | | |manpower resources |

| | |#12. |Develop and implement Indexes for improving the |

| | | |performance of the database |

3.0 Platform for Implementation of the Project

|Computing Location |HW/SW |HW/SW element |HW/SW element specification |

|Client |HW |Processor |Dual Core |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WINDOWS XP |

| | |MYSQL |MYSQL |

| | |DATA STAGE |6.0 |

| | |VISIO |7.0 |

| | |PL-SQL |2.0 |

|Server |HW |Processor |XEON |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WIDOWS 2008 |

| | |DBMS |ORACLE 9i |

Project #2 : University Management System

|Course |Database Management Systems |

|Project: |University Management system |

|Document |Project Specification |

1.0 Project description

A university such as KL University has many departments offering different programs such as B.Tech in CSE, ECE, ME etc. Each program has a number of courses offered by different departments to be studied by students to become eligible for getting degree in that program. Each course has certain credits allotted for the course. Many Instructors may work in a department but an instructor can work only in one department. Each of the department is headed by an instructor called Head and will head only one department. The courses offered by the department may be taught by instructor of the same department or different department. A course may be taught by more than one instructor and an instructor may teach any number of courses. A student can enroll for any course and a course may enrolled by any number of students. Every instructor records the day wise attendance of all the students registered for his/her course. The instructor also conducts examinations such as Test-1, Test-2 etc and records the marks obtained for all the students. Hence this project may be divided into modules such as Registrations, Course-Teacher allocation, Attendance and Examination.

2.0 Module Identification

|Serial | | | | |

|Number of |Name of the |Function |Functions to be discharged | |

|the |department |Number | | |

| | | | | |

|department | | | | |

| | |#1. |Draw the ER diagram for the database covering the all | |

| | | |the entities and relationships in the entire project | |

| | |#2. |Conduct Normalization | |

| | |#3. |Develop a DDL for creating the schema in the | |

| | | |database | |

| | |#4. |Student registration | |

| |Student |#5. |Course / Teacher selection | |

| | |#6. |Generate Course wise and Teacher wise sections of | |

|1 |Registration | | | |

| | | |students | |

| | | | | |

| | |#7. |Generate the details of unregistered students | |

| | |#8. |Generate the details of unregistered courses | |

| | |#9. |Automatic display of change of course by student | |

| | |#10. |Develop a procedure for displaying the course wise | |

| | | |registration amount. | |

| | |#11. |Generate course wise registration details for a all the | |

| | | |branches branch wise | |

| | | | | |

| | | | | |

|Serial | | | | |

|Number of |Name of the |Function |Functions to be discharged | |

|the |department |Number | | |

| | | | | |

|department | | | | |

| | |#1. |Draw the ER diagram for the database covering the all | |

| | | |the entities and relationships in the entire project | |

| | |#2. |Conduct Normalization | |

| | |#3. |Develop a DDL for creating the schema in the database | |

| | |#4. |Record and list the courses | |

| | |#5. |Record the options of teachers | |

| | |#6. |Develop a procedure for allotment of teachers to courses | |

| |Teacher |#7. |Automatically calculate the workload of teachers based | |

|2 |Course | |on course allotment. | |

| |Allotment |#8. |Generate course wise and teacher wise allotment list | |

| | |#9. |Raise an alert when a teacher of a course has changed | |

| | |#10. |Generate the list of faculty handling other branch | |

| | | |courses | |

| | |#11. |Develop a procedure to show the faculty allotment for | |

| | | |all the faculty of a branch | |

| | |#12. |Develop and implement Indexes for improving the | |

| | | |performance of the database | |

| | |#1. |Draw the ER diagram for the database covering the all | |

| | | |the entities and relationships in the entire project | |

| | |#2. |Conduct Normalization | |

| | |#3. |Develop a DDL for creating the schema in the database | |

| | |#4. |Record the attendance per course and per teacher | |

| | |#5. |Develop procedure for Computing the overall | |

| | | |attendance of students student wise | |

| | |#6. |Generate the list of students that fall under a specific | |

| |Student | |attendance for a given course | |

|3 | |#7. |Automatically Report the change of attendance | |

| |Attendance | | | |

| | |#8. |Generate the groups of students based on the attendance | |

| | | | | |

| | | |attained in a give course | |

| | |#9. |Generate the % of students who attained more than a | |

| | | |specific across all the courses in a given branch | |

| | |#10. |Develop a procedure that allows the addition of a | |

| | | |specific % of attendance for a specific course | |

| | |#11. |Generate the list of students expected to be detained due | |

| | | |to shortage of attendance for a given branch | |

| | | | | |

Project #3: Library Management system

|Course Name |Database Management Systems |

|Project Name |Library Management system |

|Document |Project Specification |

Project Description:

Library management system manages daily operations in a library. It handles the Book issue, Book return and Administration operations. It maintains the history of the books and students. The System also searches the specific student and book information from the exiting files. This management system consist of the following modules

• Book Issue

• Book return

• Administration Module

• Student records and Book Records

•

Module Identification:

| | | | |

| | | | |

|1 | |#1 |Design a database covering the function of this module |

| | | | |

| |Book Issue | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Book Issue details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Student visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 | |#1 |Design a database covering the function of this module |

| |Book return | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Book return details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Student visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 | |#1 |Design a database covering the function of this module |

| | | | |

| | | | |

| |Student records and Book Records | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Book registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Student visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #4: Railway Reservation System

|Course Name |Database Management Systems |

|Project Name |Railway Reservation System |

|Document |Project Specification |

Project Description:

This is a project based on train reservation. The program helps us to enter, display or alter the details of different trains. Moreover & most importantly the program helps us to reserve or cancel a train ticket. The program also helps us to know the present status of a reserved ticket, i.e., whether the ticket is confirmed or not. It includes various function programs to do the above mentioned tasks. Data and file handling will be managed effectively.

Module Identification:

|1 | |#1 |Design a database covering the function of this module |

| | | | |

| |Reservation | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Reservation details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 | |#1 |Design a database covering the function of this module |

| |Cancellation | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Cancellation details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Student visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 | |#1 |Design a database covering the function of this module |

| | | | |

| |Schedules | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Schedule details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #5: Airlines Reservation System

|Course Name |Database Management Systems |

|Project Name |Airline Reservation System |

|Document |Project Specification |

Project Description:

Airline Reservation System is a web portal to book airline ticket online. The objective of the project is to design an Airline Reservation System application which enables the customers to search and book flights. The Airline Reservation System project mainly consists of two types of users. The customers who access the information provided by the ARS website and the administrator who modifies and updates the information available in the website.Data and file handling will be managed effectively.

Module Identification:

|1 | |#1 |Design a database covering the function of this module |

| | | | |

| |Reservation | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Reservation details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 | |#1 |Design a database covering the function of this module |

| |Cancellation | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Cancellation details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Student visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 | |#1 |Design a database covering the function of this module |

| | | | |

| |Schedules | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Schedule details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #6 : Automation of Hospital Management System

|Course |Database Management Systems |

|Project: |Automation of Hospital Management System |

|Document |Project Specification |

Project description

Every hospital needs an online system whereby it can accommodate the patients comfortably and avoid any confusion to the doctors regarding their work. There should be a system where the patients are categorized under insurance policy and non policy holders and the system helps the hospital management to claim the bills from concerned insurance companies. All these needs and much more are fulfilled in this Automation of Hospital Management System

Automation of Hospital Management System is useful to record patient’s details along with the compliant. It also records the inpatient details and outpatient details and arranges the appointment of doctors. Automation of Hospital Management System also provides the management reports like schedules, appointments of doctors, inpatients, insurances and discharges. And also used to generate bills dynamically for the discharged patients etc.

2.0 Module Identification

|Serial Number of |Name of the |Function Number|Functions to be discharged |

|the Module |department/Module | | |

|1 |Doctors Module | |Design a database covering the functions of this Module |

| | | |Conduct Normalization |

| | | |Develop a DDL for creating the schema in the database |

| | | |Doctors Registration Details |

| | | |Appointment Scheduling (Patient /Doctor wise) |

| | | |Doctor's Schedule Summary |

| | | |Doctors Daily Schedule List |

| | | |Patient Visit History |

| | | |Report on missing data |

| | | |Initiate daily procedures |

| | | |Appointment Scheduling / Rescheduling Facility |

| | | |Surgery Scheduling Details |

|Serial Number of |Name of the |Function Number|Functions to be discharged |

|the Module |department/Module | | |

|2 |Patients& | |Design a database covering the functions of this Module |

| |Appointments Module | | |

| | | |Conduct Normalization |

| | | |Develop a DDL for creating the schema in the database |

| | | |Patient Registration Details |

| | | |Inpatient and Outpatient Registration |

| | | |Investigation / Treatment History |

| | | |Insurance Details |

| | | |Company Sponsorship Details |

| | | |Medical Alerts Details |

| | | |Diagnosis Details |

| | | |Patient Appointments |

| | | |Appointment Scheduling / Rescheduling Facility |

|3 |Discharges & | 1 |Design a database covering the functions of this Module |

| |Insurance Module | | |

| | |2 |Conduct Normalization |

| | |3 |Develop a DDL for creating the schema in the database |

| | |4 |Sponsorship Conditions Details |

| | |5 |Sponsor Verification |

| | |6 |Charges |

| | |7 |Approval from Sponsor |

| | |8 |Raise alerts when abnormal issues are caused in executing certain tasks |

| | |9 |Discharge Notification |

| | |10 | Project wise Bill amount |

| | |11 |Project wise Insurance claims |

| | |12 |Expected Date and Time of Discharge |

Platform for Implementation of the Project

|Computing Location |HW/SW |HW/SW element |HW/SW element specification |

|Client |HW |Processor |Dual Core |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WINDOWS XP |

| | |ORACLE IDE |ORACLE DBK |

| | |DATA STAGE |6.0 |

| | |VISIO |7.0 |

| | |PL-SQL |2.0 |

|Server |HW |Processor |XEON |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WIDOWS 2008 |

| | |DBMS |ORACLE 9i |

Project #7 : Hotel Reservation System

|Course |Database Management Systems |

|Project: |Hotel Reservation System. |

|Document |Project Specification |

1.0 Poject Description :

The System is to manage all the Boarding and lodging activities of a hotel. It automates the task of room reservation, bill generation, checks room availability, food orders etc. The database is the only professional structure for organizing, manipulating and retrieving deferent information structures and huge amount of data. Using database management systems (DBMS) brings several advantages, like quick access, high security, integrity, durability, automated reports and statistics, multiuser access etc. To complete a task through Manual basis is time consuming as well as it increases burden on the employee so for a better side to complete a task many of organizations are implementing computer based system. The day-to-day entries are made computerized into the book that has gotten all the relevant entries.

2.0 Module Identification

|Serial Number of |Name of the |Function Number|Functions to be discharged |

|the Module |department/Module | | |

|1 |Reservation | 1 |Design a database covering the functions of this Module |

| | |2 |Conduct Normalization |

| | |3 |Develop a DDL for creating the schema in the database |

| | |4 |Reservation details |

| | |5 |Transaction Scheduling |

| | |6 |Transaction Summary |

| | |7 |Transaction Daily Schedule List |

| | |8 |Customer visit history |

| | |9 |Report on missing data |

| | |10 |Initiate daily processes |

| | |11 |Reprocessing Facility |

| | |12 |Transaction Scheduling Details |

|Serial Number of |Name of the |Function Number|Functions to be discharged |

|the Module |department/Module | | |

|2 |Food orders | 1 |Design a database covering the functions of this Module |

| | |2 |Conduct Normalization |

| | |3 |Develop a DDL for creating the schema in the database |

| | |4 |Menu card Description |

| | |5 |Order taking |

| | |6 |Order conformation |

| | |7 |Schedule of orders |

| | |8 |Billing |

|3 |cancellation | 1 |Design a database covering the functions of this Module |

| | |2 |Conduct Normalization |

| | |3 |Develop a DDL for creating the schema in the database |

| | |4 |Reservation details |

| | |5 |Transaction Summary |

| | |6 |Hotel Cancellation |

| | |7 |Menu card Description |

| | |8 |Order taking |

| | |9 |Order conformation |

| | |10 |Schedule of orders |

| | |11 |Food Cancellation |

| | |12 | |

Platform for Implementation of the Project

|Computing Location |HW/SW |HW/SW element |HW/SW element specification |

|Client |HW |Processor |Dual Core |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WINDOWS XP |

| | |ORACLE IDE |ORACLE DBK |

| | |DATA STAGE |6.0 |

| | |VISIO |7.0 |

| | |PL-SQL |2.0 |

|Server |HW |Processor |XEON |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WIDOWS 2008 |

| | |DBMS |ORACLE 9i |

Project # 8 : Video Rental Store Database Management System.

|Course |Database Management Systems |

|Project: |Video Rental Store Database Management System. |

|Document |Project Specification |

8 Poject Description :

The Video Store Database Management Software System shall be designed and developed to provide a clear and easy to use Database Management System for our customer. The Database Management Software System shall facilitate and optimize employee management, customer interaction, and a virtual video warehouse. To complete a task through Manual basis is time consuming as well as it increases burden on the employee so for a better side to complete a task many of organizations are implementing computer based system.

The database is the only professional structure for organizing, manipulating and retrieving deferent information structures and huge amount of data. Using database management systems (DBMS) brings several advantages, like quick access, high security, integrity, durability, automated reports and statistics, multiuser access etc.

Module Identification

|1 | |#1 |Design a database covering the function of this module |

| | | | |

| |Movie Issue | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Movie Issue details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 | |#1 |Design a database covering the function of this module |

| |Movie return | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Movie return details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 | |#1 |Design a database covering the function of this module |

| | | | |

| | | | |

| |Customer records and Movie Records | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Movie registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

3.0 Platform for Implementation of the Project

|Computing Location |HW/SW |HW/SW element |HW/SW element specification |

|Client |HW |Processor |Dual Core |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WINDOWS XP |

| | |ORACLE IDE |ORACLE DBK |

| | |DATA STAGE |6.0 |

| | |VISIO |7.0 |

| | |PL-SQL |2.0 |

|Server |HW |Processor |XEON |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WIDOWS 2008 |

| | |DBMS |ORACLE 9i |

Project # 9: Football League Management System.

|Course |Database Management Systems |

|Project: |Football League Management System. |

|Document |Project Specification |

1.0 Poject Description :

Football League Management System is a system that will be used to manage football competition which using league system during the tournament. Basically the system will be designed suit with the current football tournament held in KLU. The system will be developed using MySQL as the database. It will be focused on managing all the information used during the tournament started from registration process, during the tournament and until the tournament is over.

Currently most of football organization use filing method to store and manage all the information during the tournament period. The filing method gives few complications for staff to handle all those data. The system that is going to be developed will provide a complete systematic system which will maintain all the tournament data. Therefore all the jobs during the tournament took part will become easier and manageable.

|1 | |#1 |Design a database covering the function of this module |

| | | | |

| |Player Module | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Player details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 | Player visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 | |#1 |Design a database covering the function of this module |

| |Team Module | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Team Match details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Team visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 | |#1 |Design a database covering the function of this module |

| | | | |

| | | | |

| |Matches Module | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Team registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 | Matches history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

3.0 Platform for Implementation of the Project

|Computing Location |HW/SW |HW/SW element |HW/SW element specification |

|Client |HW |Processor |Dual Core |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WINDOWS XP |

| | |ORACLE IDE |ORACLE DBK |

| | |DATA STAGE |6.0 |

| | |VISIO |7.0 |

| | |PL-SQL |2.0 |

|Server |HW |Processor |XEON |

| | |Memory |2GB |

| | |Disk Storage |300GB |

| |SW |OS |WIDOWS 2008 |

| | |DBMS |ORACLE 9i |

Project #10: Book Bank System

|Course Name |Database Management Systems |

|Project Name |Book Bank System |

|Document |Project Specification |

1.0 Project description

Book management system aims at developing an online book-bank monitoring system in any University. The content management system deals with data entry, validation and updating while the interactive system deals with system interaction with the users. The system is capable to largely address the problems mentioned in the existing system. It can generate reports on the total inventory of books in the system, books in each book-bank, list defaulters and other vital information required by the book-bank coordinator in the monitoring of the book-banks in the University.

. This management system consist of the following modules

• Borrower details

• Book Bank Staff

• Book Info

• Book copy

Project #11 : Bus Reservation System

|Course Name |Database Management Systems |

|Project Name |Bus Reservation System |

|Document |Project Specification |

Project Description:

This is a project based on Bus reservation. The program helps us to enter, display or alter the details of different buses. Moreover & most importantly the program helps us to reserve or cancel a bus ticket. The program also helps us to know the present status of a reserved ticket, i.e., whether the ticket is confirmed or not. It includes various function programs to do the above mentioned tasks. Data and file handling will be managed effectively.

Module Identification:

|1 | |#1 |Design a database covering the function of this module |

| | | | |

| |Reservation | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Reservation details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 | |#1 |Design a database covering the function of this module |

| |Cancellation | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Bus Cancellation details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Student visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 | |#1 |Design a database covering the function of this module |

| | | | |

| |Schedules | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Schedule details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #12 : Online Movie Booking System

|Course Name |Database Management Systems |

|Project Name |Online Movie Booking System |

|Document |Project Specification |

Project Description:

This is a project based on movie ticket booking. The program helps us to enter, display or alter the details of different movies. Moreover & most importantly the program helps us to reserve or cancel a movie ticket. Data and file handling will be managed effectively.

Module Identification:

|1 | |#1 |Design a database covering the function of this module |

| | | | |

| |Booking | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |New user Registration |

| | |#5 |Book ticket based on movie date and time |

| | |#6 |Transaction Scheduling |

| | |#7 |Transaction Summary |

| | |#8 |Transaction Daily Schedule List |

| | |#9 |User’s visit history |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 | |#1 |Design a database covering the function of this module |

| |Cancellation | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Movie ticket Cancellation details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |User’s visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 | |#1 |Design a database covering the function of this module |

| | | | |

| |Schedules | | |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Movie Schedule details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |User’s visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #13 : Automation of Bank Management System

|Course Name |Database Management Systems |

|Project Name |Automation of Bank Management System |

|Document |Project Specification |

Project Description:

The main aim of this project is it gives information about the Functioning of Databases in Banking System. All the Functionalities of Banking Systems are credited in this project.

Usually all persons want money for personal and commercial purposes. Banks are the oldest lending institutions in Indian scenario. They are providing all facilities to all citizens for their own purposes by their terms. To survive in this modern market every bank implements so many new innovative ideas, strategies, and advanced technologies. For that they give each and every minute detail about their institution and projects to Public.

They are providing ample facilities to satisfy their customers i.e. Net Banking, Mobile Banking, Door to Door facility, Instant facility, Investment facility, Demat facility, Credit Card facility, Loans and Advances, Account facility etc. And such banks get success to create their own image in public and corporate world. These banks always accept innovative notions in Indian banking scenario like Credit Cards, ATM machines, Risk Management etc. So, as a student business economics I take keen interest in Indian economy and for that banks are the main source of development.

Module Identification:

|SL.No |Name of the Module |Function Number |Functions to be discharged |

|1 |Customer Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |AccountInfo Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |LoanInfo Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

| | | | |

| | | | |

Project #14 : ATM Database Management System

|Course Name |Database Management Systems |

|Project Name |ATM Database Management System |

|Document |Project Specification |

Project Description:

The main aim of this project is it gives information about the Functioning of Databases in Bank ATM System. All the Functionalities of Banking Systems are credited in this project.

Usually all persons want money for personal and commercial purposes. Banks are the oldest lending institutions in Indian scenario. They are providing all facilities to all citizens for their own purposes by their terms. To survive in this modern market every bank implements so many new innovative ideas, strategies, and advanced technologies. For that they give each and every minute detail about their institution and projects to Public.

They are providing ample facilities to satisfy their customers i.e. Net Banking, Mobile Banking, Door to Door facility, Instant facility, Investment facility, Debit Card facility, and Account facility etc. And such banks get success to create their own image in public and corporate world. These banks always accept innovative notions in Indian banking scenario like Credit Cards, ATM machines, Risk Management etc. So, as a student business economics I take keen interest in Indian economy and for that banks are the main source of development.

Module Identification:

|SL.No |Name of the Module |Function Number |Functions to be discharged |

|1 |Customer Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Account and card info |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Machines info |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #15 : Hostel Database Management System

|Course Name |Database Management Systems |

|Project Name |Hostel Database Management System |

|Document |Project Specification |

Project Description:

The main aim of this project is as the name specifies “HOSTEL MANAGEMENT SYSTEM” is software developed for managing various activities in the hostel. For the past few years the numbers of educational institutions are increasing rapidly. Thereby the numbers of hostels are also increasing for the accommodation of the students studying in this institution. And hence there is a lot of strain on the person who are running the hostel and software’s are not usually used in this context.

This particular project deals with the problems on managing a hostel and avoids the problems which occur when carried manually. Identification of the drawbacks of the existing system leads to the designing of computerized system that will be compatible to the existing system with the system Which is more user friendly and more GUI oriented. We can improve the efficiency of the system, thus overcome the drawbacks of the existing system.

• Managing student’s Personal information

• Updating vacant rooms and filled rooms

• Monthly payment details

• Hostel Names

• Room Allocation Details

Module Identification:

|SL.No |Name of the Module |Function Number |Functions to be discharged |

|1 |Student Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Student registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Student visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Registration Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Student Registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Guest visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Maintenance Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Student registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Guest visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #16 : Super Market Database Management System

|Course Name |Database Management Systems |

|Project Name |Super Market Database Management System |

|Document |Project Specification |

Project Description:

The “Supermarket Management System” is based on the sales transaction of items in a supermarket. The first activity is based on adding the items to the system along with the rate which are present in the supermarket and the name of the items which the supermarket will agree to sell. This authority is given only to admin. Any modifications to be done in the item name or the in the rate can be done only by admin. He also has the right to delete any item. As the customer buys the products and comes to the billing counter, the user is supposed to enter the item name he purchased and the quantity of the item he wanted to purchase. This is not a huge a task.

The system will display all the items whose name starts with the letter selected by the user. He can select out of those displayed. Finally a separate will be generated for each customer. This will be saved in the database. Any periodic records can be viewed at any time. If the stock is not available, the supermarket orders and buys from a prescribed vendor. The amount will be paid by deducting the total amount acquired in the sales activity. Admin provides a unique username and password for each employee through which he can login.

Module Identification:

|SL.No |Name of the Module |Function Number |Functions to be discharged |

|1 |Cutomer Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Sales Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Product details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Items history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Inventory Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer Purchasing details |

| | |#5 |Transaction Scheduling |

| | |#6 |Inventory Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 | Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #17 : Real Estate Site Management System

|Course Name |Database Management Systems |

|Project Name |Real Estate Site Management System |

|Document |Project Specification |

Project Description:

The main aim of this project is as the name specifies “Real Estate Site Management System” is software developed for managing various activities in the Real Estate Company. For the past few years the numbers of real estate organizations are increasing rapidly. Thereby the numbers of ventures are also increasing for the accommodation of the customers purchasing sites in these ventures. And hence there is a lot of strain on the organizers who are sales the sites and software’s are not usually used in this context.

Real Estate site Management system is a program designed to the new real estate consultant, who recently engaged in site distribution. They purchased the land recently and converted them into sites. To manage the whole process this software is developed.

Module Identification:

|SL.No |Name of the Module |Function Number |Functions to be discharged |

|1 |Agent/User Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Agent/User registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Agent visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Venture Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Venture registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Agent visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Buyer and Transaction Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Buyer Registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Buyer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #18 : Blood Bank Management System

|Course Name |Database Management Systems |

|Project Name |Blood Bank Management System |

|Document |Project Specification |

1.0 Project Description:

The main aim of this project is as the name specifies “Blood Bank Management System” is software developed for managing various functions in the Blood Bank. This particular project deals with the problems on managing a Blood bank and avoids the problems which occur when carried manually. Identification of the drawbacks of the existing system leads to the designing of computerized system that will be compatible to the existing system with the system which is more user friendly and more GUI oriented. We can improve the efficiency of the system, thus overcome the drawbacks of the existing system.

2.0 Module Identification:

|SL.No |Name of the Module |Function Number |Functions to be discharged |

|1 |Donar Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Donar registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Donar visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Blood Request Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Blood Request registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Transaction Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Donar details |

| | |#5 |Blood Request Details |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Donar visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #19 : Mobile Store Management System

|Course Name |Database Management Systems |

|Project Name |Mobile Store Management System |

|Document |Project Specification |

Project Description:

The main aim of this project is as the name specifies “Mobile Store Management System” is software developed for managing various activities in the Mobile Store. For the past few years the numbers of Mobile stores are increasing rapidly. Thereby the numbers of mobiles are also increasing for the accommodation of the customers purchasing in this store. And hence there is a lot of strain on the person who are managing the mobile store and software’s are not usually used in this context.

This particular project deals with the problems on managing a mobile store and avoids the problems which occur when carried manually. Identification of the drawbacks of the existing system leads to the designing of computerized system that will be compatible to the existing system with the system Which is more user friendly and more GUI oriented. We can improve the efficiency of the system, thus overcome the drawbacks of the existing system.

Module Identification:

|SL.No |Name of the Module |Function Number |Functions to be discharged |

|1 |Customer Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Customer history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Mobile Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Mobile details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 | Customer Search history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|4 |Payment Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Customer details |

| | |#5 |Mobile Details |

| | |#6 |Transaction Summary |

| | |#7 |Payment Details |

| | |#8 | Mobile history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project #20 : Share Market Management System

|Course Name |Database Management Systems |

|Project Name |Share Market Management System |

|Document |Project Specification |

Project Description:

The main aim of this project is as the name specifies “Share Market Management System” is software developed for managing various share activities in the NSE. This project is used to automate the share application system using oracle. To control the ownership of the company, only 49% of the shares are being floated. As a matter of policy the company has decided to allot 20% of the shares to residents. 10% of the shares to non-residents. The shares are allotted in full on a first-come-first-server basis.

Module Identification:

|SL.No |Name of the Module |Function Number |Functions to be discharged |

|1 |Applicant Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Allotment Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 | Allotment details |

| | |#5 |Allotment Scheduling |

| | |#6 |Allotment Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Transaction Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project 21 Milk Project Data Base Management System:

In General milk is procured by the milk project from various farmers from different villages. The milk is graded and sent for preprocessing. The processed milk is then packed and made ready for sale. Various different products like Ghee, butter, cheese, puneer etc. are also made available for sale . Different stake holder information is maintained such as farmers, Customer etc. . The package milk is sent for distribution by means of transport. Some of the identified modules are

Milk Purchase module

Milk Sales Module

Processing Module

|1 |Milk purchase Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Milk purchase Scheduling |

| | |#6 |Milk purchase Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Milk sale Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 | Allotment details |

| | |#5 |Allotment Scheduling |

| | |#6 |Allotment Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Annual Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Processing Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project 22:Clinical laboratory management:

Clinical laboratory in general do perform some tests on Blood, Urine etc. The patients approach with a prescription from the doctor with the list of test to be performed. The clinical staff performs the tests and save the test results. The Report is generated and issued to the patient. Lab maintains different clinical equipment for doing testing. The following are the identified modules.

1.Patient Info

2. Testing and Report

3. Instruments and Maintenance

|1 |Patient info |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Testing Report |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 | Allotment details |

| | |#5 |Allotment Scheduling |

| | |#6 |Allotment Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Instruments and Maintenance |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project 23:Medical store database:

Medical stores procure medicines from various different distributors. The store maintains the catalog of medicines available in the store. When the customer approaches with prescription the vendor verify the availability and the location of the drug in this stores using computer app. Billing details of the patient is stored in the database. Medical store maintains customer info for booking and billing of medicines. The indent module is used to place the indent of required medicines by verifying the availability of the drugs with the database.

1.Customer Info

2.Drugs Info

3.Indent and Sales Transactions

|1 |Customer Info |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Drugs Info |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 | Allotment details |

| | |#5 |Allotment Scheduling |

| | |#6 |Allotment Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Indent and Sales Transactions |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project 24: Sugar factory:

Sugar factory purchases sugarcane from framers near and around and is graded. Factory maintains a database of framers from whome the sugarcane is purchased. Factory pays the framer according to the sugarcane grade. The sugarcane is then process and graded into sugar. The MRP rate is fixed by the factory management. The saled sugar is delivered to the customer. Data regarding the whole process is maintain in the database. The customer info,sale transactions and transportation is maintained in the database.

1.Purchase module

2.Sales Module

3.Processing and Transportation

|1 |Purchase module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Sales Module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 | Allotment details |

| | |#5 |Allotment Scheduling |

| | |#6 |Allotment Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Processing and Transportation |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project 25:CBI:

CBI is a Crime Investigation Bureau management maintains employee details. The CBI has different Investigation department such as anti-corruption, legal and prosecution division, technical forensic and coordination department, economic offences department etc., the crime that is reported the categorized and allocated to the concerned department. The crime investigation involves different stages and procedures.

1. Employee module

2.Crime details module

3.Investigation module

|1 |Employee module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |Crime details module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 | Allotment details |

| | |#5 |Allotment Scheduling |

| | |#6 |Allotment Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Investigation module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

Project 26:Film Industry:

Production manager records information about schedules of daily events, the scenes to be shooted, and the location details. The also maintains the details of the actors for each scene. He also maintains the transportation schedule and arranges accordingly. The equipment required for shooting is purchased or borrowed on loan. The maintains of the equipment is also recorded. Production manager want to build a database to maintain the above said data.

1.Production module

2.Schedules module

3.Maintenance and Transportation

|1 |Production module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|2 |schedules module |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 | Allotment details |

| | |#5 |Allotment Scheduling |

| | |#6 |Allotment Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

|3 |Maintenance and Transportation |#1 |Design a database covering the function of this module |

| | |#2 |Conduct Normalization |

| | |#3 |Develop a DDL for creating the schema in the database |

| | |#4 |Applicant registration details |

| | |#5 |Transaction Scheduling |

| | |#6 |Transaction Summary |

| | |#7 |Transaction Daily Schedule List |

| | |#8 |Applicant visit history |

| | |#9 |Report on missing data |

| | |#10 |Initiate daily processes |

| | |#11 |Reprocessing Facility |

| | |#12 |Transaction Scheduling Details |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download