TABLE OF CONTENTS

1. About Organization
2. Introduction
3. Objective
4. Design Phase
5. SDLC
6. About Training
7. Conclusion
8. Bibliography

ABOUT ORGANISATION

COMPANY PROFILE

ADDRESS OF THE ORGANIZATION

NAME        :        COMPUCOM SOFTWARE LTD.

ADDRESS        :         IT-14, 15 RIICO

                                      Industrial area

                                      Sitapura, JAIPUR-302022(RAJ.)

                                         INDIA

PHONE        :        91-141-2770131-134

                                     91- 141-5115901-902

ORGANIZATION PROFILE

• Compucom was established in 1991 , at New Jersy ,USA.
• Starred Indian operations in July 1994.
• “Best regional Software Exporter Award “from STPI, Govt. of India for 1996-1997, 1997-1998, 1999-2000.
• Strategic alliance with US$120 Mn Tekmark Global solutions Representative on the board of CSL with equity stake.
• Listed on Mumbai Stock Exchange.
• 230 Authorised   Business Associates Rajasthan.
• Already executing multi crore IT Boot Project for Rajasthan govt. spread across the state of Rajasthan.
• 1994-Compucom Technologies Pvt. LTD for AM/FM/GIS.
• 1995-Compucom software limited for software development.
• July 1999- All group software business consolidated under CSL.
• June 2000- CSL Global Solutions GMBH, Cologne, Germany.

SERVICES OF THE COMPANY

• Software design and development
• AM/FM/GIS conversion
• Customized web solutions
• 7*24 customer support and maintenance.
• Data/Drawing /Document conversion
• IT training and conversion
• Onsite staff supplementation
• Business process outsourcing

CLIENTS OF THE COMPANY

• Lucent Technologies
• Techmark Global Solutions
• Bell Atlantic
• Dun & Bradstreet
• Old Bridge Township
• Long Beach Island- Area estate agency
• RIICO
• State Bank of Bikaner & Jaipur
• Bharat Potteries Ltd.
• Chokhi Dhani Resort
• Institute for development studies
• Rajasthan Electronics Industries Ltd.
• Lok Jumbish
• Director Public Instructions Administration , Chandigarh
• Rajasthan Board of Secondary Education Ajmer.

INTODUCTION

TITLE OF PROJECT

ONLINE BILLING

PROJECT GUIDE

NAME        :        Mr. Gaurav yadav

PLATFORM USED

Windows 95, 98

LANGUAGE USED

JAVA along with JS , JavaScript , html.

DATABASE

MS ACCESS

FEASIBILITY STUDY

2.1Problem Statement :

To develop software named Online Billing .It will be developed for individual. It will have following features-

        1.        It will contain list of users along with their bill details.

        2.        It will maintain request of a user.

3.        It will be able to add or remove any entry.

                4.        It will also generate report for a user request.        

2.2 Constraints for Development :

Implementation Environment

Hardware required        : RAM-64 MB (minimum), 2 GB Hard Disk.     

Operating System                : Windows 95 & Higher Version

Front End                        : JSP

Mid End                        : Tomcat 5.0.27

Backend Software                : MS Access

Time                                : 30 days (approx.)

Human resource required (minimum) :

Project leader                   : one

Programmer                         : 2

Testing                                : one

Machine required (minimum) - one PC

Skill set: Team members should have basic knowledge of JSP , JavaScript  and MS Access 2000.        

OBJECTIVE

                              “Necessity is Mother of All Inventions”

In the current scenario record keeping and proper reporting have been the need of the hour for every transaction, including interactive interface and easy to use application, these points provided a right direction for development of this system.

          My purpose in developing this application was to provide yellow page information that will be easy to navigate and operate, proper record keeping and reporting, and application that can be implemented on desktop or client/server architecture.

I have developed this system an easy to use and operate thus I assume only a familiarity with computer operation and no specific knowledge of any software, package or language.

Concepts are presented using intuitive description, many of which are based on running application at user end. Important documentation required in software development life cycle is covered in this project report, but actual codes are omitted.

The bibliographic note contain pointers to the referred books or documents that provided a needful help in developing the documents and code.

The fundamental step used in SDLC process is based on the ISO 9001 guidelines. My aim was to follow the ISO guidelines and develop a perfect system.

The system development was organized into 5 major parts:

• Requirement Gathering

• Documentation/Design
• Coding
• Testing
• Implementation  & Maintenance

Each of the above-defined modules has their sub module. System design and Development was integrated into different modules such as:

• Login Module
• Add  User Account
• Edit User Account
• Delete User Account
• Make bill
• Submit bill
• Search Billing Informations

1- By Name

2- By Mobile No.

     3- By Phone No.

DESIGN PHASE

PRELIMINARY DESIGN

4.        PROCEDURE

        4.1        DESIGN PLAN:

                1.        Feasibility Study

                2.        Requirement definition Analysis and Specification.

        4.2        PRELIMINARY DESIGN

                4.2.1        ARCHITECTURE

To develop the System for online billing three tiers architecture is maintained and the model will work both with standalone application as well as client server model. The database and application resides on the same machine. Client working on the application perform different operations on the database and database manipulate the request and generate the result.

Typical role of client side:-

• The client should gather all needed information before making a request to the server.
• The client is responsible for all display of data to the client.
• The client should handle all data manipulation operations.
• The client provides all formatting of data and presentation of information in reports.

Typical role of server side:-

On server side the operations are broken into logical components. The server should create the result set that the client side application require.

Client-Server approach introduced a database server to replace the file server. Using RDBMS user queries could be answered directly. The client/server architecture reduced network traffic by providing a query response rather than total file transfer. It improves a multi-user updating through a GUI front end to a shared database. In client-server architecture, Remote Procedure Calls (RPC s) or Structured Query Language are typically used.

Advantages of client / server:-

The client/server architecture reduced network traffic by providing a query response rather than total file transfer. It improves a multi-user updating through a GUI front end to a shared database. It also increases performance of our application. With SQL Server, we can implement true client/server system.

4.3        DATA MODEL

As per requirement the information that is to be stored in database is:-

        1.        Information about User’s Bill (like name, address, phone etc.)

        2.        Login details (like user name, password etc.)

ARCHITECTURAL DESIGN

6.1 Architectural Design

        6.1.1        Operational and Functional Procedural Description

The complete system is developed using modular development technique. The task is divided into four major modules, namely:

• Login
• Create User
• Add Entry
• Erase Entry
• Modify Entry

1. Search Name
2. By Mobile number

Module description is given below :

Login Module:        This module takes user name and password. This module validates username and password.

Input parameter        :        user name, password

                       Output parameters        :        Permission Accepted / Denied          

Create User Module:        This process is used to create users that can access this application. The administrator can only create users.

Input parameter        :        user name, password 

                   Output parameters        :        user created/denied.

Delete User Module : This process is used to delete users that are accessing this application. The administrator can only delete users.

Input parameter        :        user name

        Output parameters        :        user deleted.

           Add Entry Module : This process is used to add the new number subscribed to users and updates the database accordingly.

Input parameter        :        name, address, phone

        Output parameters        :        entry added to database

Erase Entry Module : This process is used to erase the numbers that are surrendered to Govt. and updates the database accordingly.

Input parameter        :        username

        Output parameters        :        entry deleted from database

Modify Entry Module : This process is used to change any record already present in the database and updates the database accordingly.

Input parameter        :        name, address, phone

        Output parameters        :        entry added to database

Search module : This module provides flexibility to user for searching the list of companies of a particular location.

1. By Mobile Number :- In this module user has to enter the mobile number which in result returns the details of user’s bill.
2. By  Name:-In this module user has to enter the name  which in result returns bill details.

           3.  By Phone Number :- In this module user has to enter the phone number which in result returns the details of user’s bill.

                Input parameters – Name, Mobile Number, Phone Number.

                Output parameters – Bill Details.

TEST PLANS

SOFTWARE DEVELOPMENT LIFE CYCLE

PRINT SCREEN

Database tables:

1. Login table

2. Bill Table

1. Login page: - First page of the project

2. Page containing various operations

3. Page to add user information

4.  Page to edit information of existing user

5. Page to add bill information

ABOUT THE TRAINING

1. OBJECTIVE ANALYSIS

This stage specifies the problem definition that is it identifies the specific problem to be solved.

2. REQUIREMENT ANALYSIS

The requirement gathering process is intensified & focused specifically on software. To understand the nature of the program to be built, we must understand the information domain for the software, as well as the required function, behavior, performance and interface. Requirements for both the system & the software are documented and reviewed with the customer.

3. DISCUSSION WITH PROJECT GUIDE AND PROJECT HEAD

As this is the very first time we are preparing any project ,so we have made our project  under the guidance of our project in charge & faculty of computer science.

4.ANALYSIS OF INFORMATION

In these stage models of the system is created in an effort to better understand data & control flow ,functional processing ,operational behaviour & information content .The model serves as a foundation for software design.

5. COMPARING WITH AN EXISTING SYSTEM

The system model which is analyzed is compared with real life or existing system so that if there is any thing which is not present in our system model is provided in it.

6. DESIGNING  

Software design is an iterative process through which    requirements are translated into a “blueprint” for constructing the software .Software design is actually a multistep process that focuses on four distinct attributes of a program data structure ,software architecture ,interfaces representation & procedural (algorithmic) details.

 7 .CODING CUSTOMER CARE

The design must be translated into a machine readable form. The code generation step performs this task & we provide the actual code .

1. REVIEWING AND TESTING  

Once code has been generated, program testing begins. The testing process focus on the logic of the software , ensuring that all statements have been tested and on the functional externals ,that is ,conducting test to uncover errors and ensure that define input will produce actual result that agree with required result.

9. SUBMISSION OF PROJECT REPORT

     Once system is tested ,project report  is made and submitted to project in charge.

INTRODUCTION TO J2EE

                         The Java 2 SDK is a development environment for building applications, applets, and components that can be deployed on implementations of the Java 2 Platform. It includes tools useful for developing and testing programs written in the Java programming language and running on the Java platform.  

J2EE Architecture :

The JavaTM 2 SDK, Enterprise Edition (J2EE SDK) is the reference implementation    provided by Sun Microsystems, Inc. The following figure shows the major elements

Of the architecture for the J2EE SDK:

J2EE Server:    The J2EE server provides the following services

• Naming and Directory - allows programs to locate services and components through the Java Naming and Directory InterfaceTM (JNDI) API
• Authentication - enforces security by requiring users to log in
• HTTP - enables Web browsers to access servlets and Java Server PagesTM (JSP) files
• EJB - allows clients to invoke methods on enterprise beans

J2EE Applications:

 You assemble a J2EE application from three kinds of modules: enterprise beans, Web  components, and J2EE application clients. These modules are reusable-- you can build new applications from existing enterprise beans and components. And because the modules are portable, the application they comprise will run on any J2EE server that conforms to the specifications.

       Contents of a J2EE Application:

Figure 1-4 shows the hierarchy of a J2EE application. A J2EE application may contain  one or more enterprise beans, Web components, or J2EE application client components. An enterprise bean is composed of three class files-- the EJB class, the remote interface, and the home interface. (The next chapter discusses these class files in more detail.) A Web component may contain files of the following types: servlet class, JSP, HTML, and GIF. A J2EE application client is a Java application that runs in an environment (container) which allows it to access J2EE services.

Each J2EE application, Web component, enterprise bean, and J2EE application client has a deployment descriptor. (Figure 1-4 abbreviates a deployment descriptor as DD.) A deployment descriptor is an .xml file that describes the component. An EJB deployment descriptor, for example, declares transaction attributes and security authorizations for an enterprise bean. Because this information is declarative, it can be changed without requiring modifications to the bean's source code. At run time, the J2EE server reads this information and acts upon the bean accordingly.

FIGURE 1-4 Contents of a J2EE Application

And you bundle each module into a file with a particular format-- a J2EE application in an .ear file, an enterprise bean in an EJB .jar file, a Web component in a .war file, and a J2EE application client in a .jar file. An .ear file, for example, contains an .xml file for its deployment descriptor, and one or more EJB .jar and .war files. An EJB .jar contains its deployment descriptor the .class files for the enterprise bean. The following table lists the file type of every element residing in a J2EE application.

Supported Platforms :

• SolarisTM Operating Environment, version 2.6
• Windows NT, version 4.0

Supported Databases and JDBCTM Drivers :

This release supports database drivers that conform to versions 1.0 and 2.0 of the JDBC API. We have performed tests with the following database servers:

• Oracle8 Server, version 8.05
• Microsoft SQL Server, versions 6.5, 7.0
• Cloudscape, version 3.0.4
• Ms access  

HTML (HYPERTEXT MARKUP LANGUAGE):

HTML documents are plain-text (also known as ASCII) files that can be created using any text editor (e.g., Emacs or vi on UNIX machines; SimpleText on a Macintosh; Notepad on a Windows machine).

The markup tags in a plain-text file and imagining what the resulting page will look like. It is useful to know enough HTML to code a document before you determine the usefulness of a WYSIWYG editor, in case you want to add HTML features that your editor doesn't support.

Tags Explained

An element is a fundamental component of the structure of a text document. Some examples of elements are heads, tables, paragraphs, and lists. You use HTML tags to mark the elements of a file for your browser. Elements can contain plain text, other elements, or both.

To denote the various elements in an HTML document, you use tags. HTML tags consist of a left angle bracket (<), a tag name, and a right angle bracket (>). Tags are usually paired (e.g., <H1> and </H1>) to start and end the tag instruction. The end tag looks just like the start tag except a slash (/) precedes the text within the brackets

The Minimal HTML Document

Every HTML document should contain certain standard HTML tags. Each document consists of head and body text. The head contains the title, and the body contains the actual text that is made up of paragraphs, lists, and other elements. Browsers expect specific information because they are programmed according to HTML and SGML specifications.

Required elements are shown in this sample bare-bones document:

    <html>

    <head>

    <TITLE>A Simple HTML Example</TITLE>

    </head>

    <body>

1.HTML

This element tells your browser that the file contains HTML-coded information. The file extension .html also indicates this an HTML document and must be used. (If you are restricted to 8.3 filenames (e.g., LeeHome.htm, use only .htm for your extension.)

2.HEAD

The head element identifies the first part of your HTML-coded document that contains the title. The title is shown as part of your browser's window (see below).

3.TITLE

The title element contains your document title and identifies its content in a global context. The title is typically displayed in the title bar at the top of the browser window, but not inside the window itself. The title is also what is displayed on someone's hotlist or bookmark list.

4.BODY

The second--and largest--part of your HTML document is the body, which contains the content of your document (displayed within the text area of your browser window). The tags explained below are used within the body of your HTML document.

5.Headings

HTML has six levels of headings, numbered 1 through 6, with 1 being the largest. Headings are typically displayed in larger and/or bolder fonts than normal body text. The first heading in each document should be tagged <H1>.

6.Horizontal Rules

The <HR> tag produces a horizontal line the width of the browser window. A horizontal rule is useful to separate major sections of your document.

You can vary a rule's size (thickness) and width (the percentage of the window covered by the rule). Experiment with the settings until you are satisfied with the presentation. For example:

<HR SIZE=4 WIDTH="50%">

Displays as:

       7.Physical Styles

<B>

bold text

<I>

italic text

<TT>

<TR> ... </TR>

Specifies a table row within a table. You may define default attributes for the entire row: ALIGN (LEFT, CENTER, RIGHT) and/or VALIGN (TOP, MIDDLE, BOTTOM).

<TD> ... </TD>

Defines a table data cell. By default the text in this cell is aligned left and centered vertically. Table data cells may contain other attributes to determine the characteristics of the cell and/or its contents

8. Inline Images

Most Web browsers can display inline images (that is, images next to text) that are in X Bitmap (XBM), GIF, or JPEG format. Other image formats are also being incorporated into Web browsers [e.g., the Portable Network Graphic (PNG) format]. Each image takes additional time to download and slows down the initial display of a document..

To include an inline image, enter:

    <IMG SRC=ImageName>

where ImageName is the URL of the image file.

Typewriter text, e.g. fixed-width font

Image Size Attributes:

<IMG SRC=SelfPortrait.gif HEIGHT=100 WIDTH=65>

9.Background Color:

By default browsers display text in black on a gray background. However, you can change both elements if you want. Some HTML authors select a background color and coordinate it with a change in the color of the text.

<BODY BGCOLOR="#000000" TEXT="#FFFFFF" LINK="#9690CC">

This creates a window with a black background (BGCOLOR), white text (TEXT), and silvery hyperlinks (LINK).

Linking

The chief power of HTML comes from its ability to link text and/or an image to another document or section of a document. A browser highlights the identified text or image with color and/or underlines to indicate that it is a hypertext link (often shortened to hyperlink or just link).

HTML's single hypertext-related tag is <A>, which stands for anchor. To include an anchor in your document:

1. start the anchor with <A (include a space after the A)
2. specify the document you're linking to by entering the parameter HREF="filename" followed by a closing right angle bracket (>)
3. enter the text that will serve as the hypertext link in the current document
4. enter the ending anchor tag: </A> (no space is needed before the end anchor tag)

Here is a sample hypertext reference in a file called US.html:

    <A HREF="MaineStats.html">Maine</A>

This entry makes the word Maine the hyperlink to the document MaineStats.html, which is in the same directory as the first document

CONCLUSION AND VALIDATION

From a proper analysis of the positive points and constraints on the component, it can be safely concluded that the product is a highly efficient GUI based component. This component can be easily being plugged in many other systems.

Also the component is highly user friendly. Generally the search and updating in stores are done by non-technical people. So it is in the best interest of the organization to use such software which their employees can handle easily. This software comes with just that solution. Being mostly GUI based, this component can be used very easily. With very little training, users can learn the usage of the product. Also the search results are presented in numerous forms like report format, graphical format etc which makes it versatile. Again the GUI based system is certainly more eye-catching and attractive. Nowadays most of the companies are going global .So their business has also become distributed and diverse.

BIBLOGRAPHY

• JAVA FOR THE WEB WITH JSP AND EJB BY BUDI KURWAN

• COMPLETE REFERENCE OF JAVA(J2EE AND J2SE) BY HERBERT SCHILDT