Project Report (Discussion Forum)

Final Year Project Report

On

DISCUSSION FORUM

Submitted in the partial fulfillment of the requirement for the

Award of the degree

BACHELOR OF TECHNOLOGY

COMPUTER SCIENCE & ENGINEERING

By

Uttar Pradesh Technical University

Submitted By:

Karan Chhabra – 1022310043

Prashant Sharma – 1022310064

Nishant Sharma – 1022310056

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING

VIVEKANAND INSTITUTE OF TECHNOLOGY AND SCIENCE

GHAZIABAD

SESSION 2010-2014

ACKNOWLEDGEMENT

Without guidance and inspiration nothing is possible in this world. The project works in an exhaustive exercise and cannot be completed single handedly. This requires the constant efforts from the project partners in terms of quality, quantity, time, dedication, hard work, and also cooperation from the people related directly or indirectly to the field of project. The role of supervisor is very important as his help starts from the day of idea of project and continue throughout, till it is completed. He provides ideology, design and methodology of the project work and devotes his valuable and considerable time.

Our project “DISCUSSION FORUM” is the outcome of the great guidance, inspiration and assurance provided by the technical staff at Vivekanand Group of Institutions.

We are extremely thankful to Mr. Kushagra Bhardwaj (Project Guide) for his constant guidance, supervision he gave to the project. We wish our sincere thanks to Mr. Kushagra Bhardwaj (Project In charge) for his active help and cooperation.


Pradhant Sharma – 1022310064


CERTIFICATE

This is to certify that the project report entitled “DISCUSSION FORUM” in partial fulfillment of the requirement for the award of degree of Bachelor of Technology in Computer Science & Engineering affiliated to Uttar Pradesh Technical University, Noida is an authentic record of the work carried out during the period from September 2013 to April 2014 under the kind guidance of Mr. Kushagra Bhardwaj (Faculty of Computer Science & Engineering). The matter embodied in this period has submitted for the award of degree.

Mr. P.K. Vashishtha

Head of Department

(Computer Science & Engineering)

Mr. Kushagra Bhardwaj

(Project Guide)

DECLARATION

I hereby declare that this submission is my own and that, to the best of knowledge and belief, it contains no material previously published or written by another person nor material which to a substantial extend has been accepted for the degree or diploma of the university or other institution of higher learning, expect where due acknowledgement has been made in the text.


Prashant Sharma – 1022310064


DATE:

PREFACE

This website “DISCUSSION FORUM” is made by us for providing a platform for having discussions. This forum provides the platform under one roof to interact with different users which maybe the experts in a particular field or a normal user for seeking or to give advices. An online space on which anybody can have discussions regarding any research, academic documents or any latest technology free of cost. A website which helps to resolve doubts, queries related to any field by having discussions with other registered users.

Chapter 1 consists of problem definition and feasibility study and objective of the project.

Chapter 2 consists of hardware, software requirement, manpower requirement and functional requirement.

Chapter 3 provides the detailed description of the modules of the project.

Chapter 4 explains about the platform of implementation.

Chapter 5 gives coding description.

Chapter 6 gives purpose of testing.

Chapter 7 consists of Data Flow Diagram.

Chapter 8 consists of screen shots.

Chapter 9 gives conclusion, future scope and references.

INDEX

Chapter 1

Introduction

1.1 Problem Definition.1.2 Feasibility Study.1.3 Objective of the project.

Chapter 2

System Requirement and Specifications

2.1 Hardware Requirement.2.2 Software Requirement. 2.3 Manpower Requirement.

Chapter 3

About Modules

3.1 Admin Module3.2 Registration Module3.3 Profile Management Module3.4 Discussion Module.

Chapter 4

Platform of implementation – JSP

4.1Detailed description about the technology.

Chapter 5

Coding description

5.1 Source code in detail.

Chapter 6

Test Plan

6.1 Purpose of testing.6.2 Levels of testing.

Chapter 7

Data Flow Diagram and E-R Diagram

7.1 Data Flow Diagram

7.2 E-R Diagram

Chapter 8

8.1Screen shots

Chapter 9

Conclusion

9.1 Future scope9.2 References

Chapter 1

Introduction

PROBLEM DOMAIN

With highly growing of the telecommunication infrastructures, such as Internet and the development of the high performance have brought about new era of rapid advances in information technology. Internet has become an ocean of information related to every aspect which has existence in this world.

The main problem which our new generation is facing is lack of experience and proper guidelines related to career and what to do, what to opt to make their academics effective than before.

The main purpose of this website is to develop a one roof platform for the effective interaction, effective exposure, and a right direction toward education.

Our aim is to provide our users an opportunity to enhance their knowledge by sharing their views on this platform by having discussions with other users.

The intended audience is general users. This website will act as a healthy questionnaire which helps to give and get effective solutions with best of their experience.

FEASIBILITY STUDY

Feasibility study is the first step before starting any project. The main aim of feasibility study is to determine whether developing the product is financially and technically feasible or not. In Feasibility study we also test whether the product would be profitable. The Feasibility study involves the analysis of the problem and collection of data which would be input to the system, the processing require to be carried in this data. The output data required to be produce by the system. The collected data are analyzed to arrive at the following:

A) Technical feasibilityTechnical feasibility means whether the project is working in a perfect manner. It means the project must support or perform all the technical functions for which it is implemented. The project “DISCUSSION FORUM” through JSP TECHNOLOGY is technically feasible. This website is well capable of providing a user good interface thus this project is able to work in effective and efficient manner.

B) Economical feasibilityEconomical feasibility is a team which is related to estimation of cost required for the project. This project is feasible under the economic condition.

C) Legal feasibilityLegal feasibility means the developing project must be legal. The way by which the product is going to be implemented must be legal. The project must perform a legal task. It must be acceptable worldwide. The project is not going to perform any tasks which are not lie under the condition of law. Thus the project must be legal to use and can be acceptable by the user.

D) Operational feasibilityOperational feasibility means the project must perform its operation perfectly. If the project is working properly them we can say that the project is o Operational feasibility.

OBJECTIVE OF THE PROJECT

We the team of three professional developers put our complete efforts in order to provide a complete solution to our youth under one roof. It is the first website of its own kind that provides a ceramic way to attain and give knowledge.

Here the process of knowledge sharing is concerned with the purity of the facts and figures collected from various authentic sources. Our aim is to help the passionate people to share their views with its purity and trueness. These different users can guide each other on various aspects related to their respective career and future. Beyond this our website will give the opportunity to every user say “a lot of eminent faculties of different institution who can share their bright knowledge over the website”. Last but not the least this website also gives the opportunity to students for sharing of knowledge and for utilization of the efforts by gaining the knowledge.

Chapter 2

System Requirement

And Specifications

HARDWARE REQUIREMENT

This section will describe the hardware requirement which is at least necessary to run this website.

Processor – The minimum requirement of processor is at least Pentium IV with 900 MHz processing speed. The speed of processor determines the time taken for the execution of the instructions. Higher processing speed leads to faster execution of the instruction.

RAM – There should be minimum 256 MB of RAM available for the smooth functioning of the project. Higher memory leads in better results.

Hard disk – There should be about minimum 40GB of hard disk for smooth functioning of the project and so the recommended hard disk space is 40 GB.

Cache Memory – There must be about 512 KB of cache memory so that the accessing time can be better and compilation is easier.

SOFTWARE REQUIREMENT

Operating System – Window XP, 7, 8 and other operating systems like Linux; MacOS can also be used since .net is platform independent.

Programming Language – JSP(Java Server Page).

Web Technology –HTML5, CSS( Cascading Style Sheet).

Back End –

Oracle 10g Database.

MANPOWER REQUIREMENT

Project duration – 8 months. Project team size – 3.

Chapter 3

About Modules

Admin Module

“This is a Master creation Module. It will look after and control all the discussions being created and posted. Once the discussions are created and posted the admin has the authority to see and alter those discussions.”

Registration Module

“This module is responsible for the registration of a new user. In this module the user register’s itself by entering the required information. This module also verifies the new user details with the previously registered users.”

Profile Management Module

“This module manages the profiles of all the registered users. In this module all the details of the registered users are stored. It creates a separate record for individual users about all the discussion being created and posted.”

Discussion Module

“This module manages the discussions created by the corresponding users. It helps the user to have discussions with each other. This module helps in managing all the discussions amongst different users.”

Chapter 4

Platform of

Implementation

JSP (Java Server Page)

“Java Server Pages (JSP) is a technology that helps software developers create dynamically generated web pages based on HTML, XML, or other document types. Released in 1999 by Sun Microsystems, JSP is similar to PHP, but it uses the Java programming language.To deploy and run Java Server Pages, a compatible web server with a servlet container, such as Apache Tomcat or Jetty, is required.JSP pages use several delimiters for scripting functions. The most basic is <% ... %>, which encloses a JSP scriptlet. A scriptlet is a fragment of Java code that is run when the user requests the page. Other common delimiters include <%= ... %> for expressions, where the scriptlet and delimiters are replaced with the result of evaluating the expression, and directives, denoted with <%@ ... %>.[5]Java code is not required to be complete or self-contained within its scriptlet element block, but can straddle markup content providing the page as a whole is syntactically correct. For example, any Java if/for/while blocks opened in one scriptlet element must be correctly closed in a later element for the page to successfully compile. Markup which falls inside a split block of code is subject to that code, so markup inside an if block will only appear in the output when the if condition evaluates to true; likewise, markup inside a loop construct may appear multiple times in the output depending upon how many times the loop body runs. The following would be a valid for loop in a JSP page:

<p>Counting to three:</p><% for (int i=1; i<4; i++) { %><p>This number is <%= i %>.</p><% } %><p>OK.</p>

The output displayed in the user's web browser would be:

Counting to three:This number is 1.This number is 2.This number is 3.OK.

THE JSP MODEL 2 ARCHITECTURE

Chapter 5

Coding Description

TO REGISTER A NEW USER

<%@include file="common.jsp" %>

<%@page contentType="text/html" pageEncoding="UTF-8"%>

<%

if("Register".equals(request.getParameter("btnReg")))

{

String u=request.getParameter("txtUser");

String p=request.getParameter("txtPass");

String cp=request.getParameter("txtCPass");

String mail=request.getParameter("txtMail");

String gen=request.getParameter("cmbGen");

String dob=request.getParameter("txtDob");

String addr=request.getParameter("txtAddr");

String sq=request.getParameter("cmbQuestion");

String ans=request.getParameter("txtAns");

String insqry="insert into profile values('"+u+"','"+p+"','"+

mail+"','"+gen+"',+TO_DATE('" + dob + "', 'yyyy/mm/dd'),'"+

addr+"','"+sq+"','"+ans+"')" ;

String chkqry="select *from profile where username='"+u+"'";

Statement st1=cn.createStatement();

ResultSet rs2=st.executeQuery(chkqry);

if(rs2.next())

{

response.sendRedirect("error1.jsp");

}

else

{

if(p.equals(cp))

{

st.executeQuery(insqry);

cn.commit();

session.setAttribute("user", u);

// session.setAttribute("ut", "U");

response.sendRedirect("discussion.jsp");

}

else

{

response.sendRedirect("error.jsp");

}

}

}

%>

<!DOCTYPE html>

<html>

<head>

<meta charset="utf-8">

<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">

<title>Signup</title>

<link rel="stylesheet" href="style.css">

</head>

<body>

<div id="topdiv1">

<h1 align="center" id="toph1">Discussion Forum</h1>

<tr>

<td height="30"><div align="right"><form method="get" action="http://www.google.com/search">

<input type="text" name="q" size="31" maxlength="255" value="" />

<input type="submit" value="Google Search" align='top'/>

</form>

</div>

</td>

</tr>

</div>

<form class="login1" method="post">

<h1>Registration Form</h1>

<input type="text" name="txtUser" class="login-input" placeholder="Username" autofocus>

<input type="password" name="txtPass" class="login-input" placeholder="Password">

<input type="password" name="txtCPass" class="login-input" placeholder="Confirm Password" />

<select name="cmbQuestion" class="login-input">

<option value="-1">Select Security Question</option>

<option value="pname">Nick Name</option>

<option value="dtb">Date of Birth</option>

<option value="bfs">Best Friend's Name</option>

<option value="sch">First School Name</option>

</select>

<input type="text" name="txtAns" class="login-input" placeholder="Answer" />

<input type="text" name="txtMail" class="login-input" placeholder="Email address" />

<select name="cmbGen" class="login-input">

<option value="M">Male</option>

<option value="F">Female</option>

</select>

<input type="date" name="txtDob" class="login-input" />

<textarea name="txtAddr" class="login-input" rows="2" cols="30" placeholder="Address"></textarea>

<input type="submit" value="Register" name="btnReg" class="login-submit">

</form>

<center>

<table>

<tr>

<td><a href="http://www.facebook.com" ><img src="Images/flogo.jpg" width="100" height="100" border="0" /></a></td>

<center> <td><a href="http://twitter.com" ><img src="Images/tlogo.jpg" width="100" height="100" border="0" /></a></td></center>

<td><a href="http://www.youtube.com" ><img src="Images/ytlogo.jpg" width="100" height="100" border="0" /></a></td>

</tr>

</table>

</center>

<tr>

<td width="840" height="30" class="footer"><div align="center" class="footer"><b>© 2014 Discussion 4 All. </b></tr>

</body>

</html>

LOG IN AS REGISTERED USER:



<%

if("Login".equals(request.getParameter("btnLogin")))

{


String p=request.getParameter("txtPass");

String qry="select *from profile where username='"+u+"' and password='"+p+"'";

rs=st.executeQuery(qry);

if(rs.next())

{

session.setAttribute("user", u);

response.sendRedirect("discussion.jsp");

}

else

{

response.sendRedirect("logerror.jsp");

}

}

%>

<!DOCTYPE html>

<html>

<head>



<title>Login Form</title>


</head>

<body>

<div id="topdiv1">


<tr>

</tr>

<tr>




</form>

</div>

</td>

</tr>

</div>

<form class="login" method="post">


<input type="password" name="txtPass" class="login-input" placeholder="Password">

<input type="submit" value="Login" name="btnLogin" class="login-submit">

<p class="login-help"><a href="signup.jsp">Register Now?</a>

<a href="forgot.jsp">Forgot Password?</a></p>

</form>

<tr>

<td>

<center>

<table>

<tr>




</tr>

</table>

</center>

</td>

</tr>

<tr>


</body>

</html>

RETRIEVE FORGOT PASSWORD:



<%

if("Send".equals(request.getParameter("btnSend")))

{


String sq=request.getParameter("cmbQuestion");

String ans=request.getParameter("txtAns");

String qry="select *from profile where username='"+u+"' and security='"+sq+"' and answer='"+ans+"'";


if(rs.next())

{

session.setAttribute("pass", rs.getString(2).toString());

response.sendRedirect("showpass.jsp");

}

else

{

response.sendRedirect("error2.jsp");

}

}

%>

<!DOCTYPE html>

<html>

<head>



<title>IDF Login Form</title>


</head>

<body>

<div id="topdiv1">


<tr>




</form>

</div>

</td>

</tr>

</div>



<select name="cmbQuestion" class="login-input">

<option value="-1">Select Security Question</option>

<option value="pname">Nick Name</option>

<option value="dtb">Date of Birth</option>

<option value="bfs">Best Friend's Name</option>

<option value="sch">First School Name</option>

</select>

<input type="text" name="txtAns" class="login-input" placeholder="Answer" />

<input type="submit" value="Send" name="btnSend" class="login-submit">

</form>

<center>

<table>

<tr>




</tr>

</table>

</center>

<tr>


</body>

</html>

TO HAVE DISCUSSION:


<%@include file="format.jsp" %>

<%@page import="java.util.*" %>

<%@page import="java.text.*" %>


<%

String selqry="select username,cment,to_char(cdate,'dd-mon-yy') as cdt,to_char(cdate,'hh:mi:ss') as tdt from discuss order by cdate desc";

rs=st.executeQuery(selqry);

String txt="";

String hidtext="";

if("Publish".equals(request.getParameter("btnPost")))

{

try

{

String us=session.getAttribute("user").toString();

txt=request.getParameter("txtcmnt");

st=cn.createStatement();

java.util.Date myDate = new java.util.Date();

String strDate = "";

SimpleDateFormat formatter = new SimpleDateFormat("yyyy/MM/dd:hh:mm:ss");

strDate = formatter.format(myDate);

String query = "insert into discuss values('"+us+"', TO_DATE('" + strDate + "', 'yyyy/mm/dd hh:mi:ss'), '"+txt+"')";

st.executeQuery(query);

cn.commit();

hidtext="";

}

catch(Exception e)

{

e.printStackTrace();

}

selqry="select username,cment,to_char(cdate,'dd-mon-yy') as cdt,to_char(cdate,'hh:mi:ss') as tdt from discuss order by cdate desc";

rs=st.executeQuery(selqry);

}

%>

<script>

function check()

{

if(document.frmDiscuss.txtcmnt.value=="" || document.frmDiscuss.txtcmnt.value==null)

{

alert("Enter Message...");

return false;

}

else

{

document.frmDiscuss.txthid.value="Publish";

return true;

}

}

function set1()

{

document.getElementById('phid').style.visibility = "hidden";

}

function show()

{

document.getElementById('phid').style.visibility = "visible";

}

</script>

<!DOCTYPE html>

<html>

<head>

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">

<title>Discussion</title>


<link href="design.css" rel="stylesheet" type="text/css"/>

<script src="disablef.js">

</script>

</head>

<body onload="set1();">

<div id="topdiv1">


<tr>




</form>

</div>

</td>

</tr>

</div>

<form name="frmDiscuss" class="login2" method="POST" onsubmit="return check();">

<input type="button" value="Discuss" name="btnDisCuss" onclick="show();" />

<p id="phid">

<table border="1" id="dtab" class="login-input" align="center">

<tbody>

<tr>

<td style="background-color: #ff6666;">

Enter Your Discussion:

</td>

</tr>

<tr>

<td>

<textarea name="txtcmnt" id="txtid" rows="6" cols="80" autofocus></textarea>

</td>

</tr>

<tr>

<td>

<input type="submit" value="Publish" name="btnPost" />

<input type="reset" value="Clear" name="btnCancel" />

<input type="hidden" value="" name="txthid" value="<%=hidtext%>" />

</td>

</tr>

</tbody>

</table>

</p>

<table border="0" align="center" class="tblclass">

<tbody>

<%

if(rs!=null)

{

while(rs.next())

{

%>

<tr style="height: 50px;">

<td><%=rs.getString(1)%> : <%=rs.getString(2)%></td>

<td></td>

<td><%=rs.getString("cdt")%></td>

<td><%=rs.getString("tdt")%></td>

</tr>

<%}

}%>

</tbody>

</table>

</form>

<center>

<table>

<tr>




</tr>

</table>

</center>

<tr>


</body>

</html>

TO VIEW YOUR OWN DISCUSSION:




<!DOCTYPE html>

<%

String user=session.getAttribute("user").toString();

String qry="select username,cment,to_char(cdate,'dd-mon-yy') as cdt,to_char(cdate,'hh:mi:ss') as tdt from discuss where username='"+user+"' order by cdate desc";


%>

<html>

<head>


<title>Current User Discussion</title>

<link href="style.css" rel="stylesheet" type="text/css"/>


</head>

<body>

<div id="topdiv1">


<tr>




</form>

</div>

</td>

</tr>

</div>


<table border="0" align="center" class="tblclass">

<tbody>


<td><h1>Discussion</h1></td>

<td></td>

<td><h1>Date</h1></td>

<td><h1>Time</h1></td>

</tr>

<%

if(rs!=null)

{

while(rs.next())

{

%>


<td><%=rs.getString(2)%></td>

<td></td>

<td><%=rs.getString("cdt")%></td>

<td><%=rs.getString("tdt")%></td>

</tr>

<%}

}%>

</tbody>

</table>

</form>

<center>

<table>

<tr>




</tr>

</table>

</center>

<tr>


</body>

</html>

TO RETRIVE PASSWORD:


<!DOCTYPE html>

<html>

<head>


<title>Password Page</title>


</head>

<body>

<div id="topdiv1">


<tr>




</form>

</div>

</td>

</tr>

</div>


<%

String p=session.getAttribute("pass").toString();

out.println("<h1>Your Password is : "+p+"</h1>");

%>

<p class="login-help"><a href="login.jsp">Login Now</a></p>

</form>

<center>

<table>

<tr>




</tr>

</table>

</center>

<tr>


</body>

</html>

TO SHOW USER PROFILE:




<!DOCTYPE html>

<%

String u=session.getAttribute("user").toString();

String qry="select *from profile where username='"+u+"'";


%>

<html>

<head>


<title>User Profile</title>



</head>

<body>

<div id="topdiv1">


<tr>




</form>

</div>

</td>

</tr>

</div>


<h1>User Profile</h1>

<table class="tblclass">

<%if(rs.next())

{%>

<tr>

<td>Username : </td>


</tr>

<tr>

<td>Email : </td>


</tr>

<tr>

<td>Gender : </td>


</tr>

<tr>

<td>Address : </td>


</tr>

<%}%>

</table>

</form>

<center>

<table>

<tr>




</tr>

</table>

</center>

<tr>


</body>

</html>

TO SHOW ADMIN INFORMATION:



<!DOCTYPE html>

<html>

<head>


<title>Contact Us</title>



</head>

<body>

<div id="topdiv1">


<tr>




</form>

</div>

</td>

</tr>

</div>


<table class="tblclass">

<h1>This forum is a platform for creating and having discussions amongst different users on any particular topic and is created and managed by:</h1>

<tr><td><b>Prashant Sharma</b> (Email- [email protected])</td>

<td><b>Nishant Sharma</b> (Email- [email protected])</td>

<td><b>Karan Chhabra</b> (Email- [email protected])</td></tr>

</table>

</form>

<center>

<table>

<tr>




</tr>

</table>

</center>

<tr>


</body>

</html>

Chapter 6

Test Plan

Purpose of Testing

Testing generally involves running a suite of tests on the completed system. Each individual test, known as a case, exercises a particular operating condition of the user's environment or feature of the system, and will result in a pass or fail outcome. There is generally no degree of success or failure. The test environment is usually designed to be identical, or as close as possible, to the anticipated user's environment, including extremes of such. These test cases must each be accompanied by test case input data and/or a formal description of the operational activities to be performed. The intentions are to thoroughly elucidate the specific test case and description of the expected results.

Types of TestingUnit 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 assure that the building blocks the software uses work independently of each other.

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.

System testing or end-to-end testing, tests a completely integrated system to verify that it meets its requirements. For example, a system test might involve testing a logon interface, then creating and editing an entry, plus sending or printing results, followed by summary processing or deletion (or archiving) of entries, then logoff.

In addition, the software testing should ensure that the program, as well as working as expected, does not also destroy or partially corrupt its operating environment or cause other processes within that environment to become inoperative (this includes not corrupting shared memory, not consuming or locking up excessive resources and leaving any parallel processes unharmed by its presence)

http://en.wikipedia.org/wiki/Corner_case

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.

Accepting testing is of following two types they are:-

Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing.

Beta testing comes after alpha testing and can be considered a form of external user acceptance testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Sometimes, beta versions are made available to the open public to increase the feedback field to a maximal number of future users.

http://en.wikipedia.org/wiki/Feedback#In_organizations

http://en.wikipedia.org/wiki/Computer_bug

http://en.wikipedia.org/wiki/Beta_version

http://en.wikipedia.org/wiki/Beta_version

http://en.wikipedia.org/wiki/User_acceptance_testing

Regression testing focuses on finding defects after a major code change has occurred. Specifically, it seeks to uncover software regressions, as degraded or lost features, including old bugs that have come back. Such regressions occur whenever software functionality that was previously working, correctly, stops working as intended. Typically, regressions occur as an unintended consequence of program changes, when the newly developed part of the software collides with the previously existing code. Common methods of regression testing include re-running previous sets of test-cases and checking whether previously fixed faults have re-emerged. The depth of testing depends on the phase in the release process and the risk of the added features. They can either be complete, for changes added late in the release or deemed to be risky, or be very shallow, consisting of positive tests on each feature, if the changes are early in the release or deemed to be of low risk. Regression testing is typically the largest test effort in commercial software development, due to checking numerous details in prior software features, and even new software can be developed while using some old test-cases to test parts of the new design to ensure prior functionality is still supported.

http://en.wikipedia.org/wiki/Unintended_consequence

http://en.wikipedia.org/wiki/Software_regression

Chapter 7

Data Flow Diagram and E-R Diagram

DATA FLOW DIAGRAM:

E-R DIAGRAM:

UserPasswordUsernam

e

Check

RegisterUsername

DOB

Password Login

Success

Try Again

Home

Discuss

Publish

Logout

My Discussion

Profile

About Us

Chapter 8

Screen Shots

This is the output screen of our website when it starts in the browser.

The output screen where a user can register itself.

The output screen of the home page of discussion forum.

The output screen of user’s own discussion.

The output screen of User’s profile.

Output screen including Admin details.

Output screen for forgot password link.

Chapter 9

Conclusion

( Future Scope

And References)

Future Scope:

“This Forum can easily support any browser. Various updates can be performed in this forum in coming future. This forum will result in minimizing the gap amongst different users. This forum gives a platform which results in an easy way of communication amongst different people from different areas”

References:

1. HTML5 Book Book -Kogent.2. SQL & PL/SQL - Evan Bayross.3. www.w3schools.com 4. www.wikipedia.org 5. Complete reference of Java

http://www.wikipedia.org/

http://www.w3schools.com/

Date post:	07-Aug-2015
Category:	Documents
Upload:	karan-chhabra
View:	73 times
Download:	13 times

Project Report (Discussion Forum)

Documents