Sie sind auf Seite 1von 35

Abstract of student information system

The mission of the Student Information System project is to create an integrated information
technology environment for students, HOD , faculty, Staff and administration. Our goal is to focus on
customers, services and integration for end users.

Student Information System Web-based self-service environment for students , prospective


students, and employees; an administrative transaction processing environment for university staff to
conduct day-to -day business; an information environment for all levels of faculty and staff to do
reporting, data extraction, and information analysis.

A student information system (SIS) is a software application for educational establishments to


manage student data. Student information systems provide capabilities for entering student test and
other assessment scores, building student schedules, tracking student attendance, and managing many
other student-related data needs in a school, college or university

Our easy-to-use, integrated College administration applications are proven to reduce time spent
on administrative tasks so you can concentrate on raising student achievement. Student Information
System have to accept, process and generate reports accurately and any point of time any user can get
the student information

1
1. INTRODUCTION

3.1 BRIEF OVERVIEW OF THE SYSTEM:

Student Information System Web-based self-service environment for students , prospective


students, and employees; an administrative transaction processing environment for university staff to
conduct day-to -day business; an information environment for all levels of faculty and staff to do
reporting, data extraction, and information analysis.

A student information system (SIS) is a software application for educational establishments to


manage student data. Student information systems provide capabilities for entering student test and
other assessment scores, building student schedules, tracking student attendance, and managing many
other student-related data needs in a school, college or university

The mission of the Student Information System project is to create an integrated information
technology environment for students, HOD , faculty, Staff and administration. Our goal is to focus on
customers, services and integration for end users.

Our easy-to-use, integrated College administration applications are proven to reduce time spent
on administrative tasks so you can concentrate on raising student achievement. Student Information
2
System have to accept, process and generate reports accurately and any point of time any user can get
the student information

3.2 ADVANTAGES

Student Information System (SIS) Vision:

1. Provide better services to students, faculty, staff, prospective students, administration, etc.
1. Provide meaningful, consistent, and timely data and information to end users.

1. Promote vision of senior management to address opportunities for change.

1. Update technology infrastructure for more effective and flexible delivery of new systems.

1. Promote efficiencies by converting paper processes to electronic form.

2. MOTIVATION

The mission of the student information system project is to create an integrated information
technology environment student, HOD, faculty, staff and administration. Our goal is to focus on
customers, services and integration for end users.

3. PROBLEMSTATEMENT

1. Effective for Administration purpose

2. Cheap

3. Better Service

3
4. PROBLEM OBJECTIVES

1. Improve operational & Streamlining operations

2. Maintain student’s database

3. Maintain global standards

4. Reduce Manpower

1. Accuracy

2. Better service

3. Improved management and control

4. Neat formatted report

4
5. REQUIREMENT ANALYSIS

SOFTWARE REQUIREMENT SPECIFICATION

7.1 SOFTWARE REQUIREMENT

1. Language -j2sdk1.5

2. J2ee technologies - Servlets

3. Front End - Html

4. Back End - Oracle 10g

5. Platform -Windows XP

6. Application server -Tomcat 6.0

7.2 HARDWARE REQUIREMENT

1. Processor -Intel Pentium iv

2. RAM -32 GB

3. Hard Disk -1 GB

4. Key Board -101 keys

5. Mouse -Any pointing device

5
6. TESTING

11.1 TESTING METHODOLOGY DESCRIPTION

1. Introduction:

Testing is one of the most important phases in the software development activity. In software
development life cycle (SDLC), the main aim of testing process is the quality; the developed software
is tested against attaining the required functionality and performance.

During the testing process the software is worked with some particular test cases and the output
of the test cases are analyzed whether the software is working according to the expectations or not.

The success of the testing process in determining the errors is mostly depends upon the test
case criteria, for testing any software we need to have a description of the expected behaviour of the
6
system and method of determining whether the observed behaviour confirmed to the expected
behaviour.

2. Levels of testing:

Since the errors in the software can be injured at any stage. So, we have to carry out the
testing process at different levels during the development. The basic levels of testing are Unit,
Integration, System and Acceptance Testing.

The Unit Testing is carried out on coding. Here different modules are tested against the

specifications produced during design for the modules. In case of integration testing different

tested modules are combined into sub systems and tested in case of the system testing the full

software is tested and in the next level of testing the system is tested with user requirement

document prepared during SRS.

There are two basic approaches for testing. They are

Fuctional testing : In Functional Testing test cases are decided solely on the basis of

requirements of the program or module and the internals of the program or modules are not

considered for selection of test cases. This is also called Black Box Testing

Structural Testing : In Structural Testing test cases are generated on actual code of the

program or module to be tested. This is called White Box Testing.

3. Testing Process

A number of activities must be performed for testing software. Testing starts with test plan. Test plan
identifies all testing related activities that need to be performed along with the schedule and guide lines
for testing. The plan also specifies the levels of testing that need to be done, by

7
identifying the different testing units. For each unit specified in the plan first the test cases and reports
are produced These reports are analyzed.

Test plan:

Test plan is a general document for entire project, which defines the scope, approach to be taken and
the personal responsible for different activities of testing. The inputs for forming test plane are as
follows.

1. Project plan

2. Requirements document

3. System design

TEST CASES

Test case specification

Although there is one test plan for entire project test cases have to be specified separately for
each test case. Test case specification gives for each item to be tested. All test cases and outputs
expected for those test cases.

Test Case execution and Analysis

The steps to be performed for executing the test cases are specified in separate document called
test procedure specification. This document specify any specify requirements that exist for setting the
test environment and describes the methods and formats for reporting the results of testing.

Unit testing:

Unit testing mainly focused first in the smallest and low level modules, proceeding one at a time.
Bottom-up testing was performed on each module. As developing a driver program, that tests modules
by developed or used. But for the purpose of testing, modules themselves were used as stubs, to print
verification of the actions performed. After the lower level modules were tested, the modules that in
the next higher level those make use of the lower modules were tested.

8
Each module was tested against required functionally and test cases were developed to test the
boundary values.

Integration testing

Integration testing is a systematic technique for constructing the program structure, while at the same
time conducting tests to uncover errors associated with interfacing. As the system consists of the
number of modules the interface to be tested were between the edges of the two modules.

The software tested under this was incremental bottom-up approach.

Bottom-up approach integration strategy was implemented with the following steps.

1. Low level modules were combined into clusters that perform specific software sub functions.

2. The clusters were then tested.

System testing

System testing is a series of different tests whose primary purpose is to fully exercise the

computer- based system. It also tests to find discrepancies between the system and its original

objective , current specifications.

9
3. MAINTENANCE

Maintenance the last phase in the software engineering process. As more programs are developed,
a distributing trend has emerged the amount of effort and a resource expended on software
maintenance is growing. In total project development maintenance takes 65% of effort. In software
maintenance there are four types. They are

1. Adaptive Maintenance
2. Corrective Maintenance
3. Perfective Maintenance
4. Preventive Maintenance
Adaptive Maintenance is applied when changes in the external environment precipitate
modifications to software. It deals with adapting the software to new environments.

10
Perfective Maintenance incorporates enhancements that are requested by user community. It deals
with updating the software according to changes in user requirements.

Corrective Maintenance acts to correct errors that are uncovered after the software is in use. It
deals with fixing bugs in the code.

Preventive Maintenance improves future maintainability and reliability and provides a basis for
future enhancement. It deals with updating documentation and making the software more
maintainable. Tasks performed during the software engineering process define maintainability and have
an important impact in the success of any maintenance approach. Reverse Engineering and
Reengineering are the tools and techniques used to maintain the project.

There are four major problems that can slow down the maintenance process

1. Unstructured Code
2. Maintenance programmers having insufficient knowledge of the system
3. Documentation being absent
4. Out of Date, or at best insufficient
The success of the maintenance phase relies on these problems being fixed earlier in the life cycle

11
#include<stdio.h>
#include<conio.h>
#include<string.h>
#include<graphics.h>
#include<dos.h>
#include<process.h>
struct strudent
{
char name[60];
int id;
int mark[5];
float gp[5];
char grade[2];
}st[5];

void menu();
void menu1();
void menu2();
void mouse();
void mouse1();
void mouse2();
void message();
void single_info();
void multi_info();

12
void single_result();
void view_all();
int check(int mrk);
float s_gp(int mrk);
void grd(float gpa1,int i);
void output(int i);
unsigned initmouse();
void showmouse();
void hidemouse();
void restrictmouse(int x1,int y1,int x2,int y2);
void getmouse(int *button,int *x,int *y);
void main()
{
clrscr();
menu();
}
void menu()
{
char mnu[30];
int gd=0,gm;
initgraph(&gd, &gm,".\\BGI");
rectangle(60,350,400,60);
rectangle(145,130,300,100);
rectangle(145,190,300,160);
rectangle(250,280,350,250);
setcolor(10);

13
sprintf(mnu," STUDENT RESULT SYSTEM");
settextstyle(TRIPLEX_FONT,0,5);
outtext(mnu);

setcolor(13);
sprintf(mnu,"MAIN MENU");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(170,70,mnu);

setcolor(12);
sprintf(mnu,"STUDENT INFO");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(160,103,mnu);

setcolor(12);
sprintf(mnu,"VIEW RESULT");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(164,163,mnu);

setcolor(YELLOW);
sprintf(mnu,"EXIT");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(280,253,mnu);
message();
mouse();
}

14
void mouse()
{
int x,y,button;
if(initmouse()==0)
{
printf("Mouse support unavailable");
return;
}
restrictmouse(0,0,650,485);
showmouse();
while(1)
{
getmouse(&button,&x,&y);
if(x>=144&&x<=301&&y>=100&&y<=129&&button==1)
{
closegraph();
clrscr();
menu1();
}
else
if(x>=144&&x<=301&&y>=158&&y<=190&&button==1)//checks if exit button
is pressed or not
{
closegraph();
clrscr();
menu2();

15
}
else
if(x>=248&&x<=352&&y>=248&&y<=281&&button==1)//checks if exit button
is pressed or not
{
closegraph();
break;
}
}
}
void menu1()
{
char mnu[30];
int gd=0,gm;
initgraph(&gd, &gm,".\\BGI");
rectangle(60,350,400,60);
rectangle(145,130,300,100);
rectangle(145,190,300,160);
rectangle(250,280,350,250);
rectangle(80,280,195,250);
setcolor(10);
sprintf(mnu,"STUDENT EXAMNINATION SYSTEM");
settextstyle(TRIPLEX_FONT,0,5);
outtext(mnu);

setcolor(13);

16
sprintf(mnu,"STUDENT INFORMATION");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(125,70,mnu);

setcolor(12);
sprintf(mnu,"SINGLE STUDENT");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(149,103,mnu);

setcolor(12);
sprintf(mnu,"MULTI STUDENT");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(153,163,mnu);

setcolor(YELLOW);
sprintf(mnu,"MAIN MENU");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(86,253,mnu);

setcolor(YELLOW);
sprintf(mnu,"EXIT");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(280,253,mnu);
message();
mouse1();
}

17
void mouse1()
{
int x,y,button;
if(initmouse()==0)
{
printf("Mouse support unavailable");
return;
}
restrictmouse(0,0,650,485);
showmouse();
while(1)
{
getmouse(&button,&x,&y);
gotoxy(35,20);
if(x>=144&&x<=301&&y>=100&&y<=129&&button==1)
{
closegraph();
clrscr();
single_info();
}
else
if(x>=144&&x<=301&&y>=158&&y<=190&&button==1)//checks if exit button
is pressed or not
{
closegraph();
clrscr();

18
multi_info();
}
else
if(x>=248&&x<=352&&y>=248&&y<=281&&button==1)//checks if exit button
is pressed or not
{
closegraph();
break;
}
else
if(x>=78&&x<=196&&y>=249&&y<=281&&button==1)//checks if exit button is
pressed or not
{
closegraph();
menu();
}
}
}
void single_info()
{
int i,j=-1;
printf("\nEnter Name:");
gets(st[0].name);
printf("\nEnter id:");
scanf("%d",&st[0].id);
for(i=0;i<5;i++)

19
{
printf("\nEnter %d Mark:",i+1);
scanf("%d",&st[0].mark[i]);
j=check(st[0].mark[i]);
if(j==1)
{
printf("\nYou Enter Invalid input.");
printf("PRESS ANY KEY TO EXIT.");
getch();
exit(0);
}
}
menu();
}
void multi_info()
{
int i,j=-1,k;
for(k=0;k<5;k++)
{
printf("\nEnter %d Name:",k+1);
scanf("%s",st[k].name);
printf("\nEnter id:");
scanf("%d",&st[k].id);
for(i=0;i<5;i++)
{
printf("\nEnter %d Mark:",i+1);

20
scanf("%d",&st[k].mark[i]);
j=check(st[k].mark[i]);
if(j==1)
{
printf("\nYou Enter Invalid input.");
printf("PRESS ANY KEY TO EXIT.");
getch();
exit(0);
}
}
}
menu();
}
int check(int mrk)
{
if(mrk>100 || mrk<0)
return 1;
else
return 0;
}

void menu2()
{
char mnu[30];
int gd=0,gm;

21
initgraph(&gd, &gm,".\\BGI");
rectangle(60,350,400,60);
rectangle(145,130,300,100);
rectangle(145,190,300,160);
rectangle(250,280,350,250);
rectangle(80,280,195,250);
setcolor(10);
sprintf(mnu," STUDENT EXAMINATION SYSTEM");
settextstyle(TRIPLEX_FONT,0,5);
outtext(mnu);

setcolor(13);
sprintf(mnu,"RESULT");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(190,70,mnu);

setcolor(12);
sprintf(mnu,"SINGLE RESULT");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(155,103,mnu);

setcolor(12);
sprintf(mnu,"VIEW ALL");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(180,163,mnu);

22
setcolor(YELLOW);
sprintf(mnu,"MAIN MENU");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(86,253,mnu);

setcolor(YELLOW);
sprintf(mnu,"EXIT");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(280,253,mnu);
message();
mouse2();
}
void mouse2()
{
int x,y,button;
if(initmouse()==0)
{
printf("Mouse support unavailable");
return;
}
restrictmouse(0,0,650,485);
showmouse();
while(1)
{
getmouse(&button,&x,&y);
gotoxy(35,20);

23
if(x>=144&&x<=301&&y>=100&&y<=129&&button==1)
{
closegraph();
clrscr();
single_result();
}
else
if(x>=144&&x<=301&&y>=158&&y<=190&&button==1)//checks if exit button
is pressed or not
{
closegraph();
clrscr();
view_all();
}
else
if(x>=248&&x<=352&&y>=248&&y<=281&&button==1)//checks if exit button
is pressed or not
{
closegraph();
exit(0);
}
else
if(x>=78&&x<=196&&y>=249&&y<=281&&button==1)//checks if exit button is
pressed or not
{
closegraph();

24
menu();
}
}
}
void single_result()
{
int id1,i,flag=-1,j;
float total_gp=0,gpa;
printf("Enter Id:");
scanf("%d",&id1);
for(i=0;i<5;i++)
if(id1==st[i].id)
{
flag=1;
break;
}
if(flag==1)
{
for(j=0;j<5;j++)
{
st[i].gp[j]=s_gp(st[i].mark[j]);
total_gp+=st[i].gp[j];
}
gpa=total_gp/5;
grd(gpa,i);
output(i);

25
printf("\nPress any key to continue.......");
getch();
menu2();
}
else
{
printf("NOT FOUND.");
printf("\nPress any key to continue.......");
getch();
menu2();
}

}
void view_all()
{
float total_gp,gpa;
int i,j;
for(i=0;i<5;i++)
{
total_gp=0;
for(j=0;j<5;j++)
{
st[i].gp[j]=s_gp(st[i].mark[j]);
total_gp+=st[i].gp[j];
}
gpa=total_gp/5;

26
grd(gpa,i);
getch();
}
for(i=0;i<5;i++)
{
printf("\n %d student",i+1);
printf("\nStudent name:%s",st[i].name);
printf("\nStudent Id:%d",st[i].id);
printf("\nStudent Grade:%s",st[i].grade);
}
printf("\nPress any key to continue.......");
getch();
menu2();
}
float s_gp(int mrk)
{
float gp;
if(mrk>89)
gp=4;
else if(mrk>79)
gp=3.75;
else if(mrk>69)
gp=3.5;
else if(mrk>59)
gp=3.25;
else if(mrk>49)

27
gp=3;
else
gp=0;
return gp;
}
void grd(float gpa1,int i)
{
if(gpa1==4)
strcpy(st[i].grade,"A+");
else if(gpa1>=3.75)
strcpy(st[i].grade,"A");
else if(gpa1>=3.5)
strcpy(st[i].grade,"A-");
else if(gpa1>=3.25)
strcpy(st[i].grade,"B+");
else if(gpa1>=3)
strcpy(st[i].grade,"B");
if(gpa1<3)
strcpy(st[i].grade,"F");
}
void output(int i)
{
clrscr();
printf("\nStudent Name:%s",st[i].name);
printf("\nStudent ID:%d",st[i].id);
printf("\nStudent Grade:%s",st[i].grade);

28
}

void message()
{
char mnu[30];
setcolor(WHITE);
rectangle(637,350,420,60);
setcolor(11);
sprintf(mnu,"MADE BY:");
settextstyle(TRIPLEX_FONT,0,1);
outtextxy(440,60,mnu);

sprintf(mnu," YASHODA");
outtextxy(440,100,mnu);

sprintf(mnu," Roll No:2030");


outtextxy(440,140,mnu);

sprintf(mnu," Class: B COM-II(CAV)");


outtextxy(440,180,mnu);

}
unsigned initmouse()

29
{
_AX=0;
geninterrupt(0x33); //Generate Inpterrupt
return _AX;
}

void showmouse()
{
_AX=1;
geninterrupt(0x33);
}

void hidemouse()
{
_AX=2;
geninterrupt(0x33);
}

void restrictmouse(int x1,int y1,int x2,int y2)


{
_AX=7;
_CX=x1;
_DX=x2;
geninterrupt(0x33);
_AX=8;
_CX=y1;

30
_DX=y2;
geninterrupt(0x33);
}

void getmouse(int *button,int *x,int *y)


{
_AX=3;
geninterrupt(0x33);
*button=_BX;
*x=_CX;
*y=_DX;
}

31
32
33
5. CONCLUSION

1. The system provides an excellent support to the corporate client because they can directly mail

their problem online.

2. Computerized surveying system provides an easy, fast access and support for the users.

3. The usage of software increases the efficiency, decreases the effort

4. It has been thoroughly tested and implemented.

34
5. REFERENCES

1. SOFTWARE ENGINEERING - ROGER.S.PRESMAN

2. SYSTEM ANALYSIS AND DESIGN - ELIAS.M.AWAD

3. THE COMPLETE REFERENCE-JAVA- SCHILDT

4. UNIFIED MODELLING LANGUAGE- GRADY BOOCH

35