STUDENT RECORD MANAGEMENT

SYSTEM
INDEX :
1.Introduction
..7
2.System Requirement Specification.
.8
3.Diagrams...........
14
4.Data Dictionary ......................
19
5.Design
Consideration...........................................20
6.Screenshot of System designed
page..................23
7.Comparision with existing
system.......................26
8.Conclusion.........................................................
...27

Chapter 1 :INTRODUCTION
Our team has taken a topic that influences students and
educational institutes in day to day life. In the third
semesters we had designed canvases to study the basic
purpose of the product and its main users. Also we
studies the product features and customer revalidation. In
the fourth semester we evaluated our idea under AIEOU
framework and generated a pre-design. In this semester
we are working on its primary software implementation.

Chapter 2 :SOFTWARE REQUIREMENT

SPECIFICATION
User Characteristics
The users of the system are students, teachers and the
administrators who maintain the system. The users are
assumed to have basic knowledge of the computers and
Internet browsing. The administrators of the system to
have more knowledge of the internals of the system and
is able to rectify the small problems that may arise due to
disk crashes, power failures and other catastrophes to
maintain the system. The proper user interface, users
manual, online help and the guide to install and maintain
the system must be sufficient to educate the users on
how to use the system without any problems.
General Constraints
The information of all the users must be stored in a
database that is accessible by the Online Student
Information Management System. The university
information security system must be compatible with the
3

Internet applications. The Online Student Information

Management System is connected to the university
computer and is running all 24 hours a day. The users
must have their correct usernames and passwords to
enter into the Online Student Information Management
Assumptions and Dependencies
The users have sufficient knowledge of computers. The
University computer should have Internet connection and
Internet server capabilities. The users know the English
language, as the user interface will be provided in
English. The product can access the university student
database

INFORMATION DESCRIPTION
This section provides a detailed description of the
problem that the software must solve. Information
content flow and structure is documented.
USER INTERFACES
All pages of the system are following a consistent theme
and clear structure. The occurrence of errors should be
minimized through the use of checkboxes, radio buttons
and scroll down in order to reduce the amount of text
input from user. Script is implemented in HTML in order
to provide a Data Check before submission. HTML Tables
to display information to give a clear structure that easy
to understand by user. Error message should be located
beside the error input which clearly highlight and tell user
how to solve it. If system error, it should provide the
contact methods. The page should display the project
4

process in different colour to clearly reflect the various

states that student done. Each level of user will have its
own interface and privilege to manage and modify the
project information such as supervisor able to
monitor/manage his student progress and make comment
on it, student can change his detail, view the progress,
submit project idea. The System should provide
a feedback form for all users to give comments or asking
questions. It should provide a FAQ to minimize the
workload of system administrator.
HARDWARE INTERFACES
Server Side
The web application will be hosted on one of the
departments Linux servers and connecting to one of the
school Oracle Database server. The web server is
listening on the web standard port, port 80.

Client Side
The system is a web based application; clients are
requiring using a modern web browser such as Mozilla
Firebox 1.5, Internet Explorer 6 and Enable Cookies. The
computer must have an Internet connection in order to be
able to access the system.
SOFTWARE INTERFACES
Server Side
The UOP already has the required software to host a Java
web application. An Apache Web server will accept all
requests from the client and forward SUMS specific
requests to Tomcat 5.5Servlet Container with J2EE
5.0 and Strut 1.2.8 hosting SUMS. A development
5

database will be hosted locally (using MySQL); the

production database is hosted centrally (using Oracle).
Client Side
An OS is capable of running a modern web browser which
supports HTML version 3.2 or higher.
COMMUNICATIONS INTERFACES
The HTTP protocol will be used to facilitate
communications between the client and server.
FUNCTIONAL DESCRIPTION
This section describes in detail all the functional
requirements.
FUNCTIONALITY
Logon Capabilities
The system shall provide the users with logon
capabilities.
Mobile Devices
The Online Student Information
Management System is also supported on mobile devices
such as cell phones.
Alerts
The system can alert the administrator in case of any
problems.
Usability
The system shall allow the users to access the system
from the Internet using HTML or its derivative
technologies. The system uses a web browser as an
interface. Since all users are familiar with the general
6

usage of browsers, no specific training is required. The

system is user friendly and self-explanatory.
RELIABILITY
The system has to be very reliable due to the importance
of data and the damages incorrect or incomplete data
can do.
Availability
The system is available 100% for the user and is used 24
hrs a day and 365 days a year. The system shall be
operational 24 hours a day and 7 days a week.
Mean Time Between Failures (MTBF)
The system will be developed in such a way that it may
fail once in a year.
Mean Time to Repair (MTTR)
Even if the system fails, the system will be recovered
back up within an hour or less.
Accuracy
The accuracy of the system is limited by the accuracy of
the speed at which the employees of the library and
users of the library use the system.
Maximum Bugs or Defect Rate
Not specified.
Access Reliability
The system shall provide 100% access reliability.
PERFORMANCE

Response Time
The Splash Page or Information page should be able to be
downloaded within a minute using a 56K modem. The
information is refreshed every two minutes. The access
time for a mobile device should be less than a minute.
The system shall respond to the member in not less than
two seconds from the time of the request submittal. The
system shall be allowed to take more time when doing
large processing jobs.
Administrator/Librarian Response
The system shall take as less time as possible to provide
service to the administrator or the librarian.
Throughput
The number of transactions is directly dependent on the
number of users, the users may be the administrator,
employees of the school and also students or teachers.
Capacity
The system is capable of handling 250 users at a time.
Resource Utilization
The resources are modified according the user
requirements and also according to the books requested
by the users.
DESIGN CONSTRAINTS
Software Language Used
The languages that shall be used for coding the Online
Student Information Management System are Active
Server Pages (ASP), Java Servlets, Java Server Pages (JSP),
HTML, JavaScript, and VBScript. For working on the coding
8

phase of the Online Student Information Management

System, the Internet Information Services (IIS) Server
needs to be installed.
Development Tools
Will make use of the available Java Development Tool kits
for working with Java Beans and Java Server Pages . Also
will make use of the online references available for
developing programs in ASP, HTML and the two scripting
languages, JavaScript and VB Script .
BEHAVIORAL DESCRIPTION
Operation as a result of external events and internal
conditions
System States
Events and Actions
VALIDATION CRITERIA
Software Testing Plan (STP) will be created to define a
set of qualification methods and to specify for each
requirement in this document a method of ensuring that
the requirement is satisfied .

Chapter 3:DIAGRAMS
1.USE-CASE DIAGRAM :
9

2.DATA FLOW DIAGRAM

10

3.CLASS DIAGRAM

11

4.ACTIVITY DIAGRAM
12

5.SEQUENCE DIAGRAM

13

14

Chapter 4 :DATA DICTIONARY

STUDENT
ATTRIBUTE
S

DATA
TYPES

User Id
Password
Name
Date Of Birth
Address
Phone No.
Semester
Department
Gender
Father Name
Father Occupation
Parents Contact No.
Marks
CPI
SPI
Year Of Study

String
String
String
Date
String
Int
Int
String
String
String
String
Int
Int
Float
Float
Int

15

FACULTY
ATTRIBUTES Data Types
User Id
Password
Name
Date Of Birth
Address
Phone No.
Department
Qualification
Designation
Subjects
Salary
Gender
Marital Status

String
String
String
Date
String
Int
String
String
String
String
Int
String
String

16

Chapter 5 :DESIGN
1.Design for Performance, safety and reliability:
Design for Performance: The main purpose of our
product is to design a system which contains upto-date
information about the students.Efficient and accurate
response is our purpose. Ourproduct offers features
likeuser friendly environment, circulars are easily
provided, concurrent access is possible, redundancy is
reduced. To make the project efficient, we are also going
for customer revalidation. Based on the feedback we will
re-design our efforts.

Design for Safety : Our website is going to store

personal details of students and members of a institution.
We assure that any such information is not passed on to
any person except legalized user.Policies/procedures
regarding access security to computerized files, keeping
disks or printouts in locked cabinets, periodically updating
passwords, and ensuring that terminals are properly
signed off when not in use will be implemented.

Design for Reliability : By this project ,faculties and

admin staff of instituition can share important
circulars and academic details. Students will rely
on the system as the handling of system will be
purely in hands of authorized user.

17

2.Design for Ergonomics and Aesthetics:

Design for Ergonomics : Ergonomics is all
about designing for human factors/comforts
whenever they interact with product. Student
record mamangement system fulfills this feature
as a safe and secure environment is built up where
in students and faculties interact with each other.
There wont be any manual toil like maintaining
hardcopies of data, forms etc.
Aesthetics : Our website will be designed in userfriendly manner. For the same we will implement a
pre-design using familiar sites like Wordpress and
Weebly. From this we got a better idea to make a
website that will meet to user's expectations.
3.Design for Manufacturability and
Assembly(DFMA):
This web application is design using simple HTML
code. For the same we have used.Clients are
requiring using a modern web browser such as
Mozilla Firebox 1.5, Internet Explorer 6 and Enable
Cookies. The computer must have an Internet
connection in order to be able to access the
system. All this technical specifications are cheap
and easily available. Hence we have designed a
system at minimum cost giving maximum output.

18

4.Design for Cost, Environment :

Design for cost : We have used laptops having
specifications(8GB RAM,i3 processor,1TB hd) that
has cost us 45k. For the references we have used
Internet by wifi connection. And user have to install
software at 1 year validity and then upgrade the
version.
Design for Environment : Our project is a fully
software oriented project. We have ensured that at
minimum resources we make maximum profit.

19

Chapter 7: SCREENSHOT OF SYSTEM

DESIGNED PAGE

20

21

Chapter 8 :COMPARISION WITH EXISTING

SYSTEM
We have designed a better ,safe and secure record
management system that will work best for an
institutions. We will additionally provide the
information of ex-students. Further more a web app
will be designed that works on desktop as well as
mobile.

22

Chapter 9 :CONCLUSION
Our system can help many students and provide
information at the touch of the button. It is one big facility
that helps people to find data items according to their
requirements. Admission process, circulars, results,
seminars, and other details. And finally the customer if
free to give suggestions or feedback about the system so
that the system can be redesigned and made efficient for
the users.

23