Student Record and Information System

7/30/2019 Student Record and Information System

1/105

A PROJECT REPORT

ON

STUDENT RECORD AND INFORMATION SYSTEM

Department of Computer Applications (M.C. A.)

Submitted To: Submitted By:

Mr. Ritesh Rastogi Ashutosh Pratap Kushvaha

(1013314012)

Tamanna Sharma

(1013314055)

MCA 4th

SEM sec-A

NOIDA INSTITUTE OF ENGINEERING AND TECHNOLOGY

19, Knowledge Park- II, Institutional Area, Phase- II,Greater Noida, Uttar Pradesh

27th April, 2012


2/105

Student Record and Information System

Chapter No. Title Page No.

Bona fide i

Executive Summary ii

1 Introduction 1

2 Language and Tools To Be

Used

3

3 The Software Development

Life Cycle

5

4 Requirement Analysis 8

5 Design Constraints 10

6 System Analysis 14

7 System/Software

Requirement(SRS)

17

7.1 Module 1 19

7.2 Module 2 21

7.3 Module 3 24

8 Project Plan 26

8.1 Scope Management 27

8.2 People Management 31

8.3 Risk Management Plan 32

8.4 Communication Plan 33

8.5 Time Management Plan 34

9 Feasibility Analysis 35

10 Methodology Adopted 38


3/105


11 System Design 41

12 Coding Methods 45

13 Testing 47

14 Maintenance 50

15 Module Description 53

16 List of Tables 55

17 ER Diagram 62

18 Data Flow Diagram 64

19 Screenshots of forms 68

20 Future Scope of the Project 97

21 References 99


4/105


BONA FIDE CERTIFICATE

Certified that this project report STUDENTRECORD AND INFORMATION

SYSTEM is the bona fide work of Ashutosh Pratap Kushvaha (1013314012)and Tamanna Sharma (1013314055) who carried out the project under my

supervision.

Signature of the HOD Signature of Supervisor

SIGNATURE SIGNATURE

Mr. Ritesh Rastogi Mr. Mohit Choudhary

HEAD OF THE DEPARTMENT SUPERVISOR

(Lecturer)

M.C.A. M.C.A.

NOIDA INSTITUE OF ENGINEERING & TECHNOLOGY

19, Knowledge Park-II, Institutional Area, Phase-II,

Greater Noida, Uttar Pradesh

Pa


5/105


EXECUTIVE SUMMARY

This Project mainly records data of students and provides access to information whenever

needed. This information includes: personal and professional details of students,

attendance record, assignment record, record of marks. As a unique feature, it also

provides rating for students as per the above mentioned criteria. In the current system all

the activities are done manually. It is very time consuming and costly. But through this

project we can deal with the information related to the students through an automated

process.

SUMMARY OF THE PROJECT:

Teacher acts as admin of this system. Admin has the rights to input, update and delete data.

Login for the system is password protected to provide privacy and security of information.

User has the choice of selecting required option after login. Thus, he/she is directed towards

further options for the preferred choice. Further admin can perform above mentioned

operations according to the choices selected by him/her.

In short, Student Record and Information System reduce the paper work in record-

keeping of students. Rather it simplifies the process of maintenance of records. It also deals

with difficulty in updating and accessing the records of students. As an additional benefit,

the chances of mistakes are highly reduced due to large amount of information. This project

is time-efficient too in comparison to the traditional system.

Pa


6/105


INTRODUCTION

Pag


7/105


Student Management System is software which is helpful for the school authorities as well

as faculties. In the current system all the activities are done manually. It is very time

consuming and costly. Our Student Management System deals with the various activities

related to the students.

There are mainly 2 modules in this software

User module Mark management

In the Software we can register as a user and user is administrator. Administrator has the

power to add new user and can edit and delete a user. A student can register as user and

can add edit and delete his profile. The administrator can add edit and delete marks for the

student. All the users can see the marks.

Pag


8/105


LANGUAGES and TOOLS to be used

Pag


9/105


O/S PLATFORM : Windows 7 DBMS TOOLS/ENV. : MySQL 5.5 PROGRAMMING TOOLS/ENV. : Core Java (jdk1.6) Runtime Environment SUPPORT UTILITIES AND APPLICATIONS : Photoshop 7.0 and

Gif-Animator used to create images

Pag


10/105


THE SOFTWARE DEVELOPMENT LIFE CYCLE

Pag


11/105


1) Planning Phase

The concept is further developed to describe how the business will operate once the

approved system is implemented, and to assess how the system will impact employee and

customer privacy. To ensure the products and /or services provide the required capability

on-time and within budget, project resources, activities, schedules, tools, and reviews are

defined. Additionally, security certification and accreditation activities begin with the

identification of system security requirements and the completion of a high level

vulnerability assessment.

2) Software Requirement Analysis

Software Requirement Analysis is also known as feasibility study. In this requirement

analysis phase, the development team visits the customer and studies their system

requirement. They examine the need for possible software automation in the given

software system. After feasibility study, the development team provides a document that

holds the different specific recommendations for the candidate system.

The requirements analysis and information gathering process is intensified and focused

specially on software. To understand what type of the programs to be built, the system

analyst must study the information domain for the software as well as understand required

function, behavior, performance and interfacing. The main purpose of requirement analysis

phase is to find the need and to define the problem that needs to be solved.

3) System Analysis and Design

In System Analysis and Design phase, the whole software development process, the overall

software structure and its outlay are defined. After designing part, a software development

model is created. Analysis and Design are very important in the whole development cycle

process. Any fault in the design phase could be very expensive to solve in the software

development process. In this phase, the logical system of the product is developed.

Pa


12/105


4) Coding

In Coding phase, the design must be decoded into a machine-readable form. If the design of

software product is done in a detailed manner, code generation can be achieved without

much complication. For generation of code, Programming tools like Compilers, Interpreters,

and Debuggers are used. For coding purpose different high level programming languages

like C, C++, Pascal and Java are used. The right programming language is chosen according to

the type of application.

5) Testing

After code generation phase the software program testing begins. Different testing methods

are available to detect the bugs that were committed during the previous phases. A number

of testing tools and methods are already available for testing purpose.

6) Maintenance

Software will definitely go through change once when it is delivered to the customer. There

are large numbers of reasons for the change. Change could happen due to some

unpredicted input values into the system. In addition to this the changes in the system

directly have an effect on the software operations. The software should be implemented to

accommodate changes that could be happened during the post development period.

Pa


13/105


THE REQUIREMENT ANALYSIS

Pa


14/105


In the Requirement Analysis phase, the development team visits the customer and

studies their system requirement. They examine the need for possible software

automation in the given software system. After feasibility study, the development

team provides a document that holds the different specific recommendations for

the student system.

The Requirement Analysis is intensified and focused specially on software. To

understand what type of the programs to be built, the system analyst must study

the information domain for the software as well as understand required function,

behavior, performance and interfacing. The main purpose of requirement analysis

phase is to find the need and to define the problem that needs to be solved.

Pag


15/105


DESIGN CONSTRAINTS

Pag


16/105


The language that is used for coding the Student Record And Information System is

Java. This design document will give a detailed description of the presentation tier, the

middle tier which consists of the class diagrams, sequence diagrams for the Student Record

And Information System and finally the data tier. The Unified Modeling Language (UML) is

a standardized visual specification language for object modeling. Thus, the class diagrams

and the sequence diagrams depicted in the Architecture design document will be developed

according to the UML standard notation.

ARCHITECTURE OF THE STUDENT RECORD AND INFORMATION SYSTEM

The architecture of the Student Record and information system is based on the three-tier

architecture. This three-tier architecture mainly consists of three layers namely:

Presentation Tier Business Tier Data Access Tier

The Presentation Tier converts and displays information into a human legible form. This tier

displays information related to services such as open in window form, updating records etc. It

communicates with the other tiers by outputting results to the user tier and all the other tiers.

The Business Logic tier is mainly responsible for information exchange between the user

interface and the database of the project. The final layer of the three tiered architecture is the

Data Access tier, which mainly consists of the Database servers. The information related to

the Student Record and Information System is stored and retrieved from here.

Page


17/105


A simple representation of the three-tier architecture would be as follows:

Figure 4 - Three Tier Architecture

Pag


18/105


The architecture of the Student Record and Information System can be depicted as follows:

This includesPresentation Tier

Java Swing forms and the user

controls for the Student Record &Information System

This includes the classes orBusiness Logic Tier

the business components

This includes the Database

Data Access Tier

servers for the Student Record &

Information System

The three tier architecture would be discussed in detail in the following sections:

1. PRESENTATION TIERThe presentation tier is the top most layer of the Student Record & Information system

application. The presentation tier is mainly responsible for the user interface of the

application which deals with the presentation of data to the user. The presentation tier of the

Student Record & Information System is mainly formed by the windows forms.

2. BUSINESS LOGIC TIER

The Business Logic Tier is the middle tier of the three-tier architecture. The business logic

for the Student Record & Information System would be present here. In the case of this

project, this is the layer which is responsible for the information exchange between the user

interface and the database.

Pag


19/105


SYSTEM ANALYSIS

Pag


20/105


EXISTING SYSTEM:

System Analysis is a detailed study of the various operations performed by a system and

their relationships within and outside of the system. Here the key question is- what all

problems exist in the present system? What must be done to solve the problem?

Analysis begins when a user begins a study of the program using existing system.

During analysis, data collected on the various files, decision points and transactions

handled by the present system. The success of the system depends largely on how

clearly the problem is defined, thoroughly investigated and properly carried out through

the choice of solution. A good analysis model should provide not only the mechanisms of

problem understanding but also the framework of the solution. Thus it should be studied

thoroughly by collecting data about the system. Then the proposed system should be

analyzed thoroughly in accordance with the needs.

System analysis can be categorized into four parts:

1) System planning and initial investigation

2) Information Gathering

3) Applying analysis tools for structured analysis

4) Feasibility study

5) Cost/ Benefit analysis.

In the current system we need to keep number of records related to the student and

want to enter the details of the student and the marks manually.

In this system only the teacher and students views the mark of the student and they

want to enter the details of the student.

Page


21/105


PROPOSED SYSTEM:

In our proposed system we have the provision for adding the details of the student by

teachers only. Another advantage of the system is that it is very easy to edit the details

of the student and delete a student when it found unnecessary. The marks of the student

are added in the database and so students can also view the marks whenever they want.

Our proposed system has several advantages:

User friendly interface Fast access to database Less error More Storage Capacity Search facility Quick transaction

Page


22/105


SYSTEM/SOFTWARE REQUIREMENT

Pag


23/105


Table of contents

1.0. Introduction

1.1. Purpose

1.2. Scope

1.3. Overview

2.0. Overall Description

2.1. System Environment

2.2. Functional Requirements Specification

2.2.1. Teacher Use Case

2.3. User Characteristics

3.0. Requirements Specification

3.1. External Interface Requirements

3.2. Functional Requirement

Page


24/105


1.0. INTRODUCTION

Student Record and Information System is software which is helpful for the faculties. In

the current system all the activities are done manually. It is very time-consuming and costly.Our Student Record and Information System deals with the various activities related to the

students in an efficient but simpler way.

There are mainly 6 modules in this software:

User module Student Profile Module Marks management module Attendance module Assignment module Rating module

In this Software a teacher can register as a user and user is administrator. Teacher has

the power to add himself. Teacher can add edit and delete profile, marks, attendance,

assignments records and rating of students. All the users can see as well as edit the data.

1.1. PURPOSE

This SRS Document contains the complete software requirements for the Student

Record and Information System and describes the design decisions, architectural design

and the detailed design needed to implement the system. It provides the visibility in

the design and provides information needed for software support. New reliable and fast

information and record management software with the great user support.

Pag


25/105


1.2. SCOPE

Student Record and Information System is used to replace old paper work system

and build upon the existing information system in order to efficiently provide student

information to teachers and school administration .This increases the efficiency of report

generation and provides a mechanism to edit the student information form which

makes the system flexible.

1.3. OVERVIEW

This document has been prepared in accordance with the IEEE StandardRecommended Practice for Software Requirements Specifications .The main purpose of

the system is to provide student record. The system to be developed will be able to

manage the following:

Student profile Attendance Marks Assignments Rating

The above services should be accessible by staff anytime without additional software to

install on their computer.

Pag


26/105


2.0. OVERALL DESCRIPTION

2.1. SYSTEM ENVIRONMENT

Operating System : Windows 7

Language : J.D.K. 1.6 Runtime environment

Database : MySQL 5.5

2.2. FUNCTIONAL REQUIREMENT SPECIFICATION

Student Record and Information System software is used to maintain and manage the

information of students .This software helps the user(i.e. Teacher) to get easy access of theinformation of students .This software is helpful for the teachers because they can easily

bring changes to the records of the student. This software is also helpful in maintaining

personal, professional details, marks details, attendance details, assignment details and also

can add rating to students in accordance to his/her performance in that subject.

Pag


27/105


2.2.1. Teacher Use Case

Pag


28/105


2.3 .USER CHARACTERISTICS

The user of the system is teachers who maintain the system. The users are assumed to

have basic knowledge of the computers. The proper user interface, users manual, and the

guide to maintain the system must be sufficient to educate the users on how to use the

system without any problem .

Pag


29/105


3.0.REQUIREMENTS SPECIFICATION

3.1 EXTERNAL INTERFACE REQUIREMENT

3.1.1 User Interfaces

Keyboard, mouse and printer

3.1.2 Hardware Interfaces (minimum requirements)

Processor : Pentium III 630MHz RAM : 128 MB Hard Disk : 20GB Monitor : 15 Color monitor Key Board : 122 Keys

3.2. FUNCTIONAL REQUIREMENTS

Student information which include personal details of student, students attendance,

marks, no. of assignments submitted, report i.e. rating of each student are registered on the

system by the staff and can be changed or updated if information is incorrect.

3.2.1. Design constraints

The system needs to design base on the existed code and database using MySQL 5.5.

Pag


30/105


3.3. Software system attributes

3.3.1 Security

This application is password protected. Teacher has to be registered in order to log in theapplication. Teachers have to enter correct username and password in order to access the

application.

3.3.2 Maintainability

This application is designed in a maintainable manner, it is easy to incorporate new

requirements in the individual modules i.e. student info, marks info, assignment info,

attendance info, ratings n user accounts.

3.3.3 Portability

This application is easily portable on any windows-based system that has MySQL

installed.

Pag


31/105


PROJECT PLAN

Pag


32/105


SCOPE MANAGEMENT:

The scope is the most important element to understand about any project. All planning

and allocation of resources are anchored to this understanding. The knowledge area of

Scope Management is all about making sure that the project includes only the work

required to complete the project successfully. To be effective at scope management, you

must learn to control what is and what is not in the scope of the project. Below are some

of the best practices for successful scope management.

1. Collect Project Requirements2.

Define the Scope

3. Create a Work Breakdown Structure4. Verify the Scope and Get Feedback5. Monitor and Control the Scope1. Collect Project Requirements

The ability to define and then effectively control the scope of a project depends a lot on

the goals and requirements of the project. For this reason, you need to gather the

necessary information up front, before you ever start the project. By clearly

understanding the needs of the stakeholders and the capabilities and constraints of your

resources, you have a higher chance to succeed.

The easiest way to collect the project requirements is to perform interviews with the key

stakeholders. Ask questions about their views of the finished product, the deliverablesthey expect to receive, and the schedule of the project. Once you have the information

you need, you may want to create a Scope Management Plan to define the processes that

will be followed in defining scope, documenting scope, verifying and accepting scope,

and managing change requests.

Pag


33/105


2. Define the Scope

The scope of a project typically consists of a set of deliverables, an assigned budget, and

an expected closure time. The previously collected project requirements will help you

define the scope. Be sure to write down exactly what the project will entail and what it

will not entail. Any amount of variation in the scope of the project can affect the project

schedule, budget, and ultimately the success of the project. Getting a clear and concise

definition of the scope will help you manage changes as they occur. With a clear scope

definition, you can simply ask the question, "Does this change fall within the scope of the

project?" If the answer is yes, then vet and approve the change. If the answer is no, then

put a pin it and save it for another time or project.

3. Create a Work Breakdown Structure

A work breakdown structure or WBS is a graphical representation of the hierarchy of the

project. The WBS forces the project team to think through all levels of the project and

identify the major tasks that need to be performed for the project to be completed on

time. By starting with the end objective and then successively subdividing it into

manageable steps or components in terms of size, duration, and responsibility, the WBS

provides a high level view of the entire project. Furthermore, the framework makes

planning and controlling the scope of the project much easier since you have a graphical

chart to reference point for the tasks and subtasks needed for each phase of the project.

As a general rule of thumb, no task within the WBS should be less than 8 hours or more

than 80 hours.

Pag


34/105


4. Verify the Scope and Get Feedback

Because projects are expected to meet strict deadlines, verifying the scope of the project

is critical before and during the project cycle. Scope verification can be done after each

major task or phase is completed or if it is a smaller project, after the project has been

completed. To verify the scope, meet with the project customer or stakeholder and get

him/her to formally accept the project deliverables. This includes getting a written

acceptance of the deliverables and requesting feedback on the work performed.

Getting feedback from the customer is an excellent way for you to improve processes and

make sure the customer is happy with your work and the status of the project. The mostimportant thing here is to communicate well and often. Verifying the scope and getting

feedback will help you focus on customer acceptance, quality control, and verifying that

work performed meets the definition of the scope of the project.

5. Monitor and Control the Scope

Now that the Scope has been clearly defined, a work breakdown structure has been

organized, and the customer has formally accepted the scope of the project, it is time to

actually manage and control the scope to avoid scope creep. Scope creep refers to the

incremental expansion of the scope of the project, which may include and introduce more

requirements that may not have been a part of the initial planning phases, but add costs

and time to the original project.

Pag


35/105


To effectively monitor and control the scope of the project, make sure you have an

established process for managing change requests. Any and all requests should be vetted and

approved before they get introduced into the project. The budget and schedule of the project

should also be altered to reflect the new changes. These changes should get a formal sign-offfrom the customer or key stakeholder before proceeding. It is important that you closely

monitor and control the scope to avoid disgruntled customers, higher than expected costs, and

projects that aren't completed on time.

Pag


36/105


PEOPLE MANAGEMENT:

People management means To get things done. It is effectivemanagement of people

involved to produce outstanding results. People Management is about doing few things right

to achieve bigger goals.People Empowerment can be a very effective tool within the field of

people management. This technique can be used to involve employees in any improvement

program within an organization. Authority, accountability, and responsibility are delegated to

the participants for improving the processes which are under their control without first having

to obtain permission from management before making changes. This can be successful only

when workforce is has commitment towards problem solving.

S.No Activity Planned

Start Date

Planned End

Date

Actual

Start Date

Actual End

Date

Person

Assigned

Remark

1 Identify Project 16/2/2012 22/2/2012 18/2/2012 20/2/2012 Ashutosh Pratap

Kushvaha

2 Making Project

Plan

23/2/2012 29/2/2012 23/3/2012 28/2/2012 Tamanna

Sharma

3 System Study 1/3/2012 7/3/2012 1/3/2012 7/3/2012 Tamanna

Sharma

4 System Design 8/3/2012 15/3/2012 9/3/2012 15/3/2012 Ashutosh Pratap

Kushvaha

5 Implementation 16/3/2012 12/4/2012 16/3/2012 12/4/2012 Ashutosh Pratap

Kushvaha

6 System Testing 13/4/2012 20/4/2012 13/4/2012 20/4/2012 Tamanna

Sharma

Pag


37/105


RISK MANAGEMENT PLAN:

A Risk Management Plan is a document prepared by a project manager to foresee risks,

to estimate the impacts, and to create response plans to mitigate them. It also consists of

the risk assessment matrix.

A risk is defined as "an uncertain event or condition that, if it occurs, has a positive or

negative effect on a project's objectives." Risk is inherent with any project, and project

managers should assess risks continually and develop plans to address them. The risk

management plan contains an analysis of likely risks with both high and low impact, as

well as mitigation strategies to help the project avoid being derailed should common

problems arise. Risk management plans should be periodically reviewed by the project

team in order to avoid having the analysis become stale and not reflective of actual

potential project risks.

Most critically, risk management plans include a risk strategy. Broadly, there are four

potential strategies, with numerous variations. Projects may choose to:

Accept risk; simply take the chance that the negative impact will be incurred

Avoid risk; changing plans in order to prevent the problem from arising

Mitigate risk; lessening its impact through intermediate steps

Transfer risk; outsource risk to a capable third party that can manage the outcome

Risk management plans often include matrices.

Pag


38/105


COMMUNICATION PLAN:

Communication planning is the art and science of reaching target audiences using

marketing communication channels such as advertising, public relations, experiences or

direct mail for example. It is concerned with deciding who to target, when, with what

message and how.

The communication plan serves as a guide to the communication and sponsorship efforts

throughout the duration of the project. It is a living and working document and is updated

periodically as audience needs change. It explains how to convey the right message, from

the right communicator, to the right audience, through the right channel, at the right time.

It addresses the six basic elements of communications: communicator, message,

communication channel, feedback mechanism, receiver/audience, and time frame.

A communication plan includes:

Who - the target audiences

What the key messages that are trying to be articulated

When timing, it will specify the appropriate time of delivery for each message

Why the desired outcomes

How - the communication vehicle (how the message will be delivered)

By whom - the sender (determining who will deliver the information and how he or she

is chosen)

Pag


39/105


TIME MANAGEMENT PLAN:

Time management is the act or process of planning and exercising conscious control over

the amount of time spent on specific activities, especially to increase effectiveness, efficiency

or productivity. Time management may be aided by a range of skills, tools, and techniques

used to manage time when accomplishing specific tasks, projects and goals complying with a

due date.

This set encompasses a wide scope of activities, and these include planning, allocating,

setting goals, delegation, analysis of time spent, monitoring, organizing, scheduling, and

prioritizing. Initially, time management referred to just business or work activities, but

eventually the term broadened to include personal activities as well. A time management

system is a designed combination of processes, tools, techniques, and methods. Usually time

management is a necessity in any project development as it determines the project completion

time and scope.

Accurate time estimation is a skill essential for good project management. It is important

to get time estimates right for two main reasons:

1. Time estimates drive the setting of deadlines for delivery and planning of projects, andhence will impact on other people assessment of your reliability and competence as a

project manager.

2. Time estimates often determine the pricing of contracts and hence the profitability ofthe contract/project in commercial terms.

Pag
http://en.wikipedia.org/wiki/Managementhttp://en.wikipedia.org/wiki/Planninghttp://en.wikipedia.org/wiki/Allocatinghttp://en.wikipedia.org/wiki/Goal_settinghttp://en.wikipedia.org/wiki/Monitoringhttp://en.wikipedia.org/wiki/Monitoringhttp://en.wikipedia.org/wiki/Goal_settinghttp://en.wikipedia.org/wiki/Allocatinghttp://en.wikipedia.org/wiki/Planninghttp://en.wikipedia.org/wiki/Management


40/105


FEASIBILITY ANALYSIS

Pag


41/105


Is cancellation of a project a bad news? As per IBM report, 31% projects get

cancelled before they are completed, 53% over-run their cost estimates by an average of

189% and for every 100 projects, there are 94 restarts. Caper Jones reports that the

average cancelled project in the US is about a year behind schedule and has consumed

200% of its expected budget by the time it is cancelled. He further estimates that the work

on cancelled projects comprises about 15% of the total US software efforts.

Inspite of these statistics, cancelling a project is, in itself, neither good nor bad. The

trick is to perform the minimum amount of work necessary to determine whether the

project should be cancelled.

How do we cancel a project with the least work? One of the most effective ways is to

conduct a feasibility analysis to determine whether the full scale project is workable. This

analysis culminates in a feasibility report, which facilitates decision about rest of the project.

Whatever we think need not be feasible.It is wise to think about the feasibility of any

problem we undertake. Feasibility is the study of impact, which happens in the organization

by the development of a system. The impact can be either positive or negative. When the

positive dominates the negative, then the system is considered feasible. Here the feasibility

study can be performed in two ways such as Technical feasibility and Economical Feasibility.

Pag


42/105


TECHNICAL FEASIBILITY:

We can surely say that it is technically feasible, since there will not be much difficulty in

getting required resources for the development and maintaining the system as well.

All the resources needed for development of the software as well as the maintenance of the

same are available in the organization here. We are utilizing the resources which are already

available.

However, for most of the projects, feasibility depends on non-technical issues like:

Are the projects cost and schedule assumptions realistic? Is the business model realistic? Is there any market for the product?

ECONOMICAL FEASIBILITY:

Development of this application is highly economically feasible. The organization need

not spend much money for the development of the system already available. The only thing

to be done is making an environment for the development with an effective supervision. If we

are doing so, we can attain the maximum usability of the corresponding resources. Even

after the development, the organization need not invest more for the project .Therefore, the

system is economically feasible.

Page


43/105


METHODOLOGY ADOPTED

Pag


44/105


Structured system analysis technique had been adopted for the analysis of thealgorithm and software development.

Structured system design techniques had been adopted for the design of thealgorithm and software development.

Prototyping model for initial implementation had been used for early testing andmodule development.

Prototyping model had been used for the development of the Graphical UserInterface.

Incremental model had been used for the development of the software. Test plan was created to form the strategy of testing. This includes the decision of

testing techniques, decision of testing tools, and decision of milestones when the

testing will commence.

It is a well-recognized and acknowledged fact that there is a mismatch between the current

pattern of education and the components required by the industry. To overcome this

mismatch and to ensure that the students are able to secure employment and becomeresponsible citizens, training activities are initiated to cater to the needs of students of

different courses and streams. It is a well-recognized and acknowledged fact that there is a

mismatch between the current pattern of education and the components required by the

industry.

Pag


45/105


To overcome this mismatch and to ensure that the students are able to secure employment

and become responsible citizens, training activities are initiated to cater to the needs of

students of different courses and streams :

Class room lectures for imparting formal and theoretical knowledge. Group discussions. Self-learning techniques like public speaking through extempore, group activities,

presentations and icebreakers.

On-job training. One to one counselling.

The training methodology so adopted creates step by step environment for all round

development of skills and knowledge of the students.

Pag


46/105


SYSTEM DESIGN

Pag


47/105


INPUT DESIGN:

Input design is the process of converting user-oriented input to a computer based

format. Input design is a part of overall system design, which requires very careful attention.

Often the collection of input data is the most expensive part of the system. The main

objectives ofthe input design are:

Produce cost effective method of input Achieve highest possible level of accuracy Ensure that the input is acceptable to and understood by the staff.

INPUT DATA:

The goal of designing input data is to make entry easy, logical and free from errors as

possible. The entering data entry operators need to know the allocated space for each field;

field sequence and which must match with that in the source document. The format in which

the data fields are entered should be given in the input form. Here data entry is online; it

makes use of processor that accepts commands and data from the operator through a key

board. The input required is analyzed by the processor. It is then accepted or rejected. Input

stages include the following processes:

Data Recording Data Transcription Data Conversion Data Verification Data Control Data Transmission Data Correction

Pag


48/105


One of the aims of the system analyst must be to select data capture method and

devices, which reduce the number of stages so as to reduce both the changes of errors and the

cost .Input types, can be characterized as:

External Internal Operational Computerized Interactive

Input files can exist in document form before being input to the computer. Input design

is rather complex since it involves procedures for capturing data as well as inputting it to the

computer.

OUTPUT DESIGN:

Outputs from computer systems are required primarily to communicate the results of

processing to users. They are also used to provide a permanent copy of these results for latter

consultation. Computer output is the most important and direct source of information to the

users. Designing computer output should proceed in an organized well manner throughout.

The right output must be available for people who find the system easy to use. The outputs

have been defined during the logical design stage. If not, they should be defined at the

beginning of the output designing terms of types of output connect, format, response etc.

Pag


49/105


Various types of outputs are:

External outputs Internal outputs Operational outputs Interactive outputs Turn around outputs

All screens are informative and interactive in such a way that the user can fulfill his

requirements through asking queries.

DATABASE DESIGN:

The general theme behind a database is to handle information as an integrated whole.

A database is a collection of interrelated data stored with minimum redundancy to serve

many users quickly and effectively. After designing input and output, the analyst must

concentrate on database design or how data should be organized around user

requirements. The general objective is to make information access, easy, quick,

inexpensive and flexible for other users. During database design the following objectives

are concerned:

Controlled Redundancy Data independence Accuracy and integrity More information at low cost Recovery from failures Privacy and security Performance

Page


50/105


CODING METHODS

Pag


51/105


Event driven programming language JAVA has been used for coding the modules andprograms.

Structured English and pseudo-codes are used to refine the mechanisms using the facilityof defined objects.

Various stubs had been used to facilitate incremental coding followed by testing. The basic philosophy followed at this stage: Code one line followed by rigorous testing.

Stepwise refinement techniques had been used to code the modules.

Page


52/105


TESTING

Pag


53/105


Testing can be stated as the process of validating and verifying that a software

program/application/product:

meets the requirements that guided its design and development; works as expected; can be implemented with the same characteristics.

A primary purpose of testing is to detect software failures so that defects may be discovered

and corrected. Testing cannot establish that a product functions properly under all conditions

but can only establish that it does not function properly under specific conditions. The scope

of software testing often includes examination of code as well as execution of that code invarious environments and conditions as well as examining the aspects of code: does it do

what it is supposed to do and do what it needs to do. In the current culture of software

development, a testing organization may be separate from the development team. There are

various roles for testing team members. Information derived from software testing may be

used to correct the process by which software is developed.

The purpose of the system testing is to consider all the likely variations to which it will

be suggested and push the systems to limits.

There are two major types of testing, they are:

White Box Testing Black Box Testing

Pag


54/105


White Box Testing:

White box sometimes called Glass box testing is a test case design uses the control

structure of the procedural design to drive test case.

Using white box testing methods, the following tests where made on the system:a) All independent paths within a module have been exercised once. In our system, ensuring

that case was selected and executed checked all case structures. The bugs that were prevailing

in some part of the code where fixed.

b) All logical decisions were checked for the truth and falsity of the values.

Black box Testing:

Black box testing focuses on the functional requirements of the software. This is black

box testing enables the software engineering to derive a set of input conditions that will fully

exercise all functional requirements for a program. Black box testing is not an alternative to

white box testing rather it is complementary approach that is likely to uncover a different

class of errors that white box methods like :

Interface errors Performance in data structure Performance errors Initializing and termination errors

Pag


55/105


MAINTENANCE

Page


56/105


Software maintenance in software engineering is the modification of a software

product after delivery to correct faults, to improve performance or other attributes.

The key software maintenance issues are both managerial and technical. Key

management issues are: alignment with customer priorities, staffing, which organization does

maintenance, estimating costs. Key technical issues are: limited understanding, impact

analysis, testing, and maintainability measurement.

Maintenance activities are categorized into following four classes:

Adaptivedealing with changes and adapting in the software environment.

Perfective accommodating with new or changed user requirements which concern

functional enhancements to the software.

Correctivedealing with errors found and fixing it.

Preventiveconcerns activities aiming on increasing software maintainability and prevent

problems in the future.

An integral part of software is the maintenance one, which requires an accurate

maintenance plan to be prepared during the software development. It should specify how

users will request modifications or report problems. A new decision should be addressed for

the developing of every new system feature and its quality objectives .

This section describes the six software maintenance processes as:

The implementation process contains software preparation and transition activities,such as the conception and creation of the maintenance plan; the preparation for

handling problems identified during development; and the follow-up on product

configuration management.

The problem and modification analysis process, which is executed once theapplication has become the responsibility of the maintenance group. The

maintenance programmer must analyze each request, confirm it (by reproducing the

situation) and check its validity, investigate it and propose a solution, document the

request and the solution proposal, and finally, obtain all the required authorizations

to apply the modifications.

Pag
http://en.wikipedia.org/wiki/Change_impact_analysishttp://en.wikipedia.org/wiki/Change_impact_analysishttp://en.wikipedia.org/wiki/Change_impact_analysishttp://en.wikipedia.org/wiki/Change_impact_analysis


57/105


The process considering the implementation of the modification itself. The process acceptance of the modification, by confirming the modified work with

the individual who submitted the request in order to make sure the modification

provided a solution.

The migration process (platform migration, for example) is exceptional, and is notpart of daily maintenance tasks. If the software must be ported to another platform

without any change in functionality, this process will be used and a maintenance

project team is likely to be assigned to this task.

Finally, the last maintenance process, also an event which does not occur on a dailybasis, is the retirement of a piece of software.

Pag


58/105


MODULE DESCRIPTION

Page


59/105


This project mainly consists of following 6 modules:

User module Student Profile Module Marks management module Attendance module Assignment module Rating moduleThese modules altogether record data of students and provide access to

information whenever needed. Individually their functionalities are as follows:

User Module helps in making the system secure. It has login details ofadmin and users.

Student Profile Module includes: personal and professional details of

students.

Marks management module records the semester-wise marks of all thesubjects of the student.

Attendance Module is used to record attendance of the student forfuture reference.

Assignment Module is used to record the details of the total and

submitted assignments of the students.

Rating Module can give ratings for students as per the studentsperformance record present in above modules.

Operations like view, input, edit, delete are also applicable for these modules

individually.

Pag


60/105


LIST OF TABLES

Page


61/105


LOGIN:

FIELD TYPE SIZE

Username text

Password text

PERSONAL INFORMATION:

FIELD TYPE SIZE

Roll no. Mediumtext

Name Mediumtext

Fathers name Mediumtext

Mothers name Mediumtext

Phone Varchar 12

Sex Char 6

Date of birth Date

Caste Text

Religion Text

House no. Text

City Mediumtext

District Mediumtext

State Mediumtext

Pin Varchar 10

Joining year Varchar 4

Semester Varchar 1

Pag


62/105


HIGH SCHOOL DETAILS:

FIELD TYPE SIZE

Roll no. Mediumtext

From year Varchar 4

To year Varchar 4

University Mediumtext

Percentage Varchar 3

INTERMEDIATE DETAILS:

FIELD TYPE SIZE

Roll no. Mediumtext

From year Varchar 4

To year Varchar 4



GRADUATION DETAILS:

FIELD TYPE SIZE

Roll no. Mediumtext

From year Varchar 4

To year Varchar 4



Pag


63/105


POST GRADUATION DETAILS:

FIELD TYPE SIZE

Roll no. Mediumtext

From year Varchar 4

To year Varchar 4



OTHER QUALIFICATION DETAILS:

FIELD TYPE SIZE

Roll no. Mediumtext

From year Varchar 4

To year Varchar 4



EXPERIENCE:

FIELD TYPE SIZE

Roll no. mediumtext

From year Varchar 4

To year Varchar 4

Company mediumtext

Designation mediumtext

Pag


64/105


SEMESTER:

FIELD TYPE SIZE

Roll no. Mediumtext

Semester Varchar 1

MARKS OF SESSIONAL-1:

FIELD TYPE SIZE

Roll no. Mediumtext

Subject code Varchar 7

Sessional-1 total marks Varchar 3

Sessional-1 obtained marks Varchar 3


FIELD TYPE SIZE

Roll no. Mediumtext




Pag


65/105



FIELD TYPE SIZE

Roll no. Mediumtext




MARKS OF EXTERNAL:

FIELD TYPE SIZE

Roll no. mediumtext

Subject code varchar 7

External total marks varchar 3

External obtained marks varchar 3

ASSIGNMENT:

FIELD TYPE SIZE

Roll no. mediumtext


Total assignments varchar 2

Submitted assignments varchar 2

Pag


66/105


ATTENDANCE:

FIELD TYPE SIZE

Roll no. mediumtext


External total marks varchar 3

External obtained marks varchar 3

RATING:

FIELD TYPE SIZE

Roll no. mediumtext


Rating char 7

Pag


67/105


ER DIAGRAM

Pag


68/105


Teacher View/

Edit/

Delete

StudentHas

Attendance

Submit

Assignments

PersonalInformation

Has Has

Secured

Marks

Professional

Information

Post graduation

details

Other

qualification

10th

std.

details

12th

std.

details

Graduation

details

experience

gender

Father

name

Phone no.

Mother

name

Roll_no.

caste address

religion

name

Date of birth

Year of

joining

semester

city

district

House no.

statepin Pag


69/105


DATA FLOW DIAGRAM

Pag


70/105


Teacher

Student Record &

Information Process

Context Diagram

Teacher

Pag


71/105


Student Record and

Information process

Teacher

0 Level DFD

Database

Login

Pag


72/105


1.1 Student

Profile

1.2 Marks

1.3

Attendance

1.4 Assignment

1.5 Report

Teacher

1 Level DFD

Database

Pag


73/105


SCREENSHOTS of FORMS

Pag


74/105


Pag


75/105


Pag


76/105


Page


77/105


Page


78/105


Pag


79/105


Page


80/105


Page


81/105


Page


82/105


Page


83/105


Pag


84/105


Page


85/105


Page


86/105


Pag


87/105


Page


88/105


Page


89/105


Page


90/105


Page


91/105


Pag


92/105


Page


93/105


Page


94/105


Page


95/105


Page


96/105


Page


97/105


Pag


98/105


Page


99/105


Page


100/105


Page


101/105


Page


102/105


FUTURE SCOPE OF THE PROJECT

Page


103/105


This project can be further developed by adding other possible modules such as day-wise

academic calendar, teachers details, etc. It can be enhanced by linking it with library

management system, faculty management system. It can even be linked with affiliated

university for direct data entry. In future Student Module can be added to provide interactionwith students.

Besides these, we can even send alerts to students and their guardians regarding poor rating

and attendance of students. Along with studies it can even be extended for co-curricular

activities.

Page


104/105


REFERENCES

Pag


105/105


Database Programming with JDBC and Java by O'Reilly http://www.javaworld.com/javaworld/jw-01-1998/jw-01-bookreview.html http://www.jdbc-tutorial.com http://www.mysql.com http://www.roseindia.net Java and Software Design Concepts by APress

Documents

Student Record and Information System