Minor Report3

7/31/2019 Minor Report3

1/53

Student Management Information System

1

Chapter 1

Introduction to Student Management System

E-Campus is the strategy for the transition to the E-university. The disadvantage of having

two campus-sites within a distance of 20 kilometers will be transformed into an advantage by

intensive and innovative use of mobile and multimedia (learning-) technologies. The strategy

is based on a wholistic view, in which all the processes relevant for teaching and learning

in the university have to be taken into account in an overall perspective of change

management, if the university is to master the challenges of the 21st century. Therefore,

teaching and learning, services and infrastructures, their integration and, last not least, the

organization university as a whole have to be re-aligned and re-adapted.

E-learning identified with web-based learning - was taken up by pioneers and innovators.

Discussion and development focussed mostly on the technical possibilities and requirements

for e-learning software. The changed social paradigm, i.e. the shift from industrial society to

the information or knowledge society, had led to a fundamental reconception of education

the concept of life-long learning. E-learning seemed to be the right solution at the right time

to meet the immensely growing demands for education, and perpetual flexibility and

innovation in the educational sector. Hence, e-learning was seen as the lever to completely re-

invent education, including the universities. The vision developed then was the virtual

university, i.e. a shift to generalised Internet-based distance education.

In the existing education system, there are lots of fields to be maintained efficiently, like,

students details management, faculty management, timetable management in case of disorder

in the management, bus management in case of low strength of students coming to the

college. A campus is the combination of the above such management areas. The problem

arises in each management system is regarding the effectiveness of the system. For example,

in case of absence of the teacher or in case of exams where the faculties are not free, the

management of timetable is very crucial. In such condition a system is required for the

automation of timetable instead of making the timetable again and again. Also we can take


2/53


2

the case of the bus management system, where again the effectiveness of the system lies in

the better management of the buses during the exams, holidays and many more.

Such problem in the existing education system can be removed using the concept of E-

Campus through which the all the systems that comprises a campus can be automated and can

be made effective by making the systems modifiable, flexible. For e.g. an automated system

for timetable management system makes the management of timetable effective, project

management system allows only such projects that are new and rejects the repeated projects.

Also because of e-campus students can get books of their courses online. So, an effective e-

campus can resolve the all problems of existing campus management.

The re-take of discussions on concepts of e-learning, e-learning strategies and the role of

universities identified one crucial weakness of the first period, namely, the focus on

technical/software-development issues. It was recognized that lecturers, first and foremost

concerned with teaching and the quality of teaching, did not feel attracted or were even

alienated from ICT and e-learning. This opened the dialogue between information technology

and didactics. The second layer of e-learning strategies, consequently, saw its main goal in

creating e-learning projects with high quality content and high quality didactics. Therefore,

funding went into these directions and away from technical solutions. The vision developed

then, was that of hybridization, concepts of combining online learning with the campus

university, instead of replacing the campus by the virtual university. This again gave rise to

the implementation of many projects, mostly funded, from which a wealth of valuable lessons

can be drawn, especially in terms of innovative learning scenarios such as collaborative

learning, problem-oriented learning, mobile learning etc. Soon it became obvious, that we

were still far from a broad adaptation of new media in learning teaching or e-learning by a

second and third wave of lecturers (after the first wave of pioniers and innovators). To make

advances in this direction became the objective of the third generation of e-learning

strategies. The focus now shifted to concerns of how to address lecturers and their needs, i.e.

to the efficiency and availability of IT- and consulting services and the development of

specific support structures, such as dedicated teams for consulting/coaching of lecturers,

which were set-up in many universities throughout Europe (competence- or e-competence

teams, e-learning or learning technologies teams and similar). Most of these structures were


3/53


3

started tentatively, i.e. as time-limited projects and pursued a bottom-up approach, targetting

individual lecturers or small groups. The experiences and conclusions from these three

strategic layers resulted in the ascendancy of the fourthcurrentone. It is now increasingly

recognised that e-learning is not just another method of delivery of learning, which may be

adopted by the university (individual chair/department) or not, as they see fit. Rather, it is

understood as a requirement to enrich and change the whole range of learning settings

(time/place, technology) and learning scenarios (didactics, methods) as a sine qua non for a

modern learning/teaching culture. This change of mind (and heart) is due to a number of

factors, such as the competition of universities against each other, as a result of globalization

and the creation of a common European educational space, public comparisons (rankings)

and adaptation to market mindedness, but also the competition with external players,

notably corporate universities, such as the Cisco Netacademy (http://cisco.netacad.net).

One important element in making this change of heart more palatable has been the concept of

hybridization, which dissolved the identification of e-learning and web-based distance-

learning by including media-supported on-site learning and the development of innovations

based on that model. Also, the third layer strategy of creating project teams for specific

consulting and training support to lecturers hit a proverbial glass ceiling. Though new layers

of lecturers (members of the second wave) were undoubtedly reached, the spread of e-

competence and adoption of e-learning reached individuals rather than faclty departments. In

conclusion, these dynamics led to the need to re-position e-learning as a strategy of change,

and no longer just as a combination of skills and technologies, at the centre of the concerns of

the university leadership and from there in a now complementarytop-down approach to

every faculty and department.

E-Campus was part of a strategic initiative of the university, aimed at mapping teaching and

administrative services digitally, and to organize teaching, service and administration as

consistently as possible over the Internet.

A campus-wide portal completes the realization of our vision of the digital campus, in

mappping all services, including access to e-learning platforms and other tools, consulting

and support agencies as well as all study-related administrative facilities in one platform.

Based on a central identity-management and a unitary digital identity, employees and

students of the university will get their personalized access (my-uni-duisburg-essen) to all

the services and information systems relevant to them, including those of the administration


4/53


4

(e.g. immatriculation, exams, time tables etc.) and learning platforms. Information will be

selected and brought to the users according to their user-rights and profile. The portal will

support and extend mobility on and off campus (ubiquitous computing).

Introduction: Student Faculty Interaction

The purpose of this module is to interaction with the results of a qualitative study of student-

faculty interactions that occur outside of the classroom. The work quantifies and qualifies the

nature of student-faculty interactions, sheds light on the determinants of student-faculty

interactions, and reveals the dynamic processes that underlie contact between faculty and

students outside of the classroom. Results indicate that students have minimal contact with

faculty members outside the classroom. When contact does occur it is most often related to

specific course requirements. Students do not appear to be aware of the importance of

interacting with faculty unless it is for a specific, often course-related, matter. Results

also illustrate key factors that deter and facilitate student-faculty interactions. The

findings and their implications are of interest to faculty, student life professionals, and

administrators alike. Measured across states, tuition and fees collected per full-time-

equivalent student at public institutions of higher education rose at an average inflation-

adjusted annual rate of 4.65% over the period 1986-1996. Over the same period, inflation-

adjusted state appropriations per full-time-equivalent student remained roughly flat, rising a

paltry 0.36% (Humphreys and Wilson, 2003). These figures indicate that higher education is

both increasingly costly, and that the burden of that cost has been shifting away from

taxpayers and towards students. Given this state of affairs, it comes as no surprise that

institutions of higher education are increasingly under.

Introduction: Student Information Sharing

To have view over the present era of the interaction among the students , we can see that the

students are not having general awareness and also lack of interaction among themselves,

among students and faculties, etc. The students dont even know about the latest technology

and tools that are in the market. Also the freshers in the college, due to lack of confidence and


5/53


5

fear are not able to interact with the seniors and faculties for the information regarding the

course books. In fact the students even dont know how to attempt university papers. At the

time when the companies are coming the students are not getting the complete knowledge

about the company regarding the rounds, packages and the company profile.

So, the major area where the most of the students lack behind is the general awareness. The

students are not aware of the latest technologies, courses, tools, languages, etcEven they

dont know how to get prepared for the company i.e. how to prepare for aptitude, company

papers, interview questions. Also the students dont know how to attempt university papers.

Basic problem is thus, the awareness in them.

Awareness can be of kind:

Latest Technologies

Latest Courses

Academics Information- Related to study materials

Companies related information-like company coming to college, its criteria, rounds,

interview questions, company papers

Information related to the writing of examination papers

So it is required to have such a system that performs the functionality of all the problems

mentioned above. So this system i.e. Student Information Sharing System is to provide all

these functionalities so that there can be interaction and general awareness among the

students.

1.1Objective

1.1.1 Student Faculty Interaction

During the college hours the routine lectures are being taken by the faculties. At that time the

faculties are unable to resolve out the problems of the students. In such case the students

questions remain unanswered. So here our main objective is to provide an automated

interactive system for students to resolve their problems.


6/53


6

1.1.2 Student Information Sharing

The major area where the most of the students lack behind is the general awareness. The

students are not aware of the latest technologies, courses, tools, languages, companies that are

arriving in the campus etc. Also the students dont know how to attemp t university papers.

So we require an automized and effective system for providing and maintaining proper

information flow of everything among the students.

1.2 ModuleDescription


We know that learning requires more than high quality inputs of students and instructors. It

also requires a carefully structured means of bringing students and faculty together in ways

that stimulate learning and discovery. In other words, the environment provided to students

by university administrators, staff, faculty, and the physical campus itself, matters. One

primary contact environment between students and faculty is the classroom. However,

interactions between students and faculty that take place outside of the classroom appear to

be particularly important, as they have been shown to be significantly and positively related

to measures of the academic and social development of students as well as to student reports

of satisfaction with college.

This module is basically to work in the direction of student-faculty interactions that occur

outside of the classroom. The findings are based upon student reports of their interactions

with faculty and of their perceptions of these interactions. The work quantifies and qualifies

the nature of student-faculty interactions, sheds light on the determinants of student-faculty


students outside of the classroom.

On the basis of analysis done on the existing system of student faculty interaction this module

is designed to increase the level of interaction between faculty and students outside the

colleges for providing solutions to the students such as this module includes asking

frequently asked questions to the faculties and resolving the queries of the students.


7/53


7



also requires a carefully structured means of bringing students together and aware of the

world in ways that stimulate learning and discovery. In other words, the environment

provided to students by university administrators, staff, faculty, and the physical campus

itself, matters. A students personal growth is required for getting a high quality person

knowing each and every skill and technology along with the worlds knowledge.

This module is basically to work in the direction of student-student interactions and the

student-world interaction. The work quantifies and qualifies the nature of students

interactions with each other and with the world, sheds light on the determinants of student-

world interactions, and reveals the dynamic processes that underlie contact between student

and the world outside.On the basis of analysis done on the existing system of student information sharing this

module is designed to increase the level of interaction and awareness among the students

about the outside world and technologies for providing solutions to the students such as this

module includes sharing Latest Technologies, Latest Courses, Academics Information-

Related to study materials, Companies related information-like company coming to college,

its criteria, rounds, interview questions, company papers, Information related to the writing of

examination papers.

1.3 Scope


The scope of this module encovers the whole aspects relevant to the interaction of Students

and Faculty. The major area where this project will perform is in the colleges, schools and

institutions. This module is having the functionality to resolve the most of the queries of the

students regarding any field or any subject after class hours for making the student faculty

relationship more interactive and powerful. Such system or we can say such an interactive

system can be used everywhere and can be extended to a larger level so that it can be used for

larger systems.


8/53


8


The scope of this module encovers the whole aspects relevant to the interaction of Students

among themselves and awareness about the world. The major area where this project will

perform is in the colleges, schools and institutions. This module is having the functionality to

resolve the most of the queries of the students regarding Latest Technologies, Latest Courses,

Academics Information- Related to study materials, Companies related information-like

company coming to college, its criteria, rounds, interview questions, company papers,

Information related to the writing of examination papers. Such system or we can say such an

interactive system can be used everywhere and can be extended to a larger level so that it can

be used for larger systems.


9/53


9

Chapter 2

Feasibility Study

Feasibility Study Of Student Faculty Interaction

Depending on the result of initial investigation, the survey is expanded to a more detailed

feasibility study. A feasibility study is a test of system proposal according to its workability,

impact on the organization, ability to meet users need and effective use of resources.The

objective of feasibility study is not to solve the problem but to acquire a range of its scope..

Depending on the above definition the survey was done in the college which provides us the

following information. A survey was done keeping in mind the perspective of students,

faculty, and management. The survey was meant just for getting the whole dimensions of the

interaction that takes place between the students and the faculties and just for having the

knowledge about the existing system in colleges generally.

Students Survey

When the students of the college were asked about the normal relation that undergo between

the student and the faculty, most of the students answer was depicting their desire for

changing the existing system of interaction with the faculties. The students said that the most

of their queries remain unresolved and unanswered. They said that they are unable to interact

with the faculties in easy manner. Some said that the classroom lectures and sessions are not

so much interactive and advantageous. Faculties are not having any enough time during

college hours to resolve the student queries. Some students were complaining that they have

to suffer great financial losses due to both paying in college and also for the tuition fees. So

the survey depicted that a lot of change is required in the existing system for the students.

And the system we are introducing i.e. the student faculty interaction system is feasible.

Faculty Survey

On the faculty side, when the survey was done their response towards the system was also not

good. The faculties told that they are remaining busy during the college hours. The system is

not providing them any spare time. So they are not able to resolve the students problems

even if they want to do so. So they were also showing not so good response regarding the

system. So here also the system we are introducing is feasible.


10/53


10

Feasibility Study Of Student Information Sharing

Depending on the result of initial investigation, the survey is expanded to a more detailed

feasibility study. A feasibility study is a test of system proposal according to its workability,

impact on the organization, ability to meet users need and effect ive use of resources. The

objective of feasibility study is not to solve the problem but to acquire a range of its scope..

Depending on the above definition the survey was done in the college which provides us the

following information. A survey was done keeping in mind the perspective of students,

faculty, and management. The survey was meant just for getting the whole dimensions of the

interaction that takes place between the students and the world and also among the students

and just for having the knowledge about the existing system in colleges generally.

Students Survey

When the students were asked about the general awareness among the students, some

students replied that they are kept so busy for academics that they are having no time for

extra study. The students replied that they dont even know from where to get this

information. They were complaining that they are not given any system that can help them to

develop. They also complained that at the time when company comes to the college they arenot getting complete information about the companies. So they demanded a need for a system

that can help them grow fully. So from the survey the module student information system is

said to be feasible.

Faculty Survey

On the faculty side, when the survey was done their response towards the system was also not

good. The faculties told that they are remaining busy during the college hours. The system is

not providing them any spare time. So they are not able to resolve the students problems

even if they want to do so. They showed their interest in giving and sharing knowledge to the

students but are not able to do so. When they were explained our idea of student information

sharing they showed interest in having such a system so that the students may get developed

to the fullest.


11/53


11

2.1 Economic Feasibility


The technical issues usually raised during the feasibility stage of the investigation

Includes the following

Does the necessary technology exist to do what is suggested?

Does the proposed equipments have the technical capacity to hold the data required to

use the new system?

Will the proposed system provide adequate response to inquiries, regardless of the

number or location of users?

Can the system be upgraded if developed?

Are there technical guarantees of accuracy, reliability, ease of access and data

security?

The current system developed is technically feasible. It is a web based user interface for

students. Thus it provides an easy access to the users. The databases purpose is to create,

establish and maintain a workflow among various entities in order to facilitate all concerned

users in their various capacities or roles.

In this module no such functionalities are used or added which can increase the cost of the

system. The tools and the resources are under budget and thus are economically beneficial.

Also the functionality used is such that the factor of the cost minimization is taken into

consideration.


The technical issues usually raised during the feasibility stage of the investigation

Includes the following


Does the proposed equipments have the technical capacity to hold the data required to

use the new system?


12/53


12




Are there technical guarantees of accuracy, reliability, ease of access and datasecurity?

The current system developed is technically feasible. It is a web based user interface for

students. Thus it provides an easy access to the users. The databases purpose is to create,

establish and maintain a workflow among various entities in order to facilitate all concerned

users in their various capacities or roles.

In this module no such functionalities are used or added which can increase the cost of the

system. The tools and the resources are under budget and thus are economically beneficial.

Also the functionality used is such that the factor of the cost minimization is taken into

consideration.

2.2 Technical Feasibility


The technical issues usually raised during the feasibility stage of the Investigation includes

the following

1. Does the necessary technology exist to do what is suggested?

2. Does the proposed equipments have the technical capacity to hold the data required

to use the new system?

3. Will the proposed system provide adequate response to inquiries, regardless of the


4. Can the system be upgraded if developed?

5. Are there technical guarantees of accuracy, reliability, ease of access and data

security?


13/53


13

We are basically dealing with JSP (Java Server Pages) and interaction with PHP to provide

the open source of the system. The initial investigation tells that the interaction of the system

be well equipped with the necessary technology and it is suggested that the system enables

the adequate response to the automation of the system upgradability. This system provides

the guarantee of security that it holds the information to the complete session. Session

Tracking is also an important feature that provides the system more reliable.


The technical issues usually raised during the feasibility stage of the Investigation includes

the following


Do the proposed equipments have the technical capacity to hold the data required to

use the new system?




Are there technical guarantees of accuracy, reliability, ease of access and data

security?

We are basically dealing with JSP (Java Server Pages) and interaction with PHP to provide

the open source of the system. The initial investigation tells that the interaction of the system

is well equipped with the necessary technology and it is suggested that the system enables the

adequate response to the automation of the system upgradability. This system provides the

guarantee of security that it holds the information to the complete session. Session Tracking

is also an important feature that provides the system more reliable.

2.3 Behavioral Feasibility

2.3.1 1 Student Faculty Interaction

The behavioral issues usually raised during the feasibility stage of the Investigation includes

the following


14/53


14

Does the system provide the usual output that is required for the system?

Check the system that it doesnt shows the anomalous behavior that hurdles in getting

the desired functionality.

Does the technology understand the system behavior works according to it?The proposed system uses the Interaction to the Students by the Faculty with that the Faculty

have the full Authority to act and publish Anything on the wall according to the information

that is provided to the Students with full support of web and according to which the static and

dynamic server pages be supported by the system.The Java Technology uses the web

container to configure the system with the deployment descriptor file with the PHP full

featured support to make it the OPEN SOURCE system with Automation.


The behavioral issues usually raised during the feasibility stage of the Investigation includes

the following

Does the system provide the usual output that is required for the system?

Check the system that it doesnt shows the anomalous behavior that hurdles in getting

the desired functionality.

Does the technology understand the system behavior works according to it?

The proposed system functions for providing the information sharing to the Students by the

Student with that the Faculty have the full Authority to act and publish Anything on the wall

according to the information that is provided to the Students with full support of web and

according to which the static and dynamic server pages be supported by the system.The Java

Technology uses the web container to configure the system with the deployment descriptor

file with the PHP full featured support to make it the OPEN SOURCE system with

Automation.


15/53


15

Chapter 3

System Requirements

3.1 Problem Recognition (From Current System)


In this phase the major concern is what are the problems or condition that led the

development of New System. interactions between students and faculty that take place

outside of the classroom appear to be particularly important, as they have been shown to be

significantly and positively related to measures of the academic and social development of

students as well as to student reports of satisfaction with college Their findings indicate that

informal interactions between faculty and students have a stronger impact on more student

outcomes than do formal interactions.

The purpose of this study is three-fold. First, the study seeks to document a number of salient

features of student-faculty interactions based on student descriptions of their experiencesor

lack thereof with faculty. Second, we hope that the results of the study will provide

information useful in the design of future qualitative and quantitative studies of the impact of

faculty on students. And third, we anticipate that the information revealed by students will be

used by faculty, student life professionals, and administrators alike to enhance the impact of

college on students.

During the college hours the routine lectures are being taken by the faculties. At that time the

faculties are unable to resolve out the problems of the students. In such case the students

questions remain unanswered. The basic problem here is the lack of proper interaction

between the students and the faculties.

So we providing the interactive system with automatedopen source application.The system

fulfill the requirement of active interaction between student and faculties.


16/53


16


In this phase the major concern is what are the problems or condition that led the

development of New System. Interactions and awareness among the students appear to be

particularly important, as they have been shown to be significantly and positively related to

measures of the academic and social development of students as well as to student reports of

satisfaction with college Their findings indicate that informal interactions among the students

have a stronger impact on more student outcomes than do formal interactions.

The purpose of this study is three-fold. First, the study seeks to document a number of salient

features of student-student interactions based on student descriptions of their experiencesor

lack thereof. Second, we hope that the results of the study will provide information useful in

the design of future qualitative and quantitative studies of the impact of worlds knowledge

on students. And third, we anticipate that the information revealed by students will be used

by the other students, student life professionals, and administrators alike to enhance the

impact of college on students.

So we are providing the interactive system with automated open source application. The

system fulfills the requirement of active interaction and information sharing among the

students.

3.2 Concept Formation


This module is fetching the information from a system with the information is just stored in a

File the PATTERN Evaluation takes place in which initially the Abusive Language is stored

in the file and then according to the security measures the system makes Artificial Intelligent

System.

The system maintains three level security mechanism.

1. System-Level


17/53


17

At this level the system will check for the abusive word patterns in the questions. A

file system will be used that will store all the patterns irrelevant and discovers the

questions relevant or irrelevant. If the system founds no pattern irrelevant, the

question is processed further to next level check.

In the case of the repeated question with same pattern, the system will search for the

irrelevant pattern, and if no such pattern is found then the response for that question

will be provided to student without undergoing any further checks.

For implementing the above many pattern matching algorithms are to be used.

2. Class Representative Level

After undergoing security checks by the system, the next security check to be

performed is the CR level check. Here the CR is any student from the class and will

intelligently checks for the validity that the question is to be answered by the teacher

or not. For it here is used a check mechanism, i.e. if the CR clicks on that checkbox,

then that particular question can be answered by the teacher.

CR gets a number of questions after the system level check. CR tests the validity of

the questions to be answered by the teacher.

If repeated question with different pattern comes, then the CR intelligently responds

to that question without sending the question for next level check.

3. Faculty Level

Its the last check performed on the question. After undergoing the above security

checks its the faculty decision to provide the answer to the question. So here just the

response to the question is provided to the student.

After answering the question both the question and the answer are stored in the

system so that for the next time the occurrence of the same question may not undergo

all security checks and student may get faster response to the question.

Also in this module, if the faculty wants to post something on the wall, he is free to post

anything onto the wall.


18/53


18


This module is fetching the information from a system with the information is just

stored in a File. The latest information regarding the technologies, new courses,

subjects related information, upcoming companies information with detailed

information of each company and also about how to attempt university papers. All

this information is to be displayed on wall on the basis of daily update. The

system maintains security mechanism as.

1. System-Level

At this level the system will check for the abusive word patterns in the information to

be posted. A file system will be used that will store all the patterns irrelevant and

discovers the questions relevant or irrelevant. If the system founds no pattern

irrelevant, the information is processed further to next level check.

For implementing the above many pattern matching algorithms are to be used.

2. Class Representative Level

After undergoing security checks by the system, the next security check to be

performed is the CR level check. Here the CR is any student from the class and will

intelligently checks for the validity of the information to be pasted on the wall. For it

here is used a check mechanism, i.e. if the CR clicks on that checkbox, then that

particular information can be posted on the wall.

CR intelligently checks that the information to be posted on the wall is relevant to be

posted or not. Though the student is having the authority to post on the wall the main

authority that governs whatever information to be posted is of the faculty. Therefore,

if the faculty wants to post something on the wall, he is free to post anything onto the

wall.


19/53


19

3.3 Software Requirements

PHP

MySQL

Apache Server

3.4 Hardware Requirements

128 MB RAM (For Worst Case)

Pentium III Processor (For Worst Case)

8 GB Hard Disk (For Worst Case)


20/53


20

Chapter 4

Language Description

4.1 Introduction to PHP

PHP is a widely used, general-purpose scripting language that was originally designed

for web development to produce dynamic web pages. For this purpose PHP code is

embedded into the HTML source document and interpreted by a web server with a PHP

processor module, which generates the web page document. As a general-purpose

programming language, PHP code is processed by an interpreter application in command line

mode performing desired operating system operations and producing program output on its

standard output channel. It may also function as a graphical application. PHP is available as a

processor for most modern web servers and as standalone interpreter on almost every

operating system and computing platform.

As we've discussed previously, PHP is a server-side scripting language. This concept is not

obvious, especially if you're used to designing pages with just HTML and JavaScript. A

server-side scripting language is similar to JavaScript in many ways, as they both allow you

to embed little programs (scripts) into the HTML of a Web page. When executed, such

scripts allow you to control what will actually appear in the browser window with more

flexibility than is possible using straight HTML. The key difference between JavaScript and

PHP is simple. JavaScript is interpreted by the Web browser once the Web page that contains

the script has been downloaded. Meanwhile, server-side scripting languages like PHP are

interpreted by the Web server before the page is even sent to the browser. And, once it's

interpreted, the results of the script replace the PHP code in the Web page itself, so all the

browser sees is a standard HTML file. The script is processed entirely by the server, hence

the

Designation: server-side scripting language.

History

PHP was originally created by Rasmus Lerdorf in 1995 and has been in continuous

development ever since. PHP originally stood for personal home page. Its development


21/53


21

began in 1994 when the programmer Rasmus Lerdorf initially created a set of Perl scripts he

called 'Personal Home Page Tools' to maintain his personal homepage, including tasks such

as displaying his rsum and recording how much traffic his page was receiving. He rewrote

these scripts C programming language Comman Gateway Interface (CGI) binaries, extending

them to add the ability to work with web forms and to communicate with databases and

called this implementation 'Personal Home Page/Forms Interpreter' or PHP/FI. PHP/FI could

be used to build simple, dynamic web applications.

Zeev Surakshi and Andi Gutmans, two Israeli developers at the Technion IIT, rewrote the

parser in 1997 and formed the base of PHP 3, changing the language's name to the recursive

initialism PHP: Hypertext Preprocessor.

What is PHP?

PHP stands for PHP: Hypertext Preprocessor

PHP is a server-side scripting language, like ASP

PHP scripts are executed on the server

PHP supports many databases (MySQL, Informix, Oracle, Sybase, Solid,)

Scripting Language

A scripting language, script language or extension language is a programming language

that allows control of one or more software applications. "Scripts" are distinct from the core

code of the application, as they are usually written in a different language and are often

created or at least modified by the end user.Scripts are often interpreted from source code,

whereas the applications they control are traditionally compiled to native machine code. The

name "script" is derived from the written script of the performing arts, in which dialogue is

set down to be spoken by human actors. Early script languages were often called batch

languages orjob control languages. Such early scripting languages were created to shorten

the traditional edit-compile-link-run process


22/53


22

Features:

Free and open source software

Free/ Open source software(FLOSS) is software that is liberally licensed to grant the

right of users to use, study, change, and improve its design through the availability of

its source code. This approach has gained both momentum and acceptance as the

potential benefits have been increasingly recognized by both individuals and

corporate players.

In the context of free and open source software,free refers to the freedom to copy and

re-use the software, rather than to the price of the software. The Free Software

Foundation, an organization that advocates the free software model, suggests that, to

understand the concept, one should "think of free as in free speech, not as in free

beer".

Free and open source software is an inclusive term which covers both free software

and open source software which, despite describing similar development models,

have differing cultures and philosophies.Free software focuses on the philosophical

freedoms it gives to users while open source focuses on the perceived strengths of its

peer-to-peer development model. FOSS is a term that can be used without particular

bias towards either political approach.

Cross Platform

In computing, cross-platform, or multi-platform, is an attribute conferred to computer

software or computing methods and concepts that are implemented and inter-operate on

multiple computer platforms. Cross-platform software may be divided into two types; one

requires individual building or compilation for each platform that it supports, and the other

one can be directly run on any platform without special preparation, e.g., software written in

an interpreted language or pre-compiled portable bytecode for which the interpreters or run-

time packages are common or standard components of all platforms.


23/53


23

For example, a cross-platform application may run on Microsoft Windows on the x86

architecture, Linux on the x86 architecture and Mac OS X on either the PowerPC or x86

based Apple Macintosh systems. A cross-platform application may run on as many as all

existing platforms, or on as few as two platforms.

Why PHP?

PHP runs on different platforms (Windows, Linux, Unix, etc.)

PHP is compatible with almost all servers used today (Apache, IIS, etc.)

PHP is FREE to download from the official PHP resource: www.php.net

PHP is easy to learn and runs efficiently on the server side

4.2 Introduction to MySQL

MySQL is a relational database management system (RDBMS) that runs as a server

providing multi-user access to a number of databases. It is named for original developer

Michael Widenius's daughter My.

The MySQL development project has made its source code available under the terms of the

GNU General Public License, as well as under a variety of proprietary agreements. MySQL

is owned and sponsored by a single for-profit firm, the Swedish company MySQL AB, now

owned by Sun Microsystems, a subsidiary of Oracle Corporation.

Members of the MySQL community have created several forks such as Drizzle, OurDelta,

Percona Server, and MariaDB. All of these forks were in progress before the Oracle

acquisition (Drizzle was announced 8 months before the Sun acquisition).

Free-software projects that require a full-featured database management system often use

MySQL. Such projects include (for example) WordPress, phpBB, Drupal and other software

built on the LAMP software stack. MySQL is also used in many high-profiles, large-scaleWorld Wide Web products including Wikipedia, Google and Facebook.

Brief Introduction to MySQL

Developer(s) MySQL AB (A subsidiary of
http://en.wikipedia.org/wiki/Software_developerhttp://en.wikipedia.org/wiki/MySQL_ABhttp://en.wikipedia.org/wiki/MySQL_ABhttp://en.wikipedia.org/wiki/Software_developer


24/53


24

Oracle Corporation)

Initial release May 23, 1995 (1995-05-23)

Stable release 5.1.49 (July 22, 2010; 20 days

ago (2010-07-22)) [+/]

Preview release 5.5.5 (July 6, 2010; 36 days

ago (2010-07-06)) [+/]

Written in C, C++

Operating system Cross-platform

Available in English

Type RDBMS

License GNU General Public License

(version 2, with linking

exception) or proprietary EULA

Website www.mysql.com

dev.mysql.com

History

Original development of MySQL was by Michael Widenius and David Axmarkin 1994. First

internal release was on 23 May 1995. Windows version was released on 8 January 1998 for

Windows 95 and NT.

Version 3.23: beta from June 2000, production release January 2001

Version 4.0: beta from August 2002, production release March 2003 (unions)

Version 4.01: beta from August 2003, Jyoti adopts MySQL for database tracking

Version 4.1: beta from June 2004, production release October 2004 (R-trees and B-trees,

subqueries, prepared statements)
http://en.wikipedia.org/wiki/Oracle_Corporationhttp://en.wikipedia.org/wiki/Software_release_life_cyclehttp://en.wikipedia.org/w/index.php?title=Template:Latest_stable_software_release/MySQL&action=edithttp://en.wikipedia.org/w/index.php?title=Template:Latest_stable_software_release/MySQL&action=edit&preload=Template:LSR/syntaxhttp://en.wikipedia.org/w/index.php?title=Template:Latest_stable_software_release/MySQL&action=edit&preload=Template:LSR/syntaxhttp://en.wikipedia.org/w/index.php?title=Template:Latest_stable_software_release/MySQL&action=edit&preload=Template:LSR/syntaxhttp://en.wikipedia.org/wiki/Software_release_life_cyclehttp://en.wikipedia.org/w/index.php?title=Template:Latest_preview_software_release/MySQL&action=edithttp://en.wikipedia.org/w/index.php?title=Template:Latest_preview_software_release/MySQL&action=edit&preload=Template:LSR/syntaxhttp://en.wikipedia.org/w/index.php?title=Template:Latest_preview_software_release/MySQL&action=edit&preload=Template:LSR/syntaxhttp://en.wikipedia.org/w/index.php?title=Template:Latest_preview_software_release/MySQL&action=edit&preload=Template:LSR/syntaxhttp://en.wikipedia.org/wiki/Programming_languagehttp://en.wikipedia.org/wiki/C_(programming_language)http://en.wikipedia.org/wiki/C%2B%2Bhttp://en.wikipedia.org/wiki/Operating_systemhttp://en.wikipedia.org/wiki/Cross-platformhttp://en.wikipedia.org/wiki/Languagehttp://en.wikipedia.org/wiki/List_of_software_categorieshttp://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/Software_licensehttp://en.wikipedia.org/wiki/GNU_General_Public_Licensehttp://en.wikipedia.org/wiki/GPL_linking_exceptionhttp://en.wikipedia.org/wiki/GPL_linking_exceptionhttp://en.wikipedia.org/wiki/EULAhttp://en.wikipedia.org/wiki/Websitehttp://www.mysql.com/http://dev.mysql.com/http://en.wikipedia.org/wiki/Michael_Wideniushttp://en.wikipedia.org/wiki/David_Axmarkhttp://en.wikipedia.org/wiki/Set_operations_(SQL)http://en.wikipedia.org/wiki/R-treehttp://en.wikipedia.org/wiki/B-treehttp://en.wikipedia.org/wiki/B-treehttp://en.wikipedia.org/wiki/R-treehttp://en.wikipedia.org/wiki/Set_operations_(SQL)http://en.wikipedia.org/wiki/David_Axmarkhttp://en.wikipedia.org/wiki/Michael_Wideniushttp://dev.mysql.com/http://www.mysql.com/http://en.wikipedia.org/wiki/Websitehttp://en.wikipedia.org/wiki/EULAhttp://en.wikipedia.org/wiki/GPL_linking_exceptionhttp://en.wikipedia.org/wiki/GPL_linking_exceptionhttp://en.wikipedia.org/wiki/GNU_General_Public_Licensehttp://en.wikipedia.org/wiki/Software_licensehttp://en.wikipedia.org/wiki/Relational_database_management_systemhttp://en.wikipedia.org/wiki/List_of_software_categorieshttp://en.wikipedia.org/wiki/Languagehttp://en.wikipedia.org/wiki/Cross-platformhttp://en.wikipedia.org/wiki/Operating_systemhttp://en.wikipedia.org/wiki/C%2B%2Bhttp://en.wikipedia.org/wiki/C_(programming_language)http://en.wikipedia.org/wiki/Programming_languagehttp://en.wikipedia.org/w/index.php?title=Template:Latest_preview_software_release/MySQL&action=edit&preload=Template:LSR/syntaxhttp://en.wikipedia.org/w/index.php?title=Template:Latest_preview_software_release/MySQL&action=edithttp://en.wikipedia.org/wiki/Software_release_life_cyclehttp://en.wikipedia.org/w/index.php?title=Template:Latest_stable_software_release/MySQL&action=edit&preload=Template:LSR/syntaxhttp://en.wikipedia.org/w/index.php?title=Template:Latest_stable_software_release/MySQL&action=edithttp://en.wikipedia.org/wiki/Software_release_life_cyclehttp://en.wikipedia.org/wiki/Oracle_Corporation


25/53


25

Version 5.0: beta from March 2005, production release October 2005 (cursors, stored

1``procedures, triggers, views, XA transactions)

Documentation of some of the short-comings appears in "MySQL Federated Tables: The

Missing Manual". Sun Microsystems acquired MySQL AB on 26 February 2008.

Version 5.1: production release 27 November 2008 (event scheduler, partitioning, plugin

API, row-based replication, server log tables). Version 5.1 contained 20 known crashing and

wrong result bugs in addition to the 35 present in version 5.0. MySQL 5.1 and 6.0 showed

poor performance when used for data warehousing partly due to its inability to utilize

multiple CPU cores for processing a single query. Oracle acquired Sun Microsystems on

January 27, 2010. MySQL Server 5.5 is currently available in pre-release (as of June 2010).

Enhancements and features include:

The default storage engine is InnoDB, which supports transactions and referential integrity

constraints. MySQL Server 6.0.11-alpha was announced May 22, 2009 as the last release of

the 6.0 line.

SQL LANGUAGES:-

1. DDL (Data Definition Language):

In DDL, only the description of the data is done i.e. Meta data is processed.

No description about data in detail is done in this language.

Some of the DDL commands are:

a) Create

b) Alter

i. Add

ii. Modify

iii. Drop

c) Truncate

2. DML (Data Manipulation Language):
http://en.wikipedia.org/wiki/Cursor_(databases)http://en.wikipedia.org/wiki/Stored_procedurehttp://en.wikipedia.org/wiki/Stored_procedurehttp://en.wikipedia.org/wiki/Database_triggerhttp://en.wikipedia.org/wiki/View_(database)http://en.wikipedia.org/wiki/Database_transactionhttp://www.oreillynet.com/pub/a/databases/2006/08/10/mysql-federated-tables.htmlhttp://www.oreillynet.com/pub/a/databases/2006/08/10/mysql-federated-tables.htmlhttp://en.wikipedia.org/wiki/MySQL_ABhttp://en.wikipedia.org/wiki/Partition_(database)http://en.wikipedia.org/wiki/Server_loghttp://en.wikipedia.org/wiki/Data_warehousinghttp://lists.mysql.com/packagers/418http://lists.mysql.com/packagers/418http://en.wikipedia.org/wiki/Data_warehousinghttp://en.wikipedia.org/wiki/Server_loghttp://en.wikipedia.org/wiki/Partition_(database)http://en.wikipedia.org/wiki/MySQL_ABhttp://www.oreillynet.com/pub/a/databases/2006/08/10/mysql-federated-tables.htmlhttp://www.oreillynet.com/pub/a/databases/2006/08/10/mysql-federated-tables.htmlhttp://en.wikipedia.org/wiki/Database_transactionhttp://en.wikipedia.org/wiki/View_(database)http://en.wikipedia.org/wiki/Database_triggerhttp://en.wikipedia.org/wiki/Stored_procedurehttp://en.wikipedia.org/wiki/Stored_procedurehttp://en.wikipedia.org/wiki/Cursor_(databases)


26/53


26

In DML, the data is described in detail, i.e. all data to be processed is done

using DML language.

This language includes inserting the entries in database, deleting any entry.

Some of the commands are:

a) Insert

b) Delete

c) Update

3. DCL (Data Control Language):

In DCL, the data in the tables is controlled. It includes the command that

works for controlling the data and providing backup to the data.

Some of the commands are:

a) Commit

b) Roll Back

c) Save Point


27/53


27

Chapter 5

Module Description

5.1 Student Faculty Interaction


also requires a carefully structured means of bringing students and faculty together in ways

that stimulate learning and discovery. In other words, the environment provided to students

by university administrators, staff, faculty, and the physical campus itself, matters. One

primary contact environment between students and faculty is the classroom. However,

interactions between students and faculty that take place outside of the classroom appear tobe particularly important, as they have been shown to be significantly and positively related

to measures of the academic and social development of students as well as to student reports

of satisfaction with college.

This module is basically to work in the direction of student-faculty interactions that occur

outside of the classroom. The findings are based upon student reports of their interactions

with faculty and of their perceptions of these interactions. The work quantifies and qualifies

the nature of student-faculty interactions, sheds light on the determinants of student-faculty


students outside of the classroom.

On the basis of analysis done on the existing system of student faculty interaction this module

is designed to increase the level of interaction between faculty and students outside the

colleges for providing solutions to the students such as this module includes asking

frequently asked questions to the faculties and resolving the queries of the students.

5.2 Student Information Sharing


also requires a carefully structured means of bringing students together and aware of the

world in ways that stimulate learning and discovery. In other words, the environment

provided to students by university administrators, staff, faculty, and the physical campus


28/53


28

itself, matters. A students personal growth is required for getting a high quality person

knowing each and every skill and technology along with the worlds knowledge.

This module is basically to work in the direction of student-student interactions and the

student-world interaction. The work quantifies and qualifies the nature of students

interactions with each other and with the world, sheds light on the determinants of student-

world interactions, and reveals the dynamic processes that underlie contact between student

and the world outside.

On the basis of analysis done on the existing system of student information sharing this

module is designed to increase the level of interaction and awareness among the students

about the outside world and technologies for providing solutions to the students such as this

module includes sharing Latest Technologies, Latest Courses, Academics Information-

Related to study materials, Companies related information-like company coming to college,

its criteria, rounds, interview questions, company papers, Information related to the writing of

examination papers.


29/53


29

Chapter 6

Analysis Modelling

Software design is the activity where software requirements are analyzed in order to produce

a description of the internal structure and organization of the system that will serve as the

basis for its construction.

There are two activities:

Software architectural design: the top-level structure and organization of the system is

described and various components are identified (how the system is decomposed and

organized into components and must describe the interfaces between these components.)

Software implementation design: each component is sufficiently described to allow for its

coding.

The software design objectives can be listed as follows:

To produce various models that can be analyzed and evaluated to determine if they

will allow the various requirements to be fulfilled,

To examine and evaluate various alternative solutions and tradeoffs, and

To plan the subsequent development activities.

Software system design results in the following products:

A list of design goals derived from the nonfunctional requirements

Software architecture

Subsystem decomposition in terms of

Responsibilities

Dependencies

Mapping to hardware

Major policy decision such as

Control flow

Access control

Data storage

Access control

Boundary condition


30/53


30

6.1 Data Modeling:-

It includes the Entity Relationship Diagram.

Entity Relationship Diagrams (ERDs) illustrate the logical structure of databases. An entity is

an object or concept about which you want to store information. Attributes are the properties

or characteristics of an entity. A key attribute is the unique, distinguishing characteristic of

the entity.

For example, an employee's social security number might be the employee's key attribute.

Relationships illustrate how two entities share information in the database structure.

Cardinality specifies how many instances of an entity relate to one instance of another entity.

Ordinality is also closely linked to cardinality. While cardinality specifies the occurences of a

relationship, ordinality describes the relationship as either mandatory or optional. In other

words, cardinality specifies the maximum number of relationships and ordinality specifies the

absolute minimum number of relationships.

Entity relationship diagram represents:

Entity using a rectangle where entity is a real world objects.

Relation among these entities by a diamond.

Data flow among the entities by the arrows.


31/53


31

ERD for E-Campus project is:

Person

User_Id

Name

dob

Ph-No.

Addr

Gender

Mail-id

Register

As

Register

As

User

User_Id

Password

Last_Login

Status

Group_Id

Student

ISA

Faculty CR HOD Admin

Asks

ISA

FAQ

QId Sub_Id Stud_Id

Respond

toVerify A oint

Class Teacher

Doj Expr Branch_Id

Qualification


32/53


32

6.2 Scenario Based Modeling:-

It basically includes Use Case Diagrams and Activity Diagrams.

Use Case Diagram:

A use case is a technique for capturing the potential requirements of a new system or

software change. Each use case provides one or more scenarios that convey how the system

should interact with the end user or another system to achieve a specific business goal.

Use case diagrams depict:

Use cases: A use case describes a sequence of actions that provide something of

measurable value to an actor and is drawn as a horizontal ellipse.

Actors: An actor is a person, organization, or external system that plays a role in one

or more interactions with your system. Actors are drawn as stick figures.

Associations: Associations between actors and use cases are indicated in use case

diagrams by solid lines. An association exists whenever an actor is involved with an

interaction described by a use case. Associations are modeled as lines connecting use

cases and actors to one another, with an optional arrowhead on one end of the line.

The arrowhead is often used to indicate the direction of the initial invocation of the

relationship or to indicate the primary actor within the use case.

System boundary boxes (optional): We can draw a rectangle around the use cases,

called the system boundary box, to indicate the scope of the system. Anything within

the box represents functionality that is in scope and anything outside the box is not.

System boundary boxes are rarely used.

Packages (optional): Packages are UML constructs that enable us to organize model

elements (such as use cases) into groups. Packages are depicted as file folders and can

be used on any of the UML diagrams, including both use case diagrams and class

diagrams.

Activity Diagram:

Activity diagrams represent the business and operational workflows of a system. It is a

dynamic diagram that shows the activity and the event that causes the object to be in the

particular state. It describes the workflow behavior of a system. An Activity diagram

consists of the following behavioral elements:


33/53


33

Initial Activity: This shows the starting point or first activity of the flow. It is denoted by a

solid circle. This is similar to the notation used for Initial State.

Activity: Represented by a rectangle with rounded (almost oval) edges.

Decisions: Similar to flowcharts, a logic where a decision is to be made is depicted by a

diamond, with the options written on either sides of the arrows emerging from the diamond,

within box brackets.

Concurrent Activities: Some activities occur simultaneously or in parallel. Such activities are

called concurrent activities. For example, listening to the lecturer and looking at the

blackboard is a parallel activity. This is represented by a horizontal split (thick dark line) and

the two concurrent activities next to each other, and the horizontal line again to show the end

of the parallel activity.

Final Activity: The end of the Activity diagram is shown by a bull's eye symbol, also called

as a final activity.

6.3 Flow Oriented Modeling:-

It basically includes Data Flow Diagrams. Data flow diagrams are the diagram that depicts

the flow of data and information within the project. Here there are levels like 0-Level DFD,

1-Level DFD, 2-Level DFD.

The data flow diagram enables the software engineer to develop models of the information

domain and functional domain at the same time. As the DFD is refined into greater levels of

detail, the analyst performs an implicit functional decomposition of the system, thereby

accomplishing the fourth operational analysis principle for function. At the same time, the

DFD refinement results in a corresponding refinement of data as it moves through the

processes that embody the application.

A few simple guidelines can aid immeasurably during derivation of a data flow diagram:

(1) The level 0 data flow diagram should depict the software/system as a single bubble;

(2) Primary input and output should be carefully noted;

(3) Refinement should begin by isolating candidate processes, data objects, and stores to be

represented at the next level;

(4) All arrows and bubbles should be labeled with meaningful names;

(5) Information flow continuity must be maintained from level to level, and

(6) One bubble at a time should be refined.


34/53


34

There is a natural tendency to overcomplicate the data flow diagram. This occurs when the

analyst attempts to show too much detail too early or represents procedural aspects of the

software in lieu of information flow.

Ongoing each level ahead we will get the more detailed information of the data flow.

0-Level is the lowest level depicting the least knowledge of the data flow.

The symbols used for representing the data are:

Rectangle is used for representing entities.

Circle is used for representing the process.

Two horizontal bars are used for representing the transaction from or into the

database.

An arrow shows information flow.


35/53


35

0-Level DFD for Student Information System

0-Level DFD for Student Faculty Interaction

Student

Information

Sharing

Student Users

Query Query

ResponseResponse

Student Faculty

Interaction

Student Faculty

Query Query

Response

Interact

CR

Authenticate


36/53


36

Chapter 7

Testing

The development of software systems involves a series of production activities where

opportunities for injection of human fallibilities are enormous. Errors may begin to occur at

the very inception of the process where the objectives . . . may be erroneously or imperfectly

specified, as well as [in] later design and development stages . . .

Because of human inability to perform and communicate with perfection, software

development is accompanied by a quality assurance activity.

Software testing is a critical element of software quality assurance and represents the ultimate

review of specification, design, and code generation. The increasing visibility of software as a

system element and the attendant "costs" associated with a software failure are motivating

forces for well-planned, thorough testing. It is not unusual for a software development

organization to expend between 30 and 40 percent of total project effort on testing. In the

extreme, testing of human-rated software (e.g., flight control, nuclear reactor monitoring) can

cost three to five times as much as all other software engineering steps combined!

The methods of the testing are:

7.1 White Box Testing:-

White-box testing, sometimes called glass-box testing is a test case design method that uses

the control structure of the procedural design to derive test cases. Using white-box testing

methods, the software engineer can derive test cases that

(1) Guarantee that all independent paths within a module have been exercised at least once,

(2) Exercise all logical decisions on their true and false sides,

(3) Execute all loops at their boundaries and within their operational bounds, and

(4) Exercise internal data structures to ensure their validity.White-box testing of software is predicated on close examination of procedural detail.

Logical paths through the software are tested by providing test cases that exercise specific

sets of conditions and/or loops. The "status of the program" may be examined at various

points to determine if the expected or asserted status corresponds to the actual status.

At first glance it would seem that very thorough white-box testing would lead to "100 percent

correct programs." All we need do is define all logical paths, develop test cases to exercise


37/53


37

them, and evaluate results, that is, generate test cases to exercise program logic exhaustively.

Unfortunately, exhaustive testing presents certain logistical problems. For even small

programs, the number of possible logical paths can be very large. For example, consider the

100 line program in the language C. After some basic data declaration, the program contains

two nested loops that execute from 1 to 20 times each, depending on conditions specified at

input. Inside the interior loop, four if-then-else constructs are required. There are

approximately 1014 possible paths that may be executed in this program!

7.1.1 Basis Path:-

Basis path testing is a white-box testing technique first proposed by Tom McCabe. The basis

path method enables the test case designer to derive a logical complexity measure of a

procedural design and use this measure as a guide for defining a basis set of execution paths.

Test cases derived to exercise the basis set are guaranteed to execute every statement in the

program at least one time during testing.

Flow Graph Notation:

Before the basis path method can be introduced, a simple notation for the representation of

control flow, called a flow graph (or program graph) must be introduced. Each structured

construct has a corresponding flow graph symbol.

To illustrate the use of a flow graph, we consider the procedural design representation in

above figure. Here, a flowchart is used to depict program control structure.


38/53


38

Each circle, called aflow graph node, represents one or more procedural statements.

A sequence of process boxes and a decision diamond can map into a single node.

The arrows on the flow graph, called edges or links, represent flow of control and are

analogous to flowchart arrows. An edge must terminate at a node, even if the node

does not represent any procedural statements (e.g., the symbol for the if-then-else

construct).

Areas bounded by edges and nodes are called regions. When counting regions, we

include the area outside the graph as a region.

When compound conditions are encountered in a procedural design, the generation of a flow

graph becomes slightly more complicated. A compound condition occurs when one or more

Boolean operators (logical OR, AND, NAND, NOR) is present in a conditional statement.

Each node that contains a condition is called apredicatenode and is characterized by two or

more edges emanating from it.

Deriving Test Cases:

The basis path testing method can be applied to a procedural design or to source code. In this

section, we present basis path testing as a series of steps.

The following steps can be applied to derive the basis set:

1. Using the design or code as a foundation, draw a corresponding flow graph-

A flow graph is created using the symbols and construction rules presented a flow

graph is created by numbering those PDL statements that will be mapped into

corresponding flow graph node.

2. Determine the cyclomatic complexity of the resultant flow graph-

The cyclomatic complexity, V(G), is determined. V(G) can be determined without

developing a flow graph by counting all conditional statements in the PDL. E.g.

V(G) = 6 regions

V(G) = 17 edges _ 13 nodes + 2 = 6

V(G) = 5 predicate nodes + 1 = 6

3. Determine a basis set of linearly independent paths-

The value of V(G) provides the number of linearly independent paths through the

program control structure.


39/53


39

4. Prepare test cases that will force execution of each path in the basis set-

Data should be chosen so that conditions at the predicate nodes are appropriately set as each

path is tested.

Each test case is executed and compared to expected results. Once all test cases

havebeen completed, the tester can be sure that all statements in the program have

been executed at least once.

Some independent paths cannot be tested in stand-alone fashion. That is, the

combination of data required to traverse the path cannot be achieved in the normal

flow of the program. In such cases, these paths are tested as part of another path test.

7.1.2 Control Structure Testing:-

The basis path testing technique is one of a number of techniques for control structure testing.

Although basis path testing is simple and highly effective, it is not sufficient in itself. Other

variations on control structure testing are discussed. These broaden testing coverage and

improve quality of white-box testing.

Condition Testing-

Condition testing is a test case design method that exercises the logical conditions contained

in a program module. A simple condition is a Boolean variable or a relational expression,

possibly preceded with one NOT () operator. A relational expression takes the form

E1 E2

where E1 and E2 are arithmetic expressions and is one of the

following: , or . A compound condition is composed of two or

more simple conditions, Boolean operators, and parentheses. We assume that Boolean

operators allowed in a compound condition include OR (|), AND (&) and NOT (). A

condition without relational expressions is referred to as aBoolean expression. Therefore, the

possible types of elements in a condition include a Boolean operator, a Boolean variable, a

pair of Boolean parentheses (surrounding a simple or compound condition), a relational

operator, or an arithmetic expression.

If a condition is incorrect, then at least one component of the condition is incorrect.

Therefore, types of errors in a condition include the following:

Boolean operator error (incorrect/missing/extra Boolean operators).


40/53


40

Boolean variable error.

Boolean parenthesis error.

Relational operator error.

Arithmetic expression error.

The condition testing method focuses on testing each condition in the program. Condition

testing strategies generally have two advantages.

First, measurement of test coverage of a condition is simple.

Second, the test coverage of conditions in a program provides guidance for the generation of

additional tests for the program.

The purpose of condition testing is to detect not only errors in the conditions of a program but

also other errors in the program.

Errors are much more common in the neighborhood of logical conditions than they are in the

locus of sequential processing statements.

A number of condition testing strategies have been proposed. Branch testing is probably the

simplest condition testing strategy. For a compound condition C, the true and false branches

ofCand every simple condition in Cneed to be executed at least once.

Domain testing requires three or four tests to be derived for a relational expression. For a

Boolean expression with n variables, all of 2n possible tests are required (n > 0).

This strategy can detect Boolean operator, variable, and parenthesis errors, but it is practical

only ifn is small.

Data Flow Testing-

The data flow testing method selects test paths of a program according to the locations of

definitions and uses of variables in the program.

To illustrate the data flow testing approach, assume that each statement in a program is

assigned a unique statement number and that each function does not modify its parameters or

global variables. For a statement with S as its statement number,

DEF(S) = {X| statement S contains a definition ofX}

USE(S) = {X| statement S contains a use ofX}

If statement S is an ifor loop statement, its DEF set is empty and its USE set is based on the

condition of statement S. The definition of variable X at statement S is said to be live at


41/53


41

statement S' if there exists a path from statement S to statement S' that contains no other

definition ofX.

A definition-use (DU) chain of variable X is of the form [X, S, S'], where S and S' are

statement numbers,Xis in DEF(S) and USE(S'), and the definition ofXin statement S is live

at statement S'.

One simple data flow testing strategy is to require that every DU chain be covered at least

once. We refer to this strategy as the DU testing strategy. It has been shown that DU testing

does not guarantee the coverage of all branches of a program. However, a branch is not

guaranteed to be covered by DU testing only in rare situations such as if-then-else constructs

in which the then parthas no definition of any variable and the else partdoes not exist. In

this situation, the else branch of the ifstatement is not necessarily covered by DU testing.

Data flow testing strategies are useful for selecting test paths of a program containing nested

ifand loop statements.

Loop Testing-

Loops are the cornerstone for the vast majority of all algorithms implemented in software.

And yet, we often pay them little heed while conducting software tests. Loop testing is a

white-box testing technique that focuses exclusively on the validity of loop constructs. Four

different classes of loops can be defined: simple loops, concatenated loops, nested loops, and

unstructured loops.


42/53


42

Simple loops-

The following set of tests can be applied to simple loops, where n is the maximum number of

allowable passes through the loop.

1. Skip the loop entirely.

2. Only one pass through the loop.

3. Two passes through the loop.

4. m passes through the loop where m < n.

5. n _1, n, n + 1 passes through the loop.


43/53


43

Nested loops-

If we were to extend the test approach for simple loops to nested loops, the number of

possible tests would grow geometrically as the level of nestingincreases. This would result in

an impractical number of tests. An approach that will help to reduce the number of tests:

1. Start at the innermost loop. Set all other loops to minimum values.

2. Conduct simple loop tests for the innermost loop while holding the outer loops at their

minimum iteration parameter (e.g., loop counter) values. Add other tests for out-of-range or

excluded values.

3. Work outward, conducting tests for the next loop, but keeping all other outer loops at

minimum values and other nested loops to "typical" values.

4. Continue until all loops have been tested.

Concatenated loops-

Concatenated loops can be tested using the approach defined for simple loops, if each of the

loops is independent of the other. However, if two loops are concatenated and the loop

counter for loop 1 is used as the initial value for loop 2, then the loops are not independent.

When the loops are not independent, the approach applied to nested loops is recommended.

Unstructured loops-

Whenever possible, this class of loops should be redesigned to reflect the use of the

structured programming constructs.

7.2 Black Box Testing:-

Black-box testing, also called behavioral testing, focuses on the functional requirements of

the software. That is, black-box testing enables the software engineer to derive sets of input

conditions that will fully exercise all functional requirements for a program. Black-box


44/53


44

testing is not an alternative to white-box techniques. Rather, it is a complementary approach

that is likely to uncover a different class of errors than white-box methods.

Black-box testing attempts to find errors in the following categories:

(1) Incorrect or missing functions,

(2) Interface errors,

(3) Errors in data structures or external data base access,

(4) Behavior or performance errors, and

(5) Initialization and termination errors.

Unlike white-box testing which is performed early in the testing process, black box testing

tends to be applied during later stages of testing. Because black-box testing purposely

disregards control structure, attention is focused on the information domain. Tests are

designed to answer the following questions:

How is functional validity tested?

How is system behavior and performance tested?

What classes of input will make good test cases?

Is the system particularly sensitive to certain input values?

How are the boundaries of a data class isolated?

What data rates and data volume can the system tolerate?

What effect will specific combinations of data have on system operation?

By applying black-box techniques, we derive a set of test cases that satisfy the following

criteria:

(1) Test cases that reduce, by a count that is greater than one, the number of additional test

cases that must be designed to achieve reasonable testing and

(2) Test cases that tell us something about the presence or absence of classes of errors, rather

than an error associated only with the specific test at hand.


45/53


45

Chapter 8

Snapshots

Login Page

Fig 8.1: LOG IN Page

Register Page

Fig 8.2: Registration Page For New Users


46/53


46

Admin Home

Fig 8.3: Admin Page

HOD Home

Fig 8.4: Home Page For the HODS


47/53


47

Class Teacher

Fig 8.5: Home Page For The Class Teacher

Teacher Home

Fig 8.6: Home Page For Teachers


48/53


48

Student Home

Fig 8.7: Home Page For Students

Query Page

Fig 8.8: Page For Asking Queries


49/53


49

Answer Page

Fig 8.9:Page for Answering The Question


50/53


50

Chapter 9

Conclusion And Future Enhacements

So, in this project of Student Information Management System we successfully provided all

the features that we mentioned in the introduction part of the report. E-learning identified

with web-based learning - was taken up by pioneers and innovators. Discussion and

development focussed mostly on the technical possibilities and requirements for e-learning

software. The changed social paradigm, i.e. the shift from industrial society to the

information or knowledge society, had led to a fundamental reconception of education the

concept of life-long learning. E-learning seemed to be the right solution at the right time to

meet the immensely growing demands for education, and perpetual flexibility and innovationin the educational sector. Hence, e-learning was seen as the lever to completely re-invent

education, including the universities. The vision developed then was the virtual university,

i.e. a shift to generalised Internet-based distance education.

In the existing education system, there are lots of fields to be maintained efficiently, like,

students details management, faculty management, timetable management in case of disorder

in the management, bus management in case of low strength of students coming to the

college. A campus is the combination of the above such management areas. The problem

arises in each management system is regarding the effectiveness of the system. For example,

in case of absence of the teacher or in case of exams where the faculties are not free, the

management of timetable is very crucial. In such condition a system is required for the

automation of timetable instead of making the timetable again and again. Also we can take

the case of the bus management system, where again the effectiveness of the system lies in

the better management of the buses during the exams, holi

Minor Report3

Documents

Transcript of Minor Report3