Beruflich Dokumente
Kultur Dokumente
Project Report
On
ACADEMIC YEAR
(2010-2011)
SUBMITTED BY:
1. Ajay Krishnan (3602)
2. Parag Amritkar (3604)
3. Aliasgar Batterywala (3611)
1.Synopsis 1
2.Software development life cycle:
2. Snapshots
3. References 62
Synopsis
Project Members:
Mr. Ajay Krishnan (3602)
Ms. Parag Amritkar (3604)
Mr. Aliasgar Batterywala(3611)
Project Description:
This system will be used for the term work marks calculation for the practical subjects
based on the attendance and performance of the students. Basically there are two modules each
for attendance and assessment. Admin has to manage the student, faculty, subject, assignment
information i.e. add, update or delete.
Objective:
To provide the tool for automated tool for attendance and assessment of practical subjects for
the students in error free manner.
Scope:
The project is developed for IT department and classes SE,TE and BE Only. The attendance
and assessment is also done only for respective practical sessions only. The system will also
provide facility to add, update or delete the students, subjects and faculties of the department.
Feasibility Study:
It becomes easy to connect with the User-Friendly Modules in Microsoft Visual Basic 6.0
and is Portable throughout the Windows Versions. Oracle supports Machine Independency and
provides Virus-free atmosphere making the database Robust.
Limitations:
The System will be used for assessment of IT department only.
Resources & Requirements:
Front End:
Microsoft Visual Basic 6.0
Back End:
Oracle 9i
The project can effectively used in other departments and colleges with some changes into
existing system.
Software development life cycle:-
The system will be used for the assessment of students for the term work
marks. It can be used for recording the student’s attendance for a particular lab
session. This system also has a superuser(admin) who manages the database of
students,faculty as well as subjects and faculty uses a assessment stuff after
login.
The system proposed can be implemented efficiently using front end like
Visual Basic and backend as Oracle.
1.3 Designing :
Student
Rno Fname Mname Lname Batch Test_performance Th_attendance
Faculty
Fid Ffname fmname Flname Password qualification
Subject
Subid Subname Marks_out_of No_of_asssgns
Assessment
Rno Fid Subid Tw_marks
Assignment_info
Assgn_no Sub_id Title Perf_sch_date Perf_act_date
Assignment_eval
Assgn_no Rno Sub_id Perf_act_date Sub_act_date Rpp Spo
Faculty_sub_batch
Fid Batch Sub_id
Attendance
Rno Date_time_Batch
NOTE:
Attendance:
Rno Sub_id Date Time Status
This table will have many redundant values which will be equal to:
No. of students * No. of practical sessions in each Subject conducted
To prevent this we have made a table for each batch for taking the attendance.
This table has the roll no of the student as the primary key. When the
attendance of a session is taken by the respective faculty, a new column to the
respective table is added ,whose column name is the date and time of the
current session and subject id of the subject with which the faculty has logged
in, and the status of the student whether present or absent is stored in the
column.
In this case the total number of records will be equal to the number of
students.
Studtemp1 and Studtemp2 are two temporary tables which have been used for
sorting the students according to their names, assigning them roll numbers and
inserting them to the main table.
1.4 Scope:
The development environment for front end used was Visual Basic 6.0 and
the backend used was Oracle 9i.
1.6 Testing: