Chapter -1

INTRODUCTION

INTRODUCTION

1.1 PROJECT OVERVIEW

1.1 PROJECT DESCRIPTION

Chapter-2 Need for the project:

PROBLEM DEFINITION
PROBLEM DEFINITION
2.1 Existing System

The first step of preliminary study in the system analysis process involves the identification of needs for Truth Finder. The motivation behind this project is to overcome all the defects in the existing Truth Finder Some of the difficulties are

Registration is compulsory for user to view and search about files and Documents. Search option for user where he want to search for desired files and Documents. Purchasing of albums through credit card.

Need for Truth Finder 2.2 Proposed System

Truth Finder is specially designed for those users who want free resources from a particular data. This Truth Finder is for all type of files and documents search and also particular file search. Truth Finder is designed by young intellectuals with all latest softwares used to give more comparing looks with other Truth Finder

Some of the features of the proposed system are:

Resources

such

files

and

documents

freely

available

without

any

obstructions. New look and feel in music portal with advance option such as search. For all age groups, not for particular age group. Easy to buy music albums using credit card through online.

Latest updates of music albums and songs on music portal. Easy to use and user friendly operations. Requests to Administrator for desired music albums. Download / Listen to songs online. Administrator should have all control of Music Portal. Administrator interests. should update/delete/remove music album based user

Music Portal should have all related information such priceetc of Movies.

Chapter-3 FEASIBILITY STUDY

3. FEASIBILITY STUDY:
3.1 TECHNICAL FEASIBILITY: 3.2 OPERATIONAL FEASIBILITY: 3.3. ECONOMIC FEASIBILITY

Chapter-4

SYSTEM ANALYSIS
4. SYSTEM ANALYSIS

SOFTWARE REQUIREMENT SPECIFICATION What is SRS 1) Problem/Requirement Analysis: 2) Requirement Specification: 3) ROLE OF SRS 4) SCOPE

4.1 DATA FLOW DIAGRAMS

Level 0 for User

4.2 HARDWARE AND SOFTWARE REQUIREMENTS Hard Ware Requirements

Processor:: Pentium-III (or) Higher Ram:: 64MB (or) Higher Cache:: 512MB Hard disk:: 10GB

Soft Ware Requirements

Tools:: Micro Soft Front Operating System:: WindowsNT/2000 Server Side:: JSP with Tomcat Server Client Side:: HTML ,JavaScript Services:: JDBC Database:: Ms-Access2007 Integrated Development Environment: Eclipse

Chapter -5

SYSTEM DESIGN
5. SYSTEM DESIGN

5.1 DATABASE DESIGN:

5.2 INPUT/OUTPUT DESIGN

Chapter

-6

IMPLEMENTATION
OVERVIEW OF SOFTWARE DEVELOPMENT TOOLS
6.1 HTML

Html is a language which is used to create web pages with html marking up a page to indicate its format, telling the web browser where you want a new line to begin or how you want text or images aligned and more are possible.

We used the following tags in our project.

TABLE:

Tables are so popular with web page authors is that they let you arrange the elements of a web page in such a way that the browser wont rearrange them web page authors frequently use tables to structure web pages. <TR>: <TR> is used to create a row in a table encloses <TH> and <TD> elements. <TR> contain many attributes. Some of them are, <TH>: <TH> is used to create table heading. ALIGN: specifies the horizontal alignment of the text in the table row. BGCOLOR: Specifies the background color for the row. BORDERCOLOR: Sets the external border color for the row. VALIGN: Sets the vertical alignment of the data in this row.

 <TD>:

ALIGN: Sets the horizontal alignment of the content in the table cell. Sets LEFT, RIGHT, CENTER. BACKGROUND: Species the back ground image for the table cell. BGCOLOR: Specifies the background color of the table cell VALIGN: Sets the vertical alignment of the data. Sets to TOP, MIDDLE, BOTTOM or BASELINE. WIDTH: Specifies the width of the cell. Set to a pixel width or a percentage of the display area.

<TD> is used to create table data that appears in the cells of a table. ALIGN: Species the horizontal alignment of content in the table cell. Sets to LEFT, CENTER, RIGHT. BGCOLOR: Specifies the background image for the table cell. BGCOLOR: sets the background color of the table cells. WIDTH: Species the width of the cell

FORM:

The purpose of FORM is to create an HTML form; used to enclose HTML controls, like buttons and text fields.

ATTRIBUTES:

ACTION: Gives

the URL that will handle the form data.

NAME: Gives the name to the form so you can reference it in

code set to an alphanumeric string.

METHOD: method or protocol is used to sending data to the

target action URL. The GET method is the default, it is used to send all form name/value pair information in an URL. Using the POST method, the content of the form are encoded as with the GET method, but are sent in environment variables.

CONTROLS IN HTML

<INPUT TYPE =BUTTON>: Creates an html button in a form. ATTRIBUTES: NAME: gives the element a name. Set to alphanumeric characters. SIZE: sets the size. VALUE: sets the caption of the element.

<INPUT TYPE = PASSWORD>: Creates a password text field, which makes typed input. ATTRIBUTES: NAME: gives the element a name, set to alphanumeric characters. VALUE: sets the default content of the element.

<INPUT TYPE=RADIO>: Creates a radio button in a form. ATTRIBUTE: NAME: Gives the element a name. Set to alphanumeric character.

VALUE: Sets the default content of the element.

<INPUT TYPE=SUBMIT>: Creates a submit button that the user can click to send data in the form back to the web server. ATTRIBUTES: NAME: Gives the element a name. Set to alphanumeric characters. VALUE: Gives this button another label besides the default, Submit Query. Set to alphanumeric characters. <INPUT TYPE=TEXT>: Creates a text field that the user can enter or edit text in. ATTRIBUTES: NAME: Gives the element a name. Set to alphanumeric characters. VALUE: Holds the initial text in the text field. Set to alphanumeric characters.

6.2 JAVA SCRIPT

Java script originally supported by Netscape navigator is the most popular web scripting language today. Java script lets you embedded programs right in your web pages and run these programs using the web browser. You place these programs in a <SCRIPT> element, usually within the <HEAD> element. If you want the script to write directly to the web page, place it in the <BODY> element.

6.3 MSAccess The database has become an integral part of almost every human's life. Without it, many things we do would become very tedious, perhaps impossible tasks. Banks, universities, and libraries are three examples of organizations that

depend heavily on some sort of database system. On the Internet, search engines, online shopping , and even the website naming convention (http://www...) would be impossible without the use of a database. A database that is implemented and interfaced on a computer is often termed a database server. One of the fastest SQL (Structured Query Language) database servers currently on the market is the Msaccess server.Msaccess, available for download, offers the database programmer with an array of options and capabilities rarely seen in other database servers. What's more, Msaccess is free of charge for those wishing to use it for private and commercial use. Those wishing to develop applications specifically using Msaccess should consult Msaccess's licensing section, as there is a charge for licensing the product. These capabilities range across a number of topics, including the following: Ability to handle an unlimited number of simultaneous users. Capacity to handle 50,000,000+ records. Very fast command execution, perhaps the fastest to be found on the market. Easy and efficient user privilege system.

A database is really nothing more than a hierarchy of increasingly complex data structures. In Msaccess, the acknowledged structure for holding blocks (or records) of information is called the table. These records, in turn, are made up of the smallest object that can be manipulated by the user, known as the data type. Together, one or more of these data types form a record. A table holds the collection of records that make up part of the database. We can consider the hierarchy of a database to be that of the following: Database < Table < Record < Datatype Datatypes come in several forms and sizes, allowing the programmer to create tables suited for the scope of the project. The decisions made in choosing proper datatypes greatly influence the performance of a database, so it is wise to have a detailed understanding of these concepts.

Msaccess Datatypes Msaccess is capable of many of the datatypes that even the novice programmer has probably already been exposed to. Some of the more commonly used include:
CHAR (M)

CHAR's are used to represent fixed length strings. A CHAR string can range from 1255 characters. In later table creation, an example CHAR datatype would be declared as follows: ex.
car_model CHAR(10); VARCHAR (M)

VARCHAR is a more flexible form of the CHAR data type. It also represents data of type String, yet stores this data in variable length format. Again, VARCHAR can hold 1-255 characters. VARCHAR is usually a wiser choice than CHAR, due to it's variable length format characteristic. Although, keep in mind that CHAR is much faster than VARCHAR, sometimes up to 50%. (A CHAR stores the whole length of the declared variable, regardless of the size of the data contained within, whereas a VARCHAR only stores the length of the data, thus reducing size of the database file.) ex.
car_model VARCHAR(10); INT (M) [Unsigned]

The INT datatype stores integers ranging from -2147483648 to 2147483647. An optional "unsigned" can be denoted with the declaration, modifying the range to be 0 to 4294967295 ex.
light_years INT;

Valid integer: '-24567'. ex.

Invalid integer: '3000000000'.

Valid integer: '3000000000'.

Invalid integer: '-24567'.

A FLOAT represents small decimal numbers, used when a somewhat more precise representation of a number is required.

ex.
rainfall FLOAT (4,2);

This could be used to represent rainfall average in centimeters per year, which could be a decimal value. More specifically, FLOAT (4,2) states the fact that rainfall can hold up to four characters and two decimal places. Thus, 42.35 is valid, accurately represented. 324.45 is invalid, rounded to 324.5. 2.2 is valid, accurately represented. 34.542 is invalid, rounded to 34.54. Note: Due to the fact that FLOAT is rounded, those wishing to represent money values would find it wise to use DECIMAL, a datatype found within Msaccess that does not round values. Consult the documentation for a complete explanation.
DATE

Stores date related information. The default format is 'YYYY-MM-DD', and ranges from '0000-00-00' to '9999-12-31'. MSAccess provides a powerful set of date formatting and manipulation commands, too numerous to be covered within this article. However, one can find these functions covered in detail within the MSAccess documentation.
the_date DATE; TEXT / BLOB

The text and blob datatypes are used when a string of 255 - 65535 characters is required to be stored. This is useful when one would need to store an article such as the one you are reading. However, there is no end space truncation as with VARCHAR AND CHAR. The only difference between BLOB and TEXT is that TEXT is compared case insensitively, while BLOB is compared case sensitively.
SET

A datatype of type string that allows one to choose from a designated set of values, be it one value or several values. One can designate up to 64 values. ex.
transport SET ("truck", "wagon") NOT NULL;

From the above declaration, the following values can be held by transport:

"" "truck" "wagon" "truck,wagon" ENUM

A datatype of type string that has the same characteristics as the SET datatype, but only one set of allowed values may be chosen. Usually only takes up one byte of space, thus saving time and space within a table. ex.
transport ENUM ("truck", "wagon") NOT NULL;

From the above declaration, the following values can be held by transport:
"" "truck" "wagon"

Records Together, a group of declared datatypes form what is known as a record. A record can be as small as one data variable, or as many as deemed needed. One or more records form the structure of a table. The Bigger Picture: Tables Before we can execute commands on the database, we must first create a table in which data can be stored. This is accomplished in the following manner:
MSAccess> CREATE TABLE test ( > name VARCHAR (15), > email VARCHAR (25), > phone_number INT, > ID INT NOT NULL AUTO_INCREMENT, > PRIMARY KEY (ID));

Ensuing output:
Query OK, 0 rows affected (0.10 sec) MSAccess>

The first table in your database has now been created. Note: no two tables can have the same name. Note(2): Each dataspace is more often referred to as a column. Column Characteristics: A name may not be made up of strictly numbers. A name may start with a number. A name may be up to 64 characters.

Other table options: The following options can be placed after any datatype, adding other characteristics and capabilities to them. Primary Key. Used to differentiate one record from another. No two records can have the same primary key. This is obviously useful when it is imperative that no two records are mistaken to be the other. Auto_Increment. A column with this function is automatically incremented one value (previous + 1) when an insertion is made into the record. The datatype is automatically incremented when 'NULL' is inserted into the column. ex.
soc_sec_number INT PRIMARY KEY;

NOT NULL. Signifies that the column can never be assigned a NULL value.

No two soc_sec_number records can hold the same value.

Insertion of records Note: The originally created table, test, created in the last section will be used to illustrate the examples in this section. Here it is again, for quick reference:

MSAccess> CREATE TABLE test ( > name VARCHAR (15), > email VARCHAR (25),

> phone_number INT, > ID INT NOT NULL AUTO_INCREMENT, > PRIMARY KEY (ID));

Insertion of data into the table is accomplished, logically enough, using the INSERT command.

MSAccess> INSERT INTO test VALUES MSAccess> ('Bugs Bunny', '[email protected]', MSAccess> 5554321, NULL);

Result, assuming the command was correctly entered:

Query OK, 1 row affected (0.02 sec) MSAccess>

Selection A database would not be much use if one was not able to search and extract data from it. In MSAccess terms, this is accomplished through the SELECT statement.

MSAccess> SELECT * FROM test MSAccess> WHERE (name = "Bugs Bunny");

Result:

6.4 JAVA SERVER PAGES (JSP)

INTRODUCTION:

Java Server Pages (JSP) technology enables you to mix regular, static HTML with dynamically generated content. You simply write the regular HTML in the normal manner, using familiar Web-page-building tools. You then enclose the code for the dynamic parts in special tags, most of which start with <% and end with %>.

THE NEED FOR JSP: Servlets are indeed useful, and JSP by no means makes them obsolete. However, It is hard to write and maintain the HTML. You cannot use standard HTML tools. The HTML is inaccessible to non-Java developers.

BENEFITS OF JSP:

JSP provides the following benefits over servlets alone: It is easier to write and maintain the HTML: In this no extra backslashes, no double quotes, and no lurking Java syntax. You can use standard Web-site development tools: We use Macromedia Dreamweaver for most of the JSP pages. Even HTML tools that know nothing about JSP can used because they simply ignore the JSP tags. You can divide up your development team: The Java programmers can work on the dynamic code. The Web developers can concatenate on the representation layer. On large projects, this

division is very important. Depending on the size of your team and the complexity of your project, you can enforce a weaker or stronger separation between the static HTML and the dynamic content.

CREATING TEMPLATE TEXT:

A large percentage of our JSP document consists of static text known as template text. In almost all respects, this HTML looks just likes normal HTML follows all the same syntax rules, and simply passed through to that client by the servlet created to handle the page. Not only does the HTML look normal, it can be created by whatever tools you already are using for building Web pages.

There are two minor exceptions to the template text passed through rule. First, if you want to have <% 0r %> in the out port, you need to put <\% or %\> in the template text. Second, if you want a common to appear in the JSP page but not in the resultant document, <%-- JSP Comment -- %> HTML comments of the form: <!HTML Comment --> are passed through to the client normally.

TYPES OF JSP SCRIPTING ELEMENTS: JSP scripting elements allow you to insert Java code into the servlet that will be generated from the JSP page. There are three forms:
1.

Expressions of the form <%=Java Expression %>, which are evaluated and inserted into the servlets output. Sciptlets of the form <%Java code %>, which are inserted into the servlets_jspService method (called by service).

2.

3.

Declarations of the form<%! Field/Method Declaration %>, which are inserted into the body of the servlet class, outside any existing methods.

USING JSP EXPRESSIONS:

A JSP element is used to insert values directly into the output. It has the following form: <%= Java Expression %> The expression is evaluated, converted to a string, and inserted in the page. This evaluation is performed at runtime (when the page is requested) and thus has full access to the information about the request. For example, the following shows the date/time that the page was requested. Current time: <%=new java.util.Date () %>

PREDEFINED VARIABLES:

To simplify expressions we can use a number of predefined variables (or implicit objects). The specialty of these variables is that, the system simple tells what names it will use for the local variables in _jspService.The most important ones of these are: request, the HttpServletRequest. response, the HttpServletResponse. session, the HttpSession associated with the request out, the writer used to send output to clients.

application, the ServletContext. This is a data structure shared by all servlets and JSP pages in the web application and is good for storing shared data.

Here is an example:

Your hostname: <%= request.getRemoteHost () %>

COMPARING SERVLETS TO JSP PAGES

JSP works best when the structure of the HTML page is fixed but the values at various places need to be computed dynamically. If the structure of the page is dynamic, JSP is less beneficial. Some times servlets are better in such a case. If the page consists of binary data or has little static content, servlets are clearly superior. Sometimes the answer is neither servlets nor JSP alone, but rather a combination of both.

WRITING SCRIPTLETS

If you want to do something more complex than output the value of a simple expression .JSP scriptlets let you insert arbitrary code into the servlets _jspService method. Scriptlets have the following form: <% Java code %> Scriptlets have access to the same automatically defined variables as do expressions (request, response, session, out , etc ) .So for example you want to explicitly send output of the resultant page , you could use the out variable , as in the following example: <%

String queryData = request.getQueryString (); out.println (Attached GET data: + queryData); %> SCRIPTLET EXAMPLE:

As an example of code that is too complex for a JSP expression alone, a JSP page that uses the bgColor request parameter to set the background color of the page .Simply using <BODY BGCOLOR=<%= request.getParameter (bgcolor) %> > would violate the cardinal rule of reading form data.

USING DECLARATIONS

A JSP declaration lets you define methods or fields that get inserted into the main body of the servlet class .A declaration has the following form: <%! Field or Method Definition %> Since declarations do not generate output, they are normally used in conjunction with JSP expressions or scriptlets. In principle, JSP declarations can contain field (instance variable) definitions, method definitions, inner class definitions, or even static initializer blocks: anything that is legal to put inside a class definition but outside any existing methods. In practice declarations almost always contain field or method definitions. We should not use JSP declarations to override the standard servlet life cycle methods. The servlet into which the JSP page gets translated already makes use of these methods. There is no need for declarations to gain access to service, doget, or dopost, since calls to service are automatically dispatched to _jspService , which

is where code resulting from expressions and scriptlets is put. However for initialization and cleanup, we can use jspInit and jspDestroy- the standard init and destroy methods are guaranteed to call these methods in the servlets that come from JSP.

6.5 JAKARTA TOMCAT

Tomcat is the Servlet/JSP container. Tomcat implements the Servlet 2.4 and JavaServer Pages 2.0 specification. It also includes many additional features that make it a useful platform for developing and deploying web applications and web services.

TERMINOLOGY:

Context a Context is a web application. $CATALINA_HOME This represents the root of Tomcat installation. DIRECTORIES AND FILES: /bin Startup, shutdown, and other scripts. The *.sh files (for Unix systems) are functional duplicates of the *.bat files (for Windows systems). Since the Win32 command-line lacks certain functionality, there are some additional files in here.

/conf Configuration files and related DTDs. The most important file in here is server.xml. It is the main configuration file for the container.

/logs Log files are here by default.

/webapps This is where webapps go\

INSTALLATION:

Tomcat will operate under any Java Development Kit (JDK) environment that provides a JDK 1.2 (also known as Java2 Standard Edition, or J2SE) or later platform. JDK is needed so that servlets, other classes, and JSP pages can be compiled.

DEPLOYMENT DIRECTORIES FOR DEFAULT WEB APPLICATION: HTML and JSP Files Main Location $CATALINA_HOME/webapps/ROOT

Corresponding URLs. http://host/SomeFile.html http://host/SomeFile.jsp

More Specific Location (Arbitrary Subdirectory). $CATALINA_HOME/webapps/ROOT/SomeDirectory

Corresponding URLs http://host/SomeDirectory/SomeFile.html

http://host/SomeDirectory/SomeFile.jsp

Individual Servlet and Utility Class Files

Main Location (Classes without Packages). $CATALINA_HOME/webapps/ROOT/WEB-INF/classes

Corresponding URL (Servlets). http://host/servlet/ServletName

More Specific Location (Classes in Packages). $CATALINA_HOME/webapps/ROOT/WEB-INF/classes/packageName

Corresponding URL (Servlets in Packages). http://host/servlet/packageName.ServletName

Servlet and Utility Class Files Bundled in JAR Files

Location $CATALINA_HOME/webapps/ROOT/WEB-INF/lib

Corresponding URLs (Servlets) http://host/servlet/ServletName http://host/servlet/packageName.ServletName

Chapter -7

TES TING

7 .SOFTWARE TESTING
Testing Software testing is a critical element of software quality assurance and represents the ultimate review of specification, design and code generation.
7.1 TESTING OBJECTIVES To ensure that during operation the system will perform as per specification. TO make sure that system meets the user requirements during operation To make sure that during the operation, incorrect input, processing and output will be detected To see that when correct inputs are fed to the system the outputs are correct To verify that the controls incorporated in the same system as intended Testing is a process of executing a program with the intent of finding an error A good test case is one that has a high probability of finding an as yet undiscovered error

The software developed has been tested successfully using the following testing strategies and any errors that are encountered are corrected and again the part of the program or the procedure or function is put to testing until all the errors are removed. A successful test is one that uncovers an as yet undiscovered error.

Note that the result of the system testing will prove that the system is working correctly. It will give confidence to system designer, users of the system, prevent frustration during implementation process etc.,

7.2 TEST CASE DESIGN: White box testing

White box testing is a testing case design method that uses the control structure of the procedure design to derive test cases. All independents path in a module are exercised at least once, all logical decisions are exercised at once, execute all loops at boundaries and within their operational bounds exercise internal data structure to ensure their validity. Here the customer is given three chances to enter a valid choice out of the given menu. After which the control exits the current menu.

Black Box Testing

Black Box Testing attempts to find errors in following areas or categories, incorrect or missing functions, interface error, errors in data structures, performance error and initialization and termination error. Here all the input data must match the data type to become a valid entry. The following are the different tests at various levels:

Unit Testing:

Unit testing is essentially for the verification of the code produced during the coding phase and the goal is test the internal logic of the module/program. In the Generic code project, the unit testing is done during coding phase of data entry forms whether the functions are working properly or not. In this phase all the drivers are tested they are rightly connected or not. Integration Testing: All the tested modules are combined into sub systems, which are then tested. The goal is to see if the modules are properly integrated, and the emphasis being on the testing interfaces between the modules. In the generic code integration testing is done mainly on table creation module and insertion module.

Validation Testing

This testing concentrates on confirming that the software is error-free in all respects. All the specified validations are verified and the software is subjected to hard-core testing. It also aims at determining the degree of deviation that exists in the software designed from the specification; they are listed out and are corrected.

System Testing

This testing is a series of different tests whose primary is to fully exercise the computer-based system. This involves: Implementing the system in a simulated production environment and testing it. Introducing errors and testing for error handling.

TEST CASES

TEST CASE 1:

Test case for Login form:

When a user tries to login by submitting an incorrect ID or an incorrect Password then it displays an error message NOT A VALID USER NAME.

TEST CASE 2:
Test case for User Registration form: When a user enters user id to register and ID already exists, then this result in displaying error message USER ID ALREADY EXISTS.

TEST CASE 3:
Test case for Change Password: When the old password does not match with the new password, then this results in displaying an error message as OLD PASSWORD DOES NOT MATCH WITH THE NEW PASSWORD. Test case for Forget Password: When a user forgets his password he is asked to enter Login name, ZIP code, Mobile number. If these are matched with the already stored ones then user will get his Original password.

TEST CASE 4:
Test case for StudentID : When the student wants to write the exam he has to enter his student ID correctly otherwise we get a message INVALID USER If the student had already written the exam and if he tries tom write the exam again then we get a message USER ALREADY REGISTERED

TEST CASE 5:
Validation cases: If any data field which accept the data from the user are not filled then the corresponding error messages are generated.

Chapter -8

OUTPUT SCREENS