INDEX
S.NO PARTICULARS 1 2 3
ABSTRACT ANALYSIS DESCRIPTION OF SOFTWARE ORACLE,SQL&SQL* PLUS , DEVELOPER DEVELOPER 2000 20 00
4
HARD HARDW WARE AND SO SOFT FTW WARE US USED IN IN TH THE PRO PROJE JEC CT
5
SYSTEM DATA FLOW DIAGRAMS
6
TABLES
7
DESIGN
8
SCREENS
9
REPORTS
10
CODING
11
TESTING & MAINTENANCE
PAGE.NO
ABSTRACT Admission maintenance system is a project designed to fulfill the requirement requirement of Aditya Educational Groups. The client has many leading colleges, established with an objective of providing high quality students, with blue-chip standards. They spread into diverse areas of educational fields and placements. This project will be used on a test basis in one of the colleges. In the college there are more than 2000 students. Examination is regularly conducted by the college. So far the admissions of various students were maintained manually. The client requires a project for the automation of maintenance of student admission. a dmission. For that purpose I designed a project to maintain student’s student’s marks details with the help pf computers.
In this project I prepared prepared different forms and reports, with suitable coding, for the maintenance of student details, entry of student admission generation of reports on individual as well as a group criterion.
ANALYSIS Student admission details deals with the entry and maintenance of admission in the college files. Now a day, the E-ADMISSION maintenance system is becoming popular for maintaining the information Of the students. Aditya educational institution has established its degree college in and it has become a leading college in Kakinada. This college has strength of more than 30000 students. As the strength of the students is increasing, maintenance of student admission details and student Details became difficult for the college. So the college has decided to automate the student admission system With the use of efficient software. In order to provide prompt information regarding student admission details Our principal has decided to adopt the student Eadmission details maintenance system in the place of manual maintenance system.
SYSTEM DATA FLOW DIAGRAM
STUDENT REGISTRATION
Tables STUDENT19 CREATE TABLE STUDENT19(SNO NUMBER (5),SNAME VARCHAR2(15),D_BIRTH ARCHAR2(15 ),D_BIRTH DATE,ADDRE DATE,ADDRESS SS VARCHAR2(150),FNAME ARCHAR2(15 0),FNAME VARCHAR2(15),COURSE ARCHAR2(15 ),COURSE VARCHAR2(5),PRE_COU ARCHAR2(5), PRE_COURSE RSE VARCHAR2(5),BLOODGROU ARCHAR2(5) ,BLOODGROUP P VARCHAR2(4) VARCHAR2(4),PRE_COLL ,PRE_COLL TH VARCHAR2(10),AVG_10 NUMBER(5,2),AVG_INTER NUMBER(5,2));
ADMISSION19 CREATE TABLE ADMISSION19 (ADMNO NUMBER (4), COURSEID NUMBER (4), FIRST_LANGUAGE FIRST_LANGUAGE VARCHAR2(10),SECOND_LA ARCHAR2(10 ),SECOND_LANGUAGE NGUAGE VARCHAR2(1 VARCHAR2(10),FEE 0),FEE NUMBER(10,2));
COURSEFORM19 CREATE TABLE COURSEFORM19 (COURSEID NUMBER (4), COURSENAME VARCHAR2 (20), S1 VARCHAR2 (13), S2 VARCHAR2 (13), S3 VARCHAR2 (10), FEE NUMBER (5));
DESIGN This project is concentrate on the computerization of student’s admission maintenance system. The total project consists of two modules.
Student details module admission module • The student module deals with the entry of student details. •
The admission module deals with the entry of details of student’ admission, and its maintenance and preparation of various reports like 1. Individual Students Reports 2. Group Reports.
STUDENTS DETAILS FORM
COURSE FORM:
STUDENT ADMISSION FORM:
GROUP REPORT
ADITYA DEGREECOLLEGE FOR WOMEN KAKINADA STUDENT ADMISSION DETAILS DETAILS
COURSENAME: B.COM. YEAR YEAR : III III ADMNNO
STUDENT NAME
FE E
1 000 1 001 1 002 1003 1004 1005 1006
POOJA JAIN K. ARUNA SONAM JAIN M.B.V SAISRI G.RAMYA K.SHANTI C.H RAJESWARI
95 00 95 00 95 00 92 00 8700 9500 7600
INDIVIDUAL REPORT
ADITYA DEGREECOLLEGE FOR WOMEN KAKINADA
COURSE DETAILS
COUR COURSE SEID ID
COURS COURSEN ENAM AME E
FEE FEE
100 101 102
B.SC (MECS) B.SC (MPCS) B.SC (MSTCS)
125 00 12 8 0 0 15000
CODING
MAINFORM 1. BUTTONS o
STUDENT DETAILS
WHEN BUTTON-PRESSED GO_BLOCK (‘STUDENT’); o
COURSE DETAILS
WHEN BUTTON PRESSED GO_BLOCK (‘COURSE’); o
ADMISSION DETAILS
WHEN BUTTON-PRESSED GO_BLOCK (‘ADMN’); o
REPORT
WHEN BUTTON-PRESSED SET_ITEM_ PROPERTY (‘MAIN.GROUP’, VISIBLE, PROPERTY_TRUE); PROPERTY_TRUE); SET_ITEM_ PROPERTY (‘MAIN.SINGLE’, VISIBLE, PR OPERTY_TRUE); OPERTY_TRUE); SET_ITEM_ PROPERTY (‘MAIN.GROUP’, ENABLED, PROPERTY_TRUE); SET_ITEM_ PROPERTY (‘MAIN.SINGLE’, ENABLED, PROPERTY_TRUE); PROPERTY_TRUE);
o
GROUP
WHEN-BUTTON-PRESSED GO_BLOCK(‘GROUP’);
o
SINGLE
WHEN-BUTTON-PRESSED
GO_BLOCK(‘SINGLE’);
o
o
DATE PROPERTY PALLET INITIALVALUE = $$DATE$$
TIME PROPERTY PALLET
INITIALVALUE = $$DATE$$
o
EXIT WHEN-BUTTON-PRESSED EXIT_FORM;
STUDENTS DETAILS DETAILS 1. BUTTONS ADD WHEN-BUTTON-PRESSED DECLARE N NUMBER; K NUMBER; BEGIN GO_BLOCK(‘STUDENT’); CLEAR_BLOCK; SELECT COUNT(*) INTO K FROM STUDENT; IF K>=1 THEN SELECT MAX (STUDENT ADMNO) INTO N FROM STUDENT WHERE COURSE=’:COURSE.COURSE’ AND YEAR=: STUDENT.YEAR STUDENT.YEAR N:=N+1; ELSE N:=1; END IF; :STUDENT ADMNO:=N; GO_ITEM(‘STUDENT SNAME’); END; o
o
SAVE
WHEN –BUTTON-PRESSED BEGIN GO_BLOCK (‘STUDENT’); COMMIT_FORM; GO_ITEM (‘ADD’); END; o
VIEW
WHEN-BUTTON-PRESSED DECLARE L VARCHAR 2(10) ; A NUMBER; B NUMBER; BEGIN GO_BLOCK (‘STUDENT’); SELECT MAX (ADMNO) INTO B FROM STUDENT S TUDENT ORDER BY SCNO; L: =GET_ITEM_PROPERTY (‘VIEW’,’LABEL’,’NEXT’); IF L=’VIEW’ THEN SET_ITEM_PROPERTY (‘VIEW’,’LABEL’,’NEXT’); EXECUTE_QUERY; ELSE NEXT_RECORD; END IF; IF B=: STUDENT, SCNO THEN SET_ITEM_PROPERTY (‘VIEW’,’LABEL’,’VIEW’); ENDIF; END; o
DELETE
WHEN –BUTTON-PRESSED BEGIN GO_BLOCK (‘STUDENT’); DELETE_RECORD; COMMIT; END;
o
EXIT
WHEN BUTTON-PRESSED GO_BLOCK (‘MAIN’);
COURSE FORM
1. BUTTONS o
ADD GO_BLOCK (‘COURSE’); CLEAR_BLOCK (NO_COMMIT);
SAVE
WHEN BUTTON-PRESSED BEGIN GO_BLOCK (‘COURSE’); COMMIT_FORM; END;
DELETE WHEN-BUTTON-PRESSED BEGIN GO_BLOCK (‘COURSE’); DELETE_RECORD; END; EXIT WHEN BUTTON-PRESSED GO_BOLCK (‘MAIN’);
GROUP DETAILS BUTTONS o
DISPLAY
WHEN-BUTTON-PRESSED GO_BLOCK (‘STUDENT ‘); DECLARE PL_ID PARAMLIST; BEGIN RUN_PRODUCT (REPORTS, (REPORTS, ‘F: \ PROJECT \ STUDENT ‘, SYNCHRONOUS, RUNTIME, FILESYSTEM, PL_ID, NULL); END;
o
EXIT
WHEN-BUTTON-PRESSED GO_BLOKE (‘MAIN’);
INDIVIDUAL DETAILS BUTTONS o
DISPLAY
WHEN-BUTTON-PRESSED GO_BLOCK (‘DETAIL13’); (‘DETAIL13’); DECLARE PL_ID PARAMLIST; BEGIN
RUN_PRODUCT (REPORTS,, ‘F:\PROJECT\GROUPDETAILS’, ‘F:\PROJECT\GROUPDETAILS’, SYNCHRONOUS, RUNTIME, FILESYSTEM, PL_ID, NULL); END;
o
EXIT
WHEN BUTTON PRESSED GO_BLOCK (‘MAIN’);