You are on page 1of 68


This project Online Mentor Card System provides us a simple interface for maintenance
of student information. It can be used by educational institutes or colleges to maintain the
records of students easily. Achieving this objective is difficult using a manual system as the
information is scattered, can be redundant and collecting relevant information may be very
time consuming. All these problems are solved using this project.

Throughout the project the focus has been on presenting information in an easy and intelligible
manner. The project is very useful for those who want to know about Online Mentor Card
Systems and want to develop softwares websites based on the same concept.

The project provides facilities like profile creation of students thus reducing paperwork and
automating the record generation process in an educational institution.





ABSTRACT.............. vi

LIST OF xiii




1.1. 1


1.2. 1



2.1. Module 3
2.2.1 Login Module. .
2.2.2 Search Module.

2.2 Registration Module and Account 3

2.3 User Management .
2.4 Database Design
2.5 Create the suitable GUI complete with



3.1 Database Design
3.2 Software Testing
3.3 Requirement Plan Phase
3.4 Requirement Specification Analysis Phase
... 9

3.5 Design Phase . 9

3.5.1 Database Design . 9

3.5.2 Interface Design . Text Box. 9

10 Button . 10 Combo Box . 10 List View 10 Data Designer-Report Generator 11

3.5.3 Coding Design ...
3.6 Data Flow Diagram ...
3.7 Technology Overview ...
3.7.1 PHP
3.7.2 My SQL .
3.7.3 Apache ..
3.7.4 XAMPP .
16 Obtaining and Installing XAMPP

3.7.5 Creating a Database and Inserting Data

3.7.6 PHP My Admin 23

3.8 SRS 23

3.8.1 Specific Requirements 23

24 Functional Requirements
24 User Class- Student
. 24 User Class- Academic Staf 25

25 User Class- Mentor/Co-ordinator

26 User Class- System Administrator
.. 26 User Class- Administrator Staf 26

3.9 Product Perspective ...
3.9.1 User Interface ...
3.9.2 Hardware Interface ..
3.9.3 Software Interface
3.9.4 Communications Interface

3.10 Memory ...
3.11 System Functions .
3.11.1 Student Role ...

3.11.2 Administrative Role 29

3.11.3 Audit Trailing .
3.12 Assumptions and Dependencies
3.13 Design Phase
3.13.1 Introduction ...

34 Scope and Purpose
. 38 Overall System Design Obejectives 39

39 Structure of Design Document
3.14 System Architecture Design

3.14.1 System Architecture 42

3.15 Data Design .

3.15.1 Entity Relationship Diagram
3.16 Functional Design Description

3.16.1 Data Flow Diagram 50

3.17 Decision Tree ..

3.18 Testing Phase .. 50

3.19 Maintenance . 50

3.19.1 Perfective Maintenance 51


3.19.2 Adaptive Maintenance


3.19.3 Corrective Maintenance


3.19.4 Preventive Maintenance



4.1 Objective

4.2 Safety Requirements ..

4.3 Security Requirements ...


5.1 Conclusion .

5.2 Scope .

5.2 Limitations


Figure No. Description Page No.

Xampp Installation

Php MyAdmin

List Of Tables

Login Table

Student Table

Academic Details

Student Hostel Details


Parents Address Details


Day Scholar Address Details


Parents Personal Details


Competitive Exam Details

Student Login


Student Details

Academic Details

Parents Details

Students Academic Details



Table. No. Description Page No.

1. Software Testing Phase 7

2. Coding Design 11

3. System Architecture 30

4. Entity Relationship Diagram 31

5. Data Flow Diagram 32

6. Decision Flow Diagram 33


SRS: System requirement Specification

WWW: World Wide Web

OMCS : Online Mentor Card System

DOB : Date Of Birth

GUI : Graphic User Interface



1.1 Introduction

An Online Mentor Card System is a management information system for education

establishments to manage student data. Online mentor card provide capabilities for registering
students in courses, documenting grading, transcripts, results of student tests and
other assessment scores, building student schedules, tracking student attendance, and
managing many other student-related data needs in a college. An OMCS should not be
confused with a learning management system or virtual learning environment, where course
materials, assignments and assessment tests can be published electronically.

1.2 Purpose

The objective of Online Mentor Card System is to allow the administrator of any organization
to edit and find out the personal details of a student and allows the student to keep up to date
his profile .Itll also facilitate keeping all the records of students, such as their id, name,
mailing address, phone number, DOB etc. So all the information about a student will be
available in a few seconds. Overall, itll make Student Information Management an easier job
for the administrator and the student of any organization. The main purpose of this SRS
document is to illustrate the requirements of the project Online Mentor Card System and is
intended to help any organization to maintain and manage its students personal data.

1.3 Scope

Without Online mentor card system, managing and maintaining the details of the student is a
tedious job for any organization. Online mentor card system will store all the details of the
students including their background information, educational qualifications, personal details
and all the information related to their resume.



2.1 Modules

2.1.1 Login module:

Login module will help in authentication of user accounts. Users who have valid login id and
password can only login into their respective accounts

2.2.2 Search module:

Suppose there are hundreds of students and from this we have to search a particular student
and we know the name of the student .In manual system it is a tedious task though we know
the name of the student, but using this module we can easily search the student by specifying
the name of the student in the search criteria. Thus this module will help the administrator in
searching the student with various criteria easily.

2.2 Registration Module and Account Management:

This module will help the student get registered by the mentor. This module will really
simplify the task of on paper registration. Also after successful registration the user can update
information and change their password as and when required.

2.3 User Management:

This module will help the administrator in enabling/disabling a user account and updating user
information as required. Purpose of project is to maintain details of the students such as
storing information about:
Student id

Student password

Student name

Student DOB

Student mailing address


Registration date

Student status

Contact no




2.4 Database Design:

Database is required to improve the functionality of this project.

Therefore, the first stage of software development is to create the database.

Database is a body of information made up of related pieces of data organized so that

they can be easily been manipulated by the computer.
As for the software development, it is important to have database as all the information
needed can be saved for future used

2.5 Create the suitable GUI complete with coding:

GUI is a way to interact with a computer using pictures and other visual elements
displayed on a computer screen.

The pictures and buttons used to control many Internet sites are an example of a GUI.

GUI is important to make the user easy to understand what they need to do in order to
use the software.

GUI must be user friendly and easy to be understood.

fig 2.1



3.1 Database Design

Database is required to improve the functionality of this project.

Therefore, the first stage of software development is to create the database.

Database is a body of information made up of related pieces of data organized so that
they can be easily been manipulated by the computer.

As for the software development, it is important to have database as all the information
needed can be saved for future use

3.2 Software testing

Software testing is the process used to measure the quality of developed computer software to
determine that the software meets its required results. This testing process of executing a
program is intended of finding errors.


3.3 Requirement Plan Phase

Before developing the system, either small or large system the proper planning needs to be put
in the first place. This is to make sure that all the activities that will execute and overall
development are under control. The purpose of planning is to prepare the workflow for project
management start from early stages of project development until end of development. The
developer need to mention that it is very important to divide the project into subtasks to make

sure about time estimation and to identify source requirement to complete this Online Mentor
Card project.

In addition, the developer also needs to identify what is the hardware and software will be
used. The hardware that been used to develop this system are Personal Computer (PC),
keyboard and mouse, 128 MB of RAM, 40 GB of Memory, printer and Universal Serial Bus
Flash (USB Praline).

3.4 Requirement Specification Analysis Phase

All the requirement analysis phase will be started after the study case for this system has been
completed. Through this phase, developer will determine clearly who will use the system,
function of the system, when and where the system will be executed.

Developer will begin the study from existing system to define the strength and weakness. This
is important as it can identify the opportunities to improve the existing system to a new
system. If there are any shortcomings or defects, it can be corrected in the new system. After
this research, the concept of new system is developed. Besides, the information is collected by
using fact-finding techniques such as background reading, interviewing and observation.

As a developer, it needs to analyze the feasibility of new system, which is to improve the
system as to make sure that the new system will fulfil the user requirement. All the constraints
and limitation of the new system also need to analyze.

3.5 Design Phase

3.5.1 Database Design

To design database, it considers and concerns in many aspects. The specification will be
determined by what is the data need to be stored in database. In database design, each step of
the process needs to be done very carefully for avoiding any unexpected errors. The errors
might occur in database, it can give complex problem for the system. These databases are
designed by using MySql.

3.5.2. Interface Design:

The purpose of interface design is to determine how the layout of the system and to make sure
that this layout suitable with user requirement. The good designing can attract the users and
supposedly not confused the users with each functions of the system. For instance, the
developer also needs to concern about user-friendly interface during designing phase. Through
this system, there are some elements, which been used to design the interface. Text Box:

The user can key in the input in the text boxes. However, certain text boxes only receive
numeric inputs, but not character input such as Identity Card (IC) number. Button:

There are a few buttons which been prepared for the users usage such as accept, ok , cancel,
close, update, save , print and search button. All these buttons have their own functions. Combo Box:

The purpose of the combo box is to list all selection items there. Therefore, the users do not
need to key in any input, but they can drag down the scroll and choose the best list as their

10 List View:

All the data will be view in this list view in the system. Data Designer-Report Generator:

It used to view the report about summary of data record and list of files, which are already
kept in database.

3.5.3. Coding Design:

This coding designing showed how programming language would be implemented. It also will
explain the purpose for each coding development. SQL statement is used in order to make sure
that interfaces can be connected with database.

fig 3.2

3.6. Data Flow Diagram (DFD):

In design module, Data Flow Diagram (DFD) is used to show the data flow and how it move
or work in task on system. Therefore, DFD used several levels such as level 0 refer to synopsis
of the system and level 1.


The technology selected for implementing Student Information Management System is

PHP/MYSQL.Apache is used as the HTTP server. The development was done in a windows
using using HTML, CSS, JavaScript, PHP, MySql.

3.7.1. PHP

PHP is a general-purpose scripting language that is especially suited to server-side web

development where PHP generally runs on a web server.PHP code is embedded into the
HTML source document. Any PHP code in a requested file is executed by the PHP runtime,
usually to create dynamic web page content. It can also be used for command-line scripting
and client-side GUI applications. PHP can be deployed on many web servers and operating
systems, and can be used with many relational database management systems (RDBMS). It is
available free of charge, and the PHP Group provides the complete source code for users to
build, customize and extend for their own use.

3.7.2. MySQL

MySQL is a relational database management system (RDBMS) that runs as a server providing
multi-user access to a number of databases. MySQL is a popular choice of database for use in
web applications and is an open source product. The process of setting up a MySQL database
varies from host to host, however we will end up with a database name, a user name and a
password. Before using our Database, we must create a table. A table is a section of the
database for storing related information. In a table we will set up the different fields which will

be used in that table. Creating a table in phpMyAdmin is simple; we just type the name, select
the number of fields and click the go button. We will then be taken to a setup screen where
you must create the fields for the database. Another way of creating databases and tables in
phpMyAdmin is by executing simple SQL statements. We have used this method in order to
create our database and tables.

3.7.3 Apache

The Apache HTTP Server is web server software notable for playing a key role in the initial
growth of the World Wide Web. In 2009 it became the first web server software to surpass the
100 million web site milestone. Apache is developed and maintained by an open community of
developers under the auspices of the Apache Software Foundation. Since April 1996 Apache
has been the most popular HTTP server software in use. As of November 2010 Apache served
over 59.36% of all websites and over 66.56% of the first one million busiest websites.

3.7.4 XAMPP

XAMPP is a small and light Apache distribution containing the most common web
development technologies in a single package. Its contents, small size, and portability make it
the ideal tool for students developing and testing applications in PHP and MySQL. XAMPP is
available as a free download in two specific packages: full and lite. While the full package
download provides a wide array of development tools, XAMPP Lite contains the necessary
technologies that meet the Ontario Skills Competition standards. The light version is a small
package containing Apache HTTP Server, PHP, MySQL, phpMyAdmin, Openssl, and SQLite

14 Obtaining and Installing XAMPP

As previously mentioned, XAMPP is a free package available for download and use for
various web development tasks. All XAMPP packages and add-ons are distributed through the
Apache Friends website at the address: Once on the website,
navigate and find the Windows version of XAMPP and download the self-extracting ZIP
archive. After downloading the archive, run and extract its contents into the root path of a hard
disk or USB drive. For example, the extract path for a local Windows installation would
simply be C:\. If extracted properly we will notice a new xampp directory in the root of your
installation disk. In order to test that everything has been installed correctly, first start the
Apache HTTP Server by navigating to the xampp directory and clicking on the
apache_start.bat batch file.

Next we will test if the server is running correctly by opening an internet browser and typing
http://localhost/ into the address bar. If configured correctly, we will be presented with a screen
similar to that of the one below.

fig 3.3

3.7.5 Creating a Database and Inserting Data

Now that we have run and tested Apache and PHP, the next step is running MySQL and
creating a database and table which will hold information to be used by our website. In order
to start MySQL, navigate to the xampp directory and run the mysql_start.bat batch file. The
XAMPP package contains an application called phpMyAdmin which allows developers to
administer and maintain MySQL databases. We will be using phpMyAdmin to create a
database and table, and enter test data. Before testing phpMyAdmin, make sure that both
Apache and MySQL are running by opening their respective batch files: apache_start.bat and
mysql_start.bat. Along with Apache and MySQL running in the background, we type
http://localhost/phpMyAdmin/ into our web browser. If successful we will be presented with a
phpMyAdmin start page similar to the one shown below.

3.7.6 PHP My Admin

The first step with phpMyAdmin running is creating a new database. We create a new database
by directly executing SQL statements as shown below. The successful execution of the sql
query creates a database student with two tables in it. The tables are admin_login and
student_information.We also inserted values in the admin table. The screenshot below shows
the successful execution of the query thus creation of a database named student.

List Of Tables in Database

Login Table

Student Table

Academic Details Of Students

Student Hostel Details

Parents Address Details

Day Scholar Address Details

Parents Personal Details

Competitive Exam Details

3.8. SRS:

3.8.1. Specific requirements: Functional requirements: User class Student:

Student registration form. Student can be register on the system and fill in all detail and
forward to choose project/supervisor.

Change Detail. Student can change detail if information is incorrect such as telephone

Change Password. Student can change his login password at any time for security reason.

Forget password. Student can request his password if he/she forgotten the password. User class Academic Staff:

All staff can view the details of any student. User class Mentor or Co-ordinator:

Certain staff may be designated as Mentor or Co-ordinators and can change the details of
any student doing their unit or project .

Change Student Detail

Co-ordinator can change student detail for incorrect information.

View Student Detail

Co-ordinator can view student information and monitor their progress.

List Student

Co-ordinator can list all students in different period of different group.

Change Password

Co-ordinator can reset the students password if required. User class System Administrator:

List Student

System Administrator can list all students in different period of different group to check
any error.

Change Password

System Administrator can reset the students password if required. User class Administration Staff:

List Student

Administration Staff can list all students in different period of different group.

3.9. Product perspective:

3.9.1. 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. JavaScript implement 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 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 mange 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.

3.9.2. Hardware interfaces:

a. Server Side:
The web application will be hosted on Apache HTTP Server and connecting toMySql
Database server

b. Client Side:
The system is a web based application; clients are requiring using a modern web browser such
as Google chrome and Enable Cookies. The computer must have an Internet connection in
order to be able to access the system.

3.9.3. Software interfaces:

a. Server Side:

The web application will be hosted on Apache HTTP Server and connecting toMySql
Database server. Server side coding is done in PHP. It collects the data via form and sends it to
the server.

b. Client Side:
An OS is capable of running a modern web browser which supports HTML version 3.2 or

3.9.4. Communications interfaces:

The HTTP protocol will be used to facilitate communications between the client and server.

3.10. Memory:
The KIET already hosts a number of Java web applications, it is not anticipated that OMCS
will require any additional memory storage.

g) Operations:

Procedures are already in place as part of the KIETs IT policies for data security and Backup.

h) Site adaptation requirements:

There should no site adaptation requirement since the Web Application Server was setup and
running web application.

3.11. System functions:

3.11.1. Student role:

When it comes protecting confidential school-related data, OMCS is indeed a boon.
The highly secured database of the system can only be accessed by authorized people. So,
OMCS ensures stringent data security.
On the other hand, user-friendliness and interactive user interface are two important
features of OMCS.
With these, both school staff and studentsirrespective of their levels of computer
proficiencycan perform their tasks on OMCS.
Students can also harness the benefits of OMCS.
Apart from checking their grades and report cards, they can also form groups on this
platform in order to discuss various study-related matters.

3.11.2. Administration role:

The system administrator must be able to:

deactivate and reactivate student account login

force the sending of a new password to a student via email

change any of a student's details

3.11.3. Audit Trailing:

Each user will have an associated record of history. This will provide information on
various events such as number of times a user enters wrong password, how often the user
changes his details etc.

3.12. Assumptions and dependencies:
Although basic password authentication and role based security mechanisms will be used to
protect OMCS from unauthorised access; functionality such as email notifications are assumed
to be sufficiently protected under the existing security policies applied by the University
network team. Redundant Database is setup as the role of backup Database Server when
primary database is failure.

The correct functioning of OMCS will partly be dependent on the correctness of the data
stored and managed as part of the OMCS system. Also, the application will be hosted by the
Apache Server as one of many applications; the event of the server failing due to an error with
one of these applications might result in OMCS becoming temporarily unavailable.


3.13.1. Introduction Scope and purpose:

The purpose of the design phase is to develop a clear understanding of what the developer
want people to gain from his/her project. As you the developer work on the project, the test for
every design decision should be "Does this feature fulfil the ultimate purpose of the project?"A
purpose statement affects the design process by explaining what the developer wants the
project to do, rather than describing the project itself. The Design Document will verify that
the current design meets all of the explicit requirements contained in the system model as well

as the implicit requirements desired by the customer. Overall System Design Objectives:

The overall system design objective is to provide an efficient, modular design that will reduce
the systems complexity, facilitate change and result in an easy implementation. This will be
accomplished by designing strongly cohesion system with minimal coupling. In addition, this
document will provide interface design models that are consistent user friendly and will
provide straight forward transition through the various system functions. Structure of Design Document

System Architecture Design The System architecture section has detailed diagram of the
system, server and client architecture.

Data Design The data Design include an ERD as well as Database design.

Functional Design Description This section has the functional partitioning from the SRS,
and goes into great detail to describe each function.

3.14 System Architecture Design

3.14.1. System Architecture:

The OMCS is a system which contains major part which includes: student Detail, Student
image and resume. The user selects one of the available options as an input to the system.
According to the input by the user the system acts and the rest of the functions are performed
accordingly. The administrator can operate on any student details. But the normal student or
users can only access their details of all the functionalities.


3.15. Data Design:

3.15.1 Entity Relationship Diagram:

3.16. Functional Design Description

3.16.1 Data Flow Diagram:

3.17. Decision Tree:


System testing of software or hardware is testing conducted on a complete, integrated system

to evaluate the system's compliance with its specified requirements. System testing falls within
the scope of black-box testing, and as such, should require no knowledge of the inner design
of the code or logic.

As a rule, system testing takes, as its input, all of the "integrated" software components that
have passed integration testing and also the software system itself integrated with any
applicable hardware system(s). The purpose of integration testing is to detect any
inconsistencies between the software units that are integrated together (called assemblages) or
between any of the assemblages and the hardware. System testing is a more limited type of
testing; it seeks to detect defects both within the "inter-assemblages" and also within the
system as a whole.

General Principle Of Testing Include:

A test plan must be prepared to specify the sequence in which the modules will be coded,
in individually tested, and then integrated into the program.

Test cases must be prepared as part of the plan. Each test case should include a
specification of the data to be submitted as inputs, as well as a specification of the expected
results of the test.

All test results should be studied and recorded.

Test cases should be prepared for both valid and invalid input conditions.

Software tools are available to support testing and debugging; their use significantly
increases the effectiveness of the process.

The following are the principal levels of software testing:

1. Module testing:

After a module has been coded, the code is thoroughly reviewed and then tested with
predesigned test cases.

2. Integration testing:

After individual modules are coded and unit-tested, they are integrated into the overall
program. Generally, one module at a time is added to the structure and the resulting partial
product is tested.

3. System testing:

The system is validated against its functional specifications, in an environment and under
loads that resemble the actual operation as closely as possible. The system is subjected to
stress loads to see whether it degrades gracefully. The system's compatibility is checked
against other systems it will have to interact with. Controls and recovery procedures are also
tested. It is very important to test the documentation that will accompany the system along
with the system itself.

A beta test of software is used to test the early copies of software by the intended end users
in order to uncover problems in actual use.

4. Acceptance testing:

A set of systems tests are run in order to ensure that the requirements of all users have been
satisfied. A suite of tests validating the overall system operation is identified, documented, and
preserved for maintenance purposes.

These regression tests will be used to revalidate the system following each maintenance

5. Installation testing:

If acceptance testing was done before a system was installed in its production environment, a
set of system tests is run again following installation. The system is now ready for operation.

Although each test has different purpose, all work to verify those system elements have been
properly integrated and perform allocated functions. Types of system testing are following
Recovery Testing
Security Testing
Stress Testing
Performance Testing

Recovery Testing: Recovery testing is a system test that forces the software to fail in a variety
of ways and verify that recovery is properly performed. If recovery is automatic,
reinitialization, check pointing mechanisms, data recovery and restart are evaluated for

Security Testing: Security testing attempts to verify that protection mechanism built into a
system will, in fact, protect it from improper penetration.

Stress Testing: Stress testing executes a system in a manner that demands resources in
abnormal quantity or volume. Like test case may require maximum memory or other resources
are executed.

Performance Testing: Performance tests are often coupled with stress testing and usually
require both hardware and software instrumentation.

Here the system testing involved is the most widely used testing process consists of five stages
as shown in the figure. In general, the sequence of testing activities is component testing,
integration testing then user testing. However, as defects are discovered at any one stage, they
required program modifications to correct them and this may required other stages in the
testing process to be repeated.

Operational information systems must be maintained. Maintenance is the process of modifying

an information system to continually satisfy organizational and user requirements. There is a
vast difference between hardware and software maintenance in costs as well as in objectives.

Hardware maintenance

The purpose of maintaining computer system hardware is to keep the equipment in working
order without changing its functionality. Traditionally, this aspect of system maintenance has
been covered by maintenance contracts with equipment manufacturers.

Systems maintenance

The principal effort in system maintenance is directed at maintaining the applications

software. Software maintenance includes all modifications of a software product after it has
been turned over to operations. The cost of this maintenance over the useful life of an
application is typically twice the development cost.

Software maintenance actually consists of three types of activities:

3.19.1. Perfective maintenance

Enhancing and modifying the system to respond to changing user requirements and
organizational needs, improving system efficiency, and enhancing documentation.

3.19.2. Adaptive maintenance

Changing the application to adapt it to a new hardware or software environment. Adaptive

maintenance may involve, for example, moving an application from a mainframe to a
client/server environment, or converting it from a file to a database environment.

3.19.3. Corrective maintenance

Correcting an error discovered during operations.

3.19.4. Preventive Maintenance

Improves future maintainability and reliability and provides a basis for future enhancement. It
deals with updating documentation and making the software more maintainable. Tasks
performed during the software engineering process define maintainability and have an
important impact in the success of any maintenance approach. Reverse Engineering and
Reengineering are the tools and techniques used to maintain the project.

The Dynamics of Software Maintenance:

A software maintenance procedure consists of three steps:

We need to understand the software to be modified and identify the parts targeted for

We must then modify the appropriate components of the application system without
adversely affecting the rest of the system

We must test and thus validate the modified components, as well as the entire system.

There are four major problems that can slow down the maintenance process

Unstructured Code
Maintenance programmers having insufficient knowledge of the system
Documentation being absent
Out of Date, or at best insufficient

The success of the maintenance phase relies on these problems being fixed earlier in the life




Enable self-service for students to perform basic administrative functions and tasks in a
one-stop service and access environment.

Integrate data sources and process them through a single function that supports one-time
entry of student data.

Support the retention and recruitment of students and encourage a strong and positive
relationship with the university, alumni and other constituencies.

Support open interfaces and integration with other campus applications and database

Ensure data integrity, privacy, and security in an open-access environment.

Support faculty and staff who perform both basic and complex functions through
simplified work processes and procedures.

Enable ongoing, flexible reconfiguration of the application to extend its life cycle and to
meet the changing business processes of the university.

The First and foremost requirement of the client is the problem of computerization. Several
Queries arises are:

To achieve tasks in simpler and efficient manner.

To make data entry easier.
To reduce data inconsistency and redundancy.
To reduce manual effort, provide accuracy and enhance speed.
To generate the report .
To add or remove any records easily

Benefit of the Online Mentor Card System

Have various facilities. Few of them are:

It is easy to use and faster than manual system.

Tasks are achieved in simple and efficient manner.
It is easy to get information about student through the application.
Fast access to all the information.
Timely and accurate information is provided.
The whole authority is given to the administrator.
It is easy & beneficial for generating the report .
Error handling at the time of inserting the data retrieving the data and modifying the data
from data base.
You can generate whole Information of particular student.
Update password facility are included.
To give permission to only authorized person for the data entry.
Saving Main Power, Paper work, time, etc.

4.2. Safety Requirements:

The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.

4.3. Security Requirements:

We are going to develop a secured database. There are different categories of users namely
Administrator, Student who will be viewing either all or some specific information form the

Depending upon the category of user the access rights are decided. It means if the user is an
administrator then he can be able to modify the data, append etc. All other users only have the
rights to retrieve the information about database.


Student Login


Student Details

Academic Details

Parents Personal Details

Academic Result Details



As for the conclusion, the objectives for this project were achieved and functioned well as the
desired target. This project will help to keep track record of students and work systematically
and will make ease to the mentor in order to manage all the student data in the system. This
project will give a better performance in arranging the student information without having to
do it manually. This project will help facultys staff to arrange student matter and schedule
faster and easier. Furthermore it will allow the mentor to focus on other important tasks of the
student. As the future recommendation, the project is recommended to be built with the fully
functional software that fulfills all the criteria needed and also applied with more complicated
algorithm to the system.

5.2 Scope

Since this system has been generated by using PHP, there are every chances of reusability of
the codes in other environment even in different platforms. Also its present features can be
enhanced by some simple modification in the codes so as to reuse it in the changing scenario.
Besides these above mentioned functionalites we can also add some more features and
functionalites in the near future.
5.3 Limitations

Since, every system has some limitations so our proposed system is also not untouchable in
this regard. Although it includes every kind of features but it cant be used in a huge
organization where number of networks are very large, because the data base used in this
system is an average one. Also it doesnt have different kind of access feature for different