STUDENT MANAGEMENT SYSTEM

Contents
1. Introduction ............................................................................................................................................. 1.1 1.2 1.3 1.4 1.5 2. 3. Purpose............................................................................................................................................ Intended Audience and Reading Suggestions ................................................................................. Product Scope ................................................................................................................................. Definitions, acronyms, and abbreviations ...................................................................................... References ......................................................................................................................................

System Overview .................................................................................................................................... Design Considerations ............................................................................................................................ 3.1 3.2 Assumptions and Dependencies...................................................................................................... General Constraints ......................................................................................................................... Testing ..................................................................................................................................... Performance Requirements .................................................................................................... Security Requirements ............................................................................................................

3.2.1 3.2.2 3.2.3 3.3 4.

Goals ...............................................................................................................................................

Development Methods ............................................................................................................................ 4.1 Microsoft SQL Server .....................................................................................................................

5. Diagrams 5.1 5.2 5.3 5.3 ER-DIAGRAM ................................................................................................................................... DFD -DIAGRAM SEQUENCE DIAGRAM.. SCREEN SHOTS ................................................................................................................................

1. Introduction
1.1 Purpose
This SDS describes the various functions of our project. The actual design of the various modules and components of Student Management System is described in this document which takes care of various functionalities that our project aims to achieve and for determining the operating characteristics of the system. .

1.2 Intended Audience and Reading Suggestions

This SDS document is intended for any developers, project manager or documentation writer that needs to understand the basic system architecture and its specifications for development. Developer: The developer who wants to read, change, modify or add new requirements into the existing program, must firstly consult this document and update the requirements with appropriate manner so as to not destroy the actual meaning of them and pass the information correctly to the next phases of the development process. Tester: The tester needs this document to validate that the initial requirements of this web portal actually corresponds to the executable code correctly.

For each one of the reader types to better understand this document, here is a suggestion to read in this document: Overall description System Features External Interface Requirement Non Functional Requirement

1.3 Product Scope

Student Management System (SMS) is a Software application for students, faculty, academic staff and parents who want to get and retrieve students whole information instantly. The major benefit of this software is to store the students information at one place and it can be accessed by java The SMS Software is to replace the old and traditional file(paper work) storing process. Instead of tedious paper work, students will be able to submit required information electronically, and the departments will be able to evaluate the submissions with a much quicker turnaround.

1.4 Definitions, acronyms, and abbreviations

SMS: Student Management System CLIENT: Refers to the user of SMS. SQL: Structured Query Language; used to retrieve information from a database. SQL Server: A server used to store data in an organized format. BOOLEAN: A true/false notation UNIQUE KEY: Used to differentiate entries in a database. LAYER: Represents a section of the project. DATA STORAGE LAYER: the section of the assignment referring to where all data is recorded.

1.5 References
Books:S.No. 1

Title JAVA Complete reference

Author Herbert Shield

Edition Fourth Edition

J2EE Complete reference

Database Management System

Stephanie Bodoff Debbie Bode Carson Ian Evans Korth

Third Edition

Second Edition

Software Engineering

Roger Pressman

Sixth Edition

Figure 1.1 Reference Table Websites:

www.java.sun.com www.javagroupsvc.com

2. System Overview
Student Management System (SMS) is a software application that tracks current students academic information. It maintains academic information for ready access by office staff, students, their faculty advisors, and committee members. Instead of tedious paper work, students will be able to submit required information electronically, and the departments will be able to evaluate the submissions with a much quicker turnaround. The Student Management System has been modularized into following modules. LOGIN MODULE The purpose of this module is to provide entry to the system . Based on the type of login, the user is provided with various facilities and functionalities. The main function of this module is to allow the user to use SMS. This module provides two types of login Admin login and Student login. ADMINISTRATOR MODULE In this module when the administrator will enter his/her user name and password, then he/she will enter in to the administrator page and this page consists of two following sub modules. Student Addition/ Updation / Deletion: In SMS each Student is added, updated or deleted according to its branch. Notice/Attendance/Result Generation: In SMS information about notice, attendance and Internal result is generated. Fee Detail and Schedules: Fee information detail and schedule detail are managed.

STUDENT MODULE In this module when a user enters his student id and password, then he can visit all the following pages.

Profile View: When the student clicks on this link he/she will get his/her information like student id, student name, password, father name, date of birth, nationality, city, address, country, phone number, mobile number, email. If he/she wants then he/she can change the profile.

Notice View: When the student clicks on this link, he can see latest notices released by the administrator. Attendance View: When the student clicks on this one, the student can get his overall attendance percentage (present and absent). Internal Results View: When the student clicks on this, he/she will get the internals result in all the subjects. How much grade point he/she secure out of 20 he/she can know. Time Table View: When the student clicks on this link then he/she get all the information that on which day which room which class will be held at which time. Fee Detail View: When the student clicks this link he/she can get all the fees structure semester wise and annual fee. The Student Helpdesk: This helpdesk is staffed by faculty who are there to help you. You may contact on (faculty phone no.).

3. Design Considerations
The design consideration section shows the overall description of all technical aspects which are related to this project including hardware and software.

3.1 Assumptions and Dependencies

Although basic password authentication and role based security mechanisms will be used to protect SMS from unauthorized access; functionality such as inserting, deleting and updating are assumed to be sufficiently protected under the existing security policies applied by the SMS developing team. It describes assumptions or dependencies regarding the software and its use. These may concern such issues as: Related software:
o o o

Microsoft SQL Server 2005 to store the database. JAVA 1.6, JSP, SERVLET, HTML to develop the product. Virtual Server Apache Tomcat 6.0.18 and upward .

Related hardware:
o o o

Microprocessor Ram Hard Disk

: Pentium-4 class processor, 2.2 GHz : 1 GB of RAM : 10 gigabytes (GB) on installation drive,

Operating systems:
o

We use Windows Vista 32 bit Operating System for developing this system.

End-user characteristics
o o o

Every user must have basic knowledge of English. He should be able to work with computer. All users must have his/her unique login name and password for join web portal.

The user should know the details (meaning) of the operation.

3.2 General Constraints

3.2.1 Testing Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation. Once source code has been generated, software must be tested to uncover as many errors as possible before delivery to the customer. Our goal is to design a series of test cases that have a high likelihood of finding errors. Thats where software testing techniques come into the picture. These techniques provide systematic guidance for designing tests that exercise the internal logic of software components and exercise the input and output domains of the program to uncover errors in program function, behavior and performance.

TESTING OBJECTIVES A number of rules that can serve as testing objectives are: Testing is a process of executing a program with the intent of finding an error. A good test case is one that a high probability of finding an as-yet-undiscovered error. A successful test is one that uncovers an as-yet-undiscovered error.

TESTING TECHNIQUES White Box Testing It is also called Glass Box Testing. It is a test case design method that uses control structure of the procedural design to derive test cases. Using White Box Testing methods, the software engineer can derive test cases that Guarantee that all independent paths have been exercised at least once. Exercised all routes at their boundaries and within their operational bounds. Exercised all logical decision on their true and false sides. Exercised internal data structure to assure their validity.

Black Box Testing

Black Box 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 Testing is not an alternative to White Box Testing. Rather, it is a complementary that is likely to uncover a different class of errors than White Box Testing. Black Box Testing attempts to find errors on the following categories In-correct or missing functions. Interface errors. Errors in data structures or external database access. Performance errors. Initialization and termination errors.

3.2.2 Performance Requirements Checking the fact that the system must perform as what every user expects .So in every action-response of the system, there are no immediate delays. In case of opening web forms, of popping error messages and saving the settings or sessions there is delay much below 2 seconds, In case of opening databases, sorting questions and computing there are no delays and the operation is performed in less than 2 seconds for opening, sorting, computing > 95% of the files. Also when connecting to the server the delay is based on the distance of the 2 systems and the configuration between them so there is high probability that there will be or not a successful connection in less than 20 seconds.

3.2.3 Security Requirements This program uses object oriented mechanisms to protect its data passed using methods also there is no currently a security schema of this program. Thus the log files that are being created are readable using a simple text reader.

3.3 Goals
Quick and full information retrieval Time saving process High security level of data Multiuser environment Global access of data No repetition of data

4. Development Methods
The following methods and approaches are used to develop this project.

4.1 Microsoft SQL Server

A database management, or DBMS, gives the user access to their data and helps them transform the data into information. These systems allow users to create, update and extract information from their database. A database is a structured collection of data. Data refers to the characteristics of people, things and events. SQL Server stores each data item in its own fields. In SQL Server, the fields relating to a particular person, thing or event are bundled together to form a single complete unit

of data, called a record (it can also be referred to as raw or an occurrence). Each record is made up of a number of fields. No two fields in a record can have the same field name.

SQL Server Tables SQL Server stores records relating to each other in a table. Different tables are created for the various groups of information. Related tables are grouped together to form a database.

Primary Key Every table in SQL Server has a field or a combination of fields that uniquely identifies each record in the table. The Unique identifier is called the Primary Key, or simply the Key. The primary key provides the means to distinguish one record from all other in a table. It allows the user and the database system to identify, locate and refer to one particular record in the database.

Foreign Key When a field is one table matches the primary key of another field is referred to as a foreign key. A foreign key is a field or a group of fields in one table whose values match those of the primary key of another table.

Referential Integrity Not only does SQL Server allow you to link multiple tables, it also maintains consistency between them. Ensuring that the data among related tables is correctly matched is referred to as maintaining referential integrity.

Relational Database Sometimes all the information of interest to a business operation can be stored in one table. SQL Server makes it very easy to link the data in multiple tables. Matching an employee to the department in which they work is one example. This is what makes SQL Server a relational database management system, or RDBMS. It stores data in two or more tables and enables you to define relationships between the table and enables you to define relationships between the tables. Data Abstraction A major purpose of a database system is to provide users with an abstract view of the data. This system hides certain details of how the data is stored and maintained. Data abstraction is divided into three levels.

o o

Physical level: This is the lowest level of abstraction at which one describes how the data are actually stored. Conceptual Level: At this level of database abstraction all the attributed and what data are actually stored is described and entries and relationship among them. View level: This is the highest level of abstraction at which one describes only part of the database.

Advantages of RDBMS Redundancy can be avoided Inconsistency can be eliminated Data can be Shared Standards can be enforced Security restrictions ca be applied Integrity can be maintained Conflicting requirements can be balanced Data independence can be achieved.

Disadvantages of RDBMS A significant disadvantage of the RDBMS system is cost. In addition to the cost of purchasing of developing the software, the hardware has to be upgraded to allow for the extensive programs and the workspace required for their execution and storage. While centralization reduces duplication, the lack of duplication requires that the database be adequately backed up so that in case of failure the data can be recovered.

4.2 JAVA 1.6

The most important characteristic of Java is that it was designed from the outset to be machine independent. We can run Java programs unchanged on any machine and operating system combination that supports Java. Java programs are intrinsically more portable than programs written in other languages. An application written in Java will only require a single set of source code statements, regardless of the number of different computer platforms on which it is run, so it is very useful for internet application. Platform independence - Java programs can be run on many platforms without modification. This portability is assured by using a Virtual machine1. When a Java program is compiled bytecode is created rather than a standard executable file. Effectively, this is machine code for a virtual machine, which is then interpreted by the Java interpreter. The byte-code can be run on any platform which has a suitable interpreter.

Security - since Java has always been designed with distributed applications in mind, security has been incorporated right from the start, and if anything this has been seen to be too restrictive.

Java and the JDK The Java Development Kit contains all the necessary tools for the development of Java applications and applets, including a compiler, interpreter, class libraries, applet viewer and debugger. The current version of the JDK, 1.4.2, is freely available from Sun's web she- for machines running Windows 95, Windows NT, Solaris SPARC and Solaris x86, and a version for the Macintosh is expected later this year (version 1,0 is currently available). Ports to other machines may also be available from other sources. It should be noted that browsers may not yet support applets created using features in the latest JDK.

Characteristics of Java Simple Secure Portable Object-oriented Robust Multithreaded Architecture-neutral Interpreted High performance Distributed Dynamic

J2EE
The Java-2 Enterprise Edition (J2EE) provides a component-based approach to the design, development, assembly, and deployment of enterprise applications. The J2EE platform offers a multitiered distributed application model, reusable components, a unified security model, flexible transaction control, and web services support through integrated data interchange on Extensible Markup Language (XML)-based open standards and protocols. Components of J2EE SERVLET Java servlets are small, platform-independent Java programs that can be used to extend the functionality of a Web server in a variety of ways. Servlets are to the server what applets are to the clientsmall Java programs compiled to bytecode that can be

loaded dynamically and that extend the capabilities of the host. It is a server side programming language. JSP Java Server Pages is the extension of servlet to simplify the programming and coding of servlet. It includes HTML tags to make coding easy. Ultimately it convert into the servlet at the time of calling.

HTML Without HTML, the World Wide Web wouldnt exist. HTML allow the individual elements on the Web to be brought together and assented as a collection. Text, images, multimedia, and other files can be packed together using HTML. This section explains the basic principles behind the interaction between HTML.

4.3 ER-DIAGRAM

Figure: 5.1 E-R Diagram

4.4 USER INTERFACES

LOGIN SCREEN

Figure: 5.2 Login Screen

Description:
a. Enter user ID in Caps for student/Admin/Staff login (eg. 09MCA11/Admin/Staff) .

b. Enter password provided by admin for students login and for staff or admins login.

DFD DIAGRAM

SEQUENCE DIAGRAM

HOME PAGE

Figure: 5.3 Home Page

Description: This is the home page of Student Management System.

ADD RECORD

Figure: 5.4 add record screen

Description: After login student or administrator can fill their infornation.

DELETE RECORD

Figure: 5.5 delete record

Description: If anyone want to delete any record, then it canbe delete just by roll no.

SEARCH RECORD

Figure: 5.6 search record Screen

Description: If anyone want to search any information of the student then serch form is required.

DESIGN VIEW

Figure: 5.7 DESIGN VIEW SCREEN

DATABASE VIEW

Figure: 5.8 DATABASE VIEW SCREEN

CONCLUSION
To sum up, developing a computer based information for any college was a matter of essence. It will be the medium for the college management system for the proper management of the students information in an organised way. It is now essence for the organisation to transmit the students records on the system, without crawling any departments.