Documentation

STUDENT ACADS MANAGEMAENT DRIVE
1. INTRODUCTION
The main purpose of STUDENT ACADS MANAGEMENT DRIVE is to
computerize the existing manual system which eliminates demerits in manual system. It
gives the up-to-date records of marks and attendance of a particular student. The whole
system should be computerized inorder to make the system flexible and efficient.The
application can be used in efficient recruitment in public and private sectors. The scope of
the project is limited.
The main objective of this is to computerize the existing manual system for
efficient and transparent use. Also the retrieval of information by the end user is to be
made easy and flexible. This is done by the use of efficient forms.
1.1 EXISTING SYSTEM:

STUDENT ACADS MANAGEMENT DRIVE includes student marks and
attendance. The existing system is maintaining these records manually. The maintenance
of these details manually is a typical task. In the existing manual system, the maintenance
of daily, monthly and yearly information take many more man hours. The chances for
fraud in manual system are high comparative to computerization.
DISADVANTAGES:
1. Overhead in maintaining huge amounts of data.
2. Making reports is very difficult.
3. Problem arises if some file lost.
4. Chances of occurrence of error.
1.2 PROPOSED SYSTEM:

1
The proposed system is computerizing the existing manual system, to avoid the
conflicts in the manual system. It gives the up-to-date records of student marks .The
whole system should be computerized in order to make the system flexible and efficient.
By this proposed system, we can reduce the time complexity spent for editing and
viewing of their details.
ADVANTAGES:
SPEED: The high speed of computer operation will reduce the delays in the
manual system considerably.
FLEXIBILITY: The modifications are possible and are very easy comparable to
manual system.
ACCURACY: The accuracy is maintained and perfect calculations can be

performed.
REPORTING: Reporting different operations is easy and attractive.
SECURITY: By providing protection mechanism such as password, super

user can only have the entire permission, others can be given read only
permission. Thus the security of system is maintained.
SECRECY: By making different authorization checks on the access of data,

secrecy can be maintained.
2. REQUIREMENT SPECIFICATION
2.1 HARDWARE AND SOFTWARE REQUIREMENTS:
2.1.1 .SOFTWARE REQUIREMENTS:

Software specifications are used designing the systems and to manage the time
complexity. New tools and techniques are announced in quick succession. This has forced
the software engineers and industry to continuously look for new approaches to software
design and development. For this project we use the software requirements are as
follows:
1. WINDOWS Operating system
2. J2EE5.0 or higher
3. SERVLETS, JDBC
4. HTML for front-end
5. ORACLE10g for back-end
6. JDBC for connecting front-end and back-end
2.1.2 HARDWARE REQUIREMENTS:

The hardware specifications are used providing the efficiency and responsiveness.
By using these we can install the instructions and certificate of
authenticity.
4
A network of computer each with configurations of
Client:
Processor
: Pentium Processor
RAM
: 1 GB (Min)
Hard Disk
: 80GB (Min)
Server:
Processor
: Pentium Processor
RAM
: 3 GB (Min)
Hard Disk
: 160GB (Min)
2.1.2 Software Specifications:

Front End
: SERVLETS
Back End
: ORACLE 10g
Web Server
: Apache tomcat
2.1.3 Working Platform

Operating System
: WINDOWS XP
2.2 SOFTWARE REQUIREMENTS SPECIFICATION:

Vision:
For students of a department who would like to get the information about their
academics (such as marks attendance) and also to interact with the Faculty ,the Students
5
Acads Management Drive is a web application that provides the students the effective
way to get the required information.
For the corresponding faculty who would like to know the views posted by
various students the Students Acads Management Drive is a web application that
provides the better way to interact with the students.
For the administrator who is responsible for granting permissions to various users
of the system and to maintain the database ,the Students Acads Management Drive is a
web application that provides elegant GUI based forms.
Glossary:
Student
A person who is studying in the particular Department of a College or

University who uses this Application to view the marks or attendance
or to interact with the faculty or his friends through mail.
Staff
A Lecturer who is teaching in the particular Department of a college

or University who uses this Application to interact with the students
through mail.
Administrato The person who maintains this Application

r
User
Student, staff and administrator i.e., who are using the system
Scope:
The student/staff of a particular department of a College or University can
make use of this system. The Administrator creates accounts i.e., registers each and every
user both students and staff and issues passwords to them. The Administrator is the only
person who manages user accounts and updates the marks and attendance of each and
every student in that department.
The user (student/staff) can log into the system using his user id and password
and can view the requested details such as marks and attendance. The user can also
interact with the other users through mailing.
6
The system requires a mechanism to authenticate the student, staff and the
Administrator.
Exclusions:
Student/Faculty can register themselves.

Student/Faculty can update their marks.
Administrator can send mails
Assumptions:
The Admin should create accounts for the students and faculty using the
registration form.
The user should use only his id as his as user id.
The user can login into his account only after his registration is confirmed.
Updation of marks and attendance can be done only by administrator.
System Functions:
Sino. System Function
Description
Marks module
S1.10
Authenticate the user (Administrator/student)
S1.20
View marks
S1.30
Update marks
Attendance module
S2.10
Authenticate the user (Administrator/student)
S2.20
View attendance
S2.30
Update attendance
Mailing module
7
S3.10
Authenticate user (student/staff)
S3.20
Send mail
S3.30
Receive mail
Registration module
10
S4.10
Authenticate user (Administrator)
11
S4.20
Register the user(student/staff)
Detailed Software Requirements:

Use case model
Actor Name
Student
Actor Id
ACT-01
Description
A person who is studying in the particular department of a

college/university.
Main
Activities
It can be a person studying in the particular department of a

college/university, who uses the system to know the academic
information and to interact with other student/staff.
Frequency of
Use
High
Work
Environment
Browser
Number of
Users
Any number
Actor Name
Staff
Actor Id
ACT-02
Description
Employees of the department of a college/university.
Main Activities
It can be an employee, who uses the system to interact with the

students.
Frequency of Use High

Work
Environment
Browser
Number of Users
Any number
Actor Name
Administrator
Actor Id
ACT-03
Description
Handles all admin related tasks throughout the application
Main Activities
Uses the system to setup initial data, define access control etc.
Frequency of Use
Medium
Work Environment Browser

Number of Users
List of use cases:
View marks
View attendance
Send mail
Receive mail
Update marks
Update attendance
Registration
Use Case Diagram for a Student/Staff:
View Marks
View Attendance
Student
Faculty
Send Mail
Recieve Mail
Fig:2.1 Use Case Diagram for a student/staff
Use Case Diagram for Administrator:
10
Update Marks
Administrator
Update Attendance
Registration
Fig:2.2 Use Case Diagram for a Administrator
Use Case Descriptions
11
Use Case Name UC1

Use Case ID
View Marks
Use Case Name UC2
Actor(s)
Student
Use Case ID
View Attendance
Goal
Provides marks information for the students
Actor(s)
Student
Summary
The purpose of this use case is providing information for the students
Goal
Provides attendance information for the students
about their marks
Summary
The purpose of this use case is providing information for the students
Preconditions None
about their attendance
Main Flow
1. The user enters the use 1.1 System displays the screen for the user
Preconditions None
case.
to select the year and the semester for
Main Flow
1. The user enters the use 1.1 System displays the screen for the user
which he is interested to know the details.
case.
to select the year,semester and the month
for which he is interested to know the
2.1 Marks are displayed
details.
2.The student selects the
2.2 User is returned to main flow

2.1 Attendance is displayed
required year and the

2.The student selects the
semester
required year ,semester
Post Conditions None
and month
Cross
S1.10,S1.20
Post Conditions None
Reference
Cross
S2.10,S2.20
Assumptions Students can view only their marks profile (with proper password).
Reference
Business Rules A user should log in into his account to view his marks profile.
Assumptions Students can view their attendance (with proper password).
System
Student
System
Business Rules A user should
log in into his account to view
his attendance
Sequence
System
Student
System
Request for marks
diagram
Sequence
diagram
Marks List
Displayed
Request
for Attendance
Attendance List Displayed
12
13
Use Case Name
UC3
Use Case ID
Update Marks
Actor(s)
Admin
Goal
To update marks of the students
Summary
The purpose of this use case is to update the marks of the students
Preconditions
Form is displayed
Main Flow
1. The user enters the
1.1 System displays the screen for the user
use case.
to enter the marks.
2.1 Marks are updated in the database
2.The user enters the

marks
Post Conditions
Marks are updated in the database
Cross Reference
S1.10,S1.30
Assumptions
Updating of marks can be done only by the Administrator.
Business Rules
The Administrator should verify whether the student is registered or

not.
System Sequence
Adminstrator
diagram
System
Request for Marks Updation

Form Displayed
Fills the data
Database Updated
Use Case Name
UC4
Use Case ID
Update Attendance
Actor(s)
Admin
Goal
To update attendance of the students
Summary
The purpose of this use case is to update the attendance of the

students
Preconditions
Form is displayed
Main Flow
1. The user enters the

use case.
marks
1.1 System displays the screen for the user

to enter the attendance.
14
2.1 Attendance is updated in the database
Use Case Name
UC5
Use Case ID
Send Mail
Actor(s)
Student/staff
Goal
To send mails to the desired user
Summary
The purpose of this use case is to send mails to the student/staff
Preconditions
Show the form
Main Flow
1. The user enters the use
1.1 System displays the screen for the
case.
user to send mail to the desired user.

2.1 The mail is sent to the desired
2. The user enters the details
recipient.
and then sends.

Post Conditions Database is updated and mail is send to the recipient.
Cross Reference S3.10, S3.20
Assumptions
1 The user should use only his id as his as user id.

2. The user should fill all the fields of the form displayed for sending
the mail.
Business Rules
1. Should verify his category (student/staff).
System Sequence
Student/Faculty
diagram
System
Request to Send Mail

Form Displayed
Use Case Name UC6

Use Case ID
Receive mail
Actor(s)
Student/staff
15
Goal
To receive the mails
Summary
The purpose of this use case is to receive the mails sent by staff/student
Preconditions
none
Main Flow
1.1 System displays the received mails.
case.
The following options are given to the

user.
s1. To view the received mails.
s2. To delete the selected mails.
2.1 The selected option(sub flow) is
2.The user selects one of the executed

options s1 or s2
Sub Flows
S1: View mails
1. User selects S1.
1.1 System displays the screen for

the user to view the mails
2. User selects the mail 2.1 The system displays the content
to be viewed.
of the selected mail.

2.2 The user is returned to the main
flow.
S2: Delete mails.

1. User selects S2.
1.1 System displays the user to

select/deselect the mails to be
deleted
16
2. User selects the mails 2.1 The selected mails are deleted
to be deleted and then
by the system.
submits.
2.2 The user is returned to the
main flow.
Post
none
Conditions
Cross
S3.10, S3.30
Reference
Assumptions
The user should use only his id as his as user id.
Business Rules Should verify his category (student/staff).

System
Sequence
diagram
Student/Faculty
System
Request for Recieved Mails

Mails Displayed
17
Use Case Name
UC7
Use Case ID
Registration
Actor(s)
Administrator
Goal
To issue passwords to student/staff(i.e., to register)
Summary
The purpose of this use case is to issue passwords to student/staff
Preconditions
Form is displayed
Main Flow
1.1 System displays the screen for the
case.
user to enter the registration details.

2.1Registration is completed

details and then submits
Post Conditions Database is updated

Cross Reference S4.10,S4.20
Assumptions
Only the Administrator can issue passwords to the users.
Business Rules
Administrator is authenticated.
System Sequence
Administrator
System
diagram
1: request for registration
2: registration is provided
FUNCTIONAL REQUIREMENTS:
18
System must be provided complete access to the administrator.
Administrator must be able to register a user if he is not registered yet.
System must provide a facility to add marks, attendance details of Student by the
Administrator.
System must allow a user to view the student marks.
System must allow a user to send the mails.
System must allow a user to view the mails.
Business Rules / Validations
A user should be added by the administrator.

A user should log in into his account to view his marks and attendance.
A user should log in into his account to send a mail.
System should verify user category & should authenticate the user.
Security Requirements
User Management and Authentication:
The application must be accessed by valid user.
The Updating of all the details are done by the Administrator.
The roll number should be the identification for the user.
The user id should be the same as the roll number of the user
Non-functional requirements
The application should support interruptions for regular web browsers tasks i.e.
work any web application Mozilla or Internet explorer (Supportability)
The form should load within 2 seconds. (Performance)
19
Flexible service based architecture will be highly desirable for future extension
(Supportability)
The system should be available 24 X 7. (Reliability/ availability)
2.3 EXTERNAL INTERFACE REQUIREMENTS:

This is a window based application, through this we can design a system that
requires knowledge and effort. And there by reducing the risk involved to a great extent,
with the help of the specialized window like dialog-box. The user is wanted highlighted if
he is at fault with appropriate message.
2.4 PERFORMANCE REQUIREMENTS:

The system should provide feedback to the user in a short period of time. This
system should be available to the user maximum time. This system should provide help
for the user to navigate through the system efficiently.
The system should be well protected from unauthorized access. For this, user can
enter or utilize the system by authentication himself through password. The system
should be protected from external threats and intrusions by keeping the system in such a
place where only authorized user can gain entry.
The system should consume resources in conservative manner. The system
should respond to the user quickly there by saving time.
20
Domain Class Model

Student
rollno
name
password
+1*
+1*
viewMarks()
viewAttendance()
sendMail()
viewMail()
Staff
name
id
password
sendMail()
viewMail()
+1*
+1*
+1
+1
Administrator
name
password
updateMarks()
updateAttendance()
Registration()
Fig2.4: Class Diagram
21
3. SYSTEM DESIGN
3.1 Data Dictionary
3.1.1 login table :

Column name
USERNAME
PASSWORD
Data type
Size
VARCHAR
10
VARCHAR
50
Nulls (y/n)
N
N
Constraints
Primary key
-------
Nulls (y/n)
N
N
Y
Constraints
Primary key
--------------
Nulls (y/n)
N
N
N
Constraints
Primary key
--------------
3.1.2 Student Registration table:

Column name
USERNAME
PASSWORD
NAME
Data type
Size
VARCHAR
10
VARCHAR
50
VARCHAR
30
3.1.3 Subject details table:

Column name
SUBID
SEMID
SUBNAME
Data type
Size
VARCHAR
50
VARCHAR
2
VARCHAR
30
22
3.1.4 Marks details of internal1 and online1:

Column name
REGNO
Data type
Size
VARCHAR
50
Nulls (y/n)
N
Constraints
Primary key,
Foreignkey(USERNAME(studen
SEMID
SUBNAME
INT1
ON1
VARCHAR
VARCHAR
VARCHAR
VARCHAR
2
30
20
30
N
N
N
N
t registration table))
--------------------------
3.1.5 Marks details of internal2 and online2:

Column name
REGNO
Data type
Size
VARCHAR
50
Nulls (y/n)
N
Constraints
Primary key,
SEMID
SUBNAME
INT2
ON2
VARCHAR
VARCHAR
VARCHAR
VARCHAR
2
30
20
30
N
N
N
N
3.1.6 Marks details of externals:

23
--------------------------
Column name
REGNO
Data type
Size
VARCHAR
50
Nulls (y/n)
N
Constraints
Primary key,
SEMID
SUBNAME
EXT
VARCHAR
VARCHAR
VARCHAR
2
30
20
N
N
N
--------------------
3.1.7Attendance details:
Column name
REGNO
Data type
Size
VARCHAR
50
Nulls (y/n)
N
Constraints
Primary key,
SEMID
SUBNAME
CC(classes
VARCHAR
VARCHAR
VARCHAR
2
30
20
N
N
N
conducted)
CA(classes
VARCHAR
20
attended)
-------------------------
3.1.8 Mailing Table:

Column name Data type
Size
MAILID
VARCHAR
50
MAILFROM
VARCHAR
20
Nulls (y/n)
N
N
Constraints
Primary key
Primary key ,
24
MAILTO
VARCHAR
30
Primary key ,
SUBJECT
CC
BCC
MAIL
VARCHAR
VARCHAR
VARCHAR
VARCHAR
50
20
20
10
N
Y
Y
N
EXCHANGE
FOLDER
MAILDATE
STATUS
VARCHAR
VARCHAR
VARCHAR
20
10
10
N
N
N
------------------------------------------
3.2 LOGICAL DATABASE DESIGN

3.2.1 Normalization
Database normalization is a design technique by which relational database tables
are structured in such a way as to make them invulnerable to certain types of logical
inconsistencies and anomalies. Tables can be normalized to varying degrees: relational
database theory defines "normal forms" of successively higher degrees of stringency, so,
for example, a table in third normal form is less open to logical inconsistencies and
25
anomalies than a table that is only in second normal form. Although the normal forms are
often defined (informally) in terms of the characteristics of tables, rigorous definitions of
the normal forms are concerned with the characteristics of mathematical constructs
known as relations. Whenever information is represented relationallythat is, roughly
speaking, as values within rows beneath fixed column headingsit makes sense to ask to
what extent the representation is normalized.
3.2.2 Normal Forms:

The normal forms (abbrev. NF) of relational database theory provide criteria for
determining a table's degree of vulnerability to logical inconsistencies and anomalies. The
higher the normal form applicable to a table, the less vulnerable it is to such
inconsistencies and anomalies. Each table has a "highest normal form" (HNF): by
definition, a table always meets the requirements of its HNF and of all normal forms
lower than its HNF; also by definition, a table fails to meet the requirements of any
normal form higher than its HNF.
The normal forms are applicable to individual tables; to say that an entire database
is in normal form n is to say that all of its tables are in normal form n.
Newcomers to database design sometimes suppose that normalization proceeds in
an iterative fashion, i.e. a 1NF design are first normalized to 2NF, then to 3NF, and so on.
This is not an accurate description of how normalization typically works. A sensibly
designed table is likely to be in 3NF on the first attempt; furthermore, if it is 3NF, it is
overwhelmingly likely to have an HNF of 5NF. Achieving the "higher" normal forms
(above 3NF) does not usually require an extra expenditure of effort on the part of the
designer, because 3NF tables usually need no modification to meet the requirements of
these higher normal forms.
Edgar F. Codd originally defined the first three normal forms (1NF, 2NF, and 3NF).
These normal forms have been summarized as requiring that all non-key attributes be
dependent on "the key, the whole key and nothing but the key". The fourth and fifth
normal forms (4NF and 5NF) deal specifically with the representation of many-to-many
26
and one-to-many relationships among attributes. Sixth normal form (6NF) incorporates
considerations relevant to temporal databases.
First normal form

The criteria for first normal form (1NF) are:
A table must be guaranteed not to have any duplicate records; therefore it must
have at least one candidate key.
There
must be no repeating groups, i.e. no attributes which occur a different
number of times on different records. For example, suppose that an employee

can have multiple skills: a possible representation of employees' skills is
{Employee ID, Skill1, Skill2, Skill3 ...}, where {Employee ID} is the unique
identifier for a record. This representation would not be in 1NF.
Note that all relations are in 1NF. The question of whether a given representation
is in 1NF is equivalent to the question of whether it is a relation.
Second normal form

The criteria for second normal form (2NF) are:
The table must be in 1NF.

None of the non-prime attributes of the table are functionally dependent on a part
(proper subset) of a candidate key; in other words, all functional dependencies of
non-prime attributes on candidate keys are full functional dependencies. For
example, consider a "Department Members" table whose attributes are
Department ID, Employee ID, and Employee Date of Birth; and suppose that an
employee works in one or more departments. The combination of Department ID
and Employee ID uniquely identifies records within the table. Given that
Employee Date of Birth depends on only one of those attributes namely,
Employee ID the table is not in 2NF.
27
Note
that if none of a 1NF table's candidate keys are composite i.e. every
candidate key consists of just one attribute then we can say immediately that
the table is in 2NF.
Third normal form

The criteria for third normal form (3NF) are:
The table must be in 2NF.
There are no non-trivial functional dependencies between non-prime attributes. A

violation of 3NF would mean that at least one non-prime attribute is only
indirectly dependent (transitively dependent) on a candidate key, by virtue of
being functionally dependent on another non-prime attribute. For example,
consider a "Departments" table whose attributes are Department ID, Department
Name, Manager ID, and Manager Hire Date; and suppose that each manager can
manage one or more departments. {Department ID} is a candidate key. Although
Manager Hire Date is functionally dependent on {Department ID}, it is also
functionally dependent on the non-prime attribute Manager ID. This means the
table is not in 3NF.
3.3 UML DIAGRAMS

3.3.1 Use case Diagram
Use case diagrams are created to visualize the relationships between actors
and use cases. A use case is a pattern of behavior the system exhibits. Each use
case is a sequence of related transactions performed by an actor and the
system. Diagrammatically actor and usecase are represented by
28
View Marks
View Attendance
Faculty
Student
Send Mail
Recieve Mail
Fig3.1: Use Case Diagram for a student/staff
Update Marks
Update Attendance
Administrator
Registration
Fig3.2: Use Case Diagram for a Administrator
3.3.2 Class Diagram

A Class diagram gives an overview of a system by showing its classes and
the relationships among them. UML class is a rectangle divided into: class name,
attributes, and operations.
29
Our class diagram has three kinds of relationships.
Association -- a relationship between instances of the two classes. There is an

association between two classes if an instance of one class must know about the
other in order to perform its work
Aggregation
-- an association in which one class belongs to a collection.
An aggregation has a diamond end pointing to the part containing the whole. In
our diagram, Order has a collection of Order Details.
Generalization -- an inheritance link indicating one class is a super class of the

other
Dependency--properties of one class depend on properties of another class
30
Student
rollno
name
password
+1*
+1*
viewMarks()
viewAttendance()
sendMail()
viewMail()
Staff
name
id
password
sendMail()
viewMail()
+1*
+1*
+1
+1
Administrator
name
password
updateMarks()
updateAttendance()
Registration()
Fig3.2.1: Class Diagram

`
4. SYSTEM IMPLEMENTATION
4.1 SELECTED SOFTWARE

This is web-based software, which contains many pages and hyper links. It
handles effectively all the functions. You can switch from one page to another by clicking
the hyper links. The user interface is created with Java Servlets. So even a layman can
operate it easily.
4.1.1 JAVA (FRONT END)

JAVA was conceived by James Gosling, Patrick Naughton, Chris Warth , Ed
Frankland and Mike Sheridan at Sun Microsystems. The primary motivation was the need
for plot from neutral language.
31
4.1.1.1 FEATURES OF JAVA:
Compiled and Interpreted
Platform Independent and Portability
Object Oriented
Robust and Secure
Distributed
Multithreading and Interactive
High Performance
Dynamic and Extensible
4.1.1.2 JAVA SERVLETS:

Servlets are small programs that execute on server side of a web connection.
Servlets dynamically extend the functionality of a web server.
Servlets are the front-line in JAVA web application development. They provide
an easy way for our server side code to communicate with web-based clients.
4.1.1.3 LIFE-CYCLE OF JAVA SERVLET:
Three methods are central to the life cycle of a servlet these are init ( ),
service(),destroy ().
The servlet container creates an instance of the servlet.
The container calls the instance init( ) method.

32
If the container has a request for the servlet it calls the instances service( )
method.
Before destroying the instance,the container calls the destroy( ) method.
4.1.1.4 PRACTICAL APPLICATIONS FOR JAVA SERVLETS:

Servlets can be used for any number of web-related applications. Developing ecommerce store fronts will become one of the most common uses for java servlets .A
servlet can build an online catalog based on contents of database. Servlets can be used to
deploy web sites that open up larger legacy systems on the web, you run into access
issues.
4.1.1.5 REASONS TO USE JAVA SERVLETS:

Java servlets are one of the most new technologies.Servlets are
efficient,persistent,portable,robust,extensible,secure,and they are receiving widespread
acceptance.Servlets solve many of the common problems we run into when using CGI
and they prove to have a clear advantage over many of the other alternatives.
EFFICIENT:
A Servlet initialization code is executed only the first time the web server loads it.
After the servlet is loaded , handling new requests is only a matter of calling a service
method. This is a much more efficient technique than loading a completely new
executable with every request.
PERSISTENT:
Servlet can maintain state between requests. When a servlet is loaded, it
stays resident in memory while serving incoming request. Servlet can improve our
applications drastically.
33
PORTABLE:
Servlets are developed using java therefore they are portable. This enables
servlets to be moved to a new operating system without changing the source.
RESULT:
Because servlets are developed with access to the entire JDK, there are very
powerful and robust solutions. Java provides a very well-defined exception hierarchy for
error handling. It has a garbage collector to prevent problems with memory leaks.
EXTENSIBLE:
Another advantage servlets gain by being developed in an object-oriented
language like java is they can be extended and polymeric into new objects that better suit
our needs.
SECURE: Servlets run on the server side , inheriting the security provided by the web
server.
WIDE SPREAD ACCEPTANCE:

Because of all there is to gained from java servlets, they are being widely
acceped. Vendors are providing servlet support in two main forms. The first form is
servers that have built-in support in main forms. The first form is servers that have builtin support for servlets and the second is by using third-parity add-ones.
4.1.2 ORACLE (BACK END):

Oracle is a comprehensive operating environment that packs the
power of
mainframe relational database system into users microcomputer.Oracle has many

important features that make it an exceptional database management system and an
excellent database server choice for client/server database computing.
34
4.1.2.1 ADVANTAGES OF ORACLE:

Oracle has had for many years in the relational market offering solutions to large
and complex applications.
Following are the features of Oracle:-
1. Oracle gives you security and control.

2. Oracle performs competitively.
3. Oracle supports application development.
4. Oracle uses SQL command set.
4.1.2.2 ORGANISATION OF DATA IN ORACLE:

In oracle all data is stored and displayed in tables. A table consists of columns
and of rows. A single row of data is called a record from a table, we may select a subset
of rows or columns but the result always appears on a screen or in print as another table.
Fig shows the basic structure of a table.
A View is a desired that we can create for the purpose of display.
Although it looks like a real table with in the database, a view is only stored as a
definition.
4.1.2.3 ACCESS OF DATA IN ORACLE:

At the core of oracle is SQL which stands for Structured Query Language.
SQL is the language that it can be used to communicate with oracle, it consists of word
35
such as select and create, from which we can arrange highly structured commands and
statements in order to access and manipulate data stored in relational database.
The standard set of SQL commands falls into four categories:
i. Data definition language (DDL): It is used for creating and altering
structure of the database
ii. Data manipulation language (DML): It is used for adding and
modifying data
iii. Data control language (DCL): It is used for controlling access to
the database.
iv. Query: It is used to extract information from the database.
4.1.2.4
ORACLE ENVIRONMENT:
Oracle is a modular system that consists of the oracle database and several
functional programs (oracle tools) to perform four major kinds of tasks.
Database management tools.
Data access and manipulation tools.
Programming tools.
Connectivity tools.
36
4.2.SAMPLE CODE
LOGIN PAGE:
import java.sql.*;
import javax.servlet.http.*;
import javax.servlet.*;
import java.io.*;
import java.sql.*;
import java.lang.*;
import java.util.*;
import java.lang.String.*;
public class V extends HttpServlet{
public void processRequest(HttpServletRequest request, HttpServletResponse
response)throws ServletException,
IOException,SQLException,ClassNotFoundException {
response.setContentType("text/html");
PrintWriter pw = response.getWriter();
try{
String uname = request.getParameter("username");
String pass = request.getParameter("password");
37
Connection con = null;

boolean bool=false;
ResultSet rs = null;
Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
con=DriverManager.getConnection("jdbc:odbc:dsn2","system","XE");
PreparedStatement pst=con.prepareStatement("SELECT password from login where
username=?");
pst.setString(1,uname);
rs=pst.executeQuery();
while(rs.next())
{
bool=true;
if(pass.equalsIgnoreCase(rs.getString(1)))
response.sendRedirect("1.html");
else{
pw.println("<html><head><script>{alert('Invalid password -Please try again with the
correct password');window.history.go(-1);}</script></head></html>");
}
if(bool==false)
pw.println("<html><head><script>{alert('Invalid user - He is an unregistered
user');window.history.go(-1);}</script></head></html>");}
38
catch (Exception e){

pw.println(e);}
}
protected void doGet(HttpServletRequest request, HttpServletResponse
response)throws ServletException, IOException
{
try
{
processRequest(request,response);
}
catch(Exception e){}
}
protected void doPost(HttpServletRequest request, HttpServletResponse
response)throws ServletException, IOException {
try
{
processRequest(request,response);
}
catch(Exception e){}
}}
39
5. TESTCASES
5.1.1 Login form Login id and password:
Test case ID Input
Description
Expected result
OBS_TC01
Login Id blank
A blank Login id Invalid Use rid
Password blank
and password
Pass/Fail
Pass
given by the
Student/staff/ad
min
OBS_TC02 Valid Login id
Password blank
A valid Login id Invalid Password
Pass
and blank
Password given
by the
Student/staff/ad
min
OBS_TC03 Blank Login id

Valid Password
A blank Login id Invalid Login id
Pass
and valid
Password are
given by the
Student/staff/ad
min
OBS_TC04 Valid Login id

Valid Password
A valid Login id Go to Student/staff/admin Pass

and valid
Home pages ,As per the
Password are
user id and password
given by the
Student/staff/ad
min
5.1.2 Registration name:

40
Test case ID Input
Description
Expected result
OBS_TC01
A blank name
Display that invalid name Pass
Blank name
Pass/Fail
field is left by the

user
OBS_TC02
name with letters name with letter

without spaces
given by user
41
Accepted
pass
6. SCREENS
Fig.6.1.Login page for admin.
Here the administrator enters the user name and password and logs into the
system if he provides the system with a valid user name and password
42
Fig.6.2.Login page for admin.
If the administrator doesnt enter the valid password this message will be printed
43
Fig.6.3.Firstpage of admin.
The administrator can perform the required operation by selecting one of the
options shown on the left side of the screen
44
Fig.6.4.Admin page for Registration
The administrator issues usernames and passwords to the students and faculty
through this registration form
45
Fig.6.5.Admin page for selecting the details
The administrator selects the year, semester and the type of the exam for entering
the marks details
46
Fig.6.6.Admin page for entering marks and attendance
Admin enters the marks details and can store them in the database by submitting
47
Fig.6.7.Response page
Response page showing that the details are successfully inserted
48
Fig.6.8.Student login page
Here the student enters the user name and password and logs into the system if he
provides the system with a valid user name and password
49
Fig.6.9.First page of student
The administrator can perform the required operation by selecting one of the
options shown on the left side of the screen
50
Fig.6.10.Student page for retrieving marks
The student can select the required year and semester for which he is interested to
know the details
51
Fig.6.11.Output screen for marks
Output screen displaying the marks details of students
52
Fig.6.12.Output screen for attendance
Output screen displaying the attendance details of students
53
Fig.6.13.Mailing screen
Here the user can view either the received mails by selecting the inbox or can
send mail using the compose mail
54
Fig.6.14.Compose mail screen
The user can send the mail to any of other registered users
55
Fig.6.15.Inbox
The user can view the received mails here
56
Fig.6.16.Mailcontent
The content of the mail is displayed here
7. CONCLUSION
57
7.1. Conclusion:
The Application Student Acads Management Drive is designed to meet the
requirements of students of a department. It over comes the difficulties and risk involved
in manual maintenance. It is easy to maintain records of students details. As the
workload in any institution become more and more, manual maintenance will become
difficult. Student information could be maintained in student database. When the whole
system is computerized the information is effectively maintained. By using this project
we can also reduce the manpower and time.
7.2. Future Scope:

The application can be extended for maintaining the details of not only the
students of a particular department but also for the entire college or university.
8. BIBILOGRAPHY
58
8.1. Books Referred:
Database Management System- Raghu Ramakrishnan -TataMcGraw-Hill

ThirdEdition,2003.
J2EE UNLEASHED -Joseph J.Bambara -SAMS Edition,2002
Java Servlets- Korl Moss Tata McGraw-Hill-Second Edition,1999
Database Systems Concepts -Korth Sudarshan -Tata McGraw- Fourth

Edition,2002.
8.2. Websites:
www.w3schools.com
www.google.com
59

Documentation

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Documentation

Hochgeladen von

Copyright:

Verfügbare Formate

STUDENT ACADS MANAGEMAENT DRIVE

1.1 EXISTING SYSTEM:

1.2 PROPOSED SYSTEM:

STUDENT ACADS MANAGEMAENT DRIVE

ACCURACY: The accuracy is maintained and perfect calculations can be

REPORTING: Reporting different operations is easy and attractive.

SECURITY: By providing protection mechanism such as password, super

SECRECY: By making different authorization checks on the access of data,

STUDENT ACADS MANAGEMAENT DRIVE

2.1.1 .SOFTWARE REQUIREMENTS:

STUDENT ACADS MANAGEMAENT DRIVE

2.1.2 HARDWARE REQUIREMENTS:

STUDENT ACADS MANAGEMAENT DRIVE

A network of computer each with configurations of

2.1.2 Software Specifications:

2.1.3 Working Platform

2.2 SOFTWARE REQUIREMENTS SPECIFICATION:

STUDENT ACADS MANAGEMAENT DRIVE

A person who is studying in the particular Department of a College or

A Lecturer who is teaching in the particular Department of a college

Administrato The person who maintains this Application

STUDENT ACADS MANAGEMAENT DRIVE

Student/Faculty can register themselves.

Authenticate the user (Administrator/student)

Authenticate the user (Administrator/student)

STUDENT ACADS MANAGEMAENT DRIVE

Authenticate user (Administrator)

Register the user(student/staff)

Detailed Software Requirements:

A person who is studying in the particular department of a

It can be a person studying in the particular department of a

STUDENT ACADS MANAGEMAENT DRIVE

Employees of the department of a college/university.

It can be an employee, who uses the system to interact with the

Frequency of Use High

Handles all admin related tasks throughout the application

Work Environment Browser

List of use cases:

Use Case Diagram for a Student/Staff:

STUDENT ACADS MANAGEMAENT DRIVE

Fig:2.1 Use Case Diagram for a student/staff

Use Case Diagram for Administrator:

STUDENT ACADS MANAGEMAENT DRIVE

Fig:2.2 Use Case Diagram for a Administrator

Use Case Descriptions

STUDENT ACADS MANAGEMAENT DRIVE

Use Case Name UC1

2.2 User is returned to main flow

required year and the

STUDENT ACADS MANAGEMAENT DRIVE

Use Case Name

To update marks of the students

1. The user enters the

1.1 System displays the screen for the user

to enter the marks.

STUDENT ACADS MANAGEMAENT DRIVE

2.1 Marks are updated in the database

2.The user enters the

2.2 User is returned to main flow

Marks are updated in the database

Updating of marks can be done only by the Administrator.

The Administrator should verify whether the student is registered or

Request for Marks Updation

Use Case Name