chapters

!1
CHAPTER 1
INTRODUCTION
1.1 OBJECTIVE
The objective of this project is to develop an Online Information Portal for an
Institution so that portal admin is able to post, update and manage college circulars, notices,
events, manage hall booking and department contacts using a robust admin interface. The
project’s main objective is to overcome all the limitations and drawbacks of the existing
system by emphasising on simplicity of design and ease of implementation that helps the
administrators to manage and share most of the important and high priority information and
events going on in college premises from a single admin dashboard. This web based
application focuses on enhanced user interface and user experience for both administrators
and end users. The existing system is developed and deployed on Windows platform and
runs on commercial server provided by Microsoft. The project aims to be developed and
implemented using Open Source software and components. Rather than being a single
unified system, the modules and components of existing system are separate from each other
with each module having its own database, user interface and management console. So, to
overcome these limitations, one of the major objective of the project is to unify all the
separate modules and components into a single unified management system which utilises
same database, user interface and management console for all. The idea behind using open
source software for this project is that it gives freedom to use and modify the code by
developers and chose among various open source licenses. For many developers, peer
review and acclaim is important, so it's likely that they will prefer to build software that is
admired by their peers. Highly prized factors are clean design, reliability, scalability and
maintainability, with adherence to standards and shared community values with an ultimate
goal of managing all the aspects of circulars and notices as well as events in the college.

!2
CHAPTER 2
SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
The existing web based system is developed and deployed using a proprietary software
platform. Posting and managing circulars and notices as well as events not user friendly in a
sense that it lacks a proper admin interface for managing all the files and data. The front-end
modules and components of existing system are separate from each other with each module
having its own database, user interface and management console. The following points
highlight the main drawbacks of the existing system:
2.1.1 Drawbacks
• Lack of web based admin interface for each module.
• System does not have proper search interface for both backend and front-end.
• The existing system is not platform independent.
• Front-end is not unified with some modules lacking user friendly interface.
• Manual files and data management is time consuming.
• For developers and system maintenance team, it is a drawback that the existing system
can only be tested or debugged on Windows platform rather than having choice of
open source operating system like Linux.
• Managing various admin tasks are more complex compared to an automated system.
2.2 PROPOSED SYSTEM
The proposed system will try to overcome all the limitations and drawbacks of the
existing system by emphasising on simplicity of design and ease of implementation that helps
the administrators to manage and share most of the important and high priority information
and events going on in college premises from a single admin dashboard. The proposed system

!3
will also overcome the limitations of existing system by being platform independent. The
following points highlight the advantages of proposed system:
2.2.1 Advantages
• Robust and user friendly admin interface for all the system modules.
• Search user-interface for backend and front-end to allow administrators and users find
what they were looking for.
• The major advantage of the proposed system is the use of open source technology and
being platform independent.
• Unified backend and front-end interfaces with focus on enhanced user experience.
• Easy files and data management through admin dashboard.
• The system is developed and deployed using open source technologies which are
platform independent and eliminates the only choice of using Windows platform.
• For developers and maintenance team, it is a major advantage that the system can be
further scaled, modified, tested, debugged and enhanced in future on any operating
system of choice whether it is Windows or Linux or Mac OS.
• Various admin tasks and processes are automated for convenient files and data
management.

!4
CHAPTER 3
SYSTEM STUDY
3.1 FEASIBILITY STUDY
Feasibility study is an assessment of the practicality of a proposed project. A
feasibility study aims to objectively and rationally uncover the strengths and weaknesses of
an existing business or proposed venture, opportunities and threats present in the
environment, the resources required to carry through, and ultimately the prospects for
success. Feasibility study is a test of system proposal ac- cording to its work ability, impact
on the organisation, ability to meet user needs, and effective use of resources. The objective
for this phase is not to solve the problem but to acquire a sense of scope. During the study,
the problem definition is crystallised and aspects of the problem to be included in the system
are determined. There should be a careful assessment of each project before it is begun in
terms of economic justification, technical feasibility, operational impact and adherence to
the master development plan. We started the project by listing the possible queries that the
user might want to be satisfied. And on these lines we guided the project further.
The three main points, kept in mind at the time of project, are :
• Possible (To build it with the given technology and resources)
• Affordable (given the time and cost constraints of the organisation)
• Acceptable (for use by the eventual users of the system)
The three major areas to be considered while determining the feasibility of a project are :
• Technical Feasibility
• Operational Feasibility
• Economic Feasibility
• Timeline Feasibility

!5
3.1.1 Technical Feasibility
The technical issue usually raised during the feasibility stage of the investigation includes the
following :
• Does the necessary technology exist to do what is suggested?
• Do the proposed equipments have the technical capacity to hold the data required to
use the new system?
• Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
• Can the system be upgraded if developed?
• Are there technical guarantees of accuracy, reliability, ease of access and data
security?  
The current system developed is technically feasible. It is a web based system. Thus it
provides an easy access to the users and admin through any web browser. The databases
purpose is to create, establish and maintain a workflow among various entities in order to
facilitate all concerned users in their various capacities or roles. Permission to the users would
be granted based on the roles specified. Therefore, it provides the technical guarantee of
accuracy, reliability and security. The software and hardware requirements for the
development of this project are not many and are already available as free and open source.
The work for the project is done with the current equipment and existing software technology.
Necessary bandwidth exists for providing a fast feedback to the users irrespective of the
number of users using the system.
3.1.2 Operational Feasibility
Operational feasibility is a measure of how well a proposed system solves the
problems, and takes advantage of the opportunities identified during scope definition and how

!6
it satisfies the requirements identified in the requirements analysis phase of system
development. A systems development project is likely to be operationally feasible if it meets
the needs and expectations of the organisation. User acceptance is an important determinant of
operational feasibility. Anticipated performance and outcomes of the new system are
compared with the existing system. Under this category of service we conduct a study to
analyse and determine whether the organisation’s need can be fulfilled by using a proposed
solution. The result of this operational feasibility study will clearly outline that the solution
proposed for the organisation or the institution is operationally workable and conveniently
solves the problems under consideration after the proposal is implemented. Further in the
documentation, its precisely described how the system will interact with the users and
different systems. This feasibility report would provide results of interest to all stakeholders.
To ensure success, desired operational outcomes must be imparted during design and
development. These include such design-dependent parameters such as reliability,
maintainability, supportability, usability, producibility, disposability, sustainability,
affordability and others. These parameters are required to be considered at the early stages of
design if desired operational behaviours are to be realised. A system design and development
requires appropriate and timely application of engineering and management efforts to meet the
previously mentioned parameters.
3.1.3 Economic Feasibility
The purpose of the economic feasibility assessment is to determine the positive
economic benefits to the organisation that the proposed system will provide. It includes
quantification and identification of all the benefits expected. This assessment typically
involves a cost/ benefits analysis. This project is found to be economically feasible. More
commonly known as cost benefit analysis, the procedure is to determine the benefit and saving
that are expected from a candidate system and compare them with costs. Development of this
project on the long run was considered feasible when the various cost and benefits analysis
was done. Among the several cost elements, which affected the development of the system,

!7
were the hardware cost and facility cost. The other cost factors viz. Personal cost operating
cost and supply cost was absent or can be said negligible.
3.1.4 Timeline Feasibility
It is important to understand that a need must be fulfilled when it has to be. Some
otherwise feasible and highly desirable projects can become non-feasible due to very
restrictive timeline constraints. This fact makes it imperative that milestones are clearly linked
to the timeline and projects are well conceived with safe unforeseen margins. We make sure
that we strictly follow what has been stated above. A project will fail if it takes too long to be
completed before it is useful. Typically this means estimating how long the system will take to
develop, and if it can be completed in a given time period using some methods like payback
period. Timeline feasibility is a measure of how reasonable the project timetable is. Given our
technical expertise, are the project deadlines reasonable? Some projects are initiated with
specific deadlines. It is necessary to determine whether the deadlines are mandatory or
desirable. 
3.2 SOFTWARE REQUIREMENT SPECIFICATION DOCUMENT
3.2.1 Data Requirements
Data requirement is meant to be the data that will be used in our application. Data
required in this project is all circulars, that need to be conveyed to the user. This application
also require the username and passwords of admins in order to register them and make them
able to manage circulars, events and hall booking. So the four main requirements are:
• User details
• Circular Details
• Event Details
• Hall Details

!8
3.2.2 Functional Requirements
In order to make this application functional, we require the following:
• View web based application in browser 
A user should be able to view the application through any standards compliant web
browsers like Google Chrome, Mozilla Firefox, Safari, Opera and Internet Explorer.
The application is free and accessible to all users through web browsers.
• Admin Registration, roles and access 
Admin access to the system can be achieved by registering the user with all the
credentials provided. Various roles can be assigned to different admin users with full as
well as restricted access.
• Reset Password 
Given that a admin user has registered, then the user should be able to retrieve his/her
password as well as reset it.
• DashBoard 
Given that an admin user is logged in to the admin backend of the system, then the
first page that is shown should be the dashboard page. The user should be able to see
all the recent activities regarding posts and events.
• Front-end Homepage 
This homepage will be accessible to any user in the college premises using web
browser and given URL. The homepage consists of most recent and highlighted
circulars and notices, old circulars, archive calendar and list of upcoming events.
• Search Circular and events 
The user should be able to search for a circular by name, tag, title or description or can
easily navigate older circular and events through archive calendar on the homepage.
• Download the circulars and notices 
A user should be able to select and download any circular being posted. The user can
either view the circular in the browser itself or download for future references.
• Navigating back to circular and event list using calendar 
The user should be able to navigate back to circular list and events list from the
circular details section using calendar. This is required to give a good user experience.

!9
• Deleting, expiring and scheduling the circular 
The admin user should have the option to delete, expire and schedule the circulars
through backend admin interface.
• Posting Circular and Events 
The admin of this application should be able to post the circulars and events from the
backend. He or she should be able to add circular in the various formats like PDF,
image, HTML, MS Word Document, MS Excel along with audio and video. The files
and media can be managed from media library in the backend.
 
3.2.3 Performance Requirements
The requirements in this section provide a detailed specification of the user interaction with
the application and measurements placed on the system performance.
• Prominent search feature 
The search feature should be prominent and easy to find for the user.
• Usage of the Circular Information 
The circular link should be prominent and it should be evident that it is a usable link.
Selecting and downloading the circular link should only take one click.
• Response Time 
The response time should not be more than 5 seconds if the user is connected to the
local intranet and if the server is up and running.
• Fault Tolerance 
The fault tolerance of the system should be very good. If the system loses the
connection to the local area network or the system gets some strange input, the user
should be informed. 
3.2.4 Security Requirements
• Communication Security 
There should be security of the communication between the system and server. The
messages should be encrypted for log-in communications, so others cannot get user-
name and password from those messages. Every exchanges of information between
client and server should be encrypted so that no one can track it.

!10
• Admin Login Account Security 
If an admin tries to log in to the web portal with a non-existing account then the admin
should not be logged in. The admin should be notified about log-in failure.
• Admin Account Security 
There should be security of admin accounts. An admin and IP address should not be
able to log-in to the web portal for a certain time period after certain number of times
of failed log-in attempts.
• Admin User Create Account Security 
The security of creating account for admin users with different roles of the system
should be maintained. If a admin user wants to create an account and the desired user
name is occupied, the user should be asked to choose a different user name.
3.2.5 Maintainability Requirements
Following are the maintainability requirement of the project:
• Application extendibility 
The application should be easy to extend. The code should be written in a way that it
favours implementation of new functions. It is required in order for future functions to
be implemented easily to the application.
• Application testability 
Test environments should be built for the application to allow testing of the
applications different functions.

!11
 
CHAPTER 4
SYSTEM REQUIREMENTS
4.1 HARDWARE REQUIREMENTS
Web Server
Operating System : Ubuntu Linux or Windows Server
System : Intel Core i3 - i5
Ram : 4 - 8 GB
Hard disk : 500 GB
4.2 SOFTWARE REQUIREMENTS
Web server : Apache HTTP Server (bundled with XAMPP)
Backend : MySQL
Server side scripting : PHP 5.5 or above
Client side scripting : HTML5 / CSS3 / Javascript / JQuery
Development Tools : Sublime Text 2, Notepad++

!12
CHAPTER 5
SOFTWARE DESCRIPTION
5.1 LAMP (Software Bundle)
LAMP (referred to as WAMP for Windows and MAMP for Mac OS) is an archetypal
model of web service solution stacks, named as an acronym of the names of its original four
open-source components: the Linux operating system, the Apache HTTP Server, the MySQL
relational database management system (RDBMS), and the PHP programming language.
LAMP is suitable for building dynamic web sites and web applications.
Fig 5.1: A high-level overview of LAMP's determining components.
5.2 Apache HTTP Server
The role of LAMP's web server has been traditionally supplied by Apache. The
Apache HTTP Server has been the most popular web server on the public Internet. Apache is
developed and maintained by an open community of developers under the auspices of the

!13
Apache Software Foundation. Released under the Apache License, Apache is open-source
software. A wide variety of features are supported, and many of them are implemented as
compiled modules which extend the core functionality of Apache.
Fig 5.2: Apache Web Architecture
5.3 MySQL Server
MySQL Server is a powerful database management system and the user can create
application that requires little or no programming. It supports GUI features and an entire
programming language. PhpMyAdmin which can be used to develop rich interactive
applications. The MySQL database can act as a back end database for PHP. MySQL supports
the user with its powerful database management functions. A beginner can create his/her own
database very simply by some mouse clicks. Another good reason to use MySQL as back end
tool is that it is a component of the overwhelmingly popular Open source software.
5.4 PHP
PHP is a server-side scripting language designed for web development but also used as
a general-purpose programming language. Originally created by Rasmus Lerdorf in 1994, the

!14
PHP reference implementation is now produced by The PHP Group. PHP stands for the
recursive backronym PHP: Hypertext Preprocessor. PHP code is interpreted by a web server
via a PHP processor module, which generates the resulting web page. PHP commands can
optionally be embedded directly into an HTML source document rather than calling an
external file to process data. PHP is free software released under the terms of PHP License,
which is incompatible with the GNU General Public License (GPL) due to the restrictions
PHP License places on the usage of the term PHP.
5.5 WORDPRESS FRAMEWORK
WordPress is a free and open-source framework based on PHP and MySQL. It has a
web template system using a template processor which consists of Themes and Plugins.
Themes allow users to change the look and functionality of an application and they can be
installed without altering the content or health of the site. Plugin architecture allows users to
extend the features and functionality of a website or application.
Fig 5.3: Framework’s Working Principle

!15
CHAPTER 6
SYSTEM DESIGN
6.1 USE CASE DIAGRAM
A Use Case diagram at its simplest is a representation of a user’s interaction with the
system and depicting the specifications of a use case. A use case diagram can portray the
different types of users of a system and the various ways that they interact with the system.
This type of diagram is typically used in conjunction with the textual use case and will often
be accompanied by other types of diagrams as well. There are two types of user in this
application, user and admin. Following depicts their use case diagram:
Fig 6.1.1: Use Case Diagram for Circular Management

!16
Fig 6.1.2: Use Case Diagram for Event Management, Hall Booking and Contacts
Management

!17
6.2 ENTITY RELATIONSHIP (ER) DIAGRAM
An entity–relationship model (ER model) describes inter-related things of interest in a
specific domain of knowledge. An ER model is composed of entity types (which classify the
things of interest) and specifies relationships that can exist between instances of those entity
types. In software engineering an ER model is commonly formed to represent things that a
business needs to remember in order to perform business processes. Consequently, the ER
model becomes an abstract data model that defines a data or information structure that can be
implemented in a database, typically a relational database.
Entity–relationship modelling was developed for database design by Peter Chen and
published in a 1976 paper. However, variants of the idea existed previously, some ER
modellers show super and subtype entities connected by generalisation-specialisation
relationships, and an ER model can be used also in the specification of domain-specific
ontology. Entities may be characterised not only by relationships, but also by additional
properties (attributes), which include identifiers called "primary keys". Diagrams created to
represent attributes as well as entities and relationships may be called entity–attribute-
relationship diagrams, rather than entity-relationship models.
An ER model is typically implemented as a database. In a simple relational database
implementation, each row of a table represents one instance of an entity type, and each field in
a table represents an attribute type. In a relational database a relationship between entities is
implemented by storing the primary key of one entity as a pointer or "foreign key" in the table
of another entity. An Entity Relationship Diagram (ERD) is a visual representation of different
data using conventions that describe how these data are related to each other. ER diagrams are
most often associated with complex databases that are used in software engineering and IT
networks. In particular, ER diagrams are frequently used during the design stage of a
development process in order to identify different system elements and their relationships with
each other. For example, an inventory software used in a retail shop will have a database that
monitors elements such as purchases, item, item type, item source and item price.

!18
Fig 6.2.1: ER Diagram for Circular File Reference

!19
Fig 6.2.2: ER Diagram for Circular Posts, Options, Links, Users and Taxonomies

!20
6.3 FLOW DIAGRAM
Fig 6.3: Framework’s Flow Diagram

!21
6.4 DATABASE DESIGN
Table name: st_posts
Primary key: ID
Table 6.4.1 Circular Post Table
Table name: st_ai1ec_events
Primary key: post_id
Table 6.4.2 Event Table
Field Type Null Default
ID bigint(20) No NULL
post_date datetime No
post_title text No
post_status varchar(20) No
Field Type Null Default
post_id bigint(20) No NULL
start int(10) No
end int(10) Yes
venue varchar(255) Yes
contact_name varchar(25) Yes
contact_phone varchar(32) Yes

!22
CHAPTER 7
SYSTEM DEVELOPMENT
7.1 PROJECT DESCRIPTION
This project is to develop an Intranet based web application to post, update and
manage college circulars, notices, events, manage hall booking and department contacts using
a robust admin interface. The system has robust and user friendly admin interface for all the
system modules. It has search user-interface for backend and front-end to allow administrators
and users find what they were looking for. The major advantage of this project is the use of
open source technology and being platform independent.
7.2 MODULES
The system consists of the following modules:
• Admin
• Front-end interface
• Event
• Hall Booking
• News Tracker
• Contacts
7.2.1 Admin Module
This module is developed for administrators who can perform the tasks such as add
new circular post, schedule post, create and manage events, create users and their roles,
manage hall reservation and calendar, create plugins, add tabular data and manage news. The
admin can also manage files and data using media library. Here administrator has to login by
using their unique user name and password. Administrators are the only authorized person to

!23
access admin module for security purpose. So other user doesn’t get rights to access this
module.
The following tasks can be performed by administrators:
• Add, edit, delete and schedule circular posts.
• Create, update and manage event details and event calendars.
• Create hall categories, manage hall reservations and update booking schedules.
• Add tabular data like contacts and update them.
• Add and manage posts categories.
• Add and update news informations.
7.2.2 Front-end Interface Module
This is the front-end interface for viewing circulars, posts, notices, news, events,
contacts and hall information. This module is viewed using a web browser and a specified
URL that shows the latest circular and event details. In intranet, users can freely access this
module without any restrictions. This module focusses on enhanced user interface and user
experience through best design practices.
7.2.3 Event Module
In this module, events list is organised in a calendar form where users can select
particular department and date and can view details about upcoming events in the college.
Users have full access to calendar that is organised in daily, weekly, monthly and yearly
format. The events are listed inside the calendar.
7.2.4 Hall Booking Module
In this module, users can select one of the listed halls and can reserve for any
particular event or seminar. The hall booking module consists of calendar interface where it

!24
shows hall availability, booking status and time slots to book and reserve. Once user books a
hall, the information is sent to admin at the backend where it can be updated and managed.
7.2.5 News Tracker Module
In this module, news and information from various sources like web and news portal is
published. It is updated daily and consists of different categories of news ranging from
technology, business to world news. Daily news is archived so that users can search and view
previous news by navigating through calendar.
7.2.6 Contacts Module
In this module, updated contact details of each department is published. The contact
details can be viewed in tabular form or can be downloaded as a PDF or Word document.
Contact details can also be searched through the search interface which uses AJAX to perform
high speed search.

!25
CHAPTER 8
SYSTEM TESTING
Software testing is a process of executing a program or application with the intent of
finding the software bugs. It can also be stated as the process of validating and verifying that a
software program or application or product meets the business and technical requirements that
guided it's design and development. 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 stakeholders desire.
8.1 TYPES OF TESTING
8.1.1 Unit testing
Unit testing, also known as component testing, refers to tests that verify the
functionality of a specific section of code, usually at the function level. In an object-oriented
environment, this is usually at the class level, and the minimal unit tests include the
constructors and destructors. These types of tests are usually written by developers as they
work on code (white-box style), to ensure that the specific function is working as expected.
One function might have multiple tests, to catch corner cases or other branches in the code.
Unit testing alone cannot verify the functionality of a piece of software, but rather is used to
ensure that the building blocks of the software work independently from each other.

!26
Unit testing is a software development process that involves synchronized application of a
broad spectrum of defect prevention and detection strategies in order to reduce software
development risks, time, and costs. It is performed by the software developer or engineer
during the construction phase of the software development lifecycle. Rather than replace
traditional QA focuses, it augments it. Unit testing aims to eliminate construction errors before
code is promoted to QA; this strategy is intended to increase the quality of the resulting
software as well as the efficiency of the overall development and QA process.
Test strategy and approach
Field testing will be performed manually and functional tests will be written in detail.
Test objectives
• All field entries must work properly.
• Pages must be activated from the identified link.
• The entry screen, messages and responses must not be delayed.
Features to be tested
• Verify that the circular entries are of the correct format
• No duplicate entries should be allowed
• All links should take the user to the correct page.
Unit Testing for PHP
PHPUnit is a programmer-oriented testing framework for PHP. It is an instance of the xUnit
architecture for unit testing frameworks. PHPUnit invokes the PHPUnit command-line test
runner. The following page shows various testing phases for each type of circular post and
different types of pages.

!27
404 Page
• The 404 page displays properly
• Some content is displayed, more than merely the basic "Error 404 - Page Not Found"
message - such as some helpful text, a search form, a list of Post or Pages, etc.
• Debugger returns no PHP errors, warnings, or notices
• The browser reports no JavaScript errors
Search Results Page
• The Search Results page displays properly, with search query results displayed.
• Debugger returns no PHP errors, warnings, or notices
• The browser reports no JavaScript errors
• Circular Posts Index Pages display correctly
• Test the following posts when viewing the Circular Posts Index page. Post Titles in the
test data correlate with section titles below.
Scheduled Post
• Should not be displayed by the Theme (status "scheduled", rather than "publish").
Draft Post
• Should not be displayed by the Theme (status "draft", rather than "publish").
Layout Test
• Displays properly as a "Sticky Post."
• Page navigation links display and work properly.
Readability Test
• Displays "Read More" link properly.
• "Read More" link works properly (links to single post at "More" tag location).
Post Format Tests (All)
• If Theme supports Post Format Type, Post displays as intended in the index view
Post Format Test: Gallery
• Gallery images display as intended in the index view
Post Format Test: Image (Linked)
• Image displays as intended in the index view

!28
• Image does not overflow the content area
Post Format Test: Image (Attached)
• Image displays as intended in the index view
• Image does not overflow the content area
Post Format Test: Video
• Video displays as intended in the index view
• Video does not overflow the content area
8.1.2 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.
Integration testing works to expose defects in the interfaces and interaction between
integrated components (modules). Progressively larger groups of tested software components
corresponding to elements of the architectural design are integrated and tested until the
software works as a system.
The different types of Integration testing are as follows:
• Big Bang: In this approach, most of the developed modules are coupled together to
form a complete software system or major part of the system and then used for
integration testing. The Big Bang method is very effective for saving time in the
integration testing process.
• Top-down and Bottom-up: Bottom Up Testing is an approach to integrated testing
where the lowest level components are tested first, then used to facilitate the testing of
higher level components. The process is repeated until the component at the top of the
hierarchy is tested. Top Down Testing is an approach to integrated testing where the
top integrated modules are tested and the branch of the module is tested step by step
until the end of the related module.

!29
8.1.3 Functional Test
Functional tests provide systematic demonstrations that functions tested are available
as specified by the business and technical requirements, system documentation, and user
manuals.
Functional testing is centred on the following items:
Valid Input : identified classes of valid input must be accepted.
Invalid Input : identified classes of invalid input must be rejected.
Functions : identified functions must be exercised.
Output : identified classes of application outputs must be exercised.
Systems/Procedures : interfacing systems or procedures must be invoked.
Preparation of functional tests is focused on requirements, key functions, or special
test cases. In addition, systematic coverage pertaining to identify Business process flows; data
fields, predefined processes, and successive processes must be considered for testing. Before
functional testing is complete, additional tests are identified and the effective value of current
tests is determined.
8.1.4 System Test
System testing ensures that the entire integrated software system meets requirements.
It tests a configuration to ensure known and predictable results. An example of system testing
is the configuration oriented system integration test. System testing is based on process
descriptions and flows, emphasizing pre-driven process links and integration points.
8.1.5 White Box Testing
White-box testing (also known as clear box testing, glass box testing, transparent box
testing, and structural testing) is a method of testing software that tests internal structures or
workings of an application, as opposed to its functionality (i.e. black-box testing). In white-
box testing an internal perspective of the system, as well as programming skills, are used to
design test cases.

!30
The tester chooses inputs to exercise paths through the code and determine the
appropriate outputs. This is analogous to testing nodes in a circuit, e.g. in-circuit testing (ICT).
White-box testing can be applied at the unit, integration and system levels of the software
testing process. Although traditional testers tended to think of white-box testing as being done
at the unit level, it is used for integration and system testing more frequently today. It can test
paths within a unit, paths between units during integration, and between subsystems during a
system–level test. Though this method of test design can uncover many errors or problems, it
has the potential to miss unimplemented parts of the specification or missing requirements.
8.1.6 Black Box Testing
Black Box Testing is testing the software without any knowledge of the inner
workings, structure or language of the module being tested. Black box tests, as most other
kinds of tests, must be written from a definitive source document, such as specification or
requirements document, such as specification or requirements document. It is a testing in
which the software under test is treated, as a black box .you cannot “see” into it. The test
provides inputs and responds to outputs without considering how the software works.
8.1.7 Acceptance Testing
User Acceptance Testing is a critical phase of any project and requires significant
participation by the end user. It also ensures that the system meets the functional requirements.
Test Results: All the test cases mentioned above passed successfully. No defects encountered.

!31
CHAPTER 9
SYSTEM MAINTENANCE
The results obtained from the evaluation process help the organization to
determine whether its information systems are effective and efficient or otherwise. The
process of monitoring, evaluating, and modifying of existing information systems to make
required or desirable improvements may be termed as System Maintenance. System
maintenance is an ongoing activity, which covers a wide variety of activities, including
removing program and design errors, updating documentation and test data and updating
user support.
For the purpose of convenience, maintenance may be categorized into two classes,
namely:
• Corrective: This type of maintenance implies removing errors in a program,
which might have crept in the system due to faulty design or wrong assumptions.
Thus, in corrective maintenance, processing or performance failures are repaired.
• Adaptive: In adaptive maintenance, program functions are changed to enable the
information system to satisfy the information needs of the user. This type of
maintenance may become necessary because of organizational changes which may
include:
a) Change in the organizational procedures,
b) Change in organizational objectives, goals, policies, etc.
c) Change in forms,
d) Change in information needs of administrators.
e) Change in system controls and security needs, etc.

!32
CHAPTER 10
CONCLUSION AND FUTURE ENHANCEMENT
10.1 CONCLUSION
Online Information Portal for Institution is specially designed web portal that brings
college information together from diverse sources and all departments in a uniform way.
Usually, each information source gets its dedicated area on the page for displaying
information called a portlet. Each portlet consists of information regarding college circulars,
news, upcoming events, display different halls like seminar halls, auditoriums etc to reserve
for particular event, staff birthday details and department wise contact details. The extent to
which content is displayed in a "uniform way" may depend on the intended user and the
intended purpose, as well as the diversity of the content. This project emphasises on creating
unified and single interface and robust and secure backend for admin to manage all the
information regarding college circulars, news, upcoming events, hall reservations and contact
details.
10.2 FUTURE ENHANCEMENT
Every application has its own merits and demerits. The project has covered almost all
the requirements. Further requirements and improvements can easily be done since the coding
is done in MVC (Module View Controller) pattern. Changing the modules can append
improvements. Further enhancement can be made to the project, so that the website’s
functionality can be improved and user experience can be enhanced.
The future enhancements of the project are:
• Adding more modules related to college circular sharing.
• Adding enhanced birthday event and plugin to display staffs’ birthday.

!33
APPENDIX A
SCREEN SHOTS
A1: Circular Homepage
A2: Admin Login Page

!34
A3: Add New Circular Post Page
A4: Event Management Page

!35
A5: Hall Booking Page
A6: News Tracker Page

!36
APPENDIX B
SOURCE CODE
config.php
<?php
define( 'WPCACHEHOME', '/Applications/MAMP/htdocs/sonatimes/wp-content/plugins/wp-super-
cache/' );
define('DB_NAME', 'dbname');
define('DB_USER', 'root');
define('DB_PASSWORD', 'root');
define('DB_HOST', 'localhost');
define('DB_CHARSET', 'utf8mb4');
define('DB_COLLATE', ‘');
?>
content.php
<article id="post-<?php the_ID(); ?>" <?php post_class(); ?>>
<?php
twentyfifteen_post_thumbnail(); ?>
<header class="entry-header">
<?php
if ( is_single() ) :
the_title( '<h1 class="entry-title">', '</h1>' );
else :
the_title( sprintf( '<h2 class=“entry-title">

!37
<a href="%s" rel="bookmark">', esc_url( get_permalink() ) ), '</a></h2>' );
endif;
?>
</header
<div class="entry-content">
<?php
the_content( sprintf(__( 'Continue reading %s', 'twentyfifteen' ),
the_title( '<span class="screen-reader-text">', '</span>', false )
) );
wp_link_pages( array( 'before' => '<div class="page-links"><span class="page-links-title">' .
__( 'Pages:', 'twentyfifteen' ) . '</span>',
'after' => '</div>',
'link_before' => '<span>',
'link_after' => '</span>',
'pagelink' => '<span class="screen-reader-text">' . __( 'Page',
'twentyfifteen' ) . ' </span>%',
'separator' => '<span class="screen-reader-text">, </span>',
) );
?>
<?php
if ( is_single() && get_the_author_meta( 'description' ) ) :
get_template_part( 'author-bio' );
endif;
?>
</article>

!38
sidebar.php
<?php
if ( has_nav_menu( 'primary' ) || has_nav_menu( 'social' ) || is_active_sidebar( 'sidebar-1' ) ) : ?>
<div id="secondary" class="secondary">
<?php if ( has_nav_menu( 'social' ) ) : ?>
<nav id="social-navigation" class="social-navigation" role="navigation">
<?php
wp_nav_menu( array(
'theme_location' => 'social',
'depth' => 1,
'link_before' => '<span class="screen-reader-text">',
'link_after' => '</span>',
) );
?>
</nav> <?php endif; ?>
<?php if ( is_active_sidebar( 'sidebar-1' ) ) : ?>
<div id="widget-area" class="widget-area" role="complementary">
<?php dynamic_sidebar( 'sidebar-1' ); ?>
</div> <?php endif; ?>
</div>
<?php endif; ?>

!39
header.php
<?php body_class(); ?>>
<div id="page" class="hfeed site">
<a class="skip-link screen-reader-text" href="#content"><?php _e( 'Skip to content',
'twentyfifteen' ); ?></a>
<div id="sidebar" class="sidebar">
<header id="masthead" class="site-header" role="banner">
<div class="site-branding">
<button class="secondary-toggle"><?php _e( 'Menu and widgets',
'twentyfifteen' ); ?></button>
</div> </header>
<?php get_sidebar(); ?>
</div>
<div id="content" class="site-content">
<div class="customs-header">
<div class="sona-logo">
<a href="<?php echo esc_url( home_url( '/' ) ); ?>" rel="home" title="SonaTimes
Home">
<img src="<?php bloginfo('stylesheet_directory'); ?>/wp-images/
sonatimes_logo2.png" width="257" height="55" alt="SonaTimes - Sona College of Technology"></a>
</div>
<?php if ( has_nav_menu( 'primary' ) ) : ?>
<nav id="site-navigation" class="sona-navigation" role="navigation">
<?php
wp_nav_menu( array(
'menu_class' => 'sona-menu',

!40
'theme_location' => 'primary',
) );
?>
</nav>
<?php endif; ?>
page.php
get_header(); ?>
<div id="primary" class="content-area">
<main id="main" class="site-main" role=“main">
<?php
while ( have_posts() ) : the_post();
get_template_part( 'content', 'page' );
endwhile;
?>
</main> </div>
<?php get_footer(); ?>

!41
REFERENCES
PHP/MYSQL REFERENCE SITES
• http://www.w3schools.com
• http://www.tuxradar.com/practicalphp
• http://phpbuddy.com/index.php
• http://www.daniweb.com
• http://www.pscode.com
• http://dev.mysql.com
• http://www.mysqltutorial.org/
PHP/MYSQL REFERENCE BOOKS
1. Beginning PHP 5.3 - Matt Doyle Publication, first Edition, (October 26, 2009).
2. Expert PHP and MySQL - Andrew Curioso, Ronald Bradford, Patrick Galbraith
Publication, Fourth Edition,2010
3. Beginning Php and Mysql –W.Jason Gilmore Publication, Fourth Edition,2010
4. PHP and MySQL 24-Hour Trainer - Andrea Tarr Publication, Second Edition,2011
5. Web Database Applications with PHP & MySQL, - Hugh E. Williams (Author), David
Lane Publication, Second Edition,2009

chapters

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (13)

Similar to chapters

Similar to chapters (20)

chapters