Project Rahul

College Management System
1. COLLEGE PROFILE
1.1 UDHNA ACADEMY EDUCATION TRUST
Udhna Academy Education Trust was established in 1964 with the objective of
catering to the educational needs of the citizens of udhna area (i.e South zone of
surat city) and south Gujarat. The Trust has completed 51 years of brilliance
since inception in 1964.It has spread the light of education in the region
providing education ranging from pre-primary to Higher Secondary and
graduation.
Its pioneers started this institution with a very noble aim and far reaching vision.
As a result, today, Udhna Academy Education Trust governs the following
institutions, where about 6000 students seek high quality education.
UDHNA ACADEMY COLLEGE OF C.A & I.T. (B.C.A) -JUNE 2008

S.P.B COLLEGE OF BUSINESS ADMINISTRATION (B.B.A.) – JUNE 2005
UDHNA CITIZEN COMMERCE COLLEGE (B.com.) – JUNE 2002

R.N. NAIK H.S. SCHOOL (SCIENCE) – JUNE 2001
R.N. NAIK H.S. SCHOOL (COM.& ARTS) – JUNE 2001

UDHNA ACADEMY SHISHUVIHAR-2- JUNE 1998
SMT. MADHUKANTABEN J. MEHTA PRIMARY SCHOOL – JUNE 1998
UDHNA ACADEMY SHISHUVIHAR-2- JUNE 1998
SURAT NATIONAL PRIMARY SCHOOL- JUNE 1968

R.N. NAIK HIGH SCHOOL – JUNE 1964
VISION
“To be an eminent and vibrant institute for education, our credo will always be
excellence through innovations, sympathy, ethics and teamwork and to cater to
the ever changing needs of community at large”.
MISSION
“To impart quality education, nurture aspirations and facilitate continuous

learning and to contribute to the society by developing outstanding individuals
who would take up leadership challenges in various sectors of economy.
1.2 Salient Features
 Qualified and Experienced faculty members
 Book Bank Facility
 Well-equipped Text and References Library
 Strong Industry- Institute Interaction through seminars, Guest Lectures,

Projects, Visits.
 Faculty Feedback System to strengthen Teaching-Learning Process
 Indoor and outdoor Co-Curricular & Extra –curricular Activities
 Social Welfare Initiatives in Plantation of trees, Blood Donation Camp,

NSS Camp and relief during Natural Calamities
 NSS Sports as Character Building Activities
 Tie-up with Health centre for free medical service to all students and staff
 Well equipped computers laboratories with Broadband Internet

Connection
 Canteen Facility for Students and staff

 Scholarship to toppers in academics, extra-curricular activities and sports
 Anti-ragging Cell
 Women’s Cell
 Placement Cell
 Smart Class
 Seminars conducted by doctors
1.2 INSTITUTE STRUCTURE /CHART

Udhna Academy Education Trust
Member of the Trust
Dr. Mehul P. Desai

(I/C Principal)
B.COM B.B.A B.C.A
Dr. Mehul P. Desai Dr. Daisy Thekanlal Dr. Manish kaysth
Teaching Teaching Teaching

staf staf staf
2. EXISTING SYSTEM STUDY
System Study is a detailed study of the various operations performed by a

system and their relationships within and outside of the system. Here the key
question is –what all problems exist in the present system? What must be done
to solve the problem? Analysis begins when a user or manger begins a study of
the program using existing system. Training, experience and common sense are
required for collection of relevant information needed to develop the system.
The success of the system depends largely on how clearly the problem the is
defined, thoroughly investigated and properly carried out through the choice of
solution. A good analysis model should provide not only the mechanisms of
problem understanding but also the frame work of the solution. Thus it should
be studied thoroughly by collecting data about the system. Then the proposed
system be analysed thoroughly in accordance with the needs.
2.1 Major Components
The main focus of College Management System is to keep track on student

record & manage attendance, marks information, fees information.
 Students:
 New Student registration :
This Component is used to register new student into the database. Using this
interface you can introduce new student into database as well as modify existing
entry from. Here you can also store parent’s information and emergency contact
information which are used full for any institute to handles students.
 Student marks information:
This component is used to collect the marks information of the student of

their exams and calculate results from that information.
 Student Attendance information:
This component is used to store monthly attendance of student in the

database as well as send appropriate SMS to student’s parents about attendance.
2.2 MINIMUM HARDWARE AND SOFTWARE CONFIGURATION
Hardware Details:
Developer
Process : Intel corei3 processor, AMD Catalyst processor
RAM : 4 GB RAM
HDD : 500 GB Hard Disk
User
Process : Intel Pentium 4, Dual Core processor
RAM : 512 GB RAM
HDD : 40 GB Hard Disk
Software Details:
Developer
Apache version : Apache /2.4.10
Php version : 5.5.19
MySQL version : 5.0.11
Tools : php Myadmin (4.2.11)
Client side
Web browser: Mozilla Firefox (36.0)
Google chrome (40.0)
Users
Web browser : XAMPP
Mozilla Firefox (36.0)
Google chrome (40.0)
PhpStorm version 8.0.1
Operating system: windows 10, windows 8.1, windows 7
2.3 DRAWBACKS / LIMITATIONS(Existing System)

1) Less Interactive:
Most perceptions of interactivity are that it is an inherently good thing,

that it will change confusions which arise in the mind of student. So, it is
the foremost limitation of College Management System.
2) Time Consuming:
In Our current system, all the process are carried out by human so
naturally it require more time and in that sense, it will require more time
to complete transaction. A person is needed to enter details for every
individual newly registered student.
3) Book Record:
In every manual system has more books keeping. Like in manual College
Management System has so many registers like student admission
register, another are fees register, Attendance register, Marks record of
each and every exams, so the system have high book keeping to maintain
manual registers rather than computer software.
4) Report Creation:
Information processing is very lengthy and time consuming. So actual

data required to create or generate reports which are not on time provided
generation is delay until required data is produced.
5) Messaging facility not available:
In existing College Management System, they haven’t facility about

sending messages, if they had that facility then all the information like
result, student attendance, fees detail, exam messages etc. to parents.
6) Security /level is low:

In Our current system all the work that is done carried out the register and
so there are not any security criteria to guard our data and any person can
open data register and make changes and make effect on reports.
7) Backup and Restore Facility is not available:
In current system there is no backup facility is available. So there is no

way to restore the existing data if any loss of any files or report.
3 PROPOSE PROJECT PROFILE
3.1 INTRODUCTION
The main objective of college management system is to automate all
functionalities of a college or university. Using this system you can manage all
college management work like admission, fees submission, time table
management and result declaration. Using this college management system you
can view or update data and information about students and staff easily. This
system helps in managing the activity like student admission, student
registration and fees submission. Admin can also retrieve information of
employee/student.
The COLLEGE MANAGEMENT SYSTEM can be used to store student

information like attendance, fees, and student result etc. admin can create report
regarding any student any time using this system. Using this system you can
register new student and their course details. You can submit students’ fees and
can check fees details anytime. You can create exam result and submit in this
system. Student can check their attendance online by logging to the system. You
can also add new employee in the system and can check details of the employee
easily. Student can also check course detail online from this system.
Using this system you can manage all information of all aspects of a college, its
students, faculties, Departments, marks and other curricular activities. College
management system provides the easiest way to manage all functionalities of a
college. This system facilitates colleges to maintain the functionality related to
college employees and their students.
College Management System can store and manage all data of the various
departments of a college like Administration, Attendance, Staff details etc. using
this system user can retrieve any information related to student, teacher and
fees. Using this system teacher can check student attendance anytime. This
system also help teacher to announce the result. College administration can also
manage college work easily. Admin can check leave, salary and other details of
teacher any time. They can also create time table of classes from this system.
The Library module is used for the data process of library and book accessing
for students and staffs.
Admin can also generate following reports from this system like
Student Report
Employee Report
Course Detail Report
Marks Detail Report
In the web application we can register as a user and user has three types:
Student, faculty and administrator. Administrator has the power to add new
faculty and student and can and edit and delete a faculty and student. A student
can register as user and can edit and delete his/her profile. The faculty can add
edit and delete marks for the student. All the student can see the marks.
In our proposed system we have the provision for adding the details of the
students by themselves. So the overhead of the college authorities and the
faculty is become less. Another advantage of the systems is that it is very easy
to edit the details of the student and delete a student when it found unnecessary.
The marks of the student are added in the database and so students can also
view the marks whenever they want.
Our proposed system has several advantages.
 User friendly interface
 Online student registration
 Fast access to database
 Less error
 More storage capacity
 Search facility
 Look and feel environment
 Quick transaction
All the manual difficulties in managing details in college have been rectified by
implementing computerization.
3.2 AIM
This document is the Software Requirement Specification (SRS) for the College
Management System for College (CMS) project .The purpose of this document
is to describe the functionality, requirements and general interface of the CMS.
1) Converting manual registration entry work to online registration :
 The new system will convert manual work to the computerized work.
 By converting manual work to the computerized work in that case it will

remove all paper work.
2) Increasing accuracy and work speed :
 By maintaining all the work on computer will increase accuracy as well

as speed of work.
 The report can be generated at any time of teacher wants it.
 It will easily use and the time consuming is decreased.
3) To Store information safely :
 To store the information of all the registered students.
 To keep track of admission information for the students.
 To keep information about attendance of all students.
 To keep marks of students.
 To store information about how much fees paid and how much remaining
to pay.
 To store information of every faculty.

4) To evolve information the latest technology:
 To evolved the latest technology using internet of traditional style.
 To minimize the human effort made by the staff evolved in the manual
student management process.
5) Generate Reports in time :
 To provide timely reports to the admin as and when required.
 To produce summarized and accurate reports required for the decision

making.
 To get the result quicker than the manual process.
 College information:
Through this service one can access the complete information
about the college campus such as courses available, admission procedure,
placements, college events, achievements etc.
 Student attendance status:

It gives the attendance status of students. Faculty will update the
attendance periodically and can be seen by students and parents.
 Students’ performance in exams:

This facility provides the performance of the student in each exam
which is conducted by university or college such as midterm
performance.
Marks obtained by students in exams will be updated by faculties that can

be access by students and parents.
 Exam Notification:
This facility notifies students and parents about examination
schedule.
 Events:
It will give information about different events that will be
conducted by college time to time. Information about these events will be
updated by administrator.
 Online assignments:
This service provides the facility to faculty to upload assignments
and to students to submit these assignments online.
 Information about staff:

It will help in maintaining complete information about college
faculty members such as their department, cadre, date of joining, salary,
etc. Administrator will register new faculties and remove their account
when they leave the college.
 To provide student detailed information and faculty details.

 To make admission procedure fast and easy.
 To inform student with time to time event information and notices.
 To inform parents about student activities through email.
 To generate separate student and faculty login Id and password.
3.3 SCOPE
 Access/ Search information.
 Login to the system through the first page of the application
 Change the password after logging into the system
 View/change his/her details.
 Can get help through the help option to view different features of the
system.
 Students can give feedback on college/staff/any other student.
 It is more efficient and convenient for colleges.
 It reduces manpower needed to perform the entire administration task by

reducing the paper works needed
 Using this system, Storing and retrieving of information is easy, so work

can be done speedily in time
 By above mentioned advantages, this system can be used by various

colleges, schools and other institutions.
 An admin login should be present who can read as well as remove any
uploads
3.4 TYPES OF PROJECT

 It is general system and hence there is unique web page layout and
format.
 It is web application.
 It requires window depends on the capability of the system.
 The whole manual work depends on the capability of the system.
 It requires many operators called administrator.

3.5 TECHNOLOGY / ENVIRONMENTS TOOLS:
PHP:
 PHP is an acronym for "PHP: Hypertext Pre-processor"
 PHP is a widely-used, open source scripting language
 PHP scripts are executed on the server
 PHP is free to download and use
PHP File
 PHP files can contain text, HTML, CSS, JavaScript, and PHP code
 PHP code are executed on the server, and the result is returned to the
browser as plain HTML
 PHP files have extension ".php".
Can PHP Do?
 PHP can generate dynamic page content
 PHP can create, open, read, write, delete, and close files on the server
 PHP can collect form data
 PHP can send and receive cookies
 PHP can add, delete, modify data in your database
 PHP can be used to control user-access
 PHP can encrypt data
Why PHP?
 PHP runs on various platforms (Windows, Linux, UNIX, Mac OS X, etc.)
 PHP is compatible with almost all servers used today (Apache, IIS, etc.)
 PHP supports a wide range of databases
 PHP is free. Download it from the official PHP resource: www.php.net
 PHP is easy to learn and runs efficiently on the server side
Do I Need?
To start using PHP, you can:
 Find a web host with PHP and MySQL support
 Install a web server on your own PC, and then install PHP and MySQL
Use a Web Host with PHP Support

If your server has activated support for PHP you do not need to do anything.
Just create some .php files, place them in your web directory, and the server will
automatically parse them for you.
You do not need to compile anything or install any extra tools.
Because PHP is free, most web hosts offer PHP support.
Set Up PHP on Your Own PC
However, if your server does not support PHP, you must:
 install a web server
 install PHP
 install a database, such as MySQL
The official PHP website (PHP.net) has installation instructions for

PHP: http://php.net/manual/en/install.php
MYSQL:
 MySQL is a database management system.
 MySQL databases are relational.

 MySQL software is Open Source.
 The MySQL Database Server is very fast, reliable, scalable, and easy to
use.
MySQL Server works in client/server or embedded systems.


 A large amount of contributed MySQL software is available.
Reason of using MySQL
 Secure Money Transactions

 On-Demand Scalability
 High Availability
 Rock-Solid Reliability
 Quick-Start Capability
SCALING MYSQL
 Long Development Time

 Replication
 Database Logging Costs
 Query Caches
 High Connection Churn
3.6 APPLICABILITY OF SYSTEM

As per the name of the system “College Management System”, suggests
this system will be used for manage the College Management System which
will be based on the computer totally. The functionality of this system will be
related to the education institutes likewise, schools, colleges, universities,
tuitions, etc.
Which changing the requirement of the particular authority, the system’s

functionality is based college management process.
It will store information about all the student’s admission, student’s fees,
and their marks, attendance. By using this information system will generate
necessary daily report and yearly report for the organization.
4. SOFTWARE ANALYSIS
4.1 Preliminary Investigation

During preliminary investigation, a system analyst typically follows a series of
steps. The exact procedure depends on the nature of the request, this size of the
project and importance.
Several Steps:
1. Understanding the problem
2. Define the project scope and constraints
3. Perform Fact-Finding
4. Evaluate Feasibility
5. Estimate Project Development Time and Cost
6. Present Results and Recommendation
4.2 Problem Identification

All activities like fees collection, attendance of student, maintain record,
admission process etc. are performed in manually way. So takes more times to
generate report for particular activities. All these processes are included in our
system. So totally work is performed computerized manner with online
registration instead of manually entering records of each student. In our system,
students take admission online; sitting at home files up form & makes payment
online too. Student selects their semester & the subject of which they want to
take tuitions of.
In our system, User have to login in the system. There are different menus are
available. User can select different option from the menu and select proper
command for different process result. For Example, Result data of student. The
user can generate a report either daily or weekly in few second. So the work
becomes faster than manual activities.
 By understanding the process of system:

 What are the forms to be included?
 How to manage student admission process?
 How to manage student fees information?
 How to manage student marks sheets?
 How to manage login process?
 What type of different reports they want?
 How to manage News and Events?
 How to manage all forms?
4.3 Feasibility Study

Whatever we think need not be feasible. It is wise to think about the
feasibility of any problem we undertake. Feasibility is the study of impact,
which happens in the organization by the development of a system. The
impact can be either positive or negative. When the positives nominate the
negatives, then the system is considered feasible. Here the feasibility study
can be performed in five ways such as technical feasibility, Economical
Feasibility, Operational Feasibility, Management feasibility and time-
feasibility.
4.3.1) Technical Feasibility:
We can strongly say that it is technically feasible, since there will not be
much difficulty in getting required resources for the development and
maintaining the system as well. All the resources needed for the development of
the software as well as the maintenance of the same is available in the
organization here we are utilizing the resources which are available already.
4.3.2) Economical Feasibility:
Development of this application is highly economically feasible .The

organization needed not spend much money for the development of the system
already available. The only thing is to be done is making an environment for the
development with an effective supervision. If we are doing so, we can attain the
maximum usability of the corresponding resources. Even after the development,
the organization will not be in condition to invest more in the organization.
Therefore, the system is economically feasible.
4.3.3) Operational Feasibility:
An estimate should be made to determine how much effort and care will go
into the developing of the system including the training to be user. Usually,
people are reluctant to changes that come in their progression.
The computer initialization will certainly affected the urn over, transfer and
employee job status. Hence an additional effort is to be made train and re-
educate the users on the new way of the system.
4.3.4) Management Feasibility:
At the management point then this software have more details about students,
faculties and administrators. So, every detail has been stored in database, so it is
one type of management. Thus it seems that the project is feasible to
management.
4.3.5) Time Feasibility:

Time feasibility describes the time cost for concerting the present system to new
system. The aspect of time feasibility for our system takes approximate. This
system is developing under this time period. So we can say that this system is
time feasibility.
4.4 Requirement Analysis

4.4.1 Fact Finding Technique
A fact finding study was undertaken to study the activities involved in
marketing system of company. We have visited the various person of the
marketing system. The existing system was studied by means of
1) Interview
2) Record Review
3) Observation
1) Interview
User’s interviews were conducted to determine the qualities information. These
interviews which were unstructured interviews provided opportunity that
gathered information from respondents who are involved in the process for a
long time.
These interviews provided information such as:
A. Distinguish between fact and opinion.
B. Limitation of existing system.
C. Further any clarification obtained subsequently.
Interview allows the analyst to collect or gather the information from the
individual or group who are generally the current user of the existing system or
potential user of the proposed system.
They may be mangers or employee of the firm itself who provide the data for
the proposed system and who be affected by it.
Interview could be (a) structured (b) unstructured.
Structured Interview:
Here, it uses standardized questions as far as response of the questions is
concerned; they are divided into two formats:
(a) Open response format:
Here the questions are answered in one’s word.
(b) Closed response format:
Here set of prescribed answers are used
Unstructured interview:
Here the questions are worded to suit the respondent that provide the
information about the areas overlooked or not thought to be important.
Advantages and Disadvantages of structured and unstructured interviews:

ADVANTAGES:
 Ensures uniform wording of questions to all respondents.
 Easy to administer and evaluate.
 Less interview training required.
 Result in shorter time.
Unstructured Interview:
 Questions can be worded to suit the respondent.
 May produce the information about the areas overlooked or not thought
to be important.
DISADVANTAGES:
 Cost of preparation is high.
 Such high level of structure may not always be suitable.
 Some respondent may resist to such structure.
Unstructured Interview:
 Inefficient use of interviewer and respondent time.
 Results take a longer time.
 Extra time required for the collection of essential facts.
 The success of the interview depends on the skill of the interviewer and
his/her preparation for the interview.
 Analysts must also be aware of the kinds of difficulties at some interview,
and must know how to deal with the potential problems.
2. Record Review
To gather details about the system many kinds of records and reports were
reviewed. The study covered:
A. Standard operating procedure.
B. Reports generated by the existing system.
C. Document flow (Input/output) of the marketing.
To gather details about the recruitment analysis system, many kinds of records
and reports were reviewed. The study covered.
 Standard operating procedure system
 Reports generated by the existing system.
 Document flow (input/output) of the recruitment analysis system.
 Process of generating reports.

 Process storing the applicant and company information.
 Types and format of database registers.
For gathering basic needs and functionalities, I was meeting to the
programmer of intellect personally to understand required functionalities, also
noted down some useful features to be included. By analyzing the information
functionalities, also noted down some useful features to be included. By
analyzing the information and we have understand following process
requirement.
We analyzing our gathered information and we have decided that system

should have following functionalities.
 College Management System:

 Student
 New student registration
 Delete student registration detail
 Edit student registration detail
 Search student
 Admin
 New faculty registration
 Delete faculty registration detail
 Edit faculty registration detail
 Search faculty
 Event
 New Event add
 Delete Event detail
 Edit Event detail
 Search Event
 Fees
 Add new fees receipt
 Display left to pay student list
 Send SMS for not paying fees
 Marks
 Add new mark of External exams
 Add percentages
 List Student marks
 Extra constrains
 User friendly
 Speed of system
 GUI interface
4.4.2 timeline chart

Task Month1 Month2 Month3
1) Requirement analysis
Collected requirement from our guide
Analyse gathered information
Determine scope of the system
Milestone: requirement Analysis complete
2) Planning and risk analysis
Analyse data for possible risks
Identify technical risks
Determine different modules
Milestone: Planning completed
3) Designing
Design basic interface of the site
Design database tables
Design web form for modules
Milestone: designing completed
4) Coding and integrating modules
Implement logic for different modules
Implement database connectivity
Integrate different modules
Implement Report
Milestone: coding completed
5) Testing
Validate input control and check accuracy of
Reports
Milestone: testing completed
6) Documentation
Milestone: documentation completed
4.4.4 Model with Justification:

As a software engineering paradigm we have used “prototype model”.
Why prototype model?
Because of following problems we haven’t used “Linear sequential Model”.
Real time project rarely follows the sequential flow that the model proposes.
Thought the linear model can accommodate iteration, it does so indirectly.
In this model we also have to wait for others, because of this we cannot
complete our work in specific period of time.
The prototyping paradigm begins with requirement gathering, developer and

customer meet and define the overall objectives and websites, identify whatever
requirement are known and outline areas where further definition mandatory.
A “Quick Decision” then occurs. The quick decision focuses on representation

of those aspects of the website that will be visible to the customer/users.
Diagram of Iterative Model

Advantages of Iterative Model
 In iterative model we can only create a high-level design of the

application before we actually begin to build the product and define the
design solution for the entire product. Later on we can design and built a
skeleton version of that, and then evolved the design based on what had
been built.
 In iterative model we are building and improving the product step by

step. Hence we can track the defects at early stages. This avoids the
downward flow of the defects.
 In iterative model we can get the reliable user feedback. When presenting
sketches and blueprints of the product to users for their feedback, we are
effectively asking them to imagine how the product will work.
 In iterative model less time is spent on documenting and more time is

given for designing.
Disadvantages of iterative model
 Each phase of an iteration is rigid with no overlaps

 Costly system architecture or design issues may arise because not all
requirements are gathered up front for the entire lifecycle
4.4.4 FLOW CHART
[Figure no :- 1]
Registration Flow Chart
start
User Details
Error
Check account message
False
True
Validate and
check
Insert Data into
database
False database
True
Successful
message
End
Login Process:-
Start
Admin name and

password
Error message
False
Validate and
check database
True
Successful
message
End
[Figure no:- 2]
4.4.5 UML
Unified Modelling Language (UML) is a general purpose modelling language.
The main aim of UML is define a standard way to visualize the way a system
has been designed. It is quite similar to blueprints used in other fields of
engineering.
UML is not a programming language, it is rather a visual language. We use

UML diagrams to portray the behaviour and structure of a system. UML helps
software engineers, businessmen and system architects with modelling, design
and analysis. The Object Management Group (OMG) adopted Unified
Modelling Language as a standard in 1997. It’s been managed by OMG ever
since. International Organization for Standardization (ISO) published UML as
an approved standard in 2005. UML has been revised over the years and is
reviewed periodically.
Class Notation
UML class is represented by the following figure. The diagram is divided into
four parts.
 The top section is used to name the class.
 The second one is used to show the attributes of the class.
 The third section is used to describe the operations performed by the

class.
 The fourth section is optional to show any additional components.

Classes are used to represent objects. Objects can be anything having properties and
responsibility.
Object Notation
The object is represented in the same way as the class. The only difference is
the name which is underlined as shown in the following figure.
As the object is an actual implementation of a class, which is known as the instance of a

class. Hence, it has the same usage as the class.
Interface Notation
Interface is represented by a circle as shown in the following figure. It has a name which is
generally written below the circle.
Interface is used to describe the functionality without implementation. Interface is just like a
template where you define different functions, not the implementation. When a class
implements the interface, it also implements the functionality as per requirement.
Collaboration Notation
Collaboration is represented by a dotted eclipse as shown in the following figure. It has a
name written inside the eclipse.
Collaboration represents responsibilities. Generally, responsibilities are in a group.
Use Case Notation

Use case is represented as an eclipse with a name inside it. It may contain additional
responsibilities.
Use case is used to capture high level functionalities of a system.

Actor Notation
An actor can be defined as some internal or external entity that interacts with the system.
An actor is used in a use case diagram to describe the internal or external entities.
Initial State Notation

Initial state is defined to show the start of a process. This notation is used in almost all
diagrams.
The usage of Initial State Notation is to show the starting point of a process.
Final State Notation

Final state is used to show the end of a process. This notation is also used in almost all
diagrams to describe the end.
The usage of Final State Notation is to show the termination point of a process.
Active Class Notation

Active class looks similar to a class with a solid border. Active class is generally used to
describe the concurrent behavior of a system.
Active class is used to represent the concurrency in a system.

Component Notation
A component in UML is shown in the following figure with a name inside. Additional
elements can be added wherever required.
Component is used to represent any part of a system for which UML diagrams are made.
 Super Admin Use Case diagram
Manage
Student
Manage
Admin
Manage
Event
Manage
Login Subject
Manage
Counceller
Super Admin
 Super Admin (Manage Student)Use case diagram
Manage
Gallery
Manage
Semester
Manage
Faculty
Manage
Stream
[Figure no :- 3]
 Super Admin (Manage Students)Use case diagram
View
Detail
Login Manage Edit detail

Students
Super Admin Delete

detail
[Figure no: - 4]
 Super Admin (Manage Faculty)Use case diagram
View
detail

Faculty
Super Delete
Admin detail
[Figure no: - 5]
 Super Admin (Manage Gallery)Use case diagram
Add
Gallery
View
Gallery
Login Manage Edit

Gallery Gallery
Super Admin Delete

Gallery
Active/
Deactive
Gallery
[Figure no:-6]
Add Event
 Super Admin (Manage Event)Use case diagram
View Event
Login Manage Edit Event
Event Add Event
Delete
Event
Active/Dea
ctive Event
View
Event

Event
Super Admin Delete

Event
Active/
Deactive
Event
[Figure no: - 8]
Add Event
 Super Admin (Manage Counceller)Use case diagram
View Event
Event Add
Delete
Counceller
Event
Active/Dea
ctive Event
View
Counceller
Login Manage Edit

Counceller Counceller
Super Admin Delete

Counceller
Active/
Deactive
Counceller
[Figure no: - 9]
Add Event
 Super Admin (Manage Stream)Use case diagram
View Event
Event Add
StreamDelete
Event
Active/Dea
ctive Event
View
Stream
Login Manage Edit

Stream Stream
Super Admin
Delete
Stream
Active/
Deactive
Stream
[Figure no :- 10]
Add
Admin
 Admin Use Case diagram
View
Admin
Manage
Student
Manage
Login Manage EditProfile
Admin
Admin
Manage
Event
Manage
Delete
Subject
Admin
Login
Manage
Counceller
Active/
Deactive
Admin Manage
Admin
Gallery
Manage
semester
Manage
Faculty
Manage
Stream
[Figure no: - 10]

 Admin (Manage Faculty)Use case diagram
View
Faculty
Manage
Login Faculty
Active/
Deactive
Faculty
Admin
[Figure no :- 11]
View
Student
Login Manage
Student
Active/
Deactive
Student
Admin
[Figure no :- 12]
View
Event
Login Manage
Event
Active/
Deactive
Event
Admin
[Figure no: - 13]

 Admin (Manage Gallery)Use case diagram
View
Gallery
Login Manage
Gallery
Active/
Deactive
Gallery
Admin
[Figure no :- 14]
 Admin (Manage Counceller)Use case diagram
View
Counceller
Manage
Login Counceller
Active/
Deactive
Admin Counceller
[Figure no: - 15]

 Admin (Manage Stream)Use case diagram
Add
Stream
View
Stream
Login Manage Edit

Stream Stream
Delete
Admin Stream
Active/
Deactive
Stream
[Figure no :- 16]
 Admin (Manage Profile)Use case diagram
Edit Detail
Login Manage
Profile
View
Detail
Admin
[Figure no: - 17]

 Student Use Case diagram
View
Attendance
Manage
Profile
View Event
View
Subject
Login
View
Counceller
Student View
Gallery
View
semester
View
Faculty
View
Stream
[Figure no: - 18]

 Student (Manage Profile)Use case diagram
View
Profile
Login Manage Edit Profile

Profile
Delete
Student Profile
[Figure no :- 19]
 Faculty Use Case diagram
View
Student
Manage
attendance
Manage
Profile
View
Subject
Login
View
Counceller
Faculty
View Event
View
semester
View
Subject
View
Stream
[Figure no: - 20]

 Faculty (Manage Profile)Use case diagram
View
detail

Profile
Faculty Delete
detail
[Figure no :- 21]
 Faculty (Manage attendance)Use case diagram
Add
attendance
View
attendance
Login Manage Edit

attendance attendance
Faculty Delete
attendance
[Figure no: - 22]

 Activity Diagram for Student/Faculty Registration
[Figure no: - 22]

 Activity Diagram for Student/Faculty Registration
[Figure no :- 23]
 Sequence Diagram for Login
[Figure no :-24]
 Sequence Diagram for Registration
[Figure no:-25]
Class diagram
super Admin
Manage Admin_Id Int manage

Admin_Type Enum
Admin Faculty
add Admin()
View Faculty()
Admin_Id Int Faculty_Id Int
View Student()
Admin_Type Enum Faculty_Name Enum
View Profile() View Profile()
View Faculty() View Semester()
View Student() View Student()
manage manage
manage
Event Gallery Student

manage
Event_Id Int Gallery_Id Int Student_Id Int
Event_Name Enum Event_Image Varchar Studnet_Name Enum
add Profile() add Image() View Student()
view Event() view Image() Add Student()
delete Event() delete Image() edit Student()
Manage manage manage
Semester
Stream Subject
Semester_Id Int
Stream_Id Int Subject_Id Int
Semester_Name Varchar
Stream_Name Varchar Subject_Name Varchar
add Semester()
add Semester() add Subject()
view Semester()
view Semester() view Subject()
delete Semester()
delete Semester() delete Subject()
[Figure no: - 26]

4.4.6 Process Specification
Process specification is use to describe the bubble (process) which defined in

DFD. It’s a one kind of mini specification of all function and process. We do
specification for the lowest level (Refined level/Last Level) bubble in DFD.
It describes all the inputs and outputs to the process and also describes the
functionality of the process.
 Process Specification of our systems:

1) Search Process
Request Search Response for search

Search
This process is used to perform search operation. It takes input from

user. User sends their data and then search events are performed. After
performing search this process produce the output and result to the
Student/Faculty_Master.
2) Registration Process
User Info User Info

Registration
Registration is used to make unregistered user in to the registered user.

This take inputs like: user name, address, state, area, and city, contact no
etc. from user and store all those user information in
student_master/faculty table.
3) Login Process:
Email Id & Password Provide Authority

Login
Login Process is used to perform the login operation and provide the
authority to user. This takes password and email id as input from the user
and gives the authority as output to the
SuperAdmin/admin/student/faculty.
4) Forgot Password Process:
Email Id Password Sent To Email

Forgot Password
Forgot password is used to get the password of Student/Faculty/admin.

This process takes email id. Security question as an input from user
and sends the password as output to the use.
5) Report Process :
Report Request Produce Report

Report
Report process is used to generate the various reports of the system. This takes
request of request as input from the admin. And it produces many types of
reports as an output and sends these to Admin.
6) Change Password :
Old Password New Password

Change Password
This process is used to change the password and create a new password.
This takes old password as input from the user and creates a new
password as an output which send to the user.
7) Edit Profile :
User Info Save Edited Info

Edit Profile
Edit Profile process is used to edit all the information of the users. Here user
sends his all information like: name, address, contact no, city, state etc. to
change. It takes all information as input and create a new profile as an output.
8) Contact us Process:
Take Contact us Send Contact US to admin

Feedback
9) Student Registration
4.4.7 Data dictionary

1) Change Password
Name Change Password

Alias None
Where Used Change Password and verify login
How Used Input/output
Description Change password=old password +
new password + confirm password
2) Stream Detail
Name Stream Detail

Alias None
Where Used Accepting and retrieving Stream
Information from database
Description Stream Detail=Stream_Name
4) Semester Detail
Name Semester Detail

Alias None
Where Used Accepting and retrieving Semester
Description Semester Detail=Semester_Id +
Semester_Name+Degree_Id
5) Subject Detail
Name Subject Detail

Alias None
Where Used Accepting and retrieving Subject
Description Subject Detail=subject_Id +
Degree_Id+Semester_Id +
subjectname
6) Division Detail
Name Section List

Alias None
Where Used Accepting and retrieving Section
Description Section List=Division_Id +
Division_Name + Degree_Id
+Semester_Id
7) Student Detail
Name Student Detail

Alias Students
Where Used Accept student details for
registration, retrieving data for
modification and delete the
particular student details.
Description Studentdetail=Student_Id +
Student_RollNo + gender + DOB +
Contact_No + address + city + state
+ image + Singature + username +
password
8) Faculty detail
Name Faculty Detail

Alias FacultyReg
Where Used Accepting and retrieving faculty
Description Faculty detail=Faculty_Id+
Faculty_Name + Qualification +
Faculty_Joining_Date + gender +
Contact_No + address + DOB +
state + city + country + username +
password
9) Event Detail
Name Event Detail

Alias Event list
Where Used Accepting and retrieving Event
Description Event detail=Event_Id +
Event_Name + Event_Date +
Faculty_Id + image
4.4.8 Data dictionary

5. SOFTWARE DESIGN
The overall objective in the development of database has been to treat

data as an organizational resource and as an integrated whole. DBMS allow data
to be protected and organized separately from other resources. Database is an
integrated collection of data. The most significant form of data as seen by the
programmers is data as stored on the direct access storage device. This is the
difference between logical and physical data.
Database files are the key source of information into the system. It is the
process of designing database files, which are the key source of information to
the system. The files should be properly designed and planned for collection,
accumulation, editing and retrieving the required information.
The organization of data in database aims to achieve three major objectives:-
 Data integration.
 Data integrity.
 Data independence.
5.2 Database Design

student_master
Field Name Data type Description Constraint
Student_ID int(11) Stores The Primary Key
Unique ID for
Student
Student_First_Name varchar(25) Stores Students --
First Name
Student_Middle_Name varchar(25) Stores Students --
First Name
Student_Last_Name varchar(25) Stores Students --
First Name
Student_Gender varchar(10) Male or female --
Student_ContactNo int(10) Stores Students --
10 digit mobile
number
Student_Parent_ContactNo int(10) Stores Students --
10 digit mobile
number
Student_Address_Line_1 varchar(250) -- --
Student_Address_Line_2 varchar(250) -- --
Student_Zipcode int(7) Stores the area --
wise pin code of
student
Student_Email varchar(30) -- --
Student_Password varchar(120) Stores Students --
password in
encrypted form
Student_DOB date Students Date Of --
Birth
Student_DOJ date Students Date of --
Registration
Student Category enum(‘SC’, ‘ST’, Category Of --
‘SEBC’, ‘general’) Student
Student_Caste varchar(10) Students Caste --
Student_SubCaste varchar(15) Student’s Sub --
caste
Student_Religion varchar(15) Stores Student’s --
Religion
Student_Image varchar(250) Stores address of --
student’s image
Student_Signature varchar(250) Stores student’s --
Signature
Student_RollNo varchar(7) Stores Student’s --
Roll No
Student_Status enum(‘active,deactive’ -- --
)
Student_Entry_Date datetime -- --
Student_Last_Update_Tim datetime -- --
e
admin
Field Name data type Description Constraint
Admin_No int(11) Stores The Unique Primary Key
Id of Admin
Admin_Name varchar(50) Stores Name Of --
Admin
Admin_Password varchar(150) Stores Admin --
Password in
Encrypted Form
Admin_Email varchar(50) Stores Email Id Of --
Admin
Admin_Gender varchar(6) Stores Gender Of --
Admin
Admin_DOB date Stores DOB Of --
Admin
Admin_JoiningDate date Stores Joining --
Date Of Admin
Admin_Salary double Stores Salary Of --
Admin
Admin_ContactNo bigint Stores Contact --
Number Of Admin
Admin_AddressLine1 varchar(500) Stores Address --
Number Of Admin
Admin_AddressLine2 varchar(500) Stores Address --
Number Of Admin
Admin_CityId int -- --
Admin_StateId int -- --
Admin_Zipcode int -- --
Admin_Category enum(‘sc’, ‘st’, ‘obc’, -- --
‘general’)
Admin_Religion varchar(20) -- --
Admin_Caste varchar(20) -- --
Admin_Photo varchar(250) Stores Path of --
Admin Photo
Admin_Signature varchar(250) Stores Path Of --
Admin Signature
Admin_Type enum(‘superadmin’, Stores the type of --
‘administrator’) admin
Admin_Status enum(‘active’, -- --
‘deactive’)
Admin_Entry_Date datetime -- --
Admin_Update_Date datetime -- --
attendance
Attendance_Id int(11) Stores Unique Id Primary Key
Of each
attendance Record
Semester_Id int(11) Stores Id Of Foreign Key
Current Semester
Stream_Id int(11) Stores Id Of Foreign Key
Stream
Subject_Id int(11) Stores Id Of Foreign Key
Subject
Attendance_Date date Stores date for Foreign Key
which attendance
for which
attendance is being
taken.
Attendance_Status enum(‘Present’, Stores the status is --
‘Absent’, ‘Leave’) student is Present,
on leave or is
absent
Attendance_Entry_Date datetime Stores Entry Date --
OF Attendance
Attendance_Update_Time datetime Stores Time If --
Attendance is
Updated
city
City_Id int(11) Stores Unique Id Primary Key
Of City
City_Name varchar(50) Stores Name Of --
City
State_Id int(11) Stores Id Of State Foreign Key
City_Status enum(‘Active’, -- --
‘Deactive’)
City_Entry_Date datetime -- --
City_Update_Time datetime -- --
State
State_Id int(11) Stores Unique Id Primary Key
Of State
State_Name varchar(50) Stores Name Of --
State
State_Status enum(‘Active’, -- --
‘Deactive’ )
State_Entry_Date datetime -- --
State_Update_Time datetime -- --
contact_us
Contact_Us_Id int(11) Stores Unique id Primary Key
for each contact
entry
Contact_Us_Name varchar(50) Stores name of --
contacting person
Contact_Us_Email varchar(50) Stores Email Of --
Contacting PErson
Contact_Us_Description varchar(500) Detailed --
description of
Contact Problem
Contact_Us_Entry_Date datetime -- --
Contact_Us_Status enum(‘Active’, -- --
‘Deactive’)
Contact_Us_Entry_Time datetime -- --
counceller
Councelling_ID int(11) Stores Unique Id Primary Key
Of Each Entry
Councelling_Stream_Id int(11) Stores Id Of Foreign Key
Stream
Councelling_Division_Id int(11) Stores Id Of Foreign Key
Division
Faculty_Id int(11) Id of the Foreign Key
Counceller
Councelling_Status enum(‘Active’, -- --
‘Deactive’)
Councelling_Entry_Date datetime -- --
Councelling_Last_Update_Dat datetime -- --
e
division
Division_Id int(11) Stores Unique Id Primary Key
od division
Division_Name varchar(5) Name Of Division --
Semester_Id int(11) Id Of Semester Foreign Key
Stream_Id int(11) Id Of Stream Foreign Key
Division_Status enum(‘Active’, -- --
‘Deactive’)
Division_Entry_Status datetime -- --
Division_Last_Update_Tim datetime -- --
e
event
Event_Id int(11) Unique Id Of Primary KAey
Event
Event_Name varchar(30) Name Of Event --
Event_Date datetime Date and time of --
event
Event_Category_Id int(11) Category to which Foreign Key
event belongs
Event_Status enum(‘Active’, -- --
‘Deavtive’)
Event_Entry_Date datetime -- --
Event_Update_Time datetime -- --
event_Category
Field Name Data Type Description Constraint
Event_Category_Id int(11) Unique Id Of Primary Key
Category
Event_Category_Name varchar(50) Name Of --
Category
Event_Category_Status enum(‘Active’, -- --
‘Deactive’)
Event_Category_Entry_Time datetime -- --
Event_Category_Update_Tim datetime -- --
e
gallery_Category
Gallery_Category_Id int(11) Unique Id Of Primary Key
Category
Gallery_Category_Name varchar(30) Name Of --
Category
Gallery_Category_Description varchar(150) -- --
Event_Category_Status enum(‘Active’, -- --
‘Deactive’)
Event_Category_Entry_Time datetime -- --
gallery
Gallery _Id int(11) Unique Id Of Primary Key
Category
Gallery_Images varchar(30) Name Of --
Category
Gallery_Category_Id varchar(150) -- --
Gallery_Status enum(‘Active’, -- --
‘Deactive’)
Gallery_Entry_Date datetime -- --
inquiry
Inquiry_Id int(11) Stores Unique Id Primary Key
Of Inquiry
Inquiry_Subject varchar(100) Short description --
of inquiry
Inquiry_Description varchar(500) Brief description of --
inquiry
Inquiry_Name varchar(50) Name of user who --
is inquiring
Inquiry_Email varchar(50) Email Id of inquiry --
Person
Inquiry_Contact_No Bigint Contact number --
Inquiry_Status enum(‘Active’, -- --
‘Deactive’)
Inquiry_Entry_Date datetime -- --
Inquiry_Update_Date datetime -- --
leave_Master
Leave_Id int(11) UniqueId for each Primary Key
leave request
Leave_Level enum(‘student’, The user who --
‘faculty’) applies for leave
Student_Id int(11) If Leave_Level is Foreign Key
Student
Faculty_Id int(11) If Leave_Level is Foreign Key
Faculty
Leave_From_Date date -- --
Leave_To_Date date -- --
Leave_Reason varchar(250) Reason For Leave --
Councelling_Id int(11) Id Of the Foreign Key
counceller
Leave_Entry_Date datetime -- --
Leave_Status enum(‘Requested’, -- --
‘Granted’, ‘Rejected’)
semester
Semester_Id int(11) Unique Key For Primary Key
each Semester
Semester_Name varchar(10) Name of semester --
Stream_Id int(11) Stream to which Foreign Key
semester Belongs
Semester_Status enum(‘Active’, -- --
‘Deactive’)
Semester_Entry_Date datetime -- --
Semester_Last_Update_Tim datetime -- --
e
stream
Stream_Id int(11) Unique Key Of Primary Key
Stream
Stream_Name varchar(10) Name of Stream --
Stream_Description varchar(50) -- --
Stream_Duration int(11) Duration of course --
in years
Stream_Status enum(‘Active’, -- --
‘Deactive’)
Stream_Entry_Date datetime -- --
Stram_Last_Update_Tim datetime -- --
e
student_Class
Student_Class_Id int(11) Unique Id For each --
student’s Class
Registration
Student_Id int(11) Unique Id Of Foreign key
Student
Stream_Id int(11) Unique Id of Foreign Key
stream
Semester_Id int(11) Unique id of Foreign Key
Semester
Division_Id int(11) Unique Id Of Foreign Key
Semester
Student_RollNo int(11) Unique Id Of Foreign Key
Semester
subject
Subject_Id int(11) Unique Id Of Primary Key
Subject
Subject_Name varchar(20) Name Of Subject --
Stream_Id int(11) Unique Id Of Foreign Key
Stream
Semester_Id int(11) Unique Id of Foreign Key
Semester
Subject_Status enum(‘Active’, -- --
‘Deactive’)
Subject_Entry_Date datetime -- --
Subject_Last_Update_Tim datetime -- --
e
Faculty
Faculty_Id int(11) Unique Id Of Primary Id
Faculty
Faculty_First_Name varchar(50) First Name of --
faculty
Faculty_Middle_Name varchar(50) Middle Name of --
faculty
Faculty_Last_Name varchar(50) Last Name of --
faculty
Faculty_DOB date Date Of Birth --
Faculty_Joining_Date date -- --
Faculty_Teachable_Subjects int(11) -- --
Faculty_Salary double -- --
Faculty_email varchar(50) Email Id Of --
Faculty
Faculty_Password varchar(250) Password To Log --
In Later
Faculty_Contact_No bigint Phone Number Of --
Admin
Faculty_Qualification varchar(300) Qualifications --
Faculty_Extra_Achievemen varchar(500) Extra --
t Achievements
After Or Before
Getting into
college
Faculty_Address_1 varchar(500) -- --
Faculty_Address_2 varchar(500) -- --
Faculty_Zipcode int Zonal Pin Code --
Faculty_Type enum(‘adhoc’, ‘asst. Temporary Or --
prof’, ‘prof’) Permanent
Faculty_Religion varchar(50) -- --
Faculty_Category enum(‘general’, -- --
‘obc’, ‘sc’, ‘st’)
Faculty_Caste varchar(50) -- --
Faculty_Image varchar(500) Path of Image --
Faculty_Signature varchar(500) Signature In --
Picture Format
Faculty_City int(11) -- Foreign Key
Faculty_State int(11) -- Foreign Key
Faculty_Status enum(‘active’, -- --
‘deactive’)
Faculty_Entry_Time datetime -- --
Faculty_Update_Time datetime -- --
Forgot_password_otp int Usedwhen user --
forgets his
password
5.2.1 Justification of Normalization

Normalization is a technique of separating redundant fields and braking
up a large table in to smaller one. It is used to avoid insertion, deletion
and updating anomalies. All the tables have been normalized up to the
third normal form. In short the rules for each of the three normal forms
are as below:
 First Normal Form

A relation is said to be in 1NF if all the under lying domain of attributes
contain simple individual values.
 Second Normal Form

The 2NF is based on the concept of full functional dependency. A relation
said to be in 2NF if and only if it is in 1NF and every non-key attribute is
fully functionally dependent on candidate key of the table.
 Third Normal Form

The 3NF is based on the concept of transitive dependency. A relation 2NF
is said to be in 3NF if every non-key attribute is non-transitively.
5.3 Architectural Design
Design has been described as a multistep process in which representation

of data and program structure, interface characteristics, and procedural
detail are synthesized from information requirements.
Architectural design represents the structure of data and program

components that are required to build a computer-based system. It
considers the architectural style that the system will take, the structure
and properties of the components that constitute the system, and the
interrelationships that occur among all architectural components of a
system.
Ever since the first program was divided into modules, software systems
have had architectures, and programmers have been responsible among
the modules and the global properties of the assemblage. Historically,
architectures have been often implicit-accidents off implementation, or
legacy systems of the past. Good software developers have often adopted
one or several architectural patterns as strategies for system organization,
but they use these patterns informally and have no means to make them
explicit in the resulting system. Architectural design focuses on the
representation of the structure of software components, their properties,
and interactions.
The software architecture of program or computing system is the
structure or the system, which comprise software components, the
externally visible properties of those components, and the relationships
among them.
The architecture is not the operational software. Rather, it is a

representation that enables a software engineer to
1) Analyse the effectiveness of the design in meeting is stated

requirements.
2) Consider architectural alternatives at a stage when making design
changes is still relatively easy.
3) Reducing the risks associated with the construction of the software.
This process is used to get feedback of user. It takes different types of

feedback like: Bidding, products, service, common feedback from the
user as an input. Admin takes this all feedback to view, this process send
all this feedback to Admin as an output.
5.4 User Interface Design
User interface design creates an effective communication medium a

human and a computer. A software engineer designs the user interface by
applying an iterative process that draws on predefined design principles.
User interface design describe how the system communication and how it
reliable with the user. This design is generally developed for the better
understanding and how it reliable with the user.
The most important principle of user interface design is “know the user,
know the task”.
In our system, we follow all above process to satisfy user and to build a
good interface design.
The following are the characteristic of good interface design.
1) Speed of use.
2) Speed of recall.
3) Attractiveness.
4) Consistency.
5) Feedback.
6) User guidance and online help.
7) Error recovery.
8) Speed of learning.
9) Provide for flexible interaction.
5.6 Security Issues
Our software is totally secure.
 Admin can change the password as and when require. So there is

no issue to enter into system by anyone as if he/she fortunately
knows the password.
 In forget password link, forget password is send to the
administrator’s email account, if admin provide correct question
and answer. So there is no case to hack the password if any
strangers give correct answer or question.
 Also the password is stored in the database in Encrypted form.
5.7 Quality Measures
To produce high quality system is goal to develop the software with all kinds of
the satisfaction with user, cost and assurance, and also with the developers.
If requirement is not consider or gathered properly then the lack of the adaption
or conformation to requirement is also lack of quality. So build quality software
first we define and consider the meaningful and useful requirement.
To develop quality software we must compare our software with some known
data. So for that we measure our software in different divisions.
1) Software operation
2) Software revision
3) Software transition
1) Software operation :
In these we define the quality with correction, reliability, usability,
efficiency, and integrity.
In our system there are many different modules and sub modules are
exists and to manage their quality we follows all above factors.
 Correction: If any changes occurred in our modules then we easily correct
them. So the qualities of those modules become as usual and decrease.
 Integrity: If all modules are complete successfully then we integrate
them and manage the quality of all those modules.
2) Software Revision :
In these we concerned with those aspects related to modification of the
program such as maintainability, testability.
3) Software Transition :
It deals with quality factors like portability, interoperability and
reusability.
 Interoperability: is the effort required to couple the system with other
system and the relation of two modules.
 Reusability: is the extent to which parts of software can be reused in other
related application.
Quality in different views:

1) Quality with user satisfaction:
If user satisfied with all requirements of the product and accept the
system with no any excuses then we save that our software has good
quality and adaptability. To work on the user satisfaction we consider
the following aspect.
6. SOFTWARE CODING
6.1 Software Design

The goal of the coding phase is to translate the design. The aim in this
phase is to implement the design in the best possible manner. Well-known code
can reduce the testing and maintenance effort. During coding, the focus should
on developing programs that are easy to read and understand and not simply on
developing the programs that are easy to write, Simplicity and clarity should be
strived for during the code phase. An Important concept that helps the
understandability of the program is structured programming. The program that
should be organized as a sequence of statement and during execution of the
statements is executed into the sequence given in the program. There are many
different criteria for judging of the program, execution time and required
memory.
f- Snap Shots
6.2
Admin Side
SuperAdmin/Admin Login Page
Add Stream
Add City
Add Event
User Side
Fees
Home page
About us
Facility
B.com Student’s Strength

Faculty attendance
Change Password
Check Leave Application

Faculty List
Faculty Login Page
Faculty Profile
Faculty Attendance View

Faculty Forget Password

Forget Password Send Email ID

Change Password
Faculty Leave Management

Exam InternalTime Table
Profile Card
Print Out Profile Card

Contact Us
View Event Category
View Event
7. SOFTWARE TESTING
Is the menu bar displayed in the appropriate contested some system retaliated
futures included either in menus or tools? Do pull-Down menu operation and
tool-bars work properly? Are all menu function and pull down sub function
properly listed: is it possible to invoke each menu function using a logical
assumption that if all parts of the system are correct, the goal will be
successfully achieved. ? In adequate testing or non-testing will leads to errors
that may appear few months later. This creates two problems:
1) Time delay between the cause and appearance of the problem.
2) The effect of the system errors on files and records within the system.
The purpose of the system testing is to consider all the likely variations to
which it will be suggested and push the system to limit. The testing process
focus on the logical intervals of the software ensuring that all statements have
been tested and on functional interval is conducting tests to uncover errors and
ensure that defined input will produce actual results that agree with the required
results.
Program level testing, modules level testing integrated and carried out.
7.1 Test Cases and Test Data Design
We use many types of testing to improve the quality of our system and
develop a acceptable system by the client satisfaction we do validation,
verification and many more testing. But implements all these testing first we
should know how to develop the testing. Therefore, to improve the testing we
use two important parts for testing.
1. Test Case
2. Test Data
1) Test Case:-
Test Case is one kind of a formal discussion of predefine documentation
at the analysis phase. It is not used as a practical testing. It is only a
theoretical discussion. In this we discuses following:
 A Starting Stage:
In which we discuss the requirements of customer and checks that all
information which was define at analysis phase is full or no. we discusses
all basis requirements related to auctions is match with document or not.
 Event and Module to which software must Response:

Here we discuss that all events or modules which we developed, are
accepted the all inputs and data which user wants to puts and data which
is useful for that module or not. In our system we checks that the inputted data
for registration, service and test drive booking are related to that entire event or
not.
 Expected Output For Ending Stage:

At this stage we do discuses about the expected output of the all events
and modules. We checks that all output and results are matched with all
requirement of the client or not. In our system we discuss that search
modules, view Enquiry modules, view reports module. View user
module, etc. produces the resultant output or not.
1.1) Things which are useful for test cases:
 Analysis phase documentation is very useful when we preparing test case.

 Our online auction system is objet oriented so we used use case diagram
and activity model for preparing Test case
 Test Case
1) Login Process:
Test Test case description Expected Result Pass/Fail Actual Result

version
no:
1 Open system by Make sure that login Pass Login page
double click on setup page should be
display
2 Enter User name & Make sure that Fail Do not enter into
Password And press password is correct system
login
3 Enter password 3 Password is incorrect Pass Wait for 3 minutes
times
4 Enter password and Make sure That Pass Admin Panel page
press Login button Admin panel should display
be display
2) Forget password Process:

version
no:
1 Press The link of Make sure that it Pass It will display
forget password should take mobile the form
no and email
2 Check full information If full information Fail Please fill up
filled is not filled full information
3 Press send password Make sure that the Pass It display
button after fulfillment mobile no and message that
email is correct password send
to email
4 Enter password and Make sure That Pass Admin Panel
press Login button Admin panel page display
should be display
3) Adding Medium, Stream, Semester, Division and Subject Process:

version
no:
1 Admin enter only null No entry Fail Space or null not
allow
2 Adding all the details of Make sure that Pass Entry of medium
medium, stream, entry becomes stream,semester,
semester, correct with section
section and subject etc. validation And subject added
4) Change password Process:

version
no:
1 First enter old Make sure that Pass Ask for new
password password is correct password
2 Enter a new password Make sure that it Pass Ask for confirm
must be greater than password
5character
3 Enter confirm Match with New Pass Change password
password password successfully
5) Registration Process:

version
no:
1 Enter the information Make sure that all the Pass Register the student
of students one by information must be
one valid
6) Registration for faculty Process:

version
no:
1 Enter the information Make sure that all the Pass Register the
of faculty one by one information must be faculty
valid
7) Generating Reports Form Admin Process:

version
no:
1 List of Reports which Make sure that the Pass Generate report,pdf
are required reports are valid and
usable
2)Test data:-
Test data is also a part of the developing the testing.Here we do not discuss any
theoretical concept or topics. Here we performed many different testing as
practical form.
In test data we generally used some validation and verification on data ad check
all these validation practically and match the costraints with documentation.
We use test data in our system for check tha la constraint related to our system
like:
Service booking date s not generate then purchased date or test drive booking
date and match all the constraint which defined in documentation.
7.2 output comparison

We perform different testing to compare the many requirement and constraint
related to the system. We compare many output and data with the predefined
document and the user satisfaction.
Generally testing is used to compare all the aspects related to input , output
validation etc. But most important comparison is the output comparison for user
satisfaction and for develop useful website.
Some example of data for comparison:
Sr. Process Input Condition Valid output Invalid

No output
1 Login Email id If email and Successfully Not
&password password is registered authenticate
valid. d user
2 Registration Email id, If Successfully Invalid data
password, pass=Confir registered.
confirm1 m password
password, and valid
valid data data and
valid uid.
7.3 Testing Strategies
Testing strategies are very useful for performing the different types of
testing in the system. It shows the way that how can we use different testing
(unit testing, integration testing, validation testing, system testing) with the
different phase of software engineering (Coding, Designing, Requirement,
whole system).
The software engineering process may be viewed as the spiral illustrated
in figure, system engineering defines the role of software and leads to software
requirements analysis, when the information domain, function, behavior,
performance, constrains and validation criteria for software are established
moving.
A strategy for software testing may also be viewed in the context of the
spiral. Unit testing begins at the vortex of the spiral and concentrates on each
unit.(i.e., component ) of the software as implemented in source code.
Testing progress is moving outward along the spiral to integration testing, where
the focus is on design and the construction of the software architecture. Talking
another turn outward on the spiral, we encounter validation against the software
that has been constructed.
Finally, we arrive at system testing, where the software and other system
elements are tested as a whole. To test computer software, we spiral out along
streamlines that broaden the scope of testing with each turn.
7.4 Unit Testing
A unit corresponds to a screen / form in the package. Unit focuses on

verification of the corresponding class or screen. This testing includes testing of
control paths, interfaces, local data structures, logical decisions, boundary
conditions, and error handling. Unit testing may use test drivers, which are
control programs to co-ordinate test case inputs and outputs, and test stubs,
which replace low-level modules. A stub is a dummy subprogram.
Unit testing focuses effort on the smallest unit of software component or

module. Using the component-level design description as a guide. Important
control paths are tested to uncover errors whiten the boundary of the module.
The relative complexity of tests and uncovered errors is limited by the

constrained scope established for unit testing. The unit test is white-box
oriented, and the step can be we performed unit testing in our system to test of
small modules, report generation etc.
With unit testing we generally the white box testing in our all modules, in these
all modules we checks all coding and syntax of modules. So that unit testing is
useful in our system.
7.5 Integration Testing
Integration testing is used to verify the combining of the software

modules. Integration testing addresses the issues associated with the dual
problems of verification and program construction. System testing is used to
verify, whether the developed system meets the requirements.
Installation and Delivery:

Installation and delivery is the process of delivering the developed and
tested software to the customer. Refer the support procedures. Acceptance
and project closure:
Acceptance is the part of the project by which the customer accepts the product.
Thus will be done as per the project closure, once the customer accepts the
product; closure of the project is started. This includes metrics collection, PCD,
etc.
Integration testing is a systematic technique for constructing the program

structure while at the same time conducting the tests to uncover errors
associated with interfacing. In these we are combining all the unit modules and
test these all at the same time.
In our system we integrate all the modules and performed the integration
testing on all those.
In our system, we used three techniques in integration testing:

 Top Down Integration :
Combine the test and debug top level routines that become the
integration test harness for low level units.
 Bottom – Up Integration :
Bottom-Up integration testing begins construction and testing with
atomic modules. Because components are integrated from the bottom up,
processing required for components subordinate to a given level is always
available and the need for studs is eliminated.
A Bottom-Up integration strategy may be implemented with the following

steps:
1) Low-level components are combined into clusters that perform a specific
software sub function.
2) A driver (a control program for testing) is written to coordinate test case
input and output.
3) Drivers are removed and clusters are combined moving upward in the
program structure.
7.6 System Testing
In this testing we take the requirements documents as a references to see

whether the software meets all its requirements, goal or not. The objective of the
system testing is to promote software functionality, reliability and
maintainability. System testing is used where the software and the other system
elements are testing as a whole. Its comes at the top level of the testing which is
done after completion of different tests whose primary purpose is to fully
exercise computer based system.
We used some testing in our system such as:
Recovery Testing:
In this system testing we verify that if any failure occurred in our system
then its recover proper or not.
Security Testing:
In this testing, we attempt to verify that protection mechanism of our system.
In our system. In our system we check the security such as login and password
security. If any user want to access our deep information and want to use our
services then he/she must have to be login and other user can’t access or see the
information of the another user.
7.7 Alpha and Beta Testing
 Alpha Testing:
Alpha testing is simulated or actual operational testing by potential
users/customers or an independent test team at the developers’ site. Alpha
8. SOFTWARE IMPLMETATION
testing is often employed for ready software as a form of internal

acceptance testing, before the software goes to beta testing.
 Beta Testing:
Beta testing comes after alpha testing and primarily utilizes black box
tactics, and can be considered a form of external user acceptance testing.
Versions of the software, known as beta versions, are released to a limited
audience outside of the programming team. The software is released to
groups of people so that further testing can ensure the product has few
faults or bugs. Sometimes, beta versions are made available to the open
public to increase the feedback field to maximal number of future users
Implementation is the stage in the project where the theoretical design is turned
into working system. The implementation phase constructs, installs and operates
the new system. The most crucial stage in achieving a new successful system is
that it will work efficiently and effectively. There are several activities invoked
while implementation a new project.
9. LIMITATIONS
8.1 User Training
The successful implementation of the new system will purely upon the
involvement of the officers working in that department. The officers will be
imparted training on the new technology. User may be trained on the of
equipment.
User training is designed to prepare the user for testing and converting the
system. User involvement and training take place parallel with programming for
three reasons:
1) The system groups has time available to spend on training while the
programs are being written.
2) Initiating a user training program gives the system group a clearer image
of the user’s interest in the new system.
3) A trained user participates more effectively in the system testing.
The training programmer should be planned & organized.
Training Programmer Should:

 Identify the user & trainer’s needs.
 Design a comprehensive training programmed.
 Select the best method of instruction.
10. FUTURE ENHANCEMENT
 Determine whether the system meet the objectives.
8.2 User Manual
The user manual is prepared to serve the user. A manual is necessary when the
user is geographically separated from the project team or when the user cannot
attend the training session. The manual should be written despite of cost. It
should discuss the function available to the user and what each can do how they
are executed and how messages are handled. The manual should be well
organized and indexed for quick reference. Graphics, picture and line drawings
enhance the understand-ability of the manual.
A well-design user manual can reduce the overall cost of training and supports.
User manual are the important organizational assets.
Components of user manuals:
 Title & version of software release
 Table of content
 Features of product
 Installation guide and system requirements
 Getting started
 Frequently Asked Questions(FAQ)
 Sample scenario
Limitation:
Each and every system has some limitations that can restrict then to work on a
particular environment.
Thorough our system is provided high amount of accuracy and quick data
generation there is still some limitations that led us to in greater deficiency to
work on that system.
Some of the limitation that is observed all the process is mentioned below.
 GUI (Graphical User Interface) is required.

 We used PayPal system for money transition so we cannot maintain user
side Bank Account or Bank Related information
Constraints:
Some of the constraints are listed below with we have developed this system.
 In our system, user can’t use main service register in our system. If user
wants to take admission in our tuition then he/she have to login our
system.
 Visitor’s user can not view the details information of our website.
 If users want to access detailed information about any particular course
then he/she have to login in our system.
Future Enhancement:
Our system efficient but still we can add another new feature in
future as need arises means our system is flexible that if we needed in we can
increases or add that requirements tour system and can extend the work to our
system.
Once the software is developed, tested and implemented, the focus
is laid on the support phase. The support phase focuses on change associated,
adaptations required as the software’s environment evolves and changes due to
enhancements brought about by changing customer requirements.
11. BIBLIOGRAPHY
 Parents Module.
 Online payment
 Fees online
 Report Generation can be used on a wide scope
 An Android version can be prepared for handy usage by students and
faculties.
Website
 https://stackoverflow.com/questions/5138719/change-default-text-in-
input-type-file(10-3-2018)
 https://www.w3schools.com/php/func_filesystem_mkdir.asp(12-3-18)
 http://php.net/manual/en/function.mkdir.php(12-3-18)
 https://stackoverflow.com/questions/2303372/create-a-folder-if-it-
doesnt-already-exist(13-3-18)
 https://www.codeigniter.com/userguide3/libraries/file_uploading.html
(10-3-18)
 https://www.codeigniter.com/userguide2/database/index.html(5-3-18)
 https://stackoverflow.com/questions/22123278/parsley-js-2-0-how-to-
use-the-provided-css-file(2-3-18)
 http://parsleyjs.org/doc/index.html(5-3-18)
 https://www.w3schools.com/css/css_border.asp(2-3-18)
 https://www.w3schools.com/js/default.asp(1-3-18)

Project Rahul

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Project Rahul

Загружено:

Авторское право:

Доступные форматы

College Management System

1.1 UDHNA ACADEMY EDUCATION TRUST

UDHNA ACADEMY COLLEGE OF C.A & I.T. (B.C.A) -JUNE 2008

UDHNA CITIZEN COMMERCE COLLEGE (B.com.) – JUNE 2002

R.N. NAIK H.S. SCHOOL (COM.& ARTS) – JUNE 2001

SURAT NATIONAL PRIMARY SCHOOL- JUNE 1968

“To impart quality education, nurture aspirations and facilitate continuous

1.2 Salient Features

 Qualified and Experienced faculty members

 Book Bank Facility

 Well-equipped Text and References Library

 Strong Industry- Institute Interaction through seminars, Guest Lectures,

 Faculty Feedback System to strengthen Teaching-Learning Process

 Indoor and outdoor Co-Curricular & Extra –curricular Activities

 Social Welfare Initiatives in Plantation of trees, Blood Donation Camp,

 NSS Sports as Character Building Activities

 Well equipped computers laboratories with Broadband Internet

 Canteen Facility for Students and staff

 Seminars conducted by doctors

1.2 INSTITUTE STRUCTURE /CHART

Udhna Academy Education Trust

Member of the Trust

Dr. Mehul P. Desai

B.COM B.B.A B.C.A

Dr. Mehul P. Desai Dr. Daisy Thekanlal Dr. Manish kaysth

Teaching Teaching Teaching

System Study is a detailed study of the various operations performed by a

2.1 Major Components

The main focus of College Management System is to keep track on student

 New Student registration :

 Student marks information:

This component is used to collect the marks information of the student of

 Student Attendance information:

This component is used to store monthly attendance of student in the

Process : Intel corei3 processor, AMD Catalyst processor

HDD : 500 GB Hard Disk

Process : Intel Pentium 4, Dual Core processor

RAM : 512 GB RAM

HDD : 40 GB Hard Disk

Apache version : Apache /2.4.10

Php version : 5.5.19

MySQL version : 5.0.11

Tools : php Myadmin (4.2.11)

Google chrome (40.0)

Mozilla Firefox (36.0)

Google chrome (40.0)

PhpStorm version 8.0.1

Operating system: windows 10, windows 8.1, windows 7

2.3 DRAWBACKS / LIMITATIONS(Existing System)

Most perceptions of interactivity are that it is an inherently good thing,

Information processing is very lengthy and time consuming. So actual

5) Messaging facility not available:

In existing College Management System, they haven’t facility about

6) Security /level is low:

7) Backup and Restore Facility is not available:

In current system there is no backup facility is available. So there is no

3 PROPOSE PROJECT PROFILE

The COLLEGE MANAGEMENT SYSTEM can be used to store student

Course Detail Report

Marks Detail Report

Our proposed system has several advantages.

 User friendly interface