INFORMATION SYSTEM

A PROJECT REPORT

Submitted by
AYUSHI KAMLE (IT-2K13-13)
DEEPAK PANDEY (IT-2K13-14)
RAJAT JAIN (IT-2K13-32)

Under the Guidance of

Mrs. POONAM MANGWANI

In partial fulfillment for the award of the degree of

Master of Technology (IT)

Of

International Institute of Professional Studies

Devi Ahilya Vishwavidyalaya, MP
2016

Information System

Page 1

Table of Contents
1. Introduction .................................................................................................................... 3
1.1 Purpose ..................................................................................................................... 3
1.2 Scope ........................................................................................................................ 3
1.3 Aim ........................................................................................................................... 3
1.4 Objectives ................................................................................................................. 3
1.5 Methodologies .......................................................................................................... 4
2. Feasibility Study ............................................................................................................. 5
2.1 Economic Feasibility Study...................................................................................... 5
2.2 Technical Feasibility Study ...................................................................................... 6
2.3 Behavioral Feasibility Study .................................................................................... 6
3. Analysis .......................................................................................................................... 7
3.1 Introduction .............................................................................................................. 7
3.1.1 Project Overview ............................................................................................. 7
3.1.2 Use-Case Diagrams ......................................................................................... 8
3.2 Specific Requirements .............................................................................................. 10
3.2.1 Function Requirements.................................................................................... 10
3.2.2 Non-Functional Requirements ........................................................................ 10
3.2.3 External Interface Requirements ..................................................................... 11
3.3 Software System Attributes ...................................................................................... 12
4. System Design ................................................................................................................ 13
4.1 Entity-Relationship Diagram .................................................................................... 13
4.2 Sequence Diagram .................................................................................................... 14
4.3 Activity Diagram ...................................................................................................... 16
4.4 Class Diagram .......................................................................................................... 17
4.5 Data Flow Diagram .................................................................................................. 18
4.6 Database Diagram .................................................................................................... 20
5. Software Development Methodology ............................................................................ 21
6. System Testing ............................................................................................................... 23
6.1 Introduction .............................................................................................................. 23
6.2 Testing Methodologies ............................................................................................. 23
6.3 Test Planning ............................................................................................................ 25
6.4 Test Cases ................................................................................................................. 25
7. Output Forms and Responses ......................................................................................... 26
8. Conclusions .................................................................................................................... 29
9. Future Enhancement ....................................................................................................... 30
Bibliography ................................................................................................................... 31
Information System

Page 2

1. INTRDOCUTION
Information System is a web based application can be used by college to circulate
important information to students through notice board and E-mail. This project also
maintain the details of every student in a centralized database, useful at the time of
requirement.

1.1 PURPOSE
The purpose for developing this type of software is to give student a medium through
which they gather all important information regarding current activities of college.

1.2 SCOPE
The scope of Information System portal is global i.e. it should be able to be accessed from
anywhere through internet i.e. registered users must be able to login to their accounts by
directly accessing this Information System web application and then signing in with their
username and password anytime and anywhere.

1.3 AIM
The project aims to facilitate keeping all the records of students, such as their personal
details like contact number, email, etc. So that all the information about any student will be
available in a few seconds. Itll also make it very easy to generate statistical data or custom
data like finding certain set of students. It assists non-technical and new users very well, as
it is easier to use. No extra and complex options are included. Application performs very
fundamental function.

1.4 OBJECTIVE
In this project we are providing a web based application through which students can gather
information related to the college through Batch Mentors by notice board and email
facility. This application will provide explanatory information to students about upcoming
events, notices and other information related to college, so that they do not have to waste
their precious time during exams by coming to college or using another medium to get
information and interaction with batch mentors. This application will also gather basic
information of students which help to identify details of every student. Information System
provides an interactive GUI hence making information easily available and understandable
to user.
Information System

Page 3

1.5 METHODOLOGIES
When referring to software, tools are accessories that help developers develop software
programs more effectively. When referring to hardware, tools are what enable a person to
install, remove or perform other actions on their computer or their computer hardware.
Below is a listing of some of the tools we required for the development of this system.

Bootstrap
Xamp for PHP
Sublime-text editor / Notepad

Information System

Page 4

2. FEASIBILITY STUDY

The initial steps in carrying out a feasibility analysis for a web project, based on
information obtained interactively from a prospective client, are modeled as a rule based
expert system that draws on empirical formulas to provide a quantitative valuation of the
clients replies. The model is centered in the pre-design phase, concerned in particular with
ascertaining whether coherent aims, message, audience and services have been identified
for the web project.

2.1 ECONOMIC FEASIBILITY STUDY

Economic feasibility study can be summed up in the following: It is a process of
collecting information and data about a proposed project, then analyzing the same from the
financial, economic and technical aspects, in addition to sensitivity analysis, in order to be
aware of the extent of such project success, under the prevailing circumstances in the
market. Therefore, a decision should be made to continue or cease such project. Following
are some methods which define the economic feasibility of this system:

This website will require web designers, programmers, database managers and
technical experts.
The resources will include computer system, internet connectivity and software. Their
cost will make up a part of investment required.
Certain testing tools will be required to carry out system testing.
After project completion, website will be made online. For this domain name purchase
and web hosting will be completed. This will include cost of domain name and web
hosting charges as per services used.
Cost of domain name purchase will be incurred once and hosting plans are based on
time spans. It could be half yearly, yearly or more. Different hosting service providers
charges differently for each plan.
These are the investment requirement of this system.

This website can generate revenue by following ways:

Online ad posting.
Website user traffic.

Information System

Page 5

2.2 TECHNICAL FEASIBILITY STUDY

Creating a data schema or structure that is robust enough to include the variety of
databases in existence while being clear and straightforward enough that development
is not discouraged.
A decision by one or more keystone partners to cease participating in the portal.
Data loss on the part of one or more keystone partners.
Providing connectivity to each and every parts of website.
Rating of Colleges on the basis of technical recommendations.
A development path to implement a Web-based collaborative tool enabling common
access to academic credential-related data sets, identifying its relative benefits, risks,
resource requirements, and possibility of success.

2.3 BEHAVIORAL FEASIBILITY STUDY

In general, evaluation indicates that the following observations should be considered when
further developing the system:

The systems information collection phase should refine in order to provide more agile
means for users with a clear idea of what they want.
The systems information assessment phase should be narrowed down so that, having
identified a particular type of problem, it concentrates on the collection of information
specifically relevant to that problem during the next phase.
The non-linearity of the hyper documents and the ease of connection to other web
applications make it easy for the user to access information.
Due to fierce competition on the WWW, web site development under continuous
pressure to take up the latest technological options, and to continuously update content.
Web sites have an initial development up to the point where they are first released, and
then further development is carried out in a complex combination of fine-grained and
almost constant modifications, more substantial structural changes, and possibly even
occasional complete overhauls and re-releasing.

Information System

Page 6

3. ANALYSIS

3.1 INTRODUCTION
Information System is a web based application developed for the college in order to
maintain the details of its students in a centralized database, useful at the time of
requirement. If there will be no centralized system and if the system is not computerized
then this task of circulating information is very laborious. They would have to deal with a
lot of paper work to maintain the details of the students. Now, at times batch mentors needs
to pass some information immediately to the students. They would either pass it to the CR
or to any social network group. This is an unauthorized procedure, or else if they directly
contact with the student that would also need a lot of time.

3.1.1 PROJECT OVERVIEW

To overcome all these problems, we introduced a web based application which can be
accessed from anywhere so that it becomes easy for the person to get access to all data
anytime anywhere as required. This application would give access to only some specific
persons through secure login. All the data of the students will be centralized so that can be
accessed from anywhere, no need of physical presence at the department. The person
handling the application can access by logging in and maintain all the details. He can select
the students according to the required criteria and send information to the students directly
through an automated E-mailing system.

3.1.2 USE-CASE DIAGRAM

A use-case diagram in the Unified Modeling Language (UML) is a type of behavioral
diagram defined by and created from a Use-case analysis. Its purpose is to present a
graphical overview of the functionality provided by a system in terms of actors, their goals
(represented as use cases), and any dependencies between those use cases. The main
purpose of a use case diagram is to show what system functions are performed for which
actor. Roles of the actors in the system can be depicted.
Use-case diagrams are formally included in two modeling languages defined by the: the
Unified Modeling Language (UML) and the Systems Modeling Language. A use case
describes a sequence of actions that provide something of measurable value to an actor and
is drawn as a horizontal ellipse.

Information System

Page 7

Figure 1

Information System

Page 8

Figure 2

Information System

Page 9

3.2 SYSTEM REQUIREMENTS

The major function is to provide notice board facility to the batch mentors. Information
system application can be accessed from anywhere so that it becomes select email of those
students who are satisfying the criteria of the required information and can send mail too
easy for the person to get access to all data anytime anywhere as required. With this, there
is also security in the application by allowing only secure login and only admin (batch
mentor) through admin login is allowed to make any changes and to maintain whole data.
All the students can view the upcoming events on the website, and all details related to that
event there.

3.2.1 FUNCTIONAL REQUIREMENTS

The functional requirement is describing the behaviour of the system as it relates to the
system's functionality. It depends on the type of software, expected users and the type of
system where the software is used. Accessing the information will be provided by a unique
login id and password to student and admin.

3.2.2 NON FUNCTIONAL REQUIREMENTS

The non-functional requirement elaborates a performance characteristic of the system.
These define system properties and constraints e.g. reliability, response time and storage
requirements. Constraints are I/O device capability, system representations, etc.

Secure access to confidential data is applied.

Low cost maintenance.
The system is more user friendly, reliable and flexible.
24*7 availability of the software.

3.2.3 EXTERNAL INTERFACE REQUIREMENT

The front-end will be designed through Bootstrap page with CSS, HTML and JavaScript
for client side validation whereas all business logics will be in PHP reside at middle layer.

Information System

Page 10

HARDWARE INTERFACE
Processor

Intel Pentium or more, IBM (Intel compatible)

Hard Disk

20 GB hard disk or more

RAM

Minimum 256 MB RAM for data processing

Operating System

Microsoft Windows

Programming Environment

PHP

Database

MySQL

Web server

XAMP

Web browsers

Internet Explorer, Google Chrome, Firefox

Scripting language

JavaScript

SOFTWARE INTERFACE

USER INTERFACE
For user through web application, web browsers with latest version are mandatory.
Technology stake used in the website is such that it makes latest web browsers a necessary
condition. Web browsers requirement for this product are:

Latest Google Chrome

Latest Firefox 4+
IE 7+

SECURITY
Each user has its own username and password through which he can login into the system
and add his information as well as interact with the notice board. Admin can provide
different information through notice board. So in term of security it is necessary to enter
username and password to enter into the system and if wrong entry will be made then
system will not allow you to log into in by providing different types of validation.

Information System

Page 11

COMMUNICATION INTERFACE
Information System shall use the HTTP protocol for communication over the internet and
for the intranet communication will be through TCP/IP protocol suite.

3.3 SOFTWARE SYSTEM ATTRIBUTES

USABILITY

The system shall allow the users to access the system from the Internet using HTML or
its derivative technologies. The system uses a web browser as an interface.
Since all users are familiar with the general usage of browsers, no specific training is
required.
The system is user-friendly and self-explanatory.

RELIABILITY
The system has to be very reliable due to the importance of data and the damages incorrect
or incomplete data can do. The system shall provide 100% access reliability.

AVAILABILITY
The system is available 100% for the user and is used 24 hours a day and 365 days a year.
The system shall be operational 24 hours a day and 7 days a week.

MAINTAINIBLITY
Even if the system fails, the system will be recovered back up within an hour or less.

ACCURACY
The accuracy of the system is limited by the accuracy of the speed at which the employees
of the library and users of the library use the system.

Information System

Page 12

4. SYSTEM DESIGN
System design refers to the technical specifications that will be applied in implementing the
candidate system.

Entities Definition
An entity is a person, place, thing or event for which data is collected and maintained.

Administrator: A person responsible for the performance or management of

administrative business operations.

Stakeholder: A person, group or organization that has interest or concern in an

organization.

4.1 ENTITY-RELATIONSHIP DIAGRAM

Figure 1

Information System

Page 13

Contact No.
Name
Email

ADMIN

STUDENT

Register

Password
Gender
Username

Username

Password

Course

Figure 2

4.2 SEQUENCE DIAGRAM

A Sequence diagram is an interaction diagram that shows how processes operate with one
another and what is their order. It is a construct of a message Sequence Chart. A sequence
diagram shows object interactions arranged in time sequence. It depicts the objects and
classes involved in the scenario and the sequence of messages exchanged between the
objects needed to carry out the functionality of the scenario. Sequence diagrams are
typically associated with use case realizations in the Logical View of the system under
development. Sequence diagrams are sometimes called event diagrams or event scenarios.

Information System

Page 14

Information System

Page 15

4.3 ACTIVITY DIAGRAM

Activity diagrams are graphical representations of work flows of stepwise activities and
actions with support for choice, iteration and concurrency. In the Unified Modeling
Language, activity diagrams are intended to model both computational and organizational
processes (i.e. workflows). Activity diagrams show the overall flow of control.

Information System

Page 16

4.4 CLASS DIAGRAM

A class diagram in the Unified Modeling Language(UML) is a type of static structure
diagram that describes the structure of a system by showing the system's classes, their
attributes, operations (or methods), and the relationships among objects. The class diagram
is the main building block of object oriented modeling. It is used both for
general conceptual modeling of the systematics of the application, and for detailed
modeling translating the models into programming code. The classes in a class diagram
represent both the main objects, interactions in the application and the classes to be
programmed.

Information System

Page 17

4.5 DATA-FLOW DIAGRAMS

A data flow diagram is a graphical representation of the flow of data through an
information system, modeling its process aspects. Often they are a preliminary steps used
to create an overview of the system which can be elaborated. DFD can also be used for the
visualization of data processing (structured design).
A DFD shows what kinds of data will be input to and output from the system, where the
data will come from and go to, and where the data will be stored. It does not show
information about the timing processes, or information about whether processes will
operate in sequence or in parallel.

Level 0: Physical DFD

Interacts with

STUDENT/FACULTY

ADMIN

Database

Level 1: Logical DFD

Database

STUDENT/FACULTY

Login

Information System

ADMIN

Login

Page 18

Level 2: DFD (Student)

View
Profile

STUDENT

Edit
Profile

Login

DATABASE

Visit
Profile
View
Notice
Change
Password

Level 2 DFD (Admin)

View
Profile
Edit
Profile

FACULTY

Edit
Notice

Information System

Login

Visit
Profile

DATABASE

Change
Password

Add
Student

Page 19

4.6 DATABASE DIAGRAM

Information System

Page 20

5. SOFTWARE DEVELOPMENT METHODOLOGY

The front end of the PIB will be designed through bootstrap and JavaScript. The
connectivity of the front end and the database will be implemented through PHP which is a
server side scripting language. The some major features of the above languages and tools
are described below.

5.1 FRONT END

BOOTSTRAP
Bootstrap was developed by Mark Otto and Jacob Thornton at Twitter as a framework to
encourage consistency across internal tools. Bootstrap is a free collection of tools for
creating websites and web applications. It contains HTML and CSS-based design templates
for forms, buttons, navigation and other interface components, as well as optional
JavaScript extensions. It is the most popular project on GitHub and has been used by
NASA and many others.

5.2 BACK END

MySQL
Many programming languages with language-specific APIs include libraries for accessing
MySQL databases. The official MySQL Workbench is a free integrated environment
enables users to graphically administer databases and visually design database structures. It
replaces the previous package of software, MySQL GUI Tools. Similar to other third-party
packages, but still considered the authoritative front-end. My SQL Workbench lets users
manage the following:
Database design & modeling

SQL development replacing MySQL Query Browser.

Database administration replacing MySQL Administrator.

In our project-All database created on the MySQL. The information of examine will be
stored on to the MySQL tables and maintained as a dynamically according to new
information.

Student and faculty registration, and login database also will be inserted in to MySQL
database.

Information System

Page 21

PHP
PHP is a general-purpose scripting language that is especially suited to server-side web
development originally created by Rasmus Lerdorf in 1995, where PHP generally runs on a
web server. Any PHP code in a requested file is executed by the PHP runtime, usually to
create dynamic web page content or dynamic images used on websites or elsewhere. PHP
is easy to learn and maintain.

XAMPP
XAMPP is a free and open source cross-platform web server solution stack package,
consisting mainly of the Apache HTTP Server, MySQL database, and interpreters for
scripts written in the PHP and Perl programming languages.

Information System

Page 22

6. SYSTEM TESTING
6.1 INTRODUCTION
System testing is an expensive but critical process that can take as much as 50 percent of
the budget for program development. The common view of testing held by users is that it is
performed to prove that there are no errors in a program. However, this is virtually
impossible, since analysts cannot prove that software is free and clear of errors.
Therefore, the most useful and practical approach is with the understanding that testing is
the process of executing a program with explicit intention of finding errors that is, making
the program fail. The tester, who may be an analyst, programmer, or specialist trained in
software testing, is actually trying to make the program fail. A successful test, then, is one
that finds an error. Analysts know that an effective testing program does not guarantee
systems reliability. Reliability is a design issue. Therefore, reliability must be designed into
the system. Developers cannot test for it.

6.2 TESTING METHODOLOGIES

6.2.1 Black box testing
The end users carry out black box testing. This testing can be performed by selecting some
persons of the organizations who have to operate the systems, so that they know what
inputs are to be given in this system for different options and what should be the output
than generating by the system for those values. They can then evaluate whether the system
is working as per users requirement.

6.2.2 White box testing

White box testing considers system to be like a white box, which means that everything
about the system is known to us. We know the different programs and procedures used in
the system, inputs supplied and output produced by it. The developers of the system
generally carry out white box testing. They test the system against all odd conditions for
extreme values.

Information System

Page 23

White box testing can be carried out in two parts1. Alpha Test
2. Beta Test

Alpha Testing
Alpha testing is simulated or actual operational testing by potential users/customers or an
independent test team at the developers' site. Alpha testing is often employed for off-theshelf software as a form of internal acceptance testing. Alpha test involves testing the
system by which test each and every part of the system separately.

Beta Testing
Beta testing comes after alpha testing 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 a
maximal number of future users.

6.2.3 Unit Testing

Unit testing, also known as component testing, refer to tests that verify the functionality of
a specific section of code, usually at the function level. It is performed by the software
developer or engineer during the construction phase of the software development lifecycle.

6.2.4 Integration Testing

Integration testing is any type of software testing that seeks to verify the interfaces between
components against a software design. Software components may be integrated in an
iterative way or all together ("big bang"). Normally the former is considered a better
practice since it allows interface issues to be located more quickly and fixed.

Information System

Page 24

6.2.5 System Testing

System testing, or end-to-end testing, tests a completely integrated system to verify that it
meets its requirements. In addition, the software testing should ensure that the program, as
well as working as expected, does not also destroy or partially corrupt its operating
environment or cause other processes within that environment to become inoperative (this
includes not corrupting shared memory, not consuming or locking up excessive resources
and leaving any parallel processes unharmed by its presence).

6.3 TEST PLANNING

When an extensive range or volume of data is needed for testing then using the test data
preparation tool is of great help. They are very useful for performance and reliability
testing, where a large amount of realistic data is needed. They may be used by developers
and may also be used during system or acceptance testing.
Test data preparation tools allow (enable) data to be selected from an existing database or
created, generated, manipulated and edited for use in tests. The most sophisticated tools can
deal with a range of files and database formats.

6.4 TEST CASES

A test case, in software engineering, is a set of conditions or variables under which a tester
will determine whether an application, software system or one of its features is working as
it was originally established for it to do. Here we test each module and component of the
system very carefully. We also validate that the mandatory fields should be filled or not, if
not then it will produce error.

Information System

Page 25

7. OUTPUT FORMS AND RESPONSES

User Interface is being designed to facilitate users interaction with the software. Following
is the home page of the Placement Information Broadcasting.

Home page
After admin login the profile of admin will be look like this

Information System

Page 26

Admin Login
Admin can login with their username and password. Following is admin page

User Login
Students can login with their username and password. Following figure is shown below:

Information System

Page 27

Registration Page
Page of student registration will be look like this.

Developer page
Developer page will be look like this.

Information System

Page 28

8. CONCLUSION
Information System is an application that enables faculty to circulate important
information. This application is helpful for students to gain all important information of
course, syllabus, current activities and notices, and maintain their information into the
database.

Limitation
There are some drawbacks of the system too

Each user has to remember his Information System username and password.

For the various other details students have to visit faculties directly.

This application does not provide communication from both side, only batch mentor
can circulate the information.

Information System

Page 29

9. FUTURE ENHANCEMENT

A single sign-in facility will be provided so student can access their account through
famous Gmail or Facebook portal.

A particular student can be notified about some important notices.

The online attendance can be added to the system.

Student can ask questions directly to batch mentors regarding various issues.

Information System

Page 30

BIBLIOGRAPHY

Reference Books

Elias M. Awad, System Analysis and Design, II Edition 2009, Galgotia Publication Pvt.
Ltd, New Delhi.

V.Rajaraman, Analysis and Design of Information system, II Edition 2002, Prentice

Hall of India, New Delhi.

PHP: The Complete Reference

Head First PHP & MySQL

Web Standards

7.2 Other resource

www.php.net/manual/en/tutorial.php

www.tutorialspoint.com/php

www.w3schools.com/PHP

www.getbootstrap.com

www.startbootstrap.com

www.bootply.com

www.stackoverflow.com

www.fedena.com

Information System

Page 31