MODIFIED SIS 2

8/7/2019 MODIFIED SIS 2

1/31

The Certificate of Originality

To Whom It May Concern

This is to certify that the Project Report entitled STUDENT INFORMATION

SYSTEM, submitted to ARDENT COLLABORATIONS LIMITED, in partial

fulfillment of the requirement for the award of the degree of Bachelor of

Technology (B.Tech), is an original work carried out by Debosmita Ghosh with

University Roll Number071820102050, Falguni Das with University Roll Number

071820102052, Sauptik Basak with University Roll Number 071820102031,

Priyanka Chatterjee with University Roll Number 071690102043, Monika

Majumder with University Roll Number 08169001062, Avishek Mondol with

University Roll Number071310102040 under the guidance ofAyon Chatterjee.

The matter in this project is a genuine work done by the student and has not been

submitted elsewhere of any course of study.

Ayon Chatterjee Ardent Collaborations

Industry Seal and

Signature

1 | P a g e


2/31

A SOFTWARE REPORT ON STUDENT INFORMATION SYSTEM

Submitted By:

NAME ROLL NO.

DEBOSMITA GHOSH 071820102050

FALGUNI DAS 071820102052

SAUPTIK BASAK 071820102031

PRIYANKA CHATTERJEE 071690102043

MONIKA MAJUMDAR 08169001062

ABHISHEK MONDAL 071310102040

2 | P a g e


3/31

ACKNOWLEDGEMENT

The satisfaction that accompanies that the successful completion of any task

would be incomplete without the mention of people whose ceaseless

cooperation made it possible, whose constant guidance and encouragement

crown all effort with success.

We are grateful to our respected faculty and project guide Mr. Ayon

Chatterjee (from Ardent Collaborations) for the guidance, inspiration andconstructive suggestion that helpful us in the preparation of this project.

We also thank friends who have helped in successful completion of the

project.

______________________ ______________________ ______________________DEBASMITA GHOSH FALGUNI DAS

SAUPTIK BASAK

______________________ _________________________________________

PRIYANKA CHATTERJEE MONIKA MAJUMDARABHISHEK MONDAL

Signature of Project Guide

Date:

3 | P a g e


4/31

ABSTRACT

This Student Information System is a web application that

automates the routine tasks of an administrator & the

users.

The Student Information System includes the following

features:

To add student details to the system

To update University details of a student at any time.

To delete the University details of a student on

selecting his/her certificate number or year of passing.

CONTENTS

4 | P a g e


5/31

1. INTRODUCTION

1.1Goal or aim of STUDENT INFORMATION SYSTEM

1.2Salient features of STUDENT INFORMATION SYSTEM1.3 Scope

1.4 Technologies used

2. FEASIBILITY STUDY

2.1Steps in feasibility analysis

2.2 Feasibility study division

2.2.1 Technical feasibility

2.2.2 Economical feasibility

2.2.3 Operational Feasibility2.2.4 Schedule feasibility

2.3 Steps taken

3. SOFTWARE REQUIREMENTS & SPECIFICATION

3.1Operating environment

3.2 Overall description

4. E-R DIAGRAM / DATA FLOW DIAGRAM

4.1 E-R Diagram

4.2 Data Flow Diagram

4.2.1 Data Flow Diagram (Context Level)

4.2.2 Level 1 of User

4.2.3 Level 1 of Admin

5.SNAPSHOT VIEW

6. TESTING & TEST RUN

6.1 Coding

6.2 Testing

6.3 Maintenance

7. PROVISIONS FOR FUTURE WORK

8. BIBLIOGRAPHY & REFERENCES

8.1 Books

8.2 Website

9. USER MANUAL

10. CONCLUSION

5 | P a g e


6/31

1. INTRODUCTION

1.1Goal Or Aim of Student Information System:

Student Information System is unique software, which stores and manages

customer details.

It comprises registering of new students to the validation of existing students.

.

It can query the status of existing students in colleges under the differentuniversities.

This is a modernized approach of conventional documentation system where

administrators of the system have to keep the details of the students and universities

in a written directory. The system interacts with the users by means of some front-

end form. To enter the system a login form will appear where ID and Password for

both Administrator and for the users will have to be entered to log into the system

and then this will check the Permission of that user. According to permission the

System is loaded..

1.2 Salient Features Of Student Information System:

After Login Administrator can do several things as well as he can perform

enquiries of students, records of universities, updation of students as well as

of the universities.

Every stage data is stored in the database after checking and testing. This is

why the system is very easy to use and every user can accept the system by

thinking its utility in present and by applying the idea of Spiral Model the

system can be developed with more features in future.

It keeps the room for future development.

1.3 Scope:

6 | P a g e


7/31

The software though is in primitive in stage can be used in different states for

maintaining records on a nation-wide basis. It equips them with easy management

of Students and Universities.

1.4 Technologies used:

Outputs and Inputs:

A major objective of a system is to produce an output that has value to its user.

Whatever the nature of the output (goods, services or information), it must be in line

with the expectations of the intended user. Inputs are the elements (material, human

resources, information) that enter the system for processing. A system feeds on

input to produce output in much the same way that a business brings in human,

financial and material resources to produce goods and services. It is important to

point out here that determining the output is a first step in specifying the nature,

amount and regularity of the input needed to operate a system. For example, insystems analysis, the first concern is to determine the users requirements of a

proposed computer system that is, specification of the output that the computer is

expected to provide for meeting user requirements.

Processor(s):

The processor is the element of a system that involves the actual transformation of

input into output. It is the operational component of a system. Processors may

modify the input totally or partially depending on the specifications of the output.

This means that as the output specifications change, so does the processing. Insome cases, input is also modified to enable the processor to handle the

transformation.

Control:

The control element guides the system. It is the decision-making subsystem that

controls the pattern of activities governing input, processing and output. In an

organizational context, management as a decision-making body controls the inflow,

handling and outflow of activities that affect the welfare of the organization.

Management support is required for securing control and supporting the objective

of the proposed change.

Environment:

7 | P a g e


8/31

The environment is the suprasystem within which an organization operates. It is

the source of external elements that impinge on the system. In fact, it often

determines how a system must function.

Boundaries and Interface:

A system should be defined by its boundaries the limits that identify itscomponents, processes and interrelationships when it interfaces with another

system. Each system has boundaries that determine its sphere of influence and

control. In system analysis, knowledge of the boundaries of a given system is

crucial in determining the nature of its interface with other systems for successful

design.

2. FEASIBILITY STUDY

The main aim of feasibility study is to determine whether the developing of the

software product is financially, technically & workably feasible.

1. In a boarder spectrum, feasibility study is the study about collection of

data required as input to the system, the processing required to be carried

out on the data and the required output by the system, develop the

proposed system and test of system proposal according to its

workability, impact of the organization, ability to meet needs and

effective use of resources.

During feasibility analysis for this project, following primary areas are to be

considered. Investigation and generating ideas about system does this.

2.1 Steps In Feasibility Analysis:

Eight steps involved in the feasibility analysis are:

Form a project team and appoint a project leader.

Prepare system flowcharts.

Enumerate potential proposed system.

Define and identify characteristics of proposed system.

Determine and evaluate performance and cost effective of each proposed

system.8 | P a g e


9/31

Weight system performance and cost data.

Select the best-proposed system.

Prepare and report final project directive to management.

2.2 Feasibility Study Can Be Divided Under Following Subs

Which We Followed Are :

2.2.1 Technical Feasibility:

This evolution determines whether the technology needs for the proposed system is

available or not.

Can the work for the project be done with current equipment exiting software

technology & available personal?

2.2.2 Economical Feasibility:

Economic justification is general the Bottom line consideration for most systems.

Economic justification includes a broad range of concerns that includes cost benefitanalysis. In this way we weight the cost and benefits associated with the candidate

system and if it suits the basic purpose of the organization i.e. profit making, the

project is making to the analysis and design phase.

2.2.3 Operational Feasibility:

It is mainly related to human organizations and politics aspects. The points to be

considered are:

What changes will be brought with the system?

What organization structures are disturbed?

What new skill will be required? Do the exiting staff members have

these skills? If not, can they be trained in due of course of time?

The system is operational feasible as it very easy for the End users to operate it. It

only needs basic information about Window platform.

2.2.4 Schedule Feasibility:

9 | P a g e


10/31

Time evolution is most important considerations in the development of project. The

time schedule required for the development time effect machine time, cost and

cause delay in the development other systems.

2.3 Steps Taken:

We, our group members of this project have intensified our attention on some

following paths before doing this project.

An abstract definition on the purpose of the project.

Formulation of different strategies for the completion of project

Examination and evaluation of alternative strategies or solution of theproject by using optimum resource and minimum usage cost and time.

A cost benefit analysis is done to determine whether the solution is the

best possible way to get desired output, or the selected strategy is not

feasible as for high cost, resource constraints or any other technical

reason.

The output of all the above empowered us to determine the best possible way to

implement the project setting the project goal, bounds like part of the existing

system that cannot be changed, resources available and its limitation, funds that can

be incurred, personnel available for the project.

3.SOFTWARE REQUIREMENT & SPECIFICATION

3.1 Operating Environment :

Operating System Other software requirement

Win - XP or other higher versionMICROSOFT VISUAL STUDIO 2008

Hardware Requirement

Processor RAM Disk Space

10 | P a g e


11/31

Pentium IV or Higher 256 MB or Higher 1 GB

3.2 Overall Description :

In the project each USER has a unique id. The software has facilities like

Login For the all users and also admin can access the data from his own

homepage.

Details are available for the user and administrator.

The profiles of the required students are available as on demand.

Details of the university are available to the administrator.

Updation of students information is possible for the administrator.

4. E-R DIAGRAM / DATA FLOW DIAGRAM

4.1 E-R Diagram:

11 | P a g e


12/31

4.2 Data Flow Diagram:

4.2.1 DATAFLOW DIAGRAM (CONTEXT LEVEL):

12 | P a g e


13/31

4. Login

1. Registration 5. Add university

2. Login 6. Add student

3. Search student 7. Update University

4.2.2 Level 1 of User:

User info User info

User Id, password

13 | P a g e

USER Administrator

NATIONWISE

STUDENT

INFORMATION

SYSTEM

User

Registration

1.1


14/31

User login

Id, password

Id, password

Id, password

Authentication

Certificate no. Batch

Certificate no., batch

Student

Details

4.2.3 Level 1 of Admin:

Id, password Id, password

Administrator Administrator

Authentication

University info

14 | P a g e

Login

1.2

Search

student

1.3

1.3 11

Administrator

Login

1.4

1 11


15/31

Changed info

Student info

Un

University info Student info

Changed info

University student

5. SNAPSHOT VIEW

ADMINISTRATOR LOGIN15 | P a g e

Add

University

1.5

Update

University

1.7

Add student

1.6


16/31

ADMINISTRATOR PANEL

16 | P a g e


17/31

USER LOGIN

17 | P a g e


18/31

STUDENT DETAILS18 | P a g e


19/31

ADDING UNIVERSITY

19 | P a g e


20/31

ADDING STUDENT

20 | P a g e


21/31

SEARCH STUDENT BY YEAR OF PASSING

21 | P a g e


22/31

6. Testing and Test Run

6.1 Coding :

Student Registration

using System;

22 | P a g e


23/31

using System.Collections;

using System.Configuration;

using System.Data;

using System.Linq;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.HtmlControls;using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Xml.Linq;

public partial class Admin_StudentReg : System.Web.UI.Page

{

protected void Page_Load(object sender, EventArgs e)

{

}

protected void Button1_Click(object sender, EventArgs e)

{

string filename, iurl;

filename = System.IO.Path.GetFileName(FileUpload1.FileName);

FileUpload1.PostedFile.SaveAs(Server.MapPath("Image\\") + filename);

iurl = "~/Admin/Image/" + filename;

bool r = DBAccess.savedata("INSERT INTO studdetails VALUES ('" + TextBox3.Text + "','" +

TextBox4.Text + "','" + TextBox5.Text+ "','" + TextBox6.Text+"','"+ TextBox7.Text+"','"+

TextBox8.Text+"','" + DropDownList1.SelectedValue + "','"+TextBox10.Text+"',"+TextBox11.Text

+","+TextBox12.Text+",'" + iurl + "')");

if (r == true)

Label1.Text = "Student Added";

elseLabel1.Text = "Student Already Exist";

}

}

User & Administrator Login

public partial class Default2 : System.Web.UI.Page

{


{

}


{

DataSet ds;

if(DropDownList1.SelectedIndex==2){

ds = DBAccess.fetchdata("select * from userlogin where userid='" + TextBox1.Text + "' AND

password='" + TextBox2.Text + "'");

23 | P a g e


24/31

if (ds.Tables[0].Rows.Count != 0)

{

Session["uid"] = TextBox1.Text;

DataSet ds1 = DBAccess.fetchdata("SELECT * FROM UserInfo WHERE userid='" +

TextBox1.Text + "'");

Session["img"]=ds1.Tables[0].Rows[0][5].ToString();

Response.Redirect("UserHome.aspx");

}else

Response.Redirect("registration.aspx");

}

else if(DropDownList1.SelectedIndex==1)

{

ds = DBAccess.fetchdata("select * from admin where userid='" + TextBox1.Text + "' AND

password='" + TextBox2.Text + "'");

if (ds.Tables[0].Rows.Count != 0)

{

Response.Redirect("~/Admin/AdminHome.aspx");

}

else

Response.Redirect("student.aspx");

}

}

User Registration

public partial class Default2 : System.Web.UI.Page

{


{

}


{

string filename, iurl;

filename = TextBox1.Text + ".jpg";FileUpload1.PostedFile.SaveAs(Server.MapPath("Image\\") + filename);

iurl = "~/Image/" + filename;

24 | P a g e


25/31

bool r = DBAccess.savedata("INSERT INTO userlogin VALUES ('" + TextBox1.Text + "','" +

TextBox2.Text + "')");

if (r == true)

{

bool r1 = DBAccess.savedata("INSERT INTO userinfo VALUES ('" + TextBox1.Text + "','" +

TextBox3.Text + "','" + TextBox4.Text + "','" + TextBox5.Text + "','" + TextBox6.Text + "','" + iurl + "')");

if (r1 == true)

Label1.Text = "Student Added";else

Label1.Text = "Student Already Exist";

if (r1 == true)

{

Session["uid"] = TextBox1.Text;

Session["img"] = iurl;

Response.Redirect("UserHome.aspx");

}

else

Label1.Text = "Error:Error on Inserting Data";

}

else

{

Label1.Text = "UserId Already Exist";

}

}

Student Search

public partial class StudentSearch : System.Web.UI.Page

{


{

}


{

if (DropDownList1.SelectedIndex == 0)

{

Response.Redirect("SearchbyCer.aspx?cer=" + TextBox1.Text);}

else

if (DropDownList1.SelectedIndex == 1)

25 | P a g e


26/31

{

Response.Redirect("SearchbyYop.aspx?Yop=" + TextBox1.Text);

}

else

Response.Write("The value does not exist");

}

}

User Master

public partial class User : System.Web.UI.MasterPage

{


{

}

protected void LinkButton2_Click(object sender, EventArgs e)

{

}

protected void LinkButton3_Click(object sender, EventArgs e)

{

Session["uid"] = null;

Response.Redirect("Login.aspx");

}

}

User Home

public partial class UserHome : System.Web.UI.Page{


{

Image1.ImageUrl = Session["img"].ToString();

Label1.Text = "Welcome " + Session["uid"].ToString();

}

}

6.2 Testing:26 | P a g e


27/31

The aim of the testing process is to identify all defects existing in software product.

However, for most practical systems, even after satisfactorily carrying out the

testing phase, it cant be guaranteed that the software is error free or whether it

would work satisfactorily. This is because of the fact that the input data domain of

most software products is very large, and it is not practical to test the software

exhaustively with respect to all the values that the input data domain of most

software products is very large and it is not practical to test the software

exhaustively with respect to all the values that the input data may assume. However,

it is also true that testing does expose many defects existing in a software product,

and therefore testing provides a practical way of reducing defects in a system and

increasing the users confidence in a developed system. A software product goes

three level of testing :

Unit Testing: The purpose of unit testing ids to determine the correct working ofthe individual modules. Unit testing involves a precise definition of the test cases,

testing criteria and management cases.

Integration Testing: During integration testing different modules of a system are

integrated using an integration plan. The integration plan specifies the steps and the

order in which modules are combined to realize the full system. After each

integration step the partially integrated system is tested. The primary objective of

integration testing is to test the module interfaces.

System Testing: System tests are designed to validate a fully developed system with

a view to assure it meets its requirements. There are essentially three kinds of

system testing

1. Alpha Testing

2. Beta Testing

3. Accept Testing

6.3 Maintenance:

Maintenance means restoring something to its original condition. After

implementation, maintenance begins. This includes enhancement, modification or

27 | P a g e


28/31

any change from original specification. Maintenance can be classified as corrective,

adaptive or perfective.

Corrective maintenance means repairing or making

changes because of previously uncorrected

problems or false assumption.

Adaptive maintenance means changing the program

function.

Maintenance covers a wide range of activities,

including correcting coding and design errors,

updating documentation and test data and

upgrading user support.

7. PROVISIONS FOR FUTURE WORK

Though our Project covers almost all the general functions required for a

Student Information System, but it has the scope to extend it to furtherheights. The provisions for extensions of the project are given in the

following points:

The Software can be so developed, so that it directly connects through

internet and can automatically handle activation- deactivation process.

The software may be improved graphically with the help of other application.

The software can made user friendly so that any layman can handle it.

Developing the project more realistically.

Reusability is possible as and when requires this application. We can update

it in next version. Reusable software reduces design, coding & testing cost by

amortizing over several designs.

The method is understandable to someone other than the creator of the

method can understand the code.

It cost is under the budget and make within given time period. It is desirable

to aim for a system within a minimum cost.

28 | P a g e


29/31

8. BIBLIOGRAPHY & REFERENCES

8.1 Books

Programmers Heaven: C # School, Rasheed Faran

Programming in CSharp, Steep Willi-Hans

8.2 Website

www.google.com

www.wikipedia.org

9. User Manual

A user guide or users guide, also commonly known as manual, is technical communication

document intended to give assistance to the people using a particular system. It is usually written

by a technical writer, although user guide are written by programmers, products or project

managers, or other technical staffs, particularly in smaller companies.

User guides are almost commonly associated with electronics goods,

computer hardware & software.

Most user guides contain both a written guide & the associatedimages. In case of computer applications, it is usual to include screenshots of how the program

should look, and a hardware manual often includes clear, simplified diagrams.

10. CONCLUSION

The Project Student Information System is a mere endeavor for computerizing the login needs

of the users and the administrator who controls everything. The software takes care of all the

29 | P a g e
http://www.wikipedia.org/http://www.wikipedia.org/


30/31

requirements of a document management system of a company and is capable to provide a secure

documentation of the company. It is easy to operate and maintain the customer details with the

publication of yearly sales report.

We whole heartedly wish that the software will achieve its height on its stipulated field as

we have tried our best to develop a natural and practical outlook. We with the help of .Net

framework and server configured the software with utter seriousness to comply with the existingSIM document management system. But we have also kept open the scope of developing and

modernizing the software.

This is to certify that the project entitle has been prepare according to the regulation of degree of

bachelor in computer application under W.B.U.T. the project been submitted by students of I.T 4th

Yr. 7th semester of Institute of Science and Technology, Academy of Technology & Dumkal

Institute of Engineering and Technology (affiliated to W.B.U.T) have fulfill the requirement for

submission of this project.

Name : 1. Debosmita Ghosh 2. Falguni das 3. Sauptik Basak

4. Priyanka Chatterjee 5. Monika Majumder 6. Abhishek Mondol

The whole procedure has been carried out under my supervision & guidance. I have gone through

the project & have seen if is fulfilling the requirement of Major project under W.B.U.T.

Signature:

______________________________

Ayon Chatterjee

30 | P a g e


31/31

Documents

MODIFIED SIS 2