Project Report: "Webblog" Techindustan Private Ltd. Mohali
Project Report: "Webblog" Techindustan Private Ltd. Mohali
ON
“WEBBLOG”
IN
TecHindustan Private Ltd. Mohali
A REPORT SUBMITTED FOR SOFTWARE DEVELOPMENT PROJECT
(FOR MCA STUDENTS) IN PARTIAL FULFILMENT OF DEGREE OF
MASTER OF COMPUTER APPLICATION
SUBMITTED TO
HIMACHAL PRADESH UNIVERSITY
My efforts and wholehearted co-corporation of each and every one has ended on a
successful note. During this journey, I faced numerous unforeseen problems and
unknown challenges. However, at these junctures, a few enterprising people
stepped in and guide me in a right direction.
I’ll also express my sincere gratitude to Our Project Leader Mr. Babban Singh of
TecHindustan Pvt. Ltd., for their constant encouragement and support at all stages
of this project. I also thank them for inducing professional attitude in me.
At last but not the least, I pay my due regards to my parents and Friends, because
every time they encourage, and support me when I need or require.
Kritika Chauhan
Internal Guide’s Profile
Name :
___________________________________________
University :
___________________________________________
Designation :
___________________________________________
Current Experience :
___________________________________________
__________________________________________________________________
____
__________________________________________________________________
____
Qualification : _______________________________________
1. INTRODUCTION TO COMPANY 1
2.4.2 Application 5
3. SYSTEM MODULE 8
3.1 Module 8
5. PLATFORM 30-35
DESIGN CONSIDERATIONS 36
6.
37
SOFTWARE REQUIREMENT
38
HARDWARE REQUIREMENT
7. FEASIBILITY STUDY 39
INTRODUCTION 40
TYPES OF FEASIBILITY 43
SDLC 44
DFD 46
8. SYSTEM DESIGN 52
DATABASE 54
SNAPSHOTS OF PROJECT 55
9. INTERFACE DESIGN , CODING 70
13 CONCLUSION 118
1. Introduction to Company-:-
In recent past time Blogs are store in the paper files and difficult to search or modify any
information, for expanding the Blogs infrastructure, Awareness of environmental issues or
any other issues related to education, health, digital technology, and search for greater
safety give to information to all persons in all age groups and a new role within the
education system, I choose this project. As a result of these project initiatives phenomenal
growth has taken place in all the activities of blogs and any user can share its information
related to any topic to all users.
Existing system is manual system. It requires a lot of file work to be done. It is a time
consuming system. All customer information is maintained manually. Any searching
requires so much effort manually.
There is no way of spreading the information so fast and in cheapest manner. In previous
system all information does not get in one place. Here people can write whatever they want
to write.
a) Data redundancy and formatting: The various files are likely to have different
formats and therefore lead to redundancy and inconsistency.
c) Error prone: Existing systems are error prone, since manual work is required.
More time is consumed and errors may propagate due to human mistakes.
d) Low security feature: Due to maintenance's of records manually and shared and
could view easily by anyone. Also these could be possible loss of data and
confidential information due to some disaster in the form of fire, theft etc.
2.4.2Applications
WEBLOG enables the users to create innovative and attractive information with
photos in just few simple steps. The user just needs to upload some images of his
choice and can also upload the information or can select from the given category list.
This website will provide a personalized environment that would contain the data in
motion with images.
3. SYSTEM MODULE:-
3.1The modules involved in this project are:
1. User
2. Admin
1. User
In this module:
o User can signup
o User can login
o User can upload multiple images
o User can choose images from database
o User can add information
o User can add comments
o User can select any categories
2. Admin
In this module:
o Admin can block user id
o Admin can resume user id
o Admin can see all pages
o Admin can maintain all records of user
o Admin can maintain all site
o Admin can access and process all requests
o Admin can delete/update/select users
o Admin Provide all information related to any topic
3.2 Change Account Information:-
Update Account information like Name, Address, Email ID and their detail.
3.7 Maintenance: -
The system allows following Maintenance processes
◦ Manage Blogs
◦ Manage Blogs Categories
◦ Manage Recent posts
◦ Manage users
◦ Manage images
◦ Manage Comments
◦ Manage news
◦ Security Questions
◦ Manage Contact us
4. SYSTEM ANALYSIS
4.1 DATA ANALYSIS
Before developing this project, we first analyse existing system of study. In existing
system all greetings are given manually. As we know, now a day computer is used in
every field. We can remove the manual work by using automatic system. We see it first
that if it is feasible or not whether technically, economically, operationally. We test that
whether it properly works or not. Its technical requirements are feasible or not. We
analysed the system properly and then start designing it. After designing, we implement
this project that whether this project works properly or not. After implementing the
project, we check that whether there is any problem for the user while using this project.
Prior to stating whether the system we have to develop is feasible or not we believe that
we should emphasize on what is implied by the word “Analysis”. Analysis is the measure
of how beneficial or practical the development of the system will be to the organization.
It is a preliminary survey for the systems investigation. It aims to provide information to
facilitate a later in-depth investigation.
Types
There are various measures of analysis that helps to decide whether a particular project is feasible
or not.
These measures include –
Operational Analysis
Technical Analysis
Economic Analysis
Each of these types will be explained in detail throughout the project report
4.1.1Operational analysis
A proposed system is beneficial only if it can be turned into an information
system that will meet the operational requirements of an organization. A system
often fails if it does not fit within existing operations and if users resist the
change. Important issues a systems developer must look into are:
Will the new system be used if implemented in an organization?
Are there any major barriers to implementation or is proposed system
accepted without destructive resistance?
The whole purpose of computerizing it is to handle the work much more
accurately and efficiently with less time consumption. There will be additional
work to be completed, because now the website will have to maintain database
of both their admins as well as their Customers. Compared to the semi-
computerized system the chances of avoiding errors in a computerized system is
much higher because the user need not stress himself unnecessarily resulting in
recklessness. Unlike the semi-computerized system there would be backup data
for all the information concerning the daily transactions occurred. Another
important fact to be regarded is the security control, which is handled by the
system. Since data regarding each Customer is confidential, security is a key
issue. Information falling into the wrong hands could jeopardize the entire
website organisation. Unlike in semi-computerized systems, the proposed
system offers adequate control to protect against fraud and embezzlement and
guarantees the accuracy and Security of data and information. This is handled
by the system providing individuals with separate login names and passwords.
The new system is user-friendlier, which enables the end-user to complete
his/her work efficiently and accurately with interest. After taking the above fact
into consideration we can state the operating of the proposed system is feasible.
System security is a vital aspect when it comes to developing a system. The system
should ensure the facility of preventing unauthorized personnel from accessing the
information and the data within the system. The system should provide total protection
for each user’s information so that the integrity of data is sustained and also prevent
hackers from hacking the system. The proposed system ensures the security and the
integrity of data. This is done by providing a password login system for each authorized
users. And for example the System Administrator has access to all kinds of information.
By providing this facility information is properly managed and information is protected.
For example the system administrator’s day to day tasks are lessened and easier because
he doesn’t have to have a constant eye on the system and worry about hackers hacking
the system.
The Analysis Phase is where the project lifecycle begins. The Analysis Phase is where
you break down the deliverables in the high-level Project Charter into the more detailed
business requirements. The Analysis Phase is also the part of the project where you
identify the overall direction that the project will take through the creation of the project
strategy documents.
Gathering requirements is the main attraction of the Analysis Phase. The process of
gathering requirements is usually more than simply asking the users what they need and
writing their answers down. Depending on the complexity of the application, the process
for gathering requirements has a clearly defined process of its own. This process consists
of a group of repeatable processes that utilize certain techniques to capture, document,
communicate, and manage requirements. This formal process, which will be developed in
more detail, consists of four basic steps.
1. Elicitation – I ask questions, you talk, I listen
2. Validation – I analyze, I ask follow-up questions
3. Specification – I document, I ask follow-up questions
4. Verification – We all agree
Although gathering requirements is the main focus during the Analysis Phase, there are
other important activities during this phase as well. One is to create a Requirement
Management Plan to define how the requirements will be documented, communicated,
tracked and changed throughout the rest of the project lifecycle. This plan will
specifically address establishing a baseline, a change control process, and a way to track
the requirements through the rest of the lifecycle. Another important activity is to set the
overall direction for work that does not take place until later. This is accomplished
through a series of direction-setting strategy documents. For instance, once you have your
requirements, you can start to set the overall direction for training in a Training Strategy
document. The strategies are at a high-level and are later defined at a lower level before
they are finally implemented toward the end of the project.
5. PLATFORM
TECHNOLOGIES TO BE USED:-
Platform:
a. Front end: HTML, CSS, JAVASCRIPT, JQUERY, JSON, Ajax.
b. Back end: MYSQL 2005 as the back end.
5.1 PHP:-
Advantages of PHP
PHP is accessible.
It is available for free.
It is available with documentation in many languages.
There are many support groups and team support PHP.
There is wealth of online information regarding PHP.
It is quick to develop in PHP.
PHP is loosely typed which makes basic script much faster to develop with less
Attention to design.
It runs on many different operating systems.
5.1.1 What is the scope of PHP?
If you are planning to build your career in Web technology then PHP is the best
programming scripting language to learn and is also a good career option. PHP
Is basically a scripting language used for web development. The websites created by
PHP are dynamic and attractive. So Because of this reason it is demanded the
Most in web technology.PHP is an open source so is used freely without any cost
And so greatly in demand. Scope in PHP really high as PHP is a language knows in
The world of technology since many years. So it has gained the maximum popularity
In this era.
5.1.2 HTML:
HTML Tags:
5.1.3 CSS:
CSS Syntax:
A CSS rule has two main parts: a selector, and one or more declarations:
The selector is normally the HTML element you want to style.
Each declaration consists of a property and a value.
The property is the style attribute you want to change. Each property has a value.
5.1.4 XAMPP:-
XAMPP is a free and open source cross-platform web server solution stack package
developed by Apache Friends,[1] consisting mainly of the Apache HTTP Server, Maria
DB database, and interpreters for scripts written in the PHP and Perl programming
languages.[2][3] XAMPP stands for Cross-Platform (X), Apache (A), Maria DB (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 and deployment purposes. Everything needed
to set up a web server – server application (Apache), database (Maria DB), 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.
Acronym
Acronym Meaning
Letter
P PHP
P Perl
5.1.5 MY SQL:-:
JSON: JavaScript object notation is a lightly weight data-interchange format. It is easy for
humans to read and write. It is for machines to parse and generate. It is based on a subset
of JavaScript. Json is text format that is complete language independent but uses
conventions that are familiar to programmers of the C family of languages, including C,
C++, C#, Java, JavaScript, Perl, Python and many languages. These properties make Json
an ideal data-interchange language.
AJAX: Asynchronous JavaScript and XML. Ajax is a technique for creating fast and
dynamic web pages. Ajax allows web pages to be updated asynchronously by exchanging
small amounts of data with server behind the scenes. This means that it is possible to update
parts of web page, without reloading the whole page.
Scripting Languages:-
6.2Hardware Requirements:-
(7.1) INTRODUCTION:-
Feasibility is the measure of how beneficial or practical the development of the system
will be to the organization. It is a preliminary survey for the systems investigation. It aims
to provide information to facilitate a later in-depth investigation.
The report produced at the end of the feasibility study contains suggestions and reasoned
arguments to help management decide whether to commit further resources to the proposed
project.
Within the scheduled duration we were assigned to study both the positive and negative
aspects of the current manual system, in which we have come up with a number of
drawbacks that prevent the progress of the clinic if it is continued to function manually.
Having gone through all measures of feasibility we report to the management to figure out
if the objectives of the new system are met.
For e.g.: –
There are various measures of feasibility that helps to decide whether a particular project
is feasible or not. These measures include:
Technical Feasibility
Operational Feasibility
Economical Feasibility
Each of these types will be explained in detail throughout the project report.
(7.2.1) TECHNICAL FEASIBILITY
Based on the outline design of system requirements in terms of inputs, outputs, files,
procedures and staff, the technical issues raised during technical feasibility include:
Does the proposed equipment have the technical capacity to hold the data required
to use in the new system?
Is there any technical guarantee of accuracy, reliability, ease of access and data
security?
A system often fails if it does not fit within existing operations and if users resist the
change.
Another important fact to be regarded is the security control, which is handled by the
system. Since data regarding each user is confidential, security is a key issue. Here, in this
system, data regarding users is stored in database which can only be accessed by the
authorized administrator.
The new system is more user-friendly, which enables the end-user to complete his/her work
efficiently and accurately with interest. After taking the above fact into consideration we
can state the operating of the proposed system within the organization is feasible.
The proposed system must be justifiable in terms of cost and benefit, to ensure that the
investment in a new/changed system provide a reasonable return.
Even though finding out the costs of the proposed project is difficult we assume and
estimate the costs and benefits as follows.
According to the computerized system we propose, the costs can be broken down to two
categories:
Software engineering is a discipline that integrates process, methods, and tools for the
development of computer software. To solve actual problems in an industry setting,
software engineer or a team of software engineers must incorporate a development strategy
that encompasses, methods, and tools. This strategy is often referred to as a process model
or a software-engineering paradigm.
A number of different process models for the software engineering have been proposed,
each exhibiting strengths and weaknesses, but all having a series of generic phases in
common. Some of the commonly used software process models are:
A particular process model for software engineering is chosen on the nature of the project
and the application at hand, the methods and the tools to be used, and the controls are
required.
Status Quo
Problem Definition
Technical Development
Solution Integration
Design:
Software design is actually a multi-step process that focuses on four distinct attributes of a
program: data structures, software architecture, interface representations, and procedural
(algorithm) detail. The design process translates requirement into a representation of the
software that can be assessed for quality before code generation begins.
Code Generation:
The design must be translated in to a machine-readable form. The testing process focuses
on the logical internals of the software, assuring that all statements have been tested and
on the functional externals that is, conducting tests to uncover errors and ensure that
defined inputs will produce actual results that agree with required results.
Testing:
Once code has been generated, program testing begins. The testing process focuses on the
logical internals of the software, assuring that all statements have been tested and on the
functional externals that is, conducting tests to uncover errors and ensure that defined
inputs will produce actual results that agree with required results.
Maintenance
Software will undoubtedly undergo change after it is delivered to the customer (A possible
exception is embedded software).Change will occur because errors have been encountered,
because the software must be adapted to accommodate change in its external environment
(e.g. A change required because of a new operating system or peripheral device), or
because the customer requires functional or performance enhancements.
To understand the nature of the program(s) to be built, the software engineer (“analyst”)
must understand the information domain for the software, as well as required function,
behavior, performance, and interfacing. Requirements for the both the system and the
The software developed here assumes the use of PHP for connection between the Front
End and the database. The speed of the User’s connection will depend on how fast they
approach the site. The Admin will run the users requests and will have an access to
database.
Security- The system is well secured, i.e. admin and user both have their unique
involved.
Portability- The system is portable i.e. it can work on any other system of the
admin.
Use cases are used during the analysis phase of a project to identify system
functionality. They separate the system into actors and use cases. Actors represent
roles that are played by users of the system. Users may be humans, other computers,
Brief Description:
The user approaches the site and retrieve data of his choice.
Diagram:
Retrieve Data
User
Brief Description:
The customer submits his chosen data to the database for the implementation purpose.
Diagram:
Choose Media
User
Process
Admin
View
Request
Log In
7.4.7Object Oriented Analysis
Object–Oriented Analysis (OOA) is the procedure of identifying software engineering
requirements and developing software specifications in terms of a software system’s object
model, which comprises of interacting objects. In the system analysis or object-oriented
analysis phase of software development, the system requirements are determined, the classes
are identified and the relationships among classes are identified. The three analysis
techniques that are used in conjunction with each other for object-oriented analysis are
object modelling, dynamic modelling, and functional modelling.
Object Modelling
Object modelling develops the static structure of the software system in terms of objects. It
identifies the objects, the classes into which the objects can be grouped into and the
relationships between the objects. It also identifies the main attributes and operations that
characterize each class.
The process of object modelling can be visualized in the following steps:
Identify objects and group into classes
Identify the relationships among classes
Create user object model diagram
Define user object attributes
Define the operations that should be performed on the classes
Dynamic Modelling
After the static behavior of the system is analyzed, its behavior with respect to time and external
changes needs to be examined. This is the purpose of dynamic modelling.
Dynamic Modelling can be defined as “a way of describing how an individual object responds
to events, either internal events triggered by other objects, or external events triggered by the
outside world”.
The process of dynamic modelling can be visualized in the following steps:
Identify states of each object
Identify events and analyse the applicability of actions
Construct dynamic model diagram, comprising of state transition diagrams
Express each state in terms of object attributes
Validate the state–transition diagrams drawn
Functional Modelling
Functional Modelling is the final component of object-oriented analysis. The functional
model shows the processes that are performed within an object and how the data changes
as it moves between methods. It specifies the meaning of the operations of object
modelling and the actions of dynamic modelling. The functional model corresponds to the
data flow diagram of traditional structured analysis.
Identify constraints
In this admin page and user will redirect to this page after log in.
ADD USER
This will show the list of user that are registered by user
INACTIVE USER PAGE
In this Page it will show the deleted user and admin can activate its status
to move to list user page
CATEGORY PAGE
In this page admin can add various categories and shown in add blog page
LIST CATEGORY PAGE
In this admin can add blog and choose images from folder and select any
category related to blog
LIST BLOG PAGE
In this admin can add NEWS and choose images from folder
LIST NEWS
In this page user can add images in the slider shown in top of page
LIST OF SLIDES
In this page, it will manage the list of comments and join with user that are
registered
CONTACT PAGE
<?php
include'include/connect.php';
include'include/header.php';
if($_POST)
{
$email = $_POST ['email'];
$password = $_POST ['password'];
}
?>
<div class ="wrapper">
<div class= "container">
<div id="login" class="animate form">
<form method="post" action="" >
<h1 class = "head">Log in</h1>
<p>
<label for="username" class="uname" data-icon="u" >
Your email or username </label>
<input id="username" name="email"
required="required" type="text" placeholder="myusername or
mymail@mail.com"/>
</p>
<p>
<label for="password" class="youpasswd" data-
icon="p"> Your password </label>
<input id="password" name="password"
required="required" type="password" placeholder="eg. X8df!90EO" />
</p>
<p class="keeplogin">
<input type="checkbox"
name="loginkeeping" id="loginkeeping" value="loginkeeping" />
<label
for="loginkeeping">Keep me logged in</label>
</p>
<p class="login button">
<input type="submit" value="submit" name="submit"/>
</p>
<p class="change_link">
Not a member yet ?
<a href="usr_regis.php" class="to_register">Join us</a>
</p>
</form>
</div><!-- login ended-->
</div><!-- container ended-->
</div><!-- wrapper ended-->
<?php include'include/footer.php';?>
LOGIN PAGE
USER_REGISTRATION
CODING
if(empty($lastname))
{
$error=1;
$msg[]="plz enter your lastname";
}
/*if(empty($dob))
{
$error=1;
$msg[]="plz enter your dob";
}
if(empty($city))
{
$error=1;
$msg[]="plz enter your city";
}
if(empty($address))
{
$error=1;
$msg[]="plz enter your address";
}
if(empty($phoneno))
{
$error=1;
$msg[]="plz enter your phonenumber";
}*/
if(empty($email))
{
$error=1;
$msg[]="plz enter your email";
}
if(empty($password))
{
$error=1;
$msg[]="plz enter your password";
}
elseif($password != $cpassword)
{
$error=1;
$msg[]="password and confirm password not match!!";
}
if($error == 1)
{
foreach($msg as $val)
{
echo "<li>".$val."</li>";
}
}
$filename = $_FILES['photo']['name'];
$size = $_FILES['photo']['size'];
$type = $_FILES['photo']['type'];
$tempname = $_FILES['photo']['tmp_name'];
// create random number
if(move_uploaded_file($_FILES['photo']['tmp_name'],'../uploads/'.$filename
))
{
$ins=mysql_query("INSERT INTO
usr_registration(firstname,lastname,email,password,created_on,updated_on,ima
ge) VALUES
('".$firstname."','".$lastname."','".$email."','".$password."',NOW(),NOW(),'".$fi
lename."') ") or die(mysql_error());
}
else
{
echo "try again";
}
}
?>
<div class = "wrapper">
<div class="container">
<div id="register" class="animate form">
<form action="" autocomplete="on" method="post"
enctype="multipart/form-data">
<h1 class ="head"> Sign up </h1>
<p>
<label for="usernamesignup" class="uname" data-
icon="u">First Name</label>
<input id="usernamesignup" name="firstname"
required="required" type="text" placeholder="mysuperusername690" />
</p>
<p>
<label for="usernamesignup" class="uname" data-
icon="u">Last Name</label>
<input id="usernamesignup" name="lastname"
required="required" type="text" placeholder="lastname" />
</p>
<p>
<label for="emailsignup" class="youmail" data-icon="e"
> Your email</label>
<input id="emailsignup" name="email"
required="required" type="email" placeholder="mysupermail@mail.com"/>
</p>
<p>
<label for="passwordsignup" class="youpasswd" data-
icon="p">Your password </label>
<input id="passwordsignup" name="password"
required="required" type="password" placeholder="eg. X8df!90EO"/>
</p>
<p>
<label for="passwordsignup_confirm"
class="youpasswd" data-icon="p">Please confirm your password </label>
<input id="passwordsignup_confirm"
name="cpassword" required="required" type="password" placeholder="eg.
X8df!90EO"/>
</p>
<p>
<label for="emailsignup" class="youmail" data-icon="e"
> Profile Pic</label>
<input id="emailsignup" name="photo" type="file"/>
</p>
<p class="signin button">
<input type="submit"
value="Sign up" name="submit"/>
</p>
<p class="change_link">
Already a member ?
<a href="login.php" class="to_register"> Go and log in </a></p>
</form>
</div>
</div><!--container ended-->
</div><!--wrapper ended-->
<?php include 'include/footer.php';?>
INDEX PAGE
CODING
<?php
include("include/connect.php");
include("include/header.php");
include("include/slider.php");
//$id=$_GET[id];
if(isset($_GET['p'])){
$page = $_GET['p'];
}else{
$page = 1;
}
$cur_page = $page;
$page -= 1;
$per_page = 2;
$previous_btn = true;
$next_btn = true;
$first_btn = true;
$last_btn = true;
$start = $page * $per_page;
$pagename = 'index.php';
?>
<div class="clear"></div>
<div id="right">
<?php
$pop=mysql_query("SELECT * FROM blogs LIMIT $start, $per_page" ) or
die (mysql_error());
$count=mysql_query("SELECT * FROM blogs ") or die (mysql_error());
if(mysql_num_rows($pop) > 0)
{$count1 = 1;
while($row=mysql_fetch_array($pop)) {
?>
<div class="content"><span class="headline_one">
<a href="descrip.php?id=<?php echo $row['id'];?>"><?php echo
$row['blog_title'];?></a>
</span><br />
<br />
<div class ="line"></div>
<span class="number"><?php echo $count1;?> </span>|<span
class="date">On <?php echo date('jS F Y',
strtotime($row['createdon']));?></span><br/>
<p class ="para"><?php echo substr($row['description'], 0, 800);?></p>
<?php if($row['image'] != ""){?>
<img src="uploads/<?php echo $row['image'];?>"
style="float:left;width:100%;border-radius:20px;">
<?php }?>
<?php
$count = mysql_num_rows($count);
$no_of_paginations = ceil($count / $per_page);
if ($cur_page == $i)
$msg .= "<div class='radiodesable'>$i</div>";
else
$msg .= "<a href='$pagename?p=$i'
class='page456'>$i</a>";
}
<?php include("include/sidebar.php");?>
<?php include("include/footer.php"); ?>
SIDEBAR PAGE
CODING
<div id="left">
<form id="search-form" name="search" method="get" action="search.php">
<input id="search-input" name="s" type="text" placeholder="search here...">
</form>
<?php }?>
</ul>
</div>
CATEGORY SECTION
CODING
<?php
include("include/connect.php");
include("include/header.php");
include("include/slider.php");
$id =$_GET['id'];
?>
<?php
if(isset($_GET['p'])){
$page = $_GET['p'];
}else{
$page = 1;
}
$cur_page = $page;
$page -= 1;
$per_page = 2;
$previous_btn = true;
$next_btn = true;
$first_btn = true;
$last_btn = true;
$start = $page * $per_page;
$pagename = 'category.php';
?>
<div class="clear"></div>
<div id="right">
<?php
$pop=mysql_query("SELECT * FROM blogs WHERE category ='".$id."'
LIMIT $start, $per_page" ) or die (mysql_error());
$count = mysql_query("SELECT * FROM blogs WHERE category
='".$id."'") or die(mysql_error());
if(mysql_num_rows($pop) > 0){
$count1 = 1;
while($row=mysql_fetch_array($pop)){
?>
<div class="content"><span class="headline_one">
<a href="descrip.php?id=<?php echo $row['id'];?>"><?php echo
$row['blog_title'];?></a>
</span><br />
<br />
<div class ="line"></div>
<span class="number"><?php echo $count1;?> |</span> <span
class="date">On <?php echo date('jS F Y', strtotime($row['createdon']));?><br
/>
<span class="small_caps"> </span>
<p class ="para"><?php echo substr($row['description'], 0, 800);?></p>
<?php if($row['image'] != ""){?>
<img src="uploads/<?php echo $row['image'];?>"
style="float:left;width:100%;border-radius:20px;">
<?php }?>
<div class="comment_box"><a href="">Comments </a></div>
</div>
<?php $count1++;} ?>
<?php
$count = mysql_num_rows($count);
$no_of_paginations = ceil($count / $per_page);
if ($cur_page == $i)
$msg .= "<div class='radiodesable'>$i</div>";
else
$msg .= "<a href='$pagename?p=$i&id=$id'
class='page456'>$i</a>";
}
CODING
<?php
include("include/connect.php");
include("include/header.php");
include("include/slider.php");
//$id = $_GET['id'];
?>
<?php
if(isset($_GET['p'])){
$page = $_GET['p'];
}else{
$page = 1;
}
$cur_page = $page;
$page -= 1;
$per_page = 2;
$previous_btn = true;
$next_btn = true;
$first_btn = true;
$last_btn = true;
$start = $page * $per_page;
$pagename = 'news.php';
?>
<div class="clear"></div>
<div id="right">
<?php
$pop=mysql_query("SELECT * FROM news LIMIT $start, $per_page" ) or
die (mysql_error());
$count = mysql_query("SELECT * FROM news") or die(mysql_error());
if(mysql_num_rows($pop) > 0)
{
$count1 = 1;
while($row=mysql_fetch_array($pop)){
?>
<div class="content"><span class="headline_one">
<a href="newsdescription.php?id=<?php echo $row['id'];?>"><?php echo
$row['news_title'];?></a>
</span><br />
<br />
<div class ="line"></div>
<span class="number"><?php echo $count1;?> |</span> <span
class="date">On <?php echo date('jS F Y',
strtotime($row['created_on']));?></span>
<span class="small_caps"></span>
<p class ="para"><?php echo substr($row['definition'], 0, 800);?></p>
<?php if($row['image'] != ""){?>
<img src="uploads/<?php echo $row['image'];?>"
style="float:left;width:100%;border-radius:20px;">
<?php }?>
</div>
<?php $count1++;} ?>
<?php
$count = mysql_num_rows($count);
$no_of_paginations = ceil($count / $per_page);
if ($cur_page == $i)
$msg .= "<div class='radiodesable'>$i</div>";
else
$msg .= "<a href='$pagename?p=$i'
class='page456'>$i</a>";
}
<?php include("include/sidebar.php");?>
<?php include("include/footer.php"); ?>
<?php
include("include/connect.php");
include("include/header.php");
$id=$_GET['id'];
?>
<style>
#cmnt_data{width:100%; float:left;}
.success{color:green;}
.error{color:red;}
</style>
<head>
<script src="js/jquery-1.6.3.min.js"></script>
<!-- Include all compiled plugins (below), or include individual files as needed -
->
</head>
<div class="clear"></div>
<div id="right">
<?php
$query = mysql_query("SELECT * FROM news where id ='".$id."'") or
die(mysql_error());
$count = 1;
while($row=mysql_fetch_array($query)){
?>
<div class="content"><span class="headline_one">
<?php echo $row['news_title'];?></span><br /><br />
<span class="number">.<?php echo $count;?> |</span> <span
class="date">On <?php echo date('jS F Y', strtotime($row['created_on']));?><br
/>
<span class="small_caps">Information</span>
<p class ="para"><?php echo $row['definition'];?></p>
<img src="uploads/<?php echo $row['image'];?>"
style="float:left;width:100%;border-radius:20px;">
</div>
<?php $count++;} ?>
</div>
<?php include("include/sidebar.php");?>
<?php include("include/footer.php"); ?>
CONTACT US PAGE
CODING
if(empty($email))
{
$error=1;
$msg[]="Please enter your email";
}
if(empty($message))
{
$error=1;
$msg[]="Please enter your message";
}
else{
$ins=mysql_query("INSERT INTO
contact(name,email,message,contact_status,created_on,updated_on) VALUES
('".$name."','".$email."','".$message."','1',NOW(),NOW())") or
die(mysql_error());
}
}
?>
<div class = "wrapper">
<div class="container">
<div id="register" class="animate form">
<form action="" autocomplete="on" method="post"
enctype="multipart/form-data">
<h1 class ="head"> Contact Us </h1>
<p>
<label for="usernamesignup" class="uname" data-
icon="u">Name</label><br>
<input id="usernamesignup" name="name" type="text"
placeholder="mysuperusername690" />
</p>
<p>
<label for="emailsignup" class="youmail" data-icon="e"
> Your email</label><br>
<input id="emailsignup" name="email"
required="required" type="email" placeholder="mysupermail@mail.com"/>
</p>
<p>
<label for="emailsignup"
class="youmail" data-icon="e" > Message</label><br>
<textarea name="message"
rows="7" cols="30">
</textarea><br></p>
<p class="signin button">
<input type="submit"
value="Submit" name="submit"/>
</p>
</form>
</div>
<div class ="content">
<span class="headline_one">Contact Info:</span>
<p id ="contact">D185, Phase 8B, Industrial Area,
Mohali, Punjab<br>
Email: kritikachauhan19@gmail.com<br>
Contact No: +91 9056808418, +91 8628090521</p>
</div>
</div><!--container ended-->
</div><!--wrapper ended-->
<?php include'include/recntpost.php';?>
<?php include 'include/footer.php';?>
ABOUT US PAGE
CODING
<?php
include("include/connect.php");
include("include/header.php");
include("include/recntpost.php");?>
<div id ="right">
<img src="uploads/blog.jpg" style="width:100%;border-radius:40px;"/>
<div class="content"><span class="headline_one">About Us</span>
<p class ="para">WEBLOG is a combination of both Blog as well as
Novels. Blog contain the Information of various things related to Technology,
Education, News, International, Business, Sports, Entertainment and ongoing
college activities. The main aim of this project is to provide data to students in
only one site. Students can gather the information from one site as well as give
their feedback and create their own blog. Students can post their views and
thought and analyze themselves.</p>
<p class="para"> The WEBLOG not only provide information related
to many fields like Edu blogs, health, digital technology, latest news, trends and
can give feedback and share his/her views regarding any topic. The WEBLOG
have high quality content survive. The young generation are now moving from
static content to dynamic content like flash and updating information like
twitter. The WEBLOG provide the latest information, you just have to visit the
specific blog of your interest and view the main page. The main page of website
gives you latest information about the site content. The blogging is more taking
attention to tech news like iPhone, iPad, laptops, iPod, mobiles and other
technology news.
In the Novel section you can see the article of any blogger by clicking on author
name. Weblogs are discussing about medical treatment and how to remain
healthy and smart, so that mean you can write on other information also. People
always looking for new techniques and words. WEBLOG gives visitors a new
way of reading and not boring content. </p>
</div>
</div>
The method of Black Box Testing is used by the software engineer to derive the required
results of the test cases:
1. Black Box Testing alludes to test that are conducted at the software interface.
2. A Black Box Test examines some fundamental aspect of a system with little regard for
the internal logic structure of the software.
3. A limited number of important logical paths can be selected and exercised.
Black box testing was performed to find errors in the following categories:-
Incorrect or missing functions
Graphics error.
Errors in data in binary format.
Error in data in integer format.
File error.
Pointer error
Variable error
White Box Testing is sometimes called Glass Box Testing. Using White Box Testing
methods the software engineer can derive the following test cases:
1. Guarantee that all independent paths within a module have been exercised at least once.
2. Exercise all logical decisions on their true and false sides.
3. Execute all loops at their boundaries and within their operational bounds.
Unit Testing
Code testing was carried out to see the correctness of the logic involved and the correctness
of the modules. Tests were conducted based upon sample and live data as well. All the
modules are checked separately for assuming correctness and accuracy in all the
calculations.
Specification Testing
It examines the specification stating about what program should do and how it performs
under various conditions. This testing strategy is better strategy since it focuses on the way
the software is expected to work.
Integration Testing
The next level testing that was performed is often referred to as integration testing. During
this phase many unit tested modules were combined into subsystems, which were then
tested. The goal here was to see if modules can be integrated properly. Here the emphasis
was on testing interfaces between different constituent modules of system.
Functionality Testing
Here the entire software system was tested. The reference document for this process is the
requirements document, and the goal was to see if software solution meets its requirements.
This level of testing is essentially a validation exercise, and in many situation it is the only
validation activity.
Stress Testing
Proxy server developed for the specified purpose was testing under heavy load, i.e. a large
no. of clients were made to sit in lab and were asked to send requests for logging in and
then were asked to request for text on internet. System responded to request as desired.
Acceptance Testing
Acceptance was performed in the real environment with realistic data of the client to
demonstrate if the software developed is working satisfactorily. Here the main focus was
on the external behavior of the system; the internal logic of the program was not
emphasized.
The primary objective of test case design is to derive a set of tests that have the highest
likelihood of uncovering errors in software. The test case specification is the major activity
in the testing process. Careful selection of test cases that satisfy the criterion on approach
specified is essential for proper testing. Various characteristics of test cases that are
required for portal are:
A good test has a high probability of finding an error.
A good test is not redundant.
A good test should be “Best of Breed”.
A good test should be neither too simple not too complex.
Overview of Testing
1. Testing: Testing involves executing the program (or part of it) using sample data and
inferring from the output whether the software performs correctly or not. This can be done
either during module development (unit testing) or when several modules are combined
(system testing).
2. Direct Testing: Defect testing is testing for situation where the program does not meet
its functional specification. Performance testing tests a system's performance or reliability
under realistic loads. This may go some way to ensuring that the program meets its non-
functional requirements.
11.2Debugging
Debugging is a cycle of detection, location, repair and test. Debugging is a hypothesis
testing process. When a bug is detected, the tester must form a hypothesis about the cause
and location of the bug. Further examination of the execution of the program (possible
including many returns of it) will usually take place to confirm the hypothesis. If the
hypothesis is demonstrated to be incorrect, a new hypothesis must be formed. Debugging
tools that show the state of the program are useful for this, but inserting print statements is
often the only approach. Experienced debuggers use their knowledge of common and/or
obscure bugs to facilitate the hypothesis testing process. After fixing a bug, the sys tem
must be reset to ensure that the fix has worked and that no other bugs have been introduced.
This is called regression testing. In principle, all tests should be performed again but this
is often too expensive to do.
Test Planning
Testing needs to be planned, to be cost and time effective. Planning is setting out standards
for tests. Test plans set out the context in which individual engineers can place their own
work. Typical test plan contains:
Interface Testing: Usually done at integration stage when modules or sub-systems are
combined. Objective is to detect errors or invalid assumptions about interfaces between
modules. Reason these are not shown in unit testing is that test case may perpetuate same
incorrect assumptions made by module designer. Particularly important when OO
development has been used.
Four Types Of Interface
1. Parameter: data (or occasionally function references) passed from one unit to another.
2. Shared memory: block of memory shared between units (e.g. global variable) .One
places data there and the other retrieves it.
3. Procedural: Object-Oriented or abstract data type form of interface, encapsulating
several procedures.
4. Message passing: one sub-system requests a service by passing a message. Client-server
interface also used by some OO architectures.
Typical levels of testing:
Acceptance testing - whole system with real data (involve customer, user, etc) .Alpha
testing is acceptance testing with a single client (common for bespoke systems). Beta
testing involves distributing system to potential customers to use and provide feedback. In,
this project, Beta testing has been followed. This exposes system to situations and
errors that might not be anticipated by us.
11.3 Maintenance
Once the website is launched, it enters the maintenance phase. All systems need
maintenance. Maintenance is required because there are often some residual errors
remaining in the system that must be removed as they are discovered. Maintenance
involves understanding the effects of the change, making the changes to both the code and
the documents, testing the new parts and retesting the old parts that were not changed.
Maintenance is mainly of two types:
1. Corrective Maintenance
2. Adaptive Maintenance
Corrective Maintenance
Almost all software that is developed has residual errors or bugs in them. Many of these
surfaces only after the system have been in operation, sometimes for a long time. These
errors once discovered need to be removed, leading to the software to be changed. This is
called Corrective Maintenance.
Adaptive Maintenance
Even without bugs, software frequently undergoes change. The software often must be
upgraded and enhanced to include more features and provide more services.
Perfective Maintenance - This includes modifications and updates done in order to keep
the software usable over long period of time. It includes new features, new user
requirements for refining the software and improve its reliability and performance.
Cost of Maintenance
Reports suggest that the cost of maintenance is high. A study on estimating software
maintenance found that the cost of maintenance is as high as 67% of the cost of entire
software process cycle.
On an average, the cost of software maintenance is more than 50% of all SDLC phases.
There are various factors, which trigger maintenance cost go high, such as:
Analysis - The modification is analyzed for its impact on the system including
safety and security implications. If probable impact is severe, alternative solution
is looked for. A set of required modifications is then materialized into requirement
specifications. The cost of modification/maintenance is analyzed and estimation is
concluded.
Design - New modules, which need to be replaced or modified, are designed against
requirement specifications set in the previous stage. Test cases are created for
validation and verification.
Implementation - The new modules are coded with the help of structured design
created in the design step.Every programmer is expected to do unit testing in
parallel.
Acceptance Testing - After testing the system internally, it is tested for acceptance
with the help of users. If at this state, user complaints some issues they are
addressed or noted to address in next iteration.
Delivery - After acceptance test, the system is deployed all over the organization
either by small update package or fresh installation of the system. The final testing
takes place at client end after the software is delivered.
Training facility is provided if required, in addition to the hard copy of user manual.
Software Re-engineering
When we need to update the software to keep it to the current market, without impacting
its functionality, it is called software re-engineering. It is a thorough process where the
design of software is changed and programs are re-written.
Legacy software cannot keep tuning with the latest technology available in the market. As
the hardware become obsolete, updating of software becomes a headache. Even if
software grows old with time, its functionality does not.
For example, initially Unix was developed in assembly language. When language C came
into existence, Unix was re-engineered in C, because working in assembly language was
difficult.
Other than this, sometimes programmers notice that few parts of software need more
maintenance than others and they also need re-engineering.
Re-Engineering Process
Reverse Engineering
It is a process to achieve system specification by thoroughly analyzing, understanding the
existing system. This process can be seen as reverse SDLC model, i.e. we try to get higher
abstraction level by analyzing lower abstraction levels.
Program Restructuring
It is a process to re-structure and re-construct the existing software. It is all about re-
arranging the source code, either in same programming language or from one
programming language to a different one. Restructuring can have either source code -
restructuring and data-restructuring or both.
Re-structuring does not impact the functionality of the software but enhance reliability
and maintainability. Program components, which cause errors very frequently can be
changed, or updated with re-structuring.
The dependability of software on obsolete hardware platform can be removed via re -
structuring.
Forward Engineering
Forward engineering is a process of obtaining desired software from the specifications in
hand which were brought down by means of reverse engineering. It assumes that there
was some software engineering already done in the past.
Forward engineering is same as software engineering process with only one difference –
it is carried out always after reverse engineering.
Component reusability
A component is a part of software program code, which executes an independent task in
the system. It can be a small module or sub-system itself.
Example
The login procedures used on the web can be considered as components, printing system
in software can be seen as a component of the software.
Components have high cohesion of functionality and lower rate of coupling, i.e. they work
independently and can perform tasks without depending on other modules.
In OOP, the objects are designed are very specific to their concern and have fewer chances
to be used in some other software.
In modular programming, the modules are coded to perform specific tasks which can be
used across number of other software programs.
There is a whole new vertical, which is based on re-use of software component, and is
known as Component Based Software Engineering (CBSE).
Reuse Process
Two kinds of method can be adopted: either by keeping requirements same and adjusting
components or by keeping components same and modifying requirements.
Design - This is also a standard SDLC process step, where requirements are defined
in terms of software parlance. Basic architecture of system as a whole and its sub-
systems are created.
Contact Us
If user want to contact us he/she can contact us through the contact us option in the main
menu. Our E-mail id and contact no. is provided. User can contact us through any of the
above links.
About Us
If user want to know anything about this website then he/she can know about us through
the about us option in the main menu. Our website’s brief information is provided there.
14 Conclusion
While developing the system a conscious effort has been made to create and
develop a software package, making use of available tools, techniques and
resources – that would generate a proper system for cases.
While making the system, an eye has been kept on making it as user-friendly.
As such one may hope that the system will be acceptable to any user and will
adequately meet his/her needs. As in case of any system development process
where there are a number of short comings, there have been some
shortcomings in the development of this system also.