ABSTRACT

ONLINE E-BOOK SYSTEM is primarily meant for an educational forum and is intended to enable the members of the website to use all the facilities available. There is a registration process to become a member of this website. The users can read tutorials provided in this website After becoming a member they can read tutorials, post the Queries and problems they wish to get solved, they can post replies to queries posted by other members, send messages to each other. Members can also give tests to check their knowledge level.

TABLE OF CONTENTS
TITLE OF THE PROJECT PROJECT PROPOSAL PROJECT REPORT 1. INTRODUCTION AND OBJECTIVES 1.1. Introduction 1.2. Objectives 2. SYSTEM ANALYSIS 2.1. Identification of Need 2.2. Preliminary Investigation 2.3. Feasibility Study 2.4. Project Planning 2.5. Project Scheduling 2.6. Software Requirement Specification 2.7. Software Engineering Paradigm 2.8. Data Flow Diagram 2.9. E-R Diagram 3. SYSTEM DESIGN 3.1. Module Description 3.2. Database Design 4. CODING 4.1 Complete Project Coding 4.2 Standardization of the coding and code efficiency 4.3 Parameters calling/passing 4.4Validation checks 5. TESTING 5.1 Testing techniques and Testing strategies. 6. SECURITY FOR WEB APPLICATION 7. COST ESTIMATION OF THE PROJECT 8. SCREEN SHOTS 9. GANTT CHART and PERT CHART 9.1 Gantt chart 9.2 Pert chart 10. FUTURE SCOPE 11. BIBLIOGRAPHY 12. ENCLOSED CD
2 39 40 40 41 48 48 48 51 58 62 70 73 80 82 82 89 193

772 779 781 782 783

785 788 789

1. INTRODUCTION AND OBJECTIVES

1.1

INTRODUCTION

ONLINE E-BOOK SYSTEM is a website on an Educational Forum providing solution to the various problems faced by students and learners. It is a marvelous Discussion Board. In this system, there is a registration process to becoming a member. The users who are not a member i.e., unregistered users of our website can only read the tutorials on different topics provided by this website. The following facilities are provided to registered members:1. Members can read different Tutorials
2. Member can post their Queries on different subjects and

can view the Queries posted by other users and the solutions to those queries. 3. Members can reply for queries posted by other members 4. Provision of Online Test is also provided. 5. Members can also send Messages. 1.2 OBJECTIVES

The primary objective of the project is to provide online tutorials on different topics and also provide a platform i.e., a Discussion Board/Forum where members try to solve each others problems. Project has following other objectives: 1. Provide user-friendly environment where the user/members can feed or retrieve the required information in real time with the help of graphical user interface

2. Provide a central database where all the information are stored. It helps in reducing redundancy and efficient space utilization. 3. Update tutorials time to time which give readers current knowledge about related subject.
4. Provide security of data so that unauthorized person cant

access and manipulate any kind of information. For this every member will be provide a username and password. If username and password doesnt match no one can enter in secured region.
5. To be able to perform all the relevant validations that are

required database.

to

be

done

before

performing

particular

transaction or task or before and data needs to enter in the 6. Provide members the facility to evaluate themselves by giving tests and check their performance.

2. SYSTEM ANALYSIS

2.1

IDENTIFICATION OF NEED

The project ONLINE E-BOOK SYSTEM is a real life project.

1. There are thousand of institutes at various places. But there are number of students who have only basic knowledge related to subjects they are studying. 2. The basic problem with the Correspondence courses is that despite of being provided with good material student might not get their queries solved in time which may make them lose interest in that particular query/subject. 3. Students/Learners face lot of problems in solving their doubts

2.2

PRELIMINARY INVESTIGATION

The first step in the system development life cycle is the preliminary investigation to determine the feasibility of the system. It can be viewed as the most recent and perhaps the most comprehensive techniques for solving computer problems.

At the time of preliminary investigation my main aim was to: 1. Clarify and understand the project request. 2. Determine the size of the project. 3. Assess costs and benefits of alternative approaches. 4. Determine the technical and operational feasibility of alternative approaches. 5. Report the findings to my project guide, with recommendations outlining the acceptance or rejection of the proposal.

2.3 FEASIBILITY STUDY In order to study the feasibility of ONLINE E-BOOK SYSTEM The TELOS model which stand for Technical, Economic, Legal, Operational and Schedule was adopted.

The feasibility study of website ONLINE E-BOOK SYSTEM answer the following questions: 1. Technical Feasibility: does the technology exist to implement the proposed system? Is it a practical proposition? 2. Economic Feasibility: is the system cost effective? Do benefits out weight costs? 3. Legal Feasibility: is there any conflict between the proposed system and legal requirements? 4. Operational Feasibility: are the current work practices and procedures adequate to support this proposal? 5. Schedule Feasibility: can the system be developed In time?

Technical Feasibility This is concerned with specifying equipment and software that will successfully satisfy the user requirement. The technical needs of the system may vary considerably, but might include: 1. The facility to produce outputs in a given time. 2. Response time under certain conditions. 3. Ability to process a certain volume of transaction at a particular speed. 4. Facility to communicate data to distant location. To implement ONLINE E-BOOK SYSTEM, commonly available technologies and platforms are used and no new technology and platform is required.

Hence project is technically feasible.

Economic Feasibility Economic analysis is the most frequently used technique for evaluating the effectiveness of a proposed system. More commonly known as cost/benefit analysis in this procedure we determine the benefits and saving that are expected from the proposed system and compare them with costs. We found the benefits outweigh the cost; we take a decision to design and implement the new proposed system. In case of computerization, the cost involvement is not very high, as it used to be about 5-7 years back. So, project is economically feasible.

legal Feasibility Project has no legal issues. It is legally feasible.

Operational Feasibility

In this project we have designed the interface of the system in such a manner so that it is very easy to use and very user friendly. So the operational cost to provide the training is very quickly. So it puts good impact on the visitors who comes to the bank. The management finds it easy to keep a check and have a look at the reports. This Application is very easy to operate as it is made user friendly. Main consideration is users easy access to all the functionality of the Application.

Schedule Feasibility ONLINE E-BOOK SYSTEM is required to be developed in 4 months time. E- TUTORIALS have been planned in a modular manner and one module may be developed more or less in parallel to another. Further, object orientation and code-reuse has being adopted during the development process. Thus, it is feasible to complete ONLINE E-BOOK SYSTEM as per the required schedule.

2.4 PROJECT PLANNING

Basic planning uses bar charts that show project activities and the amount of time they will take .The Gantt charts uses horizontal bars to show the durations of actions or tasks. The left end marks the beginning of the task; the right ends its finish. Earlier tasks appear in the upper left and later ones in the lower right.

1)

Identify the activities and tasks in the stage. Each activity

must be identified to plan the completion date and allocate responsibilities among members of the project team.

In our project, there are five activities:

Design the project. Specify the requirements. Do coding/implementation. Perform testing. Prepare the users manuals.

2)

Determine the tasks for each activity and the estimated

completion times. Each activity is broken down into several tasks. Such as first of all requirements are specified and after that how these requirements will be fulfilled are decided and the expected time to accomplish them.

3) 4)

Determine the total estimated time for each activity and Plot activities on a Gantt chart. All activities, tasks, and

obtain agreement to proceed. milestones are drawn on the Gantt chart, with emphasis on simplicity and accuracy.

5)

Review and record progress periodically. The actual amount

of time spent on each activity is recorded and compared with the budgeted times

System Analysis System Design Software Development Software Testing Software Installation Software Documentation System Evaluation The timeline chart of the above task set (Time Frame: 6 months) has been prepared. The PERT Chart of the software development phase is also prepared and is depicted in figure 1. It is based on the different modules identified in the software

Input to the project: In this project user inputs authenticated username, password and other details to create account on ONLINE E-BOOK SYSTEM. Then user provides his/her personal information to become a member. User also inputs queries, replies, messages, add his/her knowledge etc so that all of us can share and advance our knowledge with the aim of getting an advantageous position in the IT Industry and also to contribute to India's IT Revolution.

Output of the project: In this project all the services provided by ONLINE E-BOOK SYSTEM to the users are considered as the output. Members of ONLINE E-BOOK SYSTEM can Post, View and Download study materials, e-books, notes, Discuss problems and post their solutions, Test their skills by giving online tests related to different topics

2.5 PROJECT SCHEDULING Project scheduling in ONLINE E-BOOK SYSTEM has been done in order to estimate the expected time to complete the various phases of the project like Feasibility Analysis and Requirements Gathering, System Analysis, System Design, Coding, Testing, Implementation and Maintenance etc. Visualization tools like PERT Chart and Gantt chart have been used to control and administer the various tasks required to complete a project. The phases and sub-phases of the tasks those were carried out while implementing the project is tabulated below:
Name of the Phase Preliminary Investigation and Feasibility Study System Analysis Name of the sub-phase Identification of need Preliminary Identification

System Design

Coding Testing

Feasibility Study Project Planning and Scheduling Requirement Analysis DFD/ER and other Diagrams Modularization Details Data Integrity and Constraints Database and Procedural Design User Interface Design Project Coding Validations and Security Checks Debugging Unit Testing Integrated Testing System Testing Implementation and Maintenance

HARDWARE AND SOFTWARE REQUIREMENTS Hardware used while developing application

Processor Ram Hard-disk : : : Intel Pentium IV 1.80 GHz. 256 MB 250 GB

Software used while developing application

OS Front tool Back End Technology : Language Platform : : : : : WinXP service pack 2 Visual Web Developer 2008 SQL Server 2005 ASP.net 3.5 VISUAL C# 2005 .NET Framework 3.5

Minimum Hardware requirement at SERVER SIDE

Processor RAM HARD-DISK : : : 1GHZ 256 MB 10 GB space (for software and application)

Minimum Software Requirement at SERVER SIDE

OS Web-Server Software Platform : : : : Windows XP sp2 Internet information server visual web developer 2008 .NET Framework 3.5

Minimum HARDWARE and SOFTWARE Required at CLIENT level

Any browser which is XHTML 1.0 compatible like Microsoft internet 6.0. Any hardware which support above said browser.

2.6 SOFTWARE REQUIREMENT SPECIFICATION

The software requirement specification (SRS) is very important part of the software building process, which describes the actual user level requirement from technical point of view. I.e. what the

user exactly wants? The objective of preparing the software requirement specification is to represent the requirements of the software in such a manner that ultimately leads to successful software implementation. It is the result of the analysis process of the software development. It should contain all the data the software is going to process, the function it will provide, and the behavior it will exhibit. Software requirement specification (and/or prototype) is conducted by both the software developer and the customer. Because the specification forms the foundation of the development phase, extreme care should be taken in conducting the review. This Software Requirements Specifications (SRS) is defined in IEEE Std. 830-1993, IEEE Recommended Practice for Software Requirements Specifications. The synopsis is prepared in the way to fulfill almost all the points needed in S.R.S.

2.7 SOFTWARE ENGINEERING PARADIGM APPLIED

As

the

application

domains

of

software

are

becoming

complicated and design of big software without a systematic approach is virtually impossible, the field of software engineering is increasingly gaining importance. It is now developing like an industry. The waterfall model provides a systematic and sequential approach to software development and is better than the build and fix approach. But the requirements should be available at the time of commencement of the project. There is no method to judge the problems of software in between different phases. The waterfall model with feedback is as follows:

Requirements Analysis

Design

Coding

Testing

Maintenance

2.8 DATA FLOW DIAGRAM

Data Flow:
An arrow represents a data flow; it represents the path over which data travels in the system. A data flow can move between processes, flow into or out of data stores, to and from external entities.

Bubbles (Process):
A circle or bubble represents that transforms data from once form to another by performing some tasks with the data.

Data store:

A data store is a place where data is held temporarily from one transaction to the next or is stored permanently.

External Entity:
Which defines a source or destination of system data also called an external entity. Based on the working process of the proposed system Data Flow Diagram (DFD), is a model, which gives the insight into the information domain and functional domain at the same time can be drawn using OMT symbols. DFD is refined into different levels. The more refined DFD is more details of the system are incorporated. In the process of creating a DFD, we decompose the system into different functional subsystems. The DFD refinement results in a corresponding refinement of data. Each break-up has been numbered as per the rule of DFD. Here we attempted to incorporate all the details of the system and still it requires further improvement since the entire system is under study.

Data Flow Diagram: 0 Level

This is the context level D.F.D. of the proposed system the whole system has been depicted in a single bubble, primary input and output has been carefully noted and depicted in the way so that information flow continuity should not be lost in the next level. The purposed system is shown as a whole process and the inputs and outputs are shown with incoming and outgoing arrow from the system

Data Flow Diagram: Level 1

This D.F.D. shows all the processes together with all the data stores (tables). It shows the true data flow i.e. how data is actually flowing in the system. Data is coming from which table and going into which table is clearly shown by this DFD. This DFD is the main reference for the development of the system. After understanding the whole system, the application developer will fall back upon this DFD during the Development phase.

Data Flow Diagram: Level 2

There can be one level 2 DFD for each process of the Level 1 DFD. Level 2 shows a process broken down into greater detail.

Level 2 for Registration Details

User Details

ID & Password Generated

User Created

Level 2(Login Process)

User ID & Password

ID & Password Verification Details

Valid User

Invalid User

Level 2 for Quaries/Replies Processing

Registered User

Post Quaries Post Replies

Read Quaries Read Replies

Level 2 for Tests Processing

Registered User

Give tests

Post Test Related Quaries Self Assesment See Test Results

2.9 Entity-Relationship Diagram

The Entity Relationship Diagrams (ERD) is the graphical notation of relationship between data object and attributes. The ERD was originally proposed by Peter Chen for the design of relational database systems and has been extended by others. Sets of primary components are identified for the ERD: data objects, attributes, relationship, and various type indicators. The primary purpose of the ERD is to represent data objects and their relationship.

Address_1 Last_nam e First_nam e Memb_code S_no.

Address_2 city state Pin_cod e Email_id Contact_n o message Send/ recei ve Quaries Ques_code Memb_code Ques_date Ques_head Ques_desc

Profile

ha s

Msg_no Msg_date Msg_detail Memb_cod e pos t

Login_name Memb_cod e password Member

Test_code Test_date Memb_code Memb_id Test_head

giv e

pos t Replies Read /uplo ad Tutorials

Rep_code Memb_code Rep_date Ques_code Rep_desc

Online Test

Tutorial_date Tutorial_head Tutorial_desc

Tquess_cod e Ans_opt1 Ans_opt2

Corrct_ans Ans_opt4 Ans_opt3

Memb_code Tutorial_code

3.1 PROJECT MODULES

3. SYSTEM DESIGN 3.1 MODULE DESCRIPTION

Project Modules & Their Description

Administrator Module Registration module Login Forget Password Module Change Password Module Tutorials Module
Queries Module

Replies Module Online Test Module Message Test Module Administrator Module In this module the Administrator of the website can modify tutorials and add more/delete tutorials.

Administrator

controls

all

the

security

area

like

password, personal information of the members etc.

Registration module In this module new user may register himself/herself to with Virtual Tutorials Website by filling his/her complete information to use the services of the website.

After filling all the information user gets registered with Virtual Tutorials Website and he/she gets the user name and password for login to the site.

Login User can get logged in by providing correct user name and password.

Based on the login he/she is linked to the appropriate page. If the user is not given appropriated name and password, he/she will not be able to log in.

Forget Password Module In the registration module user must have to select Security question and give the answer for that security question to reset the password in case user forgets his/her password.

When any member forgets his/her password the Virtual Tutorials Website security system will ask

him/her to provide his/her username. After entering in the correct username he/she will be able to get the forgotten password by answering a security question that was set up when he/she first opened the account

Change Password Module After sign in to ONLINE E-BOOK SYSTEM user can change his/her password by clicking on provided link, after clicking on link new window will open in front of them where can change password .The system will ask for the current password and new password, enter the current password and new password in the given box and click to ok button. Tutorials Module Users can read tutorials available on different topics. They can also upload their own notes/ tutorials.

Queries Module In this module members can post queries after

registration

They can post queries in different forums. Members can also read queries posted by others

Replies Module After sign in to Virtual Tutorials members can reply to the queries posted by other members.

The solution seeker may then choose among the number of solutions provided by the other members of the site.

Online Test Module There is no. of tests provided for members to check their knowledge.

Members can give tests on different topics. In tests there are objective type questions. They will get their result after test and can assess themselves.
.

Message Test Module Members can send/receive messages to/from other members.

3.2

DATABASE DESIGN

As we have discussed earlier about the under developing system, which is based on .internet technologies so our database will be centralized database which will run on SQL server. New user table:
S. No. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Field Name Membernumber Fname Lname Username gender Dateofbirth Dateofjoining education Address Pincode phone City state image Field Type Int varchar(50) varchar(50) varchar(50) varchar(50) Datetime Datetime varchar(50) varbinary(250) Int Int varchar(50) varchar(50) Image Not null Not null Constraints Primary Key Not null Not null Not null Not null Description Store unique sno for each member Store first name of the member Store last name of the member Store user name of the member Store gender Store date of birth of the member Store date of joining of the member Store education Store address of the member Store pin code of the member Store phone number Store city Store state Store profile image of the member

Contact table:

S. No. 1 2 3 4 5

Field Name Sno name emailid phoneno Msg

Field Type Int varchar(50) varchar(50) Int varchar(50)

Constraints Primary Key

Description Store unique sno for each message Store name of the user

RegularExpressionValidator (abc@pqr.xyz.)

Store Email_Id of the user Store phone no. of the user

Not null

Store the message given by user

Ctest table:
S. No. 1 2 3 4 5 6 7. 8. Field Name Sno Question Option1 Option2 Option3 Option4 Result Languages Field Type int varchar(50) varchar(250) varchar(50) Varchar(50) Varchar(50) varchar(50) Varchar(50) Constraints Primary Key Not null Not null Not null Not null Not null Not null Not null Description Store unique sno for each query Store the questions Store the option1 Store the option2 Store the option3 Store the option4 Store the result of the answer Store the lang.which we choose

answer table:

S. No. 1 2 3 4

Field Name Sno Qno Answer username

Field Type Int Int varchar(250) varchar(50)

Constraints Primary Key Foreign Key(table-html) Not null Not null

Description Store unique sno for each reply Store qno whose ans is posted Store answer by the member Store user name

question table:

S. No. 1 2 3 4

Field Name Sno Languags Questions username

Field Type Int varchar(50) varchar(250) varchar(50)

Constraints Primary Key Not null Not null Not null

Description Store unique sno for each query Store the type of language Store the type of questions Store user name

Queries1 table:

S. No. 1 2 3

Field Name Sno Title description

Field Type Int Int varchar(250)

Constraints Primary Key Foreign Key(table-java) Not null

Description Store unique sno for each reply Store query id whose reply is posted Store description of the ques.

Example table:

S. No. 1 2 3 4 5

Field Name Sno Languages Questions Username Title

Field Type Int varchar(50) varchar(250) varchar(50) Varchar(50)

Constraints Primary Key Not null Not null Not null Not null

Description Store unique sno for each query Store the type of language Store the type of questions Store the username Store the title

4. Coding Complete Project Coding

We use the following languages while doing coding of ONLINE EBOOK SYSTEM 1. JAVA SCRIPT- JavaScript is THE scripting language of the Web. JavaScript is used in millions of Web pages to add functionality, validate forms, detect browsers, and much more. It is the most popular scripting language on the internet, and works in all major browsers, such as Internet Explorer, Firefox, Chrome, Opera, and Safari.

2. HTML- HTML, which stands for Hyper Text Markup Language, is the predominant markup language for web pages. It provides a means to create structured documents by denoting structural semantics for text such as headings, paragraphs, lists etc as well as for links, quotes, and other items. It allows images and objects to be embedded and can be used to create interactive forms. HTML is a standard language, which should mean that all web browsers interpret it in exactly the same way.

3. SQL- SQL is a standard language for accessing and manipulating databases. SQL can execute queries against a database SQL can retrieve data from a database SQL can insert records in a database SQL can update records in a database SQL can delete records from a database SQL can create new databases SQL can create new tables in a database SQL can create stored procedures in a database SQL can create views in a database SQL can set permissions on tables, procedures, and views

4. CSS- CSS is used to control the style and layout of multiple Web pages all at once. With CSS we can save a lot of work. CSS defines HOW HTML elements are to be displayed. Styles are normally saved in external .css files. External style sheets enable you to change the appearance and layout of all the pages in a Web site, just by editing one single file!

5. Asp.net - ASP is a powerful tool for making dynamic and interactive Web pages. An ASP file can contain text, HTML tags and scripts. Scripts in an ASP file are executed on the server. Asp.net can do the following work: 1. Dynamically edit, change, or add any content of a Web page 2. Respond to user queries or data submitted from HTML forms 3. Access any data or databases and return the results to a browser 4. Customize a Web page to make it more useful for individual users 5. The advantages of using ASP instead of CGI and Perl, are those of simplicity and speed 6. Provide security - since ASP code cannot be viewed from the browser 7. Clever ASP programming can minimize the network traffic

5. TESTING

5.1 TESTIND TECHNIQUES AND TESTING STRATEGIES

The following Testing techniques and strategies would be implemented for the testing of ONLINE E-BOOK SYSTEM. We started testing each individual new component and worked out as unit test, integration test, high order test, customer acceptance testing and different testing techniques are used at different times in the process. White Box Testing In white box testing we exercises the internal logic of a program, examine internal program structure and derived tests from an examination of the programs logic, tested internal paths and working of the software. To perform this we used to develop test cases for unit and integration testing. Black Box Testing In black box testing we exercises the input and output requirements of a program, tested by conducting specifications of requirement for which the software should do. This test is derived from the I/O specification and used in most functional tests.

The approach of web app testing adopts the basic principle for all Software testing and applies a strategy and tactics that have been recommended for object oriented system .the following steps summarizes the approach: The content model for the web app is reviewed to uncover errors. This is like copyediting the design model for the web application as reviewed to uncover navigation error. Use cases derived as part of the analyst activity, allow a web engineer to exercise each usage scenario against the architectural and navigational design. These non executable test help uncover error in navigation. Selected processing component and web page is unit tested. When web apps are considered, the concepts of the unit changes, each web page encapsulated in itself content navigation link as Well as script, form and applet (processing element). It is not always possible or practical to test each of these characteristics individually. The architecture is constructed and integration tests are

conducted. The strategy for integration testing depend upon the architecture that has been chosen for the web application

The assembled web application is tested for overall functionality and content delivery. Like conventional validation, the validation of web based systems and application focuses on user visible action and user recognizable output from the system. To assist in the derivation of validation tests the tester should draw upon use cases the use cases provides a scenario that has high likelihood of uncovering errors in user interaction requirement. The web application is implemented in a variety of different Environmental configuration and is tested for compatibility with each configuration. The web application is tested by controlled and monitored Population of end user. Finally with the modular concept inside the application it is being also tested for its Reliability: The system reliability will be insured through data integrity rules built into the database at the backend and the system rules built into the front-end application. The system will take assurance from the user before making any changes permanent.

1. UNIT TESTING The purpose of unit testing in ONLINE E-BOOK SYSTEM is to uncover defects using formal techniques. Defects and deviations in Date formats, Special requirements in input conditions (for example Text box where only numeric or alphabets should be entered, selection based on Radio buttons etc would be identified during the Unit testing phase.

Test case No. Test Phase Functionality Result

001 Unit Test

Security test of the login facility of Project by attempting login control Pass

Test case No. Test Phase Functionality Result

002 Unit Test

Test whether the email text box rejects improper values Pass

Test case No. Test Phase Functionality Result

003 Unit Test

Test whether the data enters to the tables where textboxes are not null Pass

Test case No. Test Phase Functionality Result

004 Unit Test

Test whether the date box rejects improper values Pass

Test case No. Test Phase Functionality Result

005 Unit Test

Test whether the non-member can enter Forum section Pass

Test case No. Test Phase Functionality Result

006 Unit Test

Test whether the non-member can enter Test section Pass

Test case No. Test Phase Functionality Result

007 Unit Test

Test whether the text boxes accepts integer values whose data type is int Pass

Test case No. Test Phase Functionality Result

008 Unit Test

Test whether all given hyperlinks working properly Pass

2. INTEGTATION TESTING During Integration Testing of ONLINE E-BOOK SYSTEM, behavior of the system on the whole is observed. Individual modules are integrated and tested for the whole functionality. The objective is to take the unit tested modules and build a program structure that has been dictated by design.

Test case No. Test Phase Functionality Result

001 Integration Test

Test whether the member can post query Pass

Test case No. Test Phase Functionality Result

002 Integration Test

Test whether the member can post reply Pass

Test case No. Test Phase Functionality Result

003 Integration Test

Test whether the query posted by member is visible in the related forum Pass

Test case No. Test Phase Functionality Result

004 Integration Test

Test whether the reply posted by member is visible in the related section Pass

Test case No. Test Phase Functionality Result

005 Integration Test

Test whether the member name who posts query/reply is visible in the related Forum Pass

Test case No. Test Phase Functionality Result

006 Integration Test

Test whether the members can send messages Pass

3. SYSTEM TESTING System testing is actually a series of different test whose primary purpose is to fulfill the exercise of computer based systems. Although each test has different purpose all work to verify that all system elements have been properly integrated and performed allocated function. System testing is done to showcase the feature of software and the correct working of critical components of the software.

Test case No. Test Phase Functionality Result

001 System Test

Logging in the System and Logging out of System Pass

Test case No. Test Phase Functionality Result

002 System Test

Testing whether a new user can be created Pass

Test case No. Test Phase Functionality Result

003 System Test

Testing whether the password of an existing member can be changed successfully Pass

Test case No. Test Phase Functionality Result

004 System Test

Testing whether the members can visit other members profile Pass

Test case No. Test Phase Functionality Result

005 System Test

Testing whether the members can receive their messages Pass

Test case No. Test Phase Functionality Result

006 System Test

Testing whether the members can give tests and receive the result Pass

6. SECURITY FOR WEB APPLICATION Test case No. 007 Test Phase System Test Test whether the existing profile of a member can be modify Functionality
Result
Pass

All the clients are connected to the server in client server mode as intranet is fully functional as the server loaded with IIS is their at the development center with SQL server database so only the client has to enter the name of the local host and the page in the browser he will be getting the page he needs. All the pages, which are developed, are being kept in the root directory of the server from were a virtual path is assigned to run the codes. The site is virtually testing on the remote server. At the development site a specific web server was established to test the implementation of the site on the local INTRANET web system. All the files and directories are transferred to the virtual directory at the web server through web publishing implementation. For the system security we can take the following step which is as follows: Valid username and passwords given by the administrative control. Provide different kinds of access requirements for different people. Password stored in the database is in the encrypted form. Password is case sensitive.

 Session or Cookies

7. COST ESTIMATION OF THE PROJECT

Cost in a project is due to the requirements for software, hardware, and human resources. Hardware resources are computer time, terminal time and memory required for the project. Software resources include the tools and compilers needed during development. The bulk of cost of software development is due to human resources needed. To achieve reliable cost and effort estimates, a number of options arise:
Delay estimation until late in the project (obviously, we can

achieve

100%

accurate

estimates

after

the

project

is

complete!). Base estimates on similar projects that have already been completed. Use one or more empirical models for software cost and efforts estimation.

Cost and benefit analysis

System cost can be sub-divided into the following categories: 1. Development cost. 2. Operating Cost. 3. Intangible Cost

Development Cost
The salaries of the system analyst and the computer programmer who designed the entire computerized system. Cost of commenting and preparing data files and preparing system manuals and other supportive documents. Cost of preparing new or expanded computer facilities. Cost of testing and documenting the system, training employees and other standard cost. Cost of stationary and system maintenance etc.

Operating Cost
Cost of Hardware/Software, Rental or other Depreciation Cost. The salaries of the technical person such as computer operator. Other data processing personal who will operate the new system?

 The

salaries

of who

system will

analyst perform

and the

computer system

programmer

maintenance function. The cost of input data preparation function. Cost of data processing supplies. Cost of maintaining the proper physical facilities, including power, air conditioning appropriate furniture, power backup facilities etc. Overhead charges of the business firms. Cost of storing the data in machine code form.

8. SCREEN SHOTS

Default.aspx

Login.aspx

Change Password

Forgot Password

CreateUserWizard

Continue

Books.aspx

Cbooks.aspx

Continue

Books download

ContactUs

Logout Page

PersonalInformation.aspx

Continue:

Query1.aspx

Continue:

For fill up queries:-

Continue:

Continue:

Reply.aspx:

Continue:

Reply Output:

Continue:

Answer By User:

GANTT CHART and PERT CHART 9.1 GANTT CHART

1-feb
2-feb 2010 1-march 2010 20-Mar 2010 1-may 2010 10-may 2010

PROPOSED SYSTEM STUDY ANALYSIS

Feasibility Study DESIGNING Verification Menu Design Data Base Design CODING TESTING Unit Testing Combined Module Testing IMPLEMENTATION

Software scope describes the data and control to be processed, function performance, constraints, interfaces and reliability. Function describes in the statement of scope are evaluated and in some case refined to provide more detail prior to the beginning of the estimation. Because both cost and schedule estimates are functionally oriented, some degree of decomposition is often useful. We can implement easily this application. Reusability is possible as and when we require in this application. We can update it next version. We can add new features as and when we require. There is flexibility in all the modules. Scope of this document is to put down the requirements, clearly identifying the information needed by the user, the source of the information and outputs expected from the system.

1. Reusability Reusability is possible as and when we require in this application. We can update it next version. Reusable software reduces design, coding and testing cost by amortizing effort over several designs. Reducing the amount of code also simplifies understanding, which increases the likelihood that the code is correct. We follow up both types of reusability: Sharing of newly written code within a project and reuse of previously written code on new projects.

2. Extensibility This software is extended in ways that its original developers may not expect. The following principles enhance extensibility like Hide data structure, avoid traversing multiple links or methods, avoid case statements on object type and distinguish public and private operations. 3. Robustness Its method is robust if it does not fail even if it receives improper parameters. There is some facilities like Protect against errors, validate arguments and avoid predefined limits. 4. Understandability A method is understandable if someone other than the creator of the method can understand the code (as well as the creator after a time lapse). We use the method with small and coherent helps to accomplish this. 5. Cost-effectiveness Its cost is under the budget and make within given time period. It is desirable to aim for a system with a minimum cost subject well to the condition and that it must to satisfy all the and requirements can be rectified easily. The entire source code is structured commented ensure clarity readability.

6. Portability Since it is an internet based application so its portability and usability depends upon the client connected with the internet. The interface designed that is the web page designing which is one of the major part of web application because it is the first impression regardless of the value of its contents interface should must grab a potential user immediately.

ONLINE E-BOOK SYSTEM application can be extended in various ways for providing more and better facilities to the member. Since this system has been generated by using Object Oriented programming, there are every chances of reusability of the codes in other environment even in different platforms. Also its present features can be enhanced by some simple modification in the codes so as to reuse it in the changing scenario. Reusability is possible as and when we require in this application. We can add new features as and when we require. For example : In future this web application can be extended to make groups that share common interests. We can introduce video conferencing to make the communication among members. Blogs creation can also be implemented to extend the scope.

 We can implement chatting and mailing services to enhance the functionality.

11. BIBLIOGRAPHY

For making this ONLINE E-BOOK SYSTEM project I had gone through some sites of online educational forums like
www.santanu.in

In the course of development of the proposed website the information will be collected from the contents present in the website.

References
Database Management System Vipin C. Desai Asp.Net 3.5 Unleashed By Stephen Walther (Sams) Beginning ASP.NET 3.5 in C# 2008 by Mathew MacDonald (APRESS) SQL Server The Complete Reference.George Koth Kevin Loney Sams Teach Yourself Asp.Net 2.0 in 24 Hours McGraw Hill-- SQL - The Complete Reference