A Project Report On

STUDENT INFORMATION SYSTEM

Submitted in partial fulfillment of The requirements for the 7th Semester Sessional Examination of

BACHELOR OF TECHNOLOGY
IN Information Technology by <Scholar University Regd. No.>
Under the esteemed guidance of

<Supervisor Name>

DEPARTMENT OF INFORMATION TECHNOLOGY

GANDHI INSTITUTE OF ENGINEERING AND TECHNOLOGY

GUNUPUR 765022

DEPARTMENT OF INFORMATION TECHNOLOGY

CERTIFICATE

This is to certify that the project work entitled TOPIC is done by Name-, Regd. No.- in partial fulfillment of the requirements for the 7 th Semester Sessional Examination of Bachelor of Technology in Information

Technology, during the academic year 2013. This work is submitted to the department as a part of evaluation of 7th Semester Project.

<Supervisor Name>
P.B.Mishra) H.O.D, IT Project Supervisor

(Prof. Dr.

ACKNOWLEDGEMENT
My sincere thanks to prof. pragnyaban mishra , the head of the department of it engineering ,Gandhi engineering and technology ,Gunupur for his encouragement and valuable suggestion during period of my project work. No words should suffice to express my regards and gratitude to prof .k.murli gopal,department of information technology ,giet,Gunupur for his inspiring guidance, constand encouragement,immeence support and help during the course of the project. I express my heartfelt gratitude to principal, giet, Gunupur for permitting to carry out this project work. Subasis Mishra(1001210557) Madhusmita Das(1001210534) T.Prabin Kumar Patro( 1121210082)

ABSTRACT

The project student information system developed for providing services for getting the information of a student. It provides capabilities for entering student records, tracking student attendance. The system includes several modules such as HOD, STUD_ID, ATTENDANCE, VIEW & HELP. The Hod module has been made for Head Of The Department so he need to login him self and then only he can able to use the form where he can view , update and delete a record. The STUD_ID module consist of two sub modules such as personal information & official information where the operator can store the data. In the ATTENDANCE module the operator can store the attendance of the students in view module the user can view all the personal information , official information and attendance of the student. Help module provides the information how to use the software. This project provides the advantage of data accuracy, make student information management more secure and effective

TABLE OF CONTENT
Topics 1. Introduction
Purpose Project Scope Product Features Feasibility study

Page No

2.

System requirement specifiation

User Requirements (SRS) Hardware Requirements Software requirement

3.

System Design & Specifications

Project Model DFD E-R Diagram ( if necessary) UML ( Use Case , Class / Object Diagram, Interaction / Collaboration Diagram) Screen-Shot Diagram

4. 5.

Coding
Sample Code ( full Code for visual basic6.0)

Testing
Unit Testing Integration Testing Test cases (Input, Expected Output, Actual Output, Remedial actions)

6. 7.

Conclusion & Limitations. Reference/Bibliography

Books

Websites

INTRODUCTION
Student information system are the primary system for operating colleges the student information system allows the department to store & retrieve the data in more accurate manner. It provides capabilities for entering student records tracking student attendance and managing other student related data needs in the college or university.

Purpose
To make the application of student information system usable for the college or universities. To access the student records and get the desired information which may required. To automate the existing system of manually maintain the records of the students records, student details attendance details, etc. To increase data accuracy, make student information management more secure, effective, convenient and accessible.

Scope
This project is aimed at how the institute can improve the efficiency system. The feature implementation will be online help for the users to obtain information. In large enterprise solutions that have student data at their core. Student information system is one of the application to improve the information of any particular student. This application involves almost all the featuers of the information.

FEATUERS
Create different system users and design different roles and related permissions. Group the user together in a single account according to some criteria. Authenticate all the users of the system. In their a operator department . Use of search quarry for professional and personal data search of a student Handling records of attendance, sgpa and personal information. communicating student details to faculty through a view portal. can access any student information of the

A software life cycle model is a descriptive & diagrammatic representation of the software life cycle. A life cycle model represents all the activities required to make a software product transit through its lifecycle phases. It also captures the order in which these activities are to be under taken. In other words a life cycle model maps the different activities performed on a software product from its inception to retirement. Different life cycle models may map the basic development activities to phases in different ways thus no matter which life cycle model is followed ,the basic activities are included in all life cycle models though the activities may carried out in different orders in different life cycle models During any life cycle phase more than one activity may also be carried out. For example the design phase might consist of the structured analysis activity followed by the structured design activity. The development team must identify a suitable life cycle model for the particular project and then adhere to it. Without using a particular life cycle model the development of a software product would not be in a systematic and disciplined manner. When a software product is being developed by a team there must be a clear understanding among team members about when & what to do. Other wise it would lead to project failure This problem can be illustrated by using an example suppose a software development problem is divided into several parts and the parts are assigned to the team members. From then on suppose the team members are allowed the freedom to develop the parts assigned to them in what ever the way they like. It is possible that one member might start writing the code for his part another might decided to prepare the test document first and some other engineer might begin with the design phase of the parts assign to him this would be one of perfect recipes for the project failure.

Feasibility study:The main aim of feasibility study is to determine whether it would be technically feasible to develop the product. At first project managers or team leaders try to have a rough understanding of what required to be done by visiting the client side. They study different input data to the system and output data to be produced by the system they study what kind of processing is needed to be done on these data they look at the various constrains on the behavior of the system After they have the overall understanding of the problem they investigate the different solution that are possible then they examine each of the solution in terms of what kind of resources required what would be the cost of development and what would be the the solution is feasible financially and technically. They check whether the consumer budget would meet the cost of the product and whether they have sufficient technical expertise in the area of development . the following is an example of feasibility study under taken by an organization. It is intended to give u a feel of the activities and issues involved in the feasibility study phase of a typical software project. Time feasibility is a determination of whether a proposed project can be implemented fully with in a stipulated time frame. If project takes too much time it is likely to be rejected. development time for each solution based on this analysis they pick the best solution & determine wether

Requirement analysis and specification:The aim of the requirement analysis and specification phase is to understand the exact requirement of the consumer and to document them properly. This phase consist of two distinct activities ,namely requirements gathering and analysis, and specification. The goal of requirements gathering activity is to collect all the relevant information from the consumer regarding the product to be developed. This is done to clearly understand the consumer requirements so that in completeness and inconsistencies are removed .the requirement analysis activity is begun by collecting all relevant data regarding the product to be developed from the user of the product and from the consumer through interviews of the system. For example ,to perform the requirements analysis of a business accounting software required by an organization,the analyst might interview all the accountants of the organization to ascertain their requirements. The data collected from such a group of users usually contain several condradiction and ambiguities,since each user typically has only a partial and incomplete view of the system. Therefore it is necessary to identify all ambiguities and contradiction in the requirement and resolve them through further discussion with the customer.After all ambiguities, inconsistencies, and incompleteness have been resolved and all the requirements properly understood,the requirements specification activity can start.During this activity,the user requirements are systematically organized into a software requirements specification(SRS)document. The customer requirements identified during the requirements gathering and analysis activity are organized into SRS document.The important components of this document are functional requirements,the nonfunctional requirements,and the goals of implementation. We did the requirements gathering and analysis by current scenario interview in our college and got many requirements what actually a student wants.Finally we got the software requirement specification(SRS)document.For representing a good SRS document to follow certain rules and regulations.

These are Concise:The SRS document should be concise and at the same time unambiguous,consistent, and complete.Verbose and irrelevant description reduce readability and also increase error possibilities. Structured:It should be well-structured.A well-structured document is easy to understand and modify.In practice,the SRS document undergoes several revision to cope up with the customer requirements. Often,the customer requirements evolve over a period of time.Therefore ,in order to make the modification to the SRS document easy,it is important to make the wellstructured. Black-box view:It should only specify what the system should do and refrain from starting how to do these this means that the srs document should specify the external behabour of the system and not discuss the implementation issues. The srs document should view the system to be developed as black box, and should specify the externally visible behavior of the system. For this reason, the srs document is also called the black box specification of a system. Response to undesired events:- it should characterized acceptable responses to undesired event. These are called system response to exception conditions. Verifiable all requirements of the systems as documented in the srs document should be verifiable. This means that it should be possible to determine whether or not requirements have being met in an implementation .

To satisfy these conditions we used the following standards . 1. Paper 2. Margin : : Top & Bottom Left & Right :1 cm. :1.25cm. A4 Size

3. Heading Style: 1st Heading: Times New Roman(font size-18(B)) 2nd Heading: Times New Roman(font size-16(B)) 3rd Heading: Times New Roman(font size-17(B))

4. Document Font : Ariel(font size-12)

Line spacing :1.5cm

Our requirement analysis describe the followings.. 1. What is the problem ? 2. Why it is important to solve the problem ? 3. What are the inputs and outputs for the system ? 4. What are the possible procedure that to be followed ? 5. What might complicities that might come while solving the problems? We collected the answer. The main point is to get information of any students database without any interaction party. The solution is to develop a project that will help the department to get information easily.

SYSTEM REQUIREMENTS
Software specification
Operating system : Language windows xp professional

Hardware specification
Processor : Speed Ram : : Intel core 2 DUO 2.4 Ghz 256 MB 40 GB standard

Hard Disk : Key Board :

OPERATING SYSTEM
WindowsXP operating system is a multi-tasking,multiprogramming network operating system developed by Microsoft.WindowsXP professional is an operating system designed for corporate and high end users who want a robust and powerful operation environment.

FEATURES OF WINDOWSXP PROFESSIONAL

Windows XP professional is built to run on several different families of computer processor.In addition it can run on computer running more than one processor.It means one can run windowsXP professional on some very fast machine;it is not limited to the x86 series.

IMPORTANT FEATURES OF WINDOWS XP

Microsoft Exchange Direct X multimedia support Internet Explorer Hardware profile

SYSTEM DESIGN AND SPECIFICATION

Characteristics of a good software

The definition of a good software design can very depending on the application being designed.for example size used by a program may be an important issue to characterize a good solution for embedded software development-since embedded applications are often required to be implemented using memory of limited size due to cost.space,or power consumption considerations.for embedded applications,one may sacrifice design comprehensibility to achieve code compactness.for embedded application,factors like design comprehensibility may take a back seat while judging the goodness of design.therefore ,the criteria used to judge how good a given design solution is can vary widely depending upon the application.Not only is the goodness of design dependent on the targeted application,but also the notion of goodness of a design itself varies widely across software engineers and academicians.However,most researchers and software engineers agree on a few desirable characteristics that every good software design for general application must possess. The characteristics are listed below: Correctness:A good design should correctly implement all the functionalities identified in the SRS document. Understandability:A good design is easily understandable. Efficiency:It should be easily amenable to change.

Possibly the most important goodness criterion is design correctness.A design has to be correct to be acceptable.A design that is easy to understand is also easy to develop,maintain and change.Thus,unless a design is easily understandable,it would require tremendous effort to implement and maintin it. Example of High level and Low level design High Level Design(HLD) Project Model Structure Chart

DFD E-R Diagram UML(use cas,Class/Object Diagram,Interaction/Collaboration Diagram)

Low Level Design(LLD) Process specification(Pseudo code/Algorithm) Screen-Shot Diagram

DATA FLOW DIAGRAM

A Data Flow Diagram(DFD) is a graphical representation of the flowof Student Information System.A data flow diagram can also be used for the visualization of Data processing. It is common practice for a designer to draw a context-level DFD first Which shows the interaction between the system and outside entities.This context-level DFD is then exploded to show more detail of the sysrem being modeled.

A DFD represents flow of data through a system. Data flow diagrams are commonly used during program analysis. It views a system as a function that transforms the input into desired output. A DFD shows movement of data through the different transformation or processes in the system. Data flow diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to restock how any system is developed can be determined through a data flow diagram

Conclusion As the project student information system is one of the web based project we have been developing the project since four month. For the timing we have completed two modules. Our feature work to develop other modules which make the student information system more efficient. It has been developing in visual basic 6.0 with ms access used as the backend of the application. The complete system is thoroughly tested with the availability data and throughput reports which are prepared manually. It has been observed that now it is easier for anyone to find details in various organization matching his/her profile. These are found to be more accurate because of availability of information for different posts at different organization design procedure and output reports are presented in this project report. This design is so flexible that any new modules can be incorporated easily.

BIBILIOGRPHY 1.