Alumni Reportt

THE OXFORD COLLEGE OF SCIENCE
Department of Computer Science and Applications
(AFFILIATED TO BANGALORE UNIVERSITY)

TH
19 Main, 17th B Cross, Sector-IV, HSR Layout, Bangalore-560102
PROJECT REPORT
ON
ALUMNI MANAGEMENT SYSTEM

Submitted by:
Sweta.K.S 18RNSB7201
Under the guidance of:
Mr.Dharmendra Raju C
Project report submitted in partial fulfillment of the requirements of Fifth

Semester BCA, Bangalore University 2021
THE OXFORD COLLEGE OF SCIENCE
Department of Computer Science and Applications
(AFFILIATED TO BANGALORE UNIVERSITY)

TH
19 Main, 17thB Cross, Sector-IV, HSR layout, Bangalore-56010
CERTIFICATE
This is to certify that the Project Report titled“ALUMNI MANAGEMENT SYSTEM”is a bona fide
record of work done by Student Sweta.K.S(18RNSB7201) Bangalore University, Bangalore, in
partial fulfillment of the requirements of Sixth Semester BCA during the year 2021.
Head of the Department Project Guide

Mr. Dharmendra Raju C
Valued-by:
1.Internal Guide Name :Sweta.K.S
Register Number :18RNSB7201
2.External Guide Examination Centre:
Date of Exam :
ALUMNI MANAGEMENT SYSTEM 2018-2021
DECLARATION
I Sweta.K.S(18RNSB7201) hereby declare that this project work entitled

“ALUMNI MANAGEMENT SYSTEM” are submitted in partial fulfilment for
the award of the degree of BACHELOR OF COMPUTER APPLICATION of
Bangalore University.
We further declare that we have not submitted this project report in part or in full
to any other university for the award of any degree.
Date:
Sweta.K.S(18RNSB7201)
Place:
ACKNOWLEDGEMENT
A Mini project is a job of great enormity and it can’t be accomplished by an individual all by them.
We are thankful to Dr.B.R KavyaShree, principal of The Oxford College of Science, who provided us all the
required facilities to accomplish the project in time.
We endure our Humble and sincere gratitude to Dr.Susil Kumar Sahoo, HOD for his great encouragement
and valuable support.
We offer our sincere to our guide Mr.Dharmendra Raju C who has always given us a constant source of
inspiration and encouragement during course of our project.
We would like to mention the great-fullness of our parent’s blessings of which we are able to access and enjoy
such opportunities.
We would also like to thank our wonderful friends who also stood by our side and helped us learn more.
Last but not the least we thank our management and lab coordinator for providing us the support to complete
the project. We would like thank each and everybody who supported us throughout the long and attention
consuming project.
ABSTRACT
An alumni association is an association of graduates (alumni) or, more broadly, of former students. In the
alumni of universities, colleges, schools, fraternities and sororities often form groups with alumni from the
same organization. These associations often organize social events; publish newsletters or magazines raise
funds for the organization. Many provide a variety of benefits and services that help alumni maintain
connections to their educational institution and fellow graduates. Additionally, such groups often support new
alumni, and provide a forum to form new friendships and business relationships with people of similar
background.
Alumni associations are mainly organized around universities or departments of universities, but may also be
organized among students that studied in a certain country. In the past, they were often considered to be the
universities or schools old boy network. Today, alumni associations involve graduates of all age groups and
demographics.
This project is aimed at developing a repository for the alumni of the college, which is of importance to a
college. The Repository and Search Engine (RASE) is an Internet based application that can be accessed
throughout the World. Anyone can access the Search Engine to know about any Alumni of that college but
can’t able to add. Alumni can only update the database when they are in the college.
The project is envisaged to be completed in two phases. The initial phase will be the creation of a simple
system that will be used to capture data from current final year students before the end of term. The second
phase of development will extend the functionality of the system to allow past alumni to register.
THE OXFORD COLLEGE OF SCIENCE i

DEPARTMENT OF COMPUTER APPLICATION
Table of Contents
SL.NO INDEX DESCRIPTION PAGE

NO.
Chapter 1 1 Introduction 1
1.1 Introduction of the Project 2
1.2 Objective of the Project 2
1.3 Overview of the Project 3
1.4 Modules 3
1.5 Tools used 5
1.6 Existing System 5
1.7 Proposed System 6
Chapter 2 2 System Requirement specification 7

2.1 System analysis 8
2.2 Hardware and Software Requirements 9
2.3 Tools survey 12
2.4 Functional Requirements 12
2.5 Non Functional Requirements 13
2.6 User Requirements 14
Chapter 3 3 Design Specification 15

3.1 System Design 16
3.1.1 Use Case Diagram 17
3.1.2 Class Diagram 17
THE OXFORD COLLEGE OF SCIENCE ii

3.1.3 Sequence Diagram 18
3.3 Context Diagram 21

3.4 RDBMS Architecture 22
3.5 Data Flow Diagram 26
3.6 E-R Diagram 27
3.7 Model View Controller 28
3.8 Deployment Diagram 29
Chapter 4 4 Implementation Design 30

4.1 Coding 80
4.2 Screenshots 88
Chapter 5 5 Testing Tools 92

5.1 Software Testing 93
5.2 Unit Testng 94
5.3 Module Testing 94
5.4 Integration Testing 95
5.5 System Testing 97
5.6 User Acceptance Testing 97
5.7 Test Data Used 98
5.8 Test Cases 99
5.9 SystemImplementation 100
5.10 Black Box Testing 100
5.11 White Box Testing 101
5.12 Detailed Design
5.13 Feasibility Analysis
THE OXFORD COLLEGE OF SCIENCE iii

Software Analysis
5.14
Operational Feasibility
5.15
Economical Analysis
5.16
Chapter 6 6 Conclusion 102

6.1 Conclusion of The Project 103
6.2 Future Scope of the Project 103
6.3 Bibliography 104
THE OXFORD COLLEGE OF SCIENCE iv

THE OXFORD COLLEGE OF SCIENCE v

LIST OF FIGURES
SL NO DESCRIPTION PAGE
NO
Fig 3.1 Use Case Diagram 16
Fig 3.2 Class Diagram 17
Fig 3.3 Sequence Diagram 18
Fig 3.4 Context Diagram 19
Fig 3.5 Architecture Diagram 20
Fig 3.6 RDBMS Architecture Diagram 21
Fig 3.7 DFD For Registration 23
Fig 3.8 DFD For Login 24
Fig 3.9 DFD For Buying Product 25
Fig 3.10 Flow Chart 26
Fig 3.11 E-R Diagram 27
Fig 3.12 MVC Diagram 28
Fig 3.13 Deployment Diagram 29
THE OXFORD COLLEGE OF SCIENCE v

LIST OF TABLES
SL NO DESCRIPTION PAGE
NO
TABLE 4.1 Vendors Details 81
TABLE 4.2 Category Details 82
TABLE 4.3 Product Details 83
TABLE 4.4 Shipment Details 84
TABLE 4.5 User Information Details 85
TABLE 4.6 Order Details 86
TABLE 4.7 Poll Details 87
TABLE 4.8 Menu Details 88
TABLE 4.9 Section Details 89
TABLE 4.10 Contact Details 90
TABLE 4.11 Banner Details 91
TABLE 5.1 Login For User 95
TABLE 5.2 User Registration Page 96
THE OXFORD COLLEGE OF SCIENCE vi

DEPARTMENT OF COMPUTER APPLICATIONS
ABBREVIATIONS
 SQL: Structured Query Language

 SRS: System Requirement Specification
 OS: Operating System
 DBMS: Database Management System
 URL: Uniform Resource Locator
 IIS: Internet Information Server
 XML: Extensible Markup Language
 PHP: Hypertext Pre-Processor
THE OXFORD COLLEGE OF SCIENCE vii

DEPARTMENT OF COMPUTER APPLICATIONS
Introduction
THE OXFORD COLLEGE OF SCIENCE 1

CHAPTER 1 INTRODUCTION
1.1 Introduction of the Project
Computer plays an important role in our daily life. Anything we want we can get only in one mouse
click. Speed, reliability and accuracy of the computer make it a powerful tool for different purposes.
A very important and basic need of today’s modern business world is the quick availability and
processing of information using computer. One can easily get the type of required information
within a fraction of a second. The project that I have taken is also in this category which can be
accessed throughout the organization to manage the college information and student’s information.
1.2 Objective of the Project
This system can be used as an application for the “Alumni Management System” to manage the college
information and student’s information. The system is an online application that can be accessed throughout
the organization and outside customers as well with proper login provided, which will give better service to
the customers.
1.3 Overview of the Project
Overall description consists of background of the entire specific requirement. It also gives explanation about
actor and function which is used. It gives explanation about architecture diagram and it also gives what we are
assumed and dependencies. It also support specific requirement and also it support functional requirement,
supplementary requirement other than actor which is used. It also gives index and appendices. It also gives
explanation about any doubt and queries.

Once a student graduates from the institute, his/her professional life or career begins, with higher education
playing an important role in establishing himself/herself in the profession. In respect of College, it has been
our experience that from the very beginning, the alumni have maintained personal contacts with one another,
rather than use the channel of Alumni Association.
The advancements in information technology have certainly helped in creating new resources such as alumni
web pages, list servers etc., so as to permit greater interactions between the alum
1.4 Modules
Login Module– This module is provided for administrator and users who have registered
themselves in the system. These login are provided according to the need of the systems.
 Input – User id and password
 Process – After entering user id and password by user process of
validation occur to identify whether user id and password is available in
database or not.
 Output – Registered user can access website and can use the services.
Administrator Module – The administrator is provided with password and login-id with which
he/she can access the system. Administrator is provided right of maintaining the database, verifies
registered users.
 Input – Login id and password.
 Process– Process of validation will occur.
 Output– Administrator will maintain the database and will perform
the necessary process.
User Module– As users are the main visitor of site, the following facilities are available
through this module.
Can see all students info in the alumni according to their need.
Can see the event details , also send messages to their friends.

Can see the campus interview details.

 Input– User Id and password
 Process– Process of validation will occur.
 Output– Only genuine user can access services provided by website.
1.5 Tools used

Xampp:
 Apache:
 (Application Server) Apache , often referred to as Server, is an open-
source Java Servlet Container developed by the Apache Software
Foundation.
 MySqlServer:
 It handles larege databases much faster than existing solutions.
 It consists of multi-threaded SQL server that supports different back ends,
several different client programs and libraries, administrative tools, and
application programming interfaces (APIs)
 Its connectivity, speed, and security make MySQL Server highly suited for
accessing databases on the Internet.
 Web browsers:
 Google Chrome
 Mozilla Firefox
 Opera
 Internet Explorer

 Sublime Text 3.1.1

Sublime Text is a sophisticated text editor for code, markup and prose. You'll
love the slick user interface, extraordinary features and amazing performance
1.6 Existing System

The Existing system is a computerized system but which is maintained at individual databases i.e in excels
sheets, it’s a time delay process. And maintaining all the records in Excel sheets is difficult. If they want any
record they have to search all the records. It doesn’t provide multiple user accessibility and also doesn’t have
different user privileges. So the system is not accessible for all the employees of the organization.
Advantages over Existing System
 It is completely automated system in handling the college database

 This system provides centralized database maintenance
 This system provides easy access to the particular students account or his complete details
 This system provides student to easily navigate through the application for more information in a most
secure manner.
Limitations in Existing System
 The current system is not completely complete computerized and manual system in entering students
and staff data and handling it.
 There is no centralized database maintenance
 There is no easy access to the particular students record
 The student cannot easily navigate through the database

1.7 Proposed System
The Proposed system is a computerized system but which is maintained at Centralized databases
i.e. in automated forms it’s a very fast process. And maintaining all the records in online systems
database which makes it very easy to access and retrieve data from the database. If they want any
record they can easily search all the records. It provides multiple user accessibility and also has
different user privileges. So the system is accessible for all the employees of the organization.

System Requirement
Specification

CHAPTER 2 SYSTEM REQUIREMENTSPECIFICATION
2.1 System Analysis
System Development Life Cycles (SDLC) describes the data design and applications design. SDLS is an
interactive rather than a sequential process. Thus SDLS might help to refine Feasibility study to the user
requirements.
Fig 2.1 System Development Life Cycles (SDLC)
Planning: SDLS planning yields a general overview of the company and its objectives. An initial assessment
of the information of the flow and intents requirement must be made during this discovery portions of SDLS.

Analysis: Problems defined during the planning phase are examined in great details during analysis phase.
Analysis phase of the SDLS is an effect, a though AUDIT of the users requirements.
Detailed system Design: In this phase, the designer complete the design of the systems processes. This
include all the necessary technical specification for the screens and reports.
Implementations: In this phase hardware, DBMS software and the applications programs are installed and the
database designs is being implementations .
Maintenance: As soon as the system is operable, end users being to request in it. Those changes generates
systems maintenance activities, which can be grouped into three type:
 Perfective maintenance to enhance the system.

 Correctives maintenance in response to systems.
 Adoptive maintenance due to changes in business environment
System Analysis 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- why all problems exist
in the present system? What must be done to solve the problem? Analysis begins when a user or
manager begins a study of the program using existing system. During analysis, data collected on
the various files, decision points and transactions handled by the present system. The commonly
used tools in the system are Data Flow Diagram etc. 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 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
should be analyzed thoroughly in accordance with the needs. System analysis can be categorized
into four parts.

 System planning and initial investigation

 Applying analysis tools for structured analysis
 Feasibility study
 Cost/ Benefit analysis
2.2 Hardware and Software Requirements

Hardware requirements: The Collection of internal electronic circuits and external physical devices used in
building a computer is called Hardware.
The minimum hardware requirement specification for developing this project is as follows:-
 Processor : Any processor above 500 MHz

 RAM : 512MB RAM
 Hard Disk : 10GB
 Monitor : Standard Color Monitor
 Keyboard : Standard Keyboard
 Mouse : Standard Mouse
Software requirements: A set of programs associated with the operation of a computer is called software.
Software is the part of the computer system which enables the user to interact with several physical hardware
devices.
The minimum software requirement specifications for developing this project are as follows:-
 Operating system : Windows 2000, XP, 7/8/8.1/10

 Client side scripting tool : html, JavaScript
 Server side scripting tool : PHP Server
 Database connection : MySQL
 Web browser : Google chrome

2.3 Tools Survey
PHP
PHP, which stands for “hypertext pre-processor”, is a server side, HTML embedded scripting language used
to create dynamic web page. Much of its syntax is borrowed from C. JAVA and Perl with some unique
features thrown in. the goal of the language is to allow Web developers to write dynamically generated pages
quickly. In a Web HTML page, PHP code is enclosed within special PHP tags. When a visitor opens the page,
the processor the PHP code and then sends the output to the visitor browser. It means that, unlike JavaScript,
you don’t have to worry that someone can steal your PHP script.
What is PHP offers..?

PHP offers excellent connectivity to many databases including:
 MySQL
 Informix
 Oracle
 Sybase
 Solid
 Postgre SQL and
 Generic ODBC
 The popular PHP-MySQL combination is available on almost every UNIX host .Being web-oriented,
PHP also contains all the function to do things on the internet – connecting to remote servers, checking
email via POP3 or IMIP, url encoding, setting cookies, redirecting, etc.
 It is often pointed to as the main competitor with:
 Microsoft’s C#- visual basic.
 Sun’s Java-JSP.
What do PHP code like?

PHP is rather simple language. Much of its syntax is borrowed from c except for dealing with the types of
variable. You don’t need to think of the types of variable at all – you just work with their values, not their
types. And you don’t have to declare variable before you use them.
Basic syntax:
File name: You should save your file with the extension.PHP (earlier version used the extension .php3 and
.phtml).
Comment: // This comment extend to the end of line /* this is a multi-line Comment*/
Escaping from HTML:
A PHP code block starts with “<? php” and ends with “>; A php code block can be placed anywhere in the
HTML document
Instruction separation: Each separate instruction must end with the semicolon. The PHP closing tags (?>) also
implies the end of the instruction.
PHP files have a file extension of “.phtml” “.PHP3 ” or  “.PHP” 
What can PHP do:
Greet field for PHP you need three things to make this work, the PHP parser (CGI or server module), a web
server and web browser. You need to run the web server, with a connected PHP installation. You can access
the PHP program output with a web browser, viewing the PHP page through the server, all these can run on
your home machine if you are just experimenting with PHP programming.
Command line scripting you can make php script to run it without any server or browser. You only need the
PHP to use it this way Writing desktop application, PHP is probably not the very best language to create the
desktop application.

With a graphical user interface , but if you know PHP very well ,and would like to use some advanced PHP
features in your client – side application you can also use PHP-GTK to write such programs, you can also
have the ability to write cross – platform application this way, PHP-Anything PHP is mainly focused on
server–side scripting, so you can do anything any other CGI program can do, such as collect from data,
generate dynamic page content, or send and receive cookie. But PHP can do much more.
There are three main areas where PHP scripts are used. Server-side scripting, this is most traditional and main
GTK is an extension to PHP not available in the main distribution.
PHP security:
PHP is a power full language and the interpreter whether included in a web server as a module or executed as
a separate CGI binary, is able to access files execute commands open network connection on the server.
This property makes anything run on web server insecure by default.
PHP is designed specifically to be a more secure language for writing a CGI program then Perl or C, and with
correct selection of compile-time and run time configuration option and proper coding practice it can give you
exactly the combination of freedom and security you need.
MYSQL: Security Improvements: MySQL now enables database administrators to establish a policy for
automatic password expiration: Any user who connects to the server using an account for which the password
is past its permitted lifetime must change the password. For more information, Administrators can lock and
unlock accounts for better control over who can log in.
For more information, To make it easier to support secure connections, MySQL servers compiled using Open
SSL can automatically generate missing SSL and RSA certificate and key files at start-up.
SQL mode changes: The ERROR_FOR_DIVISION_BY_ZERO, NO_ZERO_DATE, SQL modes are now
deprecated but enabled by default. The long term plan is to have them included in strict SQL mode and to
remove them as explicit modes in a future MySQL release. Globalization improvements:

MySQL 5.7.4 includes a gb18030 character set that supports the China National Standard GB18030 character
set. For more information about MySQL character set support.
JSON support:
Beginning with MySQL 5.7.8, MySQL supports a native JSON type. JSON values are not stored as strings,
instead using an internal binary format that permits quick read access to document elements. JSON documents
stored in JSON columns are automatically validated whenever they are inserted or updated, with an invalid
document producing an error.
JSON documents are normalized on creation, and can be compared using most comparison operators such as
=, <, <=, >, >=, <>, !=, and <=>; for information about supported operators as well as precedence and other
rules that MySQL follows when comparing JSON values
Sys Schema:
MySQL distributions now include the sys schema, which is a set of objects that help DBAs and developers
interpret data collected by the Performance Schema. sys schema objects can be used for typical tuning and
diagnosis use cases. For more information
Condition handling:
MySQL now supports stacked diagnostics areas. When the diagnostics area stack is pushed, the first (current)
diagnostics area becomes the second (stacked) diagnostics area and a new current diagnostics area is created
as a copy of it. Within a condition handler, executed statements modify the new current diagnostics area, but
GET STACKED DIAGNOSTICS can be used to inspect the stacked diagnostics area to obtain information
about the condition that caused the handler to activate, independent of current conditions within the handler
itself. (Previously, there was a single diagnostics area. To inspect handler-activating conditions within a
handler,

Master dump thread improvements:
The master dump thread was refectories to reduce lock contention and improve master throughput. Previous
to MySQL 5.7.2, the dump thread took a lock on the binary log whenever reading an event; in MySQL 5.7.2
and later, this lock is held only while reading the position at the end of the last successfully written event. This
means both that multiple dump threads are now able to read concurrently from the binary log file, and that
dump threads are now able to read while clients are writing to the binary log.
Multi-source replication is now possible:

MySQL Multi-Source Replication adds the ability to replicate from multiple masters to a slave. MySQL
Multi-Source Replication topologies can be used to back up multiple servers to a single server, to merge table
shards.
Features of apache server:
UNIX Threading: On UNIX systems with POSIX threads support, Apache can now run in a hybrid
multiprocessor, multithreaded mode. This improves scalability for many, but not all configurations.
New Build System: The build system has been rewritten from scratch to be based on auto conf and libation.
This makes Apache's configuration system more similar to that of other packages.
Multiprotocol Support: Apache now has some of the infrastructure in place to support serving multiple
protocols. Mod echo has been written as an example.
Better support for non-Unix platforms: Apache 2.0 is faster and more stable on non Unix platforms such as
BeOS, OS/2, and Windows. With the introduction of platform specific multi-processing modules (MPMs) and
the Apache Portable Runtime (APR), these platforms are now implemented in their native API, avoiding the
often buggy and poorly performing POSIX-emulation layers.

New Apache API: The API for modules has changed significantly for 2.0. Many of the module-ordering/-
priority problems from 1.3 should be gone. 2.0 does much of this automatically, and module ordering is now
done per-hook to allow more flexibility. Also, new calls have been added that provide additional module
capabilities without patching the core Apache server.
IPv6 Support: here IPv6 is supported by the underlying Apache Portable Runtime library, Apache gets IPv6
listening sockets by default. Additionally, the Listen, Name Virtual Host, and Virtual Host directives support
IPv6 numeric address strings (e.g., "Listen [2001:db8:1]:8080").
Filtering: Apache modules may now be written as filters which act on the stream of content as it is delivered
to or from the server, the module mod_ext_filter allows external programs to act as filters in much the same
way that CGI programs can act as handlers.
2.4 Funcional Requirements

1. Login to the system through the first page of the application.
2. Change the password after login to the application.
3. See his/her details and change it.
4. Help from the system.
GENERAL OPERATIONS:
Student
 User can Register to Alumni
 Students can login to the system
 Update the Profile
 Students can see all students information in the alumni
 They can see the events details
 They can also send messages to their friends
 Students also can see the campus interview details

Admin users
 Has full access to all the modules of this system.
 Responsible for the accounts of all students.
 Update, modify or delete event details
 Update, modify or delete campus interviews details
 Prepares and submits also Daily reports, user reports, event reports, etc.
Normal users:
 Has restricted access. i.e., Normal users have access to some of the modules only i.e. user can search
the list of all their friends.
 They cannot send messages to their batch mates
2.5 Non – Functional Requirements
Performance Requirements:
The proposed system that we are going to develop will be used as the Chief performance system for providing help to
the organization in managing the whole database of the Alumni Management System. Therefore, it is expected that the
database would perform functionally all the requirements that are specified.
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.
Security Requirements:
We are going to develop a secured database. There are different categories of users Alumni Management
System,Student who will be viewing either all or some specific information form the database.
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.

2.6 USER REQUIREMENTS:
The user requires these features from the proposed system:
 Quick generation of data entry forms
 Quick processing of information
 Quick retrieval of data
 Quick and correct updating of data.
 Least storage requirements

 Secured and controllable data storage
 Full backups of data
 Readable, clean, up to date and timely reports
Note: These are some of the basic requirements, which the system should provide, but additional
Requirements can be different for other online program.

Design
Specification
CHAPTER 3 DESIGN SPECIFICATION

3.1 SYSTEM DESIGN
Software design sits at the technical kernel of the software engineering process and is applied regardless of the
development paradigm and area of application. Design is the first step in the development phase for any
engineered product or system. The designer’s goal is to produce a model or representation of an entity that
will later be built. Beginning, once system requirement have been specified and analyzed, system design is the
first of the three technical activities - design, code and test that is required to build and verify software.
The importance can be stated with a single word “Quality”. Design is the place where quality is fostered in
software development. Design provides us with representations of software that can assess for quality. Design
is the only way that we can accurately translate a customer‟s view into a finished software product or system.
Software design serves as a foundation for all the software engineering steps that follow. Without a strong
design we risk building an unstable system – one that will be difficult to test, one whose quality cannot be
assessed until the last stage.
During design, progressive refinement of data structure, program structure, and procedural details are
developed reviewed and documented. System design can be viewed from either technical or project
management perspective. From the technical point of view, design is comprised of four activities –
architectural design, data structure design, interface design and procedural design.
3.1.1 Use Case Diagram
Above figure represents Use Case Diagram of the project and is a useful technique for identifying,
clarifying, and organizing system requirements. It describes how a user uses a system to accomplish
a particular goal. Use cases help ensure that the correct system is developed by capturing the
requirements from the user's point of view.

Figure 3.1 Use Case Diagram
Fig 3.2 Administrator Use Case

3.1.2 CLASS DIAGRAM
CLASS DIAGRAM which shows a domain model for online shopping. The purpose of the diagram is
to introduce some common terms, "dictionary" for online shopping - Customer, Web User, Account,
Shopping Cart, Product, Order, Payment, etc. and relationships between. It could be used as a common
ground between business analysts and software developers.
Figure 3.3 Class Diagram
3.1.3 SEQUENCE DIAGRAM

A sequence diagram is a type of interaction diagram because it describes how—and in what order—a
group of objects works together. A sequence diagram specifically focuses on lifelines, or the
processes and objects that live simultaneously, and the messages exchanged between them to perform
a function before the lifeline ends.
Fig 3.4 Sequence Diagram

3.2 Context Diagram

Context diagram is all about seeing how a system to be sorted out and outlining the general structure
of the system. In the model of the product improvement process as appeared building process it is the
basic connection amongst plan and necessities designing as it recognizes the basic fundamental
segments in a system and connection between them.
In lithe process it is by and large acknowledged that at the beginning time of the improvement
procedure ought to be worried about setting up a general system design. Incremental advancement of
structures isn’t generally effective. While restoring segments in light of changes is typically
moderately simple, refactoring a system engineering is probably going to be costly.
Fig 3.5 Context Diagram
3.3 Relational Database Management System (RDBMS) :

This is an RDBMS based project which is currently using MySQL for all the transaction
statements. MySQL is an opensource RDBMS System.
Brief Introduction about RDBMS:
Fig 3.6 RDBMS Diagram

A relational database management system (RDBMS) is a database management system (DBMS) that
is based on the relational model as invented by E. F. Codd, of IBM's San Jose Research
Laboratory. Many popular databases currently in use are based on the relational database model.
RDBMSs have become a predominant choice for the storage of information in new databases
used for financial records, manufacturing and logistical information, personnel data, and much
more since the 1980s. Relational databases have often replaced legacy hierarchical databases and
network databases because they are easier to understand and use. However, relational databases
have been challenged by object databases, which were introduced in an attempt to address the
object relational impedance mismatch in relational database, and XML databases.

3.4 Data Flow Diagram
A data flow diagram is graphical tool used to describe and analyze movement of data through a system. These are the
central tool and the basis from which the other components are developed. The transformation of data from input to
output, through processed, may be described logically and independently of physical components associated with the
system. These are known as the logical data flow diagrams. The physical data flow diagrams show the actual
implements and movement of data between people, departments and workstations. A full description of a system
actually consists of a set of data flow diagrams. Process is further identified with a number that will be used for
identification purpose. The development of DFD‟S is done in several levels. Each process in lower level diagrams can
be broken down into a more detailed DFD in the next level. The top- level diagram is often called context diagram. The
process in the context level diagram is exploded into other process at the first level DFD.
The idea behind the explosion of a process into more process is that understanding at one level of detail is exploded into
greater detail at the next level. This is done until further explosion is necessary and an adequate amount of detail is
described for analyst to understand the process.
Larry Constantine first developed the DFD as a way of expressing system requirements in a graphical from, this lead to
the modular design.
A DFD is also known as a “bubble Chart” has the purpose of clarifying system requirements and identifying
major transformations that will become programs in system design. So it is the starting point of the design to
the lowest level of detail. A DFD consists of a series of bubbles joined by data flows in the system.
In the DFD, there are four symbols

1. A square defines a source(originator) or destination of system data
2. An arrow identifies data flow. It is the pipeline through which the information flows
3. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of data

CONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFD‟S:
1. Process should be named and numbered for an easy reference. Each name should be representative of the
process.
2. The direction of flow is from top to bottom and from left to right. Data traditionally flow from source to the
destination although they may flow back to the source. When a process is exploded into lower level details,
they are numbered.
3. The names of data stores and destinations are written in capital letters. Process and dataflow names have
the first letter of each work capitalized A DFD typically shows the minimum contents of data store. Each data
store should contain all the data elements that flow in and out.
SAILENT FEATURES OF DFD’S
1. The DFD shows flow of data, not of control loops and decision are controlled considerations do not appear
on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the dataflow take place daily,
weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.
Admin Process

User Login
Groups User permisssions

Management New User Management
Permissions
Grou Permissiondb Userdb Folderdb

pdb
Group Permission User Group

UserGroupdb
GroupPermissiondb
Fig 3.7 Admin Process Diagram

User Process
ManipulateAccount
Folderdb
GroupPermissiondb
File Creation
Folderdb
Filedb
fileactivitydb
Fig 3.8 User Process Diagram

regno dailyupdates groupcreate

name imageload
admin
student
year
Manage
Forumcreate
Mob num
addr subject
imageload
newsid
news
description
upload
forumid
name newsid subject

createforum
imageloaddd
forum news
category upload
description
userquery
Fig 3.9 E-R Diagram

3.5 E-R DIAGRAM
Entity-Relation model is based on the notion of real-world entities and the relationship between them.

ER modeling helps you to analyze data requirements systematically to produce a well-designed

database. So, it is considered a best practice to complete ER modeling before implementing your
database.

IMPLEMENTATION
DETAILS

CHAPTER 4 IMPLEMENTATION DESIGN

4.1 CODING
<!
DOCTYPE
html>
<html lang="en">
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />
<meta name="description" content="" />
<meta name="author" content="" />
<title>Alumni Management System</title>

<link rel="icon" type="image/x-icon" href="assets/img/favicon.ico" />

<script src="https://use.fontawesome.com/releases/v5.13.0/js/all.js"
crossorigin="anonymous"></script>

<link href="https://fonts.googleapis.com/css?family=Merriweather+Sans:400,700"
rel="stylesheet" />
<link href="https://fonts.googleapis.com/css?
family=Merriweather:400,300,300italic,400italic,700,700italic" rel="stylesheet"
type="text/css" />

<link href="admin/assets/css/jquery.datetimepicker.min.css" rel="stylesheet">
<link href="https://cdnjs.cloudflare.com/ajax/libs/magnific-popup.js/1.1.0/magnific-
popup.min.css" rel="stylesheet" />

<link href="admin/assets/vendor/bootstrap-datepicker/css/bootstrap-datepicker.css"
rel="stylesheet" />
<link href="css/styles.css" rel="stylesheet" />
<link type="text/css" rel="stylesheet" href="admin/assets/css/jquery-te-1.4.0.css">
<link href="admin/assets/css/select2.min.css" rel="stylesheet">
<script src="admin/assets/vendor/jquery/jquery.min.js"></script>
<script src="admin/assets/vendor/bootstrap-datepicker/js/bootstrap-datepicker.js"></script>
<script type="text/javascript" src="admin/assets/js/select2.min.js"></script>
<script type="text/javascript" src="admin/assets/js/jquery.datetimepicker.full.min.js"></script>
<script type="text/javascript" src="admin/assets/js/jquery-te-1.4.0.min.js" charset="utf-

8"></script>
<style>
header.masthead {
background: url(admin/assets/uploads/1628909220_alumni-neon-sign-vector-graduation-260nw-
1203038266.jpg);
background-repeat: no-repeat;
background-size: cover;
}
#viewer_modal .btn-close {
position: absolute;
z-index: 999999;
/*right: -4.5em;*/
background: unset;
color: white;
border: unset;
font-size: 27px;
top: 0;
}
#viewer_modal .modal-dialog {
width: 80%;
max-width: unset;
height: calc(90%);
max-height: unset;
}
#viewer_modal .modal-content {
background: black;
border: unset;
height: calc(100%);
display: flex;
align-items: center;
justify-content: center;
}
#viewer_modal img,#viewer_modal video{
max-height: calc(100%);
max-width: calc(100%);
}
body, footer {
background: #000000e6 !important;
}

a.jqte_tool_label.unselectable {
height: auto !important;
min-width: 4rem !important;
padding:5px
}/*
a.jqte_tool_label.unselectable {
height: 22px !important;
}*/
</style>
<body id="page-top">

<div class="toast" id="alert_toast" role="alert" aria-live="assertive" aria-atomic="true">
<div class="toast-body text-white">
</div>
</div>
<nav class="navbar navbar-expand-lg navbar-light fixed-top py-3" id="mainNav">
<div class="container">
<a class="navbar-brand js-scroll-trigger" href="./">Alumni Management System</a>
<button class="navbar-toggler navbar-toggler-right" type="button" data-toggle="collapse" data-
target="#navbarResponsive" aria-controls="navbarResponsive" aria-expanded="false" aria-
label="Toggle navigation"><span class="navbar-toggler-icon"></span></button>
<div class="collapse navbar-collapse" id="navbarResponsive">
<ul class="navbar-nav ml-auto my-2 my-lg-0">
<li class="nav-item"><a class="nav-link js-scroll-trigger" href="index.php?
page=home">Home</a></li>
page=alumni_list">Alumni</a></li>
page=gallery">Gallery</a></li>
page=careers">Jobs</a></li>
page=forum">Forums</a></li>
page=about">About</a></li>
<li class="nav-item">
<div class=" dropdown mr-4">
<a href="#" class="nav-link js-scroll-trigger" id="account_settings" data-toggle="dropdown"
aria-haspopup="true" aria-expanded="false">Admin <i class="fa fa-angle-down"></i></a>

<div class="dropdown-menu" aria-labelledby="account_settings" style="left: -2.5em;">

<a class="dropdown-item" href="index.php?page=my_account" id="manage_my_account"><i
class="fa fa-cog"></i> Manage Account</a>
<a class="dropdown-item" href="admin/ajax.php?action=logout2"><i class="fa fa-power-
off"></i> Logout</a>
</div>
</div>
</li>
</ul>
</div>
</div>
</nav>
<style>
#portfolio .img-fluid{
width: calc(100%);
height: 30vh;
z-index: -1;
position: relative;
padding: 1em;
}
.event-list{
cursor: pointer;
}
span.hightlight{
background: yellow;
}
.banner{
display: flex;
justify-content: center;
align-items: center;
min-height: 26vh;
width: calc(30%);
}
.banner img{
width: calc(100%);
height: calc(100%);
cursor :pointer;
}
.event-list{

cursor: pointer;
border: unset;
flex-direction: inherit;
}
.event-list .banner {
width: calc(40%)
}
.event-list .card-body {
width: calc(60%)
}
.event-list .banner img {
border-top-left-radius: 5px;
border-bottom-left-radius: 5px;
min-height: 50vh;
}
span.hightlight{
background: yellow;
}
.banner{
min-height: calc(100%)
}
</style>
<header class="masthead">
<div class="container-fluid h-100">
<div class="row h-100 align-items-center justify-content-center text-center">
<div class="col-lg-8 align-self-end mb-4 page-title">
<h3 class="text-white">Welcome to Alumni Management System</h3>
<hr class="divider my-4" />
<div class="col-md-12 mb-2 justify-content-center">
</div>
</div>
</div>
</div>
</header>
<div class="container mt-3 pt-2">
<h4 class="text-center text-white">Upcoming Events</h4>
<hr class="divider">
<div class="card event-list" data-id="1">

<div class='banner'>
<img src="admin/assets/uploads/1629862500_2d645063a9ce3463aaf58e8c8ab04f99.jpg"
alt="">
</div>
<div class="card-body">
<div class="row align-items-center justify-content-center text-center h-100">
<div class="">
<h3><b class="filter-txt">College Reunion</b></h3>
<div><small><p><b><i class="fa fa-calendar"></i> September 23, 2021 12:00
PM</b></p></small></div>
<hr>
<larger class="truncate filter-txt">It can be great catching up with old friends, colleagues or
relatives. Reunions often spark a bit of nostalgia, and fond memories. Remember the good times
with the collection of wise and insightful reunion The sweetness of reunion is the joy
of heaven.Richard Paul Evans</larger>
<br>
<hr class="divider" style="max-width: calc(80%)">
<button class="btn btn-primary float-right read_more" data-id="1">Read More</button>
</div>
</div>
</div>
</div>
<br>
<img src="admin/assets/uploads/1629862920_FUND.jfif" alt="">
</div>
<div class="">
<h3><b class="filter-txt">Fundraising Management</b></h3>
<div><small><p><b><i class="fa fa-calendar"></i> October 25, 2021 11:00
AM</b></p></small></div>
<hr>
<larger class="truncate filter-txt">As an educator, you get a chance to leverage funds from the
industry experts, who were your students at one point in time!You can conduct, streamline, and
manage fundraising events by sending out a digital invitation to your students.With the help of a
secured online payment gateway & inbuilt AI-powered analytics dashboard, you can
track the number of entries and collect the online payments done by them.You can utilize the

money for institutional growth in terms of providing the best facilities to the students.</larger>
<br>
</div>
</div>
</div>
</div>
<br>
<img src="admin/assets/uploads/1629862680_download.png" alt="">
</div>
<div class="">
<h3><b class="filter-txt">Job Opportunities For Students</b></h3>
<div><small><p><b><i class="fa fa-calendar"></i> October 30, 2021 12:00
PM</b></p></small></div>
<hr>
<larger class="truncate filter-txt">Not every student is as sharp as “David”!Some
students might not have got a good job opportunity at the time they were studying. Even after
their studies get completed & they leave college, it’s your responsibility to help
them build a career.You can accomplish it easily by connecting your alumni batch with the
recruiters.College alumni management software gives you the provision to compile, store
& save the information of thousands of alumni students with 100% data security. You
can refer the students to recruiters directly by forwarding their personal & academic
info.This way, you’ll not just help the students grow financially but build a strong bond
with them forever!</larger>
<br>
</div>
</div>
</div>
</div>
<br>
</div>
<script>

$('.read_more').click(function(){
location.href = "index.php?page=view_event&id="+$(this).attr('data-id')
})
$('.banner img').click(function(){
viewer_modal($(this).attr('src'))
})
$('#filter').keyup(function(e){
var filter = $(this).val()
$('.card.event-list .filter-txt').each(function(){
var txto = $(this).html();
txt = txto
if((txt.toLowerCase()).includes((filter.toLowerCase())) == true){
$(this).closest('.card').toggle(true)
}else{
$(this).closest('.card').toggle(false)
}
})
})
</script>
<div class="modal fade" id="confirm_modal" role='dialog'>
<div class="modal-dialog modal-md" role="document">
<div class="modal-content">
<div class="modal-header">
<h5 class="modal-title">Confirmation</h5>
</div>
<div class="modal-body">
<div id="delete_content"></div>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" id='confirm' onclick="">Continue</button>
<button type="button" class="btn btn-secondary" data-dismiss="modal">Close</button>
</div>
</div>
</div>
</div>
<div class="modal fade" id="uni_modal" role='dialog'>

<h5 class="modal-title"></h5>
</div>
</div>
<div class="modal-footer">
<button type="button" class="btn btn-primary" id='submit' onclick="$('#uni_modal
form').submit()">Save</button>
<button type="button" class="btn btn-secondary" data-dismiss="modal">Cancel</button>
</div>
</div>
</div>
</div>
<div class="modal fade" id="uni_modal_right" role='dialog'>
<div class="modal-dialog modal-full-height modal-md" role="document">
<h5 class="modal-title"></h5>
<button type="button" class="close" data-dismiss="modal" aria-label="Close">
<span class="fa fa-arrow-righ t"></span>
</button>
</div>
</div>
</div>
</div>
</div>
<div class="modal fade" id="viewer_modal" role='dialog'>
<button type="button" class="btn-close" data-dismiss="modal"><span class="fa fa-
times"></span></button>
<img src="" alt="">
</div>
</div>
</div>
<div id="preloader"></div>
<footer class=" py-5">
<div class="container">

<div class="row justify-content-center">

<div class="col-lg-8 text-center">
<h2 class="mt-0 text-white">Contact us</h2>
<hr class="divider my-4" />
</div>
</div>
<div class="row">
<div class="col-lg-4 ml-auto text-center mb-5 mb-lg-0">
<i class="fas fa-phone fa-3x mb-3 text-muted"></i>
<div class="text-white">+9000500060</div>
</div>
<div class="col-lg-4 mr-auto text-center">
<i class="fas fa-envelope fa-3x mb-3 text-muted"></i>

<script
src="https://stackpath.bootstrapcdn.com/bootstrap/4.5.0/js/bootstrap.bundle.min.js"></script>



<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery-
easing/1.4.1/jquery.easing.min.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/magnific-popup.js/1.1.0/jquery.magnific-
popup.min.js"></script>

<script src="js/scripts.js"></script> </body>
<script type="text/javascript">
$('#login').click(function(){
uni_modal("Login",'login.php')
})
</script>
</html>
<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <meta content="width=device-width,
initial-scale=1.0" name="viewport"> <title>Alumni Management System</title> <meta content=""
name="descriptison"> <meta content="" name="keywords">  <link
href="https://fonts.googleapis.com/css?family=Open+Sans:300,300i,400,400i,600,600i,700,700i|
Raleway:300,300i,400,400i,500,500i,600,600i,700,700i|
Poppins:300,300i,400,400i,500,500i,600,600i,700,700i" rel="stylesheet"> <link rel="stylesheet"
href="assets/font-awesome/css/all.min.css">  <link
href="assets/vendor/bootstrap/css/bootstrap.min.css" rel="stylesheet"> <link
href="assets/vendor/icofont/icofont.min.css" rel="stylesheet"> <link
href="assets/vendor/boxicons/css/boxicons.min.css" rel="stylesheet"> <link
href="assets/vendor/venobox/venobox.css" rel="stylesheet"> <link
href="assets/vendor/animate.css/animate.min.css" rel="stylesheet"> <link
href="assets/vendor/remixicon/remixicon.css" rel="stylesheet"> <link
href="assets/vendor/owl.carousel/assets/owl.carousel.min.css" rel="stylesheet"> <link
href="assets/vendor/bootstrap-datepicker/css/bootstrap-datepicker.min.css" rel="stylesheet"> <link
href="assets/DataTables/datatables.min.css" rel="stylesheet"> <link
href="assets/css/jquery.datetimepicker.min.css" rel="stylesheet"> <link href="assets/css/select2.min.css"
rel="stylesheet">  <link href="assets/css/style.css" rel="stylesheet"> <link
type="text/css" rel="stylesheet" href="assets/css/jquery-te-1.4.0.css"> <script

src="assets/vendor/jquery/jquery.min.js"></script> <script
src="assets/DataTables/datatables.min.js"></script> <script
src="assets/vendor/bootstrap/js/bootstrap.bundle.min.js"></script> <script
src="assets/vendor/jquery.easing/jquery.easing.min.js"></script> <script src="assets/vendor/php-email-
form/validate.js"></script> <script src="assets/vendor/venobox/venobox.min.js"></script> <script
src="assets/vendor/waypoints/jquery.waypoints.min.js"></script> <script
src="assets/vendor/counterup/counterup.min.js"></script> <script
src="assets/vendor/owl.carousel/owl.carousel.min.js"></script> <script src="assets/vendor/bootstrap-
datepicker/js/bootstrap-datepicker.min.js"></script> <script type="text/javascript"
src="assets/js/select2.min.js"></script> <script type="text/javascript"
src="assets/js/jquery.datetimepicker.full.min.js"></script> <script type="text/javascript" src="assets/font-
awesome/js/all.min.js"></script> <script type="text/javascript" src="assets/js/jquery-te-1.4.0.min.js"
charset="utf-8"></script> </head> <style> body{ width: 100%; height: calc(100%); /*background: #007bff;*/
} main#main{ width:100%; height: calc(100%); background:white; } #login-right{ position: absolute; right:0;
width:40%; height: calc(100%); background:white; display: flex; align-items: center; } #login-left{ position:
absolute; left:0; width:60%; height: calc(100%); background:#59b6ec61; display: flex; align-items: center;
background: url(assets/uploads/1628909220_alumni-neon-sign-vector-graduation-260nw-1203038266.jpg);
background-repeat: no-repeat; background-size: cover; } #login-right .card{ margin: auto; z-index: 1 } .logo {
margin: auto; font-size: 8rem; background: white; padding: .5em 0.7em; border-radius: 50% 50%; color:
#000000b3; z-index: 10; } div#login-right::before { content: ""; position: absolute; top: 0; left: 0; width:
calc(100%); height: calc(100%); background: #000000e0; } </style> <body> <main id="main" class=" bg-
dark"> <div id="login-left"> </div> <div id="login-right"> <div class="card col-md-8"> <div class="card-
body"> <form id="login-form" > <div class="form-group"> <label for="username" class="control-
label">Username</label> <input type="text" id="username" name="username" class="form-control"> </div>
<div class="form-group"> <label for="password" class="control-label">Password</label> <input
type="password" id="password" name="password" class="form-control"> </div> <center><button
class="btn-sm btn-block btn-wave col-md-4 btn-primary">Login</button></center> </form> </div> </div>
</div> </main> <a href="#" class="back-to-top"><i class="icofont-simple-up"></i></a> </body> <script> $
('#login-form').submit(function(e){ e.preventDefault() $('#login-form

button[type="button"]').attr('disabled',true).html('Logging in...'); if($(this).find('.alert-danger').length > 0 ) $

(this).find('.alert-danger').remove(); $.ajax({ url:'ajax.php?action=login', method:'POST', data:$
(this).serialize(), error:err=>{ console.log(err) $('#login-form
button[type="button"]').removeAttr('disabled').html('Login'); }, success:function(resp){ if(resp == 1)
{ location.href ='index.php?page=home'; }else{ $('#login-form').prepend('<div class="alert alert-
danger">Username or password is incorrect.</div>') $('#login-form
button[type="button"]').removeAttr('disabled').html('Login'); } } }) }) </script> </html>
4.2 Screenshots
DATABASE AND TABLES OF THE PROJECT
USER TABLE:

Id int Unchecked
Userid varchar(50) Checked
Fname varchar(50) Checked
Lname varchar(50) Checked
userpwd varchar(50) Checked
Address varchar(150) Checked
usercity varchar(50) Checked
userstate varchar(50) Checked
usercountry varchar(50) Checked
Aboutu varchar(150) Checked
Specialinu varchar(150) Checked
hobbies varchar(150) Checked
photname varchar(50) Checked
userphoto image Checked
useremail varchar(50) Checked
dateofcreation varchar(50) Checked
dateofmodification varchar(50) Checked
lastaccessdate varchar(50) Checked
lastaccesstime varchar(50) Checked
Unchecked
TABLE 4.1 USER
NEWS TABLE
newsid int Unchecked

newsheading varchar(250) Checked

newsdetail varchar(500) Checked
imageexists varchar(50) Checked
imagename varchar(50) Checked
newspicture image Checked
Unchecked
TABLE 4.2 NEWS
MESSAGE TABLE
msgid int Unchecked

senderid varchar(50) Checked
receiverid varchar(50) Checked
postedmsg varchar(350) Checked
posteddate varchar(50) Checked
msgviewed varchar(50) Checked
Unchecked
TABLE 4.3 MESSAGE
IMAGE TABLE
imageid int Unchecked

imagename varchar(50) Checked
userphoto image Checked
userid varchar(50) Checked
Unchecked
TABLE 4.4 IMAGE
FRIEND LIST

listid int Unchecked

friendid varchar(50) Checked
Rstatus varchar(50) Checked
dateofrequest varchar(50) Checked
dateofconform varchar(50) Checked
Unchecked
TABLE 4.5 FRIEND LIST
FORUM TABLE
forumid int Unchecked

forumname varchar(50) Checked
topicid varchar(50) Checked
topicname varchar(50) Checked
Unchecked
TABLE 4.6 FORUM
FORUM MESSAGE
forummsgid int Unchecked

forumname varchar(50) Checked
topicname varchar(50) Checked
usermsg varchar(500) Checked
Unchecked
TABLE 4.7 FORUMMSG

TABLE 4.8 HOME
TABLE 4.8.1 HOME

TABLE 4.9 ALUMNI
TABLE 4.10 GALLERY

TABLE 4.11 JOBS
TABLE 4.12 FORUMS

TABLE 4.13 ABOUT US
TABLE 4.14 LOGIN

TABLE 4.15 ADMIN
TABLE 4.16 ADMIN HOME

TABLE 4.17 ADMIN GALLERY
TABLE 4.18 ADMIN COURSE LIST

TABLE 4.19 ADMIN ALUMNI LIST
TABLE 4.20 ADMIN JOBS

TABLE 4.21 ADMIN EVENTS
TABLE 4.22 ADMIN FORUM

TABLE 4.23 ADMIN USERS
TABLE 4.24 ADMIN SYSTEM SETTINGS

TESTING
TOOLS

CHAPTER 5 TESTING TOOLS

5.1 SOFTWARE TESTING
Testing is the process of executing a program with the intent of finding errors. Although software
testing is itself an expensive activity, yet launching of software without may lead to cost potentially
much higher than that of testing, especially in systems where human safety is involved. Effective
software testing will contribute to the delivery of higher quality software products, more satisfied
users, and lower maintenance costs, more accurate and reliable results. Software testing is necessary
and important activity of software development process.
Is an investigation conducted to provide stakeholders with information about the quality of the product or
service under test. Software testing can also provide an objective, independent view of the software to allow
the business to appreciate and understand the risks of software implementation. Test techniques include the
process of executing a program or application with the intent of finding software bugs (errors or other
defects).
Software testing involves the execution of a software component or system component to evaluate one or
more properties of interest. In general, these properties indicate the extent to which the component or system
under test:
 meets the requirements that guided its design and development,

 responds correctly to all kinds of inputs,
 performs its functions within an acceptable time,
 is sufficiently usable,
 can be installed and run in its intended environments, and
 Achieves the general result its stakeholder’s desire.
Software testing can provide objective, independent information about the quality of software and risk of its
failure to users and/or sponsors. As the number of possible tests for even simple software components is

practically infinite, all software testing uses some strategy to select tests that are feasible for the available time
and resources.
As a result, software testing typically (but not exclusively) attempts to execute a program or application with
the intent of finding software bugs (errors or other defects).The job of testing is an iterative process as when
one bug is fixed it can illuminate other deeper bugs or can even create new ones. Software testing can be
conducted as soon as executable software (even if partially complete) exists.
The overall approach to software development often determines when and how testing is conducted. For
example, in a phased process, most testing occurs after system requirements have been defined and then
implemented in testable programs. In contrast, under an Agile approach, requirements, programming, and
testing are often done concurrently.
Levels of Testing:
 Unit Testing.
 Module Testing.
 Integration Testing.
 System Testing.
 User Acceptance Testing.

FIG 5.1 LEVELS OF TESTING
5.2 UNIT TESTING

Unit testing: In computer programming, unit testing is a software testing method by which individual units of
source code, sets of one or more computer program modules together with associated control data, usage
procedures, and operating procedures, are tested to determine whether they are fit for use.
Intuitively, one can view a unit as the smallest testable part of an application. In procedural programming, a
unit could be an entire module, but it is more commonly an individual function or procedure. In object-
oriented programming, a unit is often an entire interface, such as a class, but could be an individual method.
Unit tests are short code fragments created by programmers or occasionally by white box testers during the
development process. It forms the basis for component testing.
Ideally, each test case is independent from the others. Substitutes such as method stubs, mock objects, fakes,
and test harnesses can be used to assist testing a module in isolation. Unit tests are typically written and run by
software developers to ensure that code meets its design and behaves as intended .
5.4 MODULE TESTING

Module test plans must be created prior to module test execution. The following is a module testing test plan
for the microwave oven example.

FIG 5.2 V-MODEL DIAGRAM
5.4 INTEGRATION TESTING

Software Integration Testing is performed according to the Software Development Life Cycle (SDLC) after
module and functional tests. The cross-dependencies for software integration testing are: schedule for
integration testing, strategy and selection of the tools used for integration, define the cyclomatical complexity
of the software and software architecture, reusability of modules and life-cycle / versioning management.

The purpose of integration testing is to verify functional, performance, and reliability requirements placed on
major design items. These "design items", i.e., assemblages (or groups of units), are exercised through their
interfaces using black box testing, success and error cases being simulated via appropriate parameter and data
inputs. Simulated usage of shared data areas and inter-process communication is tested and individual
subsystems are exercised through their input interface.
 Top Down Approach- Top Down integration proceeds down the invocation hierarchy,
adding one module at a time until an entire tree level is generated.
 Bottom Up Approach – The Bottom up strategy works similarly from the bottom to up.
 Sandwich Strategy – A sandwich strategy runs from top and bottom simultaneously.
5.5 SYSTEM TESTING

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 wholeTesting the whole system.
System testing is performed on the entire system in the context of a Functional Requirement Specification(s)
(FRS) and/or a System Requirement Specification (SRS). System testing tests not only the design, but also the
behavior and even the believed expectations of the customer. It is also intended to test up to and beyond the
bounds defined in the software/hardware requirements specification(s).
5.5.1 Static vs. dynamic testing:

There are many approaches available in software testing. Reviews, walkthroughs, or inspections are referred
to as static testing, whereas actually executing programmed code with a given set of test cases is referred to as
dynamic testing. Static testing is often implicit, as proofreading, plus when programming tools/text editors
check source code structure or compilers (pre-compilers) check syntax and data flow as static program
analysis.
Dynamic testing takes place when the program itself is run. Dynamic testing may begin before the program is
100% complete in order to test particular sections of code and are applied to discrete functions or modules.
Typical techniques for this are either using stubs/drivers or execution from a debugger environment.
Static testing involves verification, whereas dynamic testing involves validation. Together they help improve
software quality. Among the techniques for static analysis, mutation testing can be used to ensure the test-
cases will detect errors which are introduced by mutating the source code.
5.6 USER ACCEPTANCE TESTING

User acceptance testing (UAT) consists of a process of verifying that a solution works for the user. It is not
system testing (ensuring software does not crash and meets documented requirements), but rather ensures that
the solution will work for the user i.e., test the user accepts the solution (software vendors often refer to this as
"Beta testing").
This testing should be undertaken by a subject-matter expert (SME), preferably the owner or client of the
solution under test, and provide a summary of the findings for confirmation to proceed after trial or review.
In software development, UAT as one of the final stages of a project often occurs before a client or customer
accepts the new system. Users of the system perform tests in line with what would occur in real-life scenarios.
It is important that the materials given to the tester be similar to the materials that the end user will have.
Provide testers with real-life scenarios such as the three most common tasks or the three most difficult tasks
you expect an average user will undertake. Instructions on how to complete the tasks must not be provided.
The UAT acts as a final verification of the required business functionality and proper functioning of the
system, emulating real-world usage conditions on behalf of the paying client or a specific large customer. If

the software works as required and without issues during normal use, one can reasonably extrapolate the same
level of stability in production. User tests, usually performed by clients or by end-users, do not normally
focus on identifying simple problems such as spelling errors or cosmetic problems, nor on showstopper
defects, such as software crashes; testers and developers previously identify and fix these issues during earlier
unit testing, integration testing, and system testing phases.
UAT should be executed against test scenarios. Test scenarios usually differ from System or Functional test
cases in the sense that they represent a "player" or "user" journey. The broad nature of the test scenario
ensures that the focus is on the journey and not on technical or system-specific key presses, staying away from
"click-by-click" test steps to allow for a variance in users' steps through systems. Test scenarios can be broken
down into logical "days", which are usually where the actor (player/customer/operator) or system (back office,
front end) changes.
In engineering and its various sub disciplines, acceptance testing is a test conducted to determine if the
requirements of specification or contract are met. It may involve chemical tests, physical tests, or performance
tests.
In systems engineering it may involve black-box testing performed on a system (for example: a piece of
software, lots of manufactured mechanical parts, or batches of chemical products) prior to its delivery.
In software testing the ISTQB defines acceptance as: formal testing with respect to user needs, requirements,
and business processes conducted to determine whether a system satisfies the acceptance criteria and to enable
the user, customers or other authorized entity to determine whether or not to accept the system. Acceptance
testing is also known as user acceptance testing (UAT), end-user testing, and operational acceptance testing
(OAT) or field (acceptance) testing. A smoke test may be used as an acceptance test prior to introducing a
build of software to the main testing process
5.7 TEST DATA USED

The proper selection of the data is very important. If the test data is not appropriate or representative
of the data to be provided by the user, the reliability of the output is susceptible.
Two different sources were during testing of the system-:
 Using Live Test Data – Live test are those that are actually extracted from the organization files. Use
of the live data make testing easier by obtaining most expected outputs and if it is found that the

program can handle the entries processing of the system accurately.

 Using Artificial Test Data - Live data is difficult to obtain insufficient amount to conduct
extensive testing. It does not test all the combination or formats that can be done by entering to the
system. Therefore artificial test data were used at the time of unit testing. Artificial test data was
created solely for test purposes which provide extreme values for testing the limit of candidate system.
TEST CASES
Test cases are constructed to test whether all the components within assemblages interact correctly, for
example across procedure calls or process activations, and this is done after testing individual modules, i.e.,
unit testing. The overall idea is a "building block" approach, in which verified assemblages are added to a
verified base which is then used to support the integration testing of further assemblages.
 System is properly linked or not - Whether they are redirected to desired page or not.
 Information passed– If a page passes some parameter to another page then it should be checked that
the page get the correct information, whatever is passed by the previous page.
 Output should be correct– Every functionality of the system should be checked properly whether it
gives the right result or not generally test is performed with known results. If the output of the system
is matched with that result the system is working fine.
Serial Description Expected Actual Result Result

No Result
1. This page contains User Respective Passed
2 fields user name home user home
and password and page page is
a login button to should opening after
submit the open after successful
information. User successful login by user.
is entering correct login.

information.
2. If either user name An error When wrong Passed
or password is message information
filled incorrect or should be is entered by
left blank. displayed and user then an
user should be error
asked fill the message is
information displayed.
again.
TABLE 5.3 LOGIN FOR USER
Serial Description Expected Actual Result Result

No Result
1. User registration page 1 After After Passed
consist of detail submitting submitting
information about User information information
and a submit button to User User
submit the information registration registration
.Here user is entering page 2 should page 2 is
correct information. be displayed. displayed.
2. If the information entered An error An error Passed
by user in incorrect or message should message is
left somewhere blank. be displayed occurred if the
and ask the user information is

to fill the incorrect or left

information blank.
again.
TABLE 5.4 USER REGISTRATION PAGE
5.9 SYSTEM IMPLEMENTATION

This is the phase in the software life cycle where the actual software is implemented. The result of this phase
consists of source code, together with documentation to make the code reliable. Implementation is the action
that must follow any preliminary in order for something to actually happen. It encompasses all the processes
involved in getting new software and hardware operating properly in its environment, including installation,
configuration, running, testing and making necessary changes.
The word deployment is sometimes used to mean the same thing. Implementation refers to post sales process
of guiding a client from purchase to use of the software or hardware that was purchased.
This includes Requirement Analysis, Scope Analysis, Customizations, System Integrations, User Policies,
User Training and Delivery. These steps are often overseen by a Project Management Methodologies set forth
in the Project Management Body of Knowledge. Software Implementations involve several professionals that
are relatively new to the knowledge based economy such as business Analysts, Technical Analysts, Solution
Architect and Project Managers.
There are 6 Stages in Software Implementation:

1) verification and validation
Purpose:
 Verify that a system confirms that to its specification and validate that the systems is what the
customer wanted.

Activities:
 Inspections and reviews.

 Testing: Unit Testing, Integration Testing, System Testing, Acceptance Testing, etc.
2) Integration
Purpose:
 Assemble the system from subsystems.
Approaches
 Incremental integration or big-bang?
Problems:
 Interface mismatches or misunderstanding.
 Resources Conflicts: Memory, Control, Physical
 Communication Problems.
 Integration with COTS.
3) Installation
Purpose:
 System is installed in the environment and made for ready for use.
Problems
 Unexpected issues such as too little space, power, heat, etc.
 Configuration problems and tuning.
 Training

4) Software Evolution and Maintenance

Purpose
 Change the system while it is first in use to handle changing requirements.
Covers:
 Trouble fixing (Corrective maintenance).
 Adaptation to new platform/technology(Adaptive Maintenance).
 New requirements (Perfective Maintenance).
Activities:
 Assess existing software.
 Propose change, Modify System.
5) System De-commissioning
Purpose:
 Take the system out of use at the end of its life-time.
 Should be carefully planned for large systems.
Issues:
 Safety or security considerations
 Reuse of software or data.
6) Project Management
Planning
 Approaches, Resources, Schedule, Increments or Deliveries and Budget and Managing all these.
Cost Estimation
 HW, SW, Organization

While there are number of software tools to develop and implement the web based online shopping system, I
have chosen those are open source, so that it will reduce the developing cost of the project. For designing the
project HTML, CSS, Bootstraps, Apache server as web server, PHP for making the system dynamic. MySQL
as database server. All of the tools are open source.
HTML In this project HTML used for design the structure. HTML is a markup language for describing web
documents and stands for Hyper Text Markup Language, a markup language is a set of markup tags.HTML
documents are described by HTML tags. Each HTML tag describes different document content. HTML used
because: • Easy to learn. • Easy to use. • Supported by all browser.
PHP In this project making the web page content dynamic and for interconnecting with database coding done
by PHP. PHP stats for Hypertext Preprocessor.
The reason of using PHP are:
• PHP can generate dynamic page content.
• PHP can create, open, read, write, delete, and close files on the server
• PHP can send and receive cookies.
• PHP can add, delete, and modify data in database.
• PHP can be used to control user-access.
• PHP can encrypt data. With PHP we cannot limited to output HTML.
We can output images, PDF files, and even flash movies. We can also output any text, such as XHTML and
XML.
MySQL MySQL is a database system used for the web application and it runs that runs on a server. The
reason of using MySQL are:
• MySQL is ideal for both small and large applications.
• MySQL is very fast, reliable, and easy to use.
• MySQL uses standard SQL.
• MySQL compiles on a number of platforms.
• MySQL is free to download and use.

XAMPP server XAMPP is a free and open source cross-platform web server solution stack package
developed by Apache Friends, consisting mainly of the Apache HTTP Server, MariaDB database, and
interpreters for scripts written in the PHP and Perl programming languages. XAMPP stands for Cross-
Platform (X), Apache (A), MariaDB (M), PHP (P) and Perl (P).
It is a simple, lightweight Apache distribution that makes it extremely easy for developers to create a local
web server for testing purposes. Everything needed to set up a web server – server application (Apache),
database (MariaDB), and scripting language (PHP) – is included in an extractable file. XAMPP is also cross-
platform, which means it works equally well on Linux, Mac and Windows. Since most actual web server
deployments use the same components as XAMPP, it makes transitioning from a local test server to a live
server extremely easy as well.
TESTING Exhaustive testing for the project is not possible. Some testing strategies and stage designed
manually. For this project Black box and White box testing are chosen. This two type testing applied different
part of the project.
5.10 BLACK BOX TESTING
Black Box Testing, also known as Behavioural Testing, is a software testing method in which the internal
structure/ design/ implementation of the item being tested is not known to the tester.
These tests can be functional or non-functional, though usually functional. This method is named so because
the Software program, in the eyes of the tester, is like a black box; inside which one cannot see. This method
attempts to find errors in the following categories:
• Incorrect or missing functions
• Interface errors
• Errors in data structures or external database access
• Behavior or performance errors
• Initialization and termination errors

FIG 5.5 BLACK BOX TESTING
5.11 WHITE BOX TESTING

White Box Testing also known as Clear Box Testing, Open Box Testing, Glass Box Testing, Transparent Box
Testing, Code-Based Testing or Structural Testing is a software testing method in which the internal structure/
design/ implementation of the item being tested is known to the tester.
The tester chooses inputs to exercise paths through the code and determines the appropriate outputs.
Programming know-how and the implementation knowledge is essential. White box testing is testing
beyond the user interface. The white box testing perform normally in this project different part.

FIG 5.12 WHITE BOX TESTING
5.12 DETAILED DESIGN AND NOTATIONS, DEVELOPMENT

PROBLEM
The DFD also known as the Bubble Chart is a simple graphical formalism that can be used to
represent a system in terms of the input data to the system. Various processing carried out on
these data, and the output data generated by the system. The main reason why the DFD technique
is so popular is probably because of the fact that DFD is a very simple formalism-it is simple to
understand and use. A DFD uses a very limited number of primitive symbols to represent the
functions performed by a system and the data flow among these functions. Starting with a set of
high-level functions that a system performs, a DFD model hierarchically represents various sub
functions. The five different types of primitive symbols used for constructing DFDs are:
SYMBOLS USED:
PROCESS:

A function is represented using a circle. This symbol is called a process or a bubble. Bubbles
are annotated with the names of the corresponding functions.
EXTERNAL ENTITY:
An external entity such as a librarian, a library member, etc. is represented by a rectangle. The
external entities are essentially those physical entities external to the software system that interact
with the system by inputting data to the system or by consuming the data produced bythe system. In
addition to the human users, the external entity symbols can be used to represent external hardware
and software such as application software.
DATA FLOW:
A directed arc or an arrow is used as a data flow symbol. A data flow symbol represents the data flow
occurring between two processes, or between an external entity and a process, in the direction of the
data flow arrow. Data flow symbols are usually annotated with the corresponding data names.
DATA STORE:
A data store represents a logical file. It is represented using two parallel lines. A logical file can
represent either a data store symbol, which can represent either a data structure, or a physical file
on disk. Each data store is connected to a process by means of a data flow symbol. The direction
of the data flow arrow shows whether data is being read from or written into a data store. A
arrow flowing in or out of a data store implicitly represents the entire data of the data store and

hence connecting to a data store need not be annotated with the name of the corresponding data
items.
OUTPUT SYMBOL:
The output symbol is used when a hard copy is produced and the user of the copies cannot be
clearly specified or there are several users of the output.
Development Problem:-
 Problem in running XAMPP.
 To debug the error during the development.
 To show a relationship between entity.
 Minor error with database table.
5.13 Feasibility Analysis

A feasibility analysis is conducted once the problem is clearly understood. The purpose of the study is
to determine whether the problem is worth solving. It is an analysis and evaluation of a proposed
project to determine if it is technically feasible.
5.14 Software Analysis

● Consumes a long-time for development of web application.
● Research and analysis cost to determine the actual need in real world.
● Implementation of application in the server and cost associated with the space in server.

5.15 Operational Feasibility

The system is operational feasible as the system can be operate by normal users with basic computer
skills without any additional trainings. We have developed this system with the willingness and
ability to create, manage and operate the system which is easy for the end users to operate it.
5.16 Economical Analysis

The economic feasibility of a system is used to evaluate the benefits achieved from and the costs incurred for
the project or system. This is done by a process called cost benefit analysis. It provides tangible and intangible
benefits like reduction in cost, more flexibility, faster activities, proper database management, etc.
The application is medium scale application and is economically feasible for us to accomplish it.
This involves cost benefits analysis. Thus there is no problem of high cost and cost benefits analysis.

CONCLUSION

CHAPTER 6 CONCLUSION
6.1 CONCLUSION
So the Alumni Management System is mainly used to share the views between the users of the
application which is very useful to upgrade the knowledge of everyone. The application is also
serve as a useful site to know what is going on in our in our college and can also know about the
various opportunities of the outer world. The application can be further expanded by following
the future scope of the project mentioned below.
6.2 FUTURE SCOPE OF THE PROJECT:
It is not possible to develop a system that makes all the requirements of the user. User
requirements keep changing as the system is being used. Some of the future enhancements that
can be done to this system are:
 As the technology emerges, it is possible to upgrade the system and can be adaptable to
desired environment.
 Because it is based on object-oriented design, any further changes can be easily
adaptable.
 Based on the future security issues, security can be improved using emerging
technologies.
 Attendance module can be added
 sub admin module can be added
6.3 BIBLIOGRAPHY
 http://www.bluedart.com/
 http://www.wampserver.com/en/
 http://www.php.net/
 http://www.tutorialspoint.com/mysql/

 httpd.apache.org/docs/2.0/misc/tutorials.html
 http://www.w3schools.com/php/ http://www.w3schools.com/css/
 http://www.php.net

Alumni Reportt

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alumni Reportt

Uploaded by

Copyright:

Available Formats

THE OXFORD COLLEGE OF SCIENCE

Department of Computer Science and Applications

(AFFILIATED TO BANGALORE UNIVERSITY)

ALUMNI MANAGEMENT SYSTEM

Under the guidance of:

Project report submitted in partial fulfillment of the requirements of Fifth

(AFFILIATED TO BANGALORE UNIVERSITY)

record of work done by Student Sweta.K.S(18RNSB7201) Bangalore University, Bangalore, in

Head of the Department Project Guide

1.Internal Guide Name :Sweta.K.S

Register Number :18RNSB7201

2.External Guide Examination Centre:

I Sweta.K.S(18RNSB7201) hereby declare that this project work entitled

THE OXFORD COLLEGE OF SCIENCE i

SL.NO INDEX DESCRIPTION PAGE

Chapter 2 2 System Requirement specification 7

Chapter 3 3 Design Specification 15

THE OXFORD COLLEGE OF SCIENCE ii

3.1.3 Sequence Diagram 18

3.3 Context Diagram 21

Chapter 4 4 Implementation Design 30

Chapter 5 5 Testing Tools 92

THE OXFORD COLLEGE OF SCIENCE iii

Chapter 6 6 Conclusion 102

THE OXFORD COLLEGE OF SCIENCE iv

THE OXFORD COLLEGE OF SCIENCE v

THE OXFORD COLLEGE OF SCIENCE v

THE OXFORD COLLEGE OF SCIENCE vi

 SQL: Structured Query Language

THE OXFORD COLLEGE OF SCIENCE vii

THE OXFORD COLLEGE OF SCIENCE 1

1.1 Introduction of the Project

1.2 Objective of the Project

1.3 Overview of the Project

THE OXFORD COLLEGE OF SCIENCE 2

THE OXFORD COLLEGE OF SCIENCE 3

Can see the campus interview details.

1.5 Tools used

THE OXFORD COLLEGE OF SCIENCE 4

 Sublime Text 3.1.1

1.6 Existing System

Advantages over Existing System

 It is completely automated system in handling the college database

Limitations in Existing System

THE OXFORD COLLEGE OF SCIENCE 5

1.7 Proposed System

THE OXFORD COLLEGE OF SCIENCE 6

THE OXFORD COLLEGE OF SCIENCE 7

CHAPTER 2 SYSTEM REQUIREMENTSPECIFICATION

2.1 System Analysis

Fig 2.1 System Development Life Cycles (SDLC)

THE OXFORD COLLEGE OF SCIENCE 8

 Perfective maintenance to enhance the system.

THE OXFORD COLLEGE OF SCIENCE 9

 System planning and initial investigation

2.2 Hardware and Software Requirements

 Processor : Any processor above 500 MHz

 Operating system : Windows 2000, XP, 7/8/8.1/10

THE OXFORD COLLEGE OF SCIENCE 10

2.3 Tools Survey

What is PHP offers..?

What do PHP code like?

THE OXFORD COLLEGE OF SCIENCE 11