Objective

Brief Report - Students co-operated well in:

Self Learning FOSS, DBMS Mini-Project, Using Google tools/Google SMS services for discussions/forums.

Sunday, February 21, 2010

Self Learning - FOSS

!Self Learning!

Hello friends. Since this semester, we have some extra time we can do a bit of self learning. Only thing is you have to is, fill this form with topics/anything which you want to learn and are not a part of our academics. If we have more than 10 learners in a topic, we will post the topic open for anybody who wants to teach the topic. Once done, we will request department to provide us with classroom/other nessecities and proceed.
 

Project Report Format

Saturday, February 20, 2010

DBMS - Mini Project - Synopsis Submission Form

DBMS - Mini Project . Synopsis Submission Form

The Synopsis reflects your understanding of the problem domain as of now i.e before implementation of the project. You are allowed to change it during and after implementation of your project, as, you will be having a better understanding of the project then. In the form given below for synopsis submission, if any field is irrelevant or Not Applicable, then you can leave it blank or write N / A.
 


DBMS - Mini Project - Synopsis Submission Form - Entries Filled


Sunday, February 14, 2010

Assignment of DBMS - Mini Project

 
 
For any clarification regarding any project, meet me in the DBMS lab tomorrow [ Both 6 - A and  B, Batch wise].
 
Do remember that you have to submit the synopsis before 19th of this month.
 
Also find the End Users / Remarks column against your assigned project.Now your next step is to collect the requirements from the ACTUAL END-USERS of the software being developed by YOU.
 
Go through the list and come prepared tomorrow with your understanding of the software [mini-project] on pen and paper.
 
[This phase is known as SOFTWARE REQUIREMENTS COLLECTION phase.]

Tuesday, February 9, 2010

DBMS Mini Project

DBMS Mini-project has 2 phases. 1.PART - A for 1 month , to get familiar with SQL basics. 2.PART - B ,actual mini-project implementation [Related work to be done in parallel in PART - A, refer deadlines given below.] ---------------------------------------------------------------------------------- PART - A CODE: CS353 DATABASE MANAGEMENT SYSTEMS LAB / MINI PROJECT COMPUTER SCIENCE DEPARTMENT, SDMCET, Dharwad All PART - A,term-works are based on the below problem domain or SRS. [From Navathe] The COMPANY database keeps track of a company's employee, departments and projects. Suppose that after the requirements collection and analysis phase, the database designers provided the following description of the 'miniworld' - the part of the company to be represented in the database. 1. A company is organized into departments. Each department has a unique name, unique number and a particular employee who manages the department. We keep track of the start date when that employee began managing the department. A department may have several locations. 2. A department controls a number of projects, each of which has a unique name, a unique number and a single location. 3. We store each employee's name, social security number, address, salary, sex and birth date. An employee is assigned to one department but may work on several projects, which are not necessarily controlled by the same department. We keep track of the number of hours per week that an employee works on each project. We also keep track of the direct supervisor of each employee. 4. We want to keep track of the dependents of each employee for insurance purposes. We keep each dependent's first name, sex, birth date and relationship to the employee. ------------------------------------------------------------------------------------ TERM WORKS [FOR A DIV ONLY] ------------------------------------------------------------------------------------ Week Term Work Date 1 Lab -1 : Feb 1st-6th A. Introduction and getting familiar with Oracle software. B. CREATE table Employee,Department & Dept_Location. C. Use INSERT,DELETE,SELECT,DROP table queries. Lab -2: A. CREATE all the required tables . B. INSERT at least 5 rows into each table. C. Use DEFAULT,PRIMARY KEY,FOREIGN KEY,ALIASES etc wherever required. D. Use ALTER table,UPDATE table,DROP Column,SELECT, FROM, WHERE clause wherever required. 2 2 Lab -1 : Feb 8th-13th A. Use GROUP BY,HAVING, ORDER BY etc wherever required B. Renaming,Commenting table/Column etc Lab -2: A. Use SQL Operators:AND, OR,NOT,ANY,UNION,MINUS, INTERSECTION,<,>,<>,=,IN,BETWEEN,NOT IN,EXIST, NOT EXIST, LIKE , NULL etc 3 Lab -1 : Feb 15th-20th A. Use of Built in Functions: ABS,CEIL,FLOOR, MOD,POWER,ROUND,SIGN,SQRT,TRUNC,CHAR,INITCAP, LOWER,SOUNDEX,COUNT(*),DATE related functions. Lab -2 : A. Co-Related Sub Query,JOIN (Inner,Outer,Left,Right etc), Writing queries for user search requirements. 4 A. PL-SQL,Triggers,Cursors,Stored procedures Feb 22nd-27th -------------------------------------------------------------------------------- PART - B ------------------------------------------------------------------------------ PLEASE NOTE: 1. MINIMUM 1 and MAXIMUM 4 studnets per team. 2. Team members should belong to the same batch. 3. Team once formed will not be allowed to change. 4. No TEAM is alowed do the same project. 5. In the below form, just write down names of your team members and the 2 preferences of your project, from the below given list.[In case of any clashes,it will be resolved by me.] 6. Teams of A & B divisons will have to do different projects. 7. Ultimately all projects will be finalized by us[MBP/UPK]. STICK TO THE DEADLINES MENTIONED BELOW. ------------------------------------------------------------------- Sl.No | Activity | Last Date | ------------------------------------------------------------------- 1 | SYNOPSYS SUBMISSION* | 19 / Feb / 2010 | 2 | SUBMISSION OF DESIGN (ER Diagram) | 26 / Feb / 2010 | 3 | IMPLEMENTATION | 26 / Mar / 2010 | 4 | TESTING | 09 / Apr / 2010 | 5 | REPORT & PPT | 16 / Apr / 2010 | 6 | DEMONSTRATION | 23 / Apr / 2010 | ------------------------------------------------------------------- *Regarding SYNOPSYS SUBMISSION: Soon after the finalizing your project problem domain, you have to collect the requirements from the end-users of the software[mini-preoject],[Will be expalined to you by me] which you have to submit as the SYNOPSYS or SRS [Software Requirements Sepcification]. CHOOSE one among the following as your preference [to be mention in the form below]. 1.Leave Application System for faculty 2.Blood Group Tracker for students 3.Library Management Software 4.Inter-communication Software for college 5.Final Year Projects List Managements 6.Generalized event registration software for students 7.Digital Work Dairy for staff at College level – Activity Tracker 8.Hobby Management for students 9.Dynamic Website for Industrial Estate – Gokul Road 10.Hospital Management Software 11.Shop Management Software 12.Simulating tally, and then modifying it according to client's name. 13.Alumni Block Booking, Seminar Hall, CCF Booking etc 14.Automated Birth day wisher thru mail,SMS 15.Placement Details Tracker 16.Alumni Data Bank – Highly Complicated 17.Buy-Sell Electronic goods within SDM 18.Buy-Sell Property within Hubli-Dharwad 19.Social Networking site only for SDMCET students, Alumni-Highly Complicated. 20.Career Launcher – For students, Keep all last date of all competitive exams 21.Insurance reminder – For students, faculty 22.All forms of all application , B.E , M-Tech, MBA, MCA , QIP, Alumni Block booking form, etc etc – Scan it, store it – With different templates 23.Book my show in Hubli, Dharwad, 24.Tours- Travels Network in Hubli Dharwad 25.Kalyan Mantap booking(Marriage Hall,Decorates,Caters etc) in Hubli – Dharwad 26.Provide mobile medical services for Senior Citizens, by storing health infmtn 27.Second hand computer peripherals sale in Hubli-Dharwad 28.Showroom Database System - Project 29.Time-Table Scheduler 30.Retail Management System 

Click here for the form

Monday, February 1, 2010

DBMS Lesson Plan

DBMS Mini-Project

Each student is required to post at-least one project idea. Ex: Leave Application,Blood group Tracker etc. Please Note: 1.Team Size MINIMUM 1 and MAXIMUM 4 students per team. 2.TEAM MEMBERS SHOULD BELONG TO THE SAME LAB BATCH. Ex: 1 student from A1 and 2 students from A2 and 1 from A3 are not allowed.

Click here to access the form