Document e Transactions

PROJECT TITLE

Universal Dossier

INDEX

1. Introduction

2. System Analysis

a. Existing System

b. proposed System

3. Feasibility Report

a. Technical Feasibility

b. Operational Feasibility

c. Economical Feasibility

4. System Requirement Specification Document

a. Overview

b. Modules Description

c. Process Flow

d. SDLC Methodology

e. Software Requirements

f. Hardware Requirements

5. System Design

a. DFD

b. E-R diagram

c. UML

d. Data Dictionary

6. Technology Description

7. Coding

8. Testing & Debugging Techniques

9. Output Screens

10. Reports

11. Future Enhancements

12. Conclusion

13. Bibliography

INTRODUCTION

ABSTRACTProviding an Internet based application for supporting the E-Business and thus changing the way people conduct their Business utilizing the latest developments in the field of computer technology. E-transactions are a lot quicker than shopping at the mall, because you can do them without leaving your home.

E-Transactions are internet-based transactions performed electronically by individuals, companies, corporations, and government which use Internet e-Card system to make the payments while purchasing over the internet. E-Card is a prepaid card denomination through their bank accounts. The e-Card provides the users a secure payment structure without any misuse of their account. The security is maintained by providing the customer with their personal identification number. And E-Transaction is not only buying and selling of goods via the internet, beyond that it is one that executes exactly-once despite failures. E-Transactions are any form of data transaction, including financial and knowledge management

PROBLEM ANALYSIS

Scope specifies Products, Functions, Benefits and Goals of the System. Scope is a physical view of the System that explains how it performs, what are the products that involve in System process. BY seeing the Scope we can understand the benefits that come by using System and what goals will we reach.

The e-Transactions are an Online Transactions that performed using Internet Rupeyaa Card (IRC) to make the payments while purchasing over the Internet. IRC is a prepaid card purchased as prepaid denominations through Credit cards or Saving Accounts.

IRC is a Secure and Universal payment card. Due to the misuse of Credit cards, many online users are reluctant to use that facility. The e-Rupeyaa card provides the users with a secure payment structure without any misuse of their amount.

The security is maintained by providing the Customers with their individual Personal Identification Number(PIN).Definitely using IRC is more secure than using the Credit card.

NEED FOR AUTOMATION

The e-Transactions are an Online Transactions that performed using Internet Rupeyaa Card (IRC) to make the payments while purchasing over the Internet. IRC is a prepaid card purchased as prepaid denominations through Credit cards or Saving Accounts.

IRC is a Secure and Universal payment card. Due to the misuse of Credit cards numbers, many online users are reluctant to use that facility. The e-Rupeyaa card provides the users with a secure payment structure without any misuse of their amount.

The security is maintained by providing the Customers with their individual Personal Identification Number (PIN).Definitely using IRC is more secure than using the Credit card.

Features involved in the System:

The system uses a secure and safe methodology for Shopping Online.

The system maintains the accounts of the Customer and Manufacturer or Supplier.

The Administrator has complete access to the accounts of Manufactures and Users.

The system also provides links to different shopping sites which are in mutual understanding with e- Card Company.

The e- Card Company takes the responsibility for payment of the price only after the product reaches the customer.

The e- Card Company is only limited to placing orders and confirming it to the user and the manufacturer.

The websites of the Companies regularly not meeting with the expectations will be removed from the e- Card Membership.

EXISTING SYSTEM

E-Transactions is nothing but Online Shopping .The system contains distributor and clients .There are so many MLM (Multi Level Marketing companies),nothing but the Markets which produces the products at different levels. MLMs want to increase their business as their existing depends on it. But they have limited number of Distributors. MLMs are not in a position to have their own Shopping-Site. Distributors have problems to buy the products from companies as they are at different locations.

And also for Online shopping the Existing system uses Credit Cards, which are very dangerous while purchasing over Internet.

LIMITATIONS OF EXISTING: For credit card we must have bank A/C

For different banks there are different servers by using credit card

We have to pay the charge for every month.

We must pay the interest on purchasing through credit card.

More chances to misuse of our credit card information

We have to use only limited amount

There is a chance to hacking into your A/C.

The Difference between a Credit card and a Debit card:

A Credit card gives the Customers a spending limit and then they are billed at the end of each month, paying interest on the money that has already been spent. With a Debit card, Customers put money on the card first and then spend it however they wish.

Since Internet Rupeyaa Cards are prepaid Debit cards, there is no Line of Credit extended. This means that the spending limit is determined by the amount of money that is loaded to the Internet Rupeyaa Card. Best of all, because it is not a Credit card, there are no finance charges, no late fees, and no accumulation of debt.

FEASIBILITY REPORTFEASIBILITY REPORT

TECHNICAL FEASIBILITY:

Evaluating the technical feasibility is the trickiest part of a feasibility study. This is because, at this point in time, not too many detailed design of the system, making it difficult to access issues like performance, costs on (on account of the kind of technology to be deployed) etc. A number of issues have to be considered while doing a technical

analysis.

i) Understand the different technologies involved in the proposed system:

Before commencing the project, we have to be very clear about what are the technologies that are to be required for the development of the new system.

ii) Find out whether the organization currently possesses the required technologies:

Is the required technology available with the organization?

If so is the capacity sufficient?

For instance

Will the current printer be able to handle the new reports and forms required for the new system?

OPERATIONAL FEASIBILITY:

Proposed projects are beneficial only if they can be turned into information systems that will meet the organizations operating requirements. Simply stated, this test of feasibility asks if the system will work when it is developed and installed. Are there major barriers to Implementation? Here are questions that will help test the operational feasibility of a project:

Is there sufficient support for the project from management from users? If the current system is well liked and used to the extent that persons will not be able to see reasons for change, there may be resistance.

Are the current business methods acceptable to the user? If they are not, Users may welcome a change that will bring about a more operational and useful systems.

Have the user been involved in the planning and development of the project?

Early involvement reduces the chances of resistance to the system and in

General and increases the likelihood of successful project.

Since the proposed system was to help reduce the hardships encountered. In the existing manual system, the new system was considered to be operational feasible.

ECONOMIC FEASIBILITY:

Economic feasibility attempts 2 weigh the costs of developing and implementing a new system, against the benefits that would accrue from having the new system in place. This feasibility study gives the top management the economic justification for the new system.

A simple economic analysis which gives the actual comparison of costs and benefits are much more meaningful in this case. In addition, this proves to be a useful point of reference to compare actual costs as the project progresses. There could be various types of intangible benefits on account of automation. These could include increased customer satisfaction, improvement in product quality better decision making timeliness of information, expediting activities, improved accuracy of operations, better documentation and record keeping, faster retrieval of information, better employee morale.

SYSTEM REQUIREMENT SPECIFICATION

INTRODUCTION:

The E-Transactions are an Online Transactions that performed using Internet Rupeyaa Card (IRC) to make the payments while purchasing over the Internet.IRC is a prepaid card purchased as prepaid denominations through Credit cards or Saving Accounts.

IRC is a Secure and Universal payment card. Due to the misuse of Credit cards, many online users are reluctant to use that facility. The e-Rupeyaa card provides the users with a secure payment structure without any misuse of their amount.

The security is maintained by providing the Customers with their individual Personal Identification Number(PIN).Definitely using IRC is more secure than using the Credit card.

These concepts helps us to understand the System at Initial stage i.e., at Introduction Area. Introduction is an actual comment about the entire System. Introduction will categorized in to some parts, that are Purpose, Scope, Definitions, Acronyms, Abbreviations and Overview.

PURPOSE:

The E-Transactions are invented by Prima Impact Informatics Solutions & Pvt. Ltd .Impact is acting as Impact Service Provider (ISP) which manages the entire processes by providing relevant services.

The E-Transactions is actually implemented by 8 Clients and these clients are deal with their different Products. The Clients are related with Multi Level Marketing (MLM) Systems.

The E-Transactions are Online Transactions that performed using Internet Rupeyaa Card (IRC) to make payments while purchasing the goods over the Internet. IRC is a Secure and Universal payment card. There are more chances to occur the misuse of Credit card numbers. Due to these reason many Online users are hesitate to that facility.

The IRC provides the users with a secure payment without any misuse of their amount. The security is maintained by providing the Customers with their Individual PIN Number. Internet Rupeyaa Card is so far better and secure than using the Credit Card.

DEFINITIONS:

System has some terms and their definitions as follows,

DISTRIBUTOR:

Distributor is the Customer who utilize the System and who purchases the product

from the clients.

Each Distributor has his own unique Identification Number and Password.

CLIENT:

Client is the Supplier who has Products that are available to Distributors.

Client should also have his own Identification Number and Password. Each Client has his own Products and as well as its own Distributors.

ISP:

ISP is an acronym for Impact Service Providers. ISP manages all the services and processes that involved in the System. ISP maintains database of both Client and Distributor separately.

ISP has complete idea about what are the Products under Particular Client and their list of Distributors.

IRC:

IRC is an acronym for Internet Rupeyaa Card. The IRC is issued to Customer And he purchases Products through IRC over Internet. IRC is a prepaid card that

Contain some amount which Customer can spend to purchase the goods.

MLM:

MLM stand for Multi Level Marketing. MLM is a process of marketing the Products by maintaining the levels. The Distributors in each level have their own goals. If they are succeeding in reach goals, will forward to the next level.

ACRONYMS and ABBREVIATIONS :

Abbreviations and Acronyms are the short forms of regularly used words. Abbreviations and Acronyms are used for our convenience. In our System we are using several short forms instead of complete Description. They are,

ABBREVIATION DESCRIPTION

ISP Impact Service Providers

IRC Internet Rupeyaa Card

MLM Multi Level Marketing

IMC Impact Master Card

IEC Impact Execute Card

ISC Impact Silver Card

IGC Impact Golden Card

ID Identification Name

PIN Personal Index Number

Automated Processes:A process which is executed by the System automatically, when a process is completed with the interaction of human actor. That is the human actor will interact with the system in order perform some task. When the task is completed, thee ISP will update the database automatically.

In our System following are the Automated Processes,

i. Creating Distributor Information

ii. Issuing the Card Number and PIN

iii. Posting order details to Clients

iv. Transaction History

v. Reporting details for Clients, Distributors and ISP.

Distributors Registration and Verification

i. Client Registration and Verification

ii. Applying for the Cards

iii. Shopping Cart

iv. Products Creation and Updating

v. Clearances for Order

vi. Renewals

vii. Editing Clients and Distributors Personal Information

viii. Change Password facilities to Clients and Distributors

Non-automated Processes:

A process which is completely executed by the human actor is called a Non-automated Process. When a process is taken place with the interaction of human actor, if any modifications required to the System, they are also handled by the human actor. In the Non-automated there is no process which the machine has to perform automatically in response to the human actors interaction.

In our System we are using following Non-automated processes,

1. TRANSPORTATION.

2. P/L A/C

3. BALANCE SHEET PREPARATION.

OVERVIEW :

Overview gives an idea about the entire System and how it performs among the Terminators. Each Terminator has its own function and is related to other Terminator. Overview views on how Actors are interacting with System and how System responses for those actions.The entire System consist three External entities, they are

Distributors

Clients

ISP (Impact Service Providers)

The actual process runs among these three entities. Both Client and Distributor must register individually their identity in the System through ISP. ISP provides a unique Id and Password to them separately.

ISP maintains separate databases for Distributors and as well as for the Clients. Client database consist its particular list of Products. And ISP maintains the list of Distributors and for which Client they belong to.

Each Client has their own list of Distributors and such Distributors only eligible to purchase that Client Products. Client also maintains the database of its Distributors list. Distributor need to submit his Id and Password while purchasing the goods.

ISP is the Administrator for the System, manages complete processes among the entities. ISP administrates the actions that are performed among external entities i.e., Clients and Distributors interactions.

OVERALL DESCRIPTION:

In this phase it specifies what are the main modules and sub modules available in the system i.e., E-Transactions. It also provides details about each process, external entities and business rules.

Product Perspectives:

ISP provides most secured and efficient system called e-Transactions which handles the transactions of MLM distributors and clients. ISP gets a middleware between a distributor and client. The e-Transaction system provided by ISP has various modules and sub-modules and we are going to list all those modules in this case.

The e-Transaction system developed by ISP has five Main Modules. They are

Registration

Apply for Cards/Debit Card

Shopping Cart

Transactions

Clearance

Sub Modules of e-Transaction Systems main modules are listed as,

Distributor Registration

Client Registration

Payment for Card Selection

Issue Card Number and Id

Shopping Cart

Posting Order

Production Creation

Accounts

Renewals

Change Id & Password for Distributor & Client

Editing Personal Information of Client & DistributorProduct Function:

In this case user is trying to give complete description about each of the modules available in the system.

Registration:

To get the most benefits and use E-Transaction system developed by ISP it is mandatory for distributor and client to get register them selves with ISP.

The sub-modules are distributor and client registration.

ISP maintains the database of clients and distributors. So whenever a distributor registers him to ISP it will check for validity of distributors with client and then allots him the logon validation i.e.; ID and PASSWORD.

Apply for Card:

Distributor gets ID and PASSWORD by ISP by making successfully login validation. Distributor can view a window consists of following things such as product list, client list, cards, apply for cards.

When a user clicks cards option we get to see four types of IRCs Provided by ISP through which distributor purchases products of client.

Classification of cards is based on amount limitation and time laps such as

Impact Master Card-Rs.2000

Impact Executive Card-Rs.4000

Impact Silver Card-Rs.6000

Impact Gold Card-Rs-8000

The Sub modules in this process are payment mode and getting pin and cards number of IRC for a distributor.

A distributor can own any card specified by up for this he has to make payment through DD and A/C Transfer only And Credit Card based payments are not allowed in this system because it lack security any one can get Card No and misuse for their needs.

Another sub module in this case is getting Pin and Card No for distributors IRC. A distributor receives Pin and Card No as a report send by ISP with these thing he can make purchases of client products and also perform other activities such as renewals.

ISP maintains the database of both client and distributor. It also maintains account database as when a product is purchased by distributor the amount is reflected cash in flow A/C and product derived to distributor as out flow A/C.

Transaction: -

Distributor transaction such as buying products, cards, applying for cards and making renewals all these transactions are handled by ISP and every transaction performed should be reflected n their respective databases.

Clients transactions such as replacing products, adding product to client product list and other transaction should be reflected n their respective databases. Accuracy of data can be achieved by making note correctly of each and every transaction and these roles played by ISP as he makes note of all the accounts of distributor and client.

User Characteristics:

In this case we will discuss about the external entities who uses the services of system called E-Transactions.

The external entities will interact with the system they are

Distributors.

Clients.

ISP Administrator.Distributors:

A distributor makes registration with ISP to use the E-Transaction system and ISP checks whether the distributor is a valid person or not. If a valid distributor that is he/she is distributor of any client who gets registered with ISP it will provide distributor an ID and Password for logon purpose.

Once he makes successful logon the distributor can view menu and after applying for card and after making payment through DD or A/c transfer he will get a PIN & CARD NO through which he can buy or purchase client product. A distributor can edit his personal information.

Clients:

A client provides all the products for distributors. A client registers to ISP, which makes the whole process of purchasing client product more sophisticated and secured one.

Client maintains its distributors list and when client registers to ISP it will provide

ISP about its distributors, products list and also updating to its product list and a client edit his personal information.

Impact service provider: ISP introduces most secured way of purchasing client products for a distributor of MLM by a special way of issuing IRC. ISP overwrites the concept of credit card system as these are not more secured payment system the PIN can be stolen and can be misused by others.

ISP acts as a middleware, it handles the database s of client and distributors will not be charging any amount from the client it will only charge from distributor as it provides more services to distributor by giving acknowledgements.

Each and every transaction done by client and distributor will be done via ISP and ISP maintains up to date database of client and distributor each and every change made by ISP will also reflect to databases which ISP handles i.e. client and distributor databases.

General Constraints

Preconditions:

Distributor must be member of any to get registered with ISP.

Valid distributor should login to buy cards.

Payment mode should be DD (or) A/c transfer.

After getting PIN & IRCNO only he can own a product.

Business Rules: ISP will only charge from distributors not from clients.

Payment for card selection is through DD and Account to Account transfer.

Cards are categorized on the basis of amount and time lapse.

Renewals are made when amount or time lapse is finished.

Post Conditions:

After placing an order in shopping cart we need to enter again PIN and card no to own the product.

Check box option for product confirmation is must in shopping cart.External Specification Requirements.

User Interface Requirements:

The User Interface created for the proposed system is easy to understand and simple to use. Below screens show how the system will appear to the user.

User Interface:

JSP

SERVLETS

XML

XSL

XSLT

HTMLList of forms used:

Login form

Distributor registration form

Apply for cards form

Payment mode

Re-login form

Renewal form

Change password form

Client registration form

TCP/IP (Transmission Control Protocol/Internet Protocol) is the network

Protocol used on the Internet. TCP/IP allows reasonably efficient and error

free transmission between different systems. Because it is a File Transfer

Protocol, it can send large amount of information across networks with

Great assurance is that the data will arrive uncorrupted.

Layered Technology: -

FUNCTIONAL DESCRIPTION:

Impact service provider (ISP) is like a middleware service, which operates through Internet Rupeyaa card (IRC), which is drastically different to the conventional credit card system. Internet Rupeyaa card is a prepaid debit card service provided by our system.

Impact service provider provides healthy &communicative environment between client and distributors. It maintains detailed and up-to-date information about the clients & distributors.

Impact service provider provides the registration for the distributors by interactive environment by taking one time Registration costs. ISP provides detailed information about the distributors information. ISP also provides detailed and update information about other clients information.

This system provides detailed information about the product such as Product ID, description, Qty & unit price for the product. It also lists the total products list offered by the client. The information stored about client is stored in the database.

Impact service provider provides the detailed information about the clients to the distributors. Impact service provider provides the Registration facility and for that provides the unique ID and password which is distinguishable with others. The registration of distributors is stored in the Registration database. The Registration database is changing according to the situation i.e. according to arrival of new distributors.

Whenever a distributor wants to buy the products, the Impact service provider provides the list of clients & information about the products offered by the clients such as product identifier, product name, Qty, payment mode etc. ISP provides prepaid debt card in 4 forms1) Impact master prepaid card.

2) Impact executive play prepaid card.

3) Impact SILVER prepaid card.

4) Impact gold prepaid card.

ISP also allows doing the transaction through Demand Draft (DD) or account to account transferring. If it is account-to-account transfer, them the distributor provided by type information such as the distribution is such as a\c no, Branch, place, and etc. if it is DD, then the distributor is provided by IPE information such as DD no, date, bank, and branch office.

The IPC also provides facilities like renewal of Registration whenever the time is expired. The IPE also provides the Balance information whenever the distribution requires. It also provides free Access to the web.

The Administrative/ISP used interactive, update information about the client, distribution by using database.

PROCESS FLOW

Architecture Diagram

DATA FLOW DIAGRAMSDATA FLOW DIAGRAMS:

There are three types of DFDs they are

1. Context Level DFD

2. Top Level DFD and

3. Context Level DFD:

In the Context Level the whole system is shown as a single process.

No data stores are shown.

Inputs to the overall system are shown together with data sources (as External entities).

Outputs from the overall system are shown together with their destinations (as External entities).

Context Level DFD:

The Top Level DFD gives the overview of the whole system identifying the major system processes and data flow. This level focuses on the single process that

are drawn in the context diagram by Zooming in on its contents and illustrates what

it does in more detail.

TOP LEVEL DFD:

E-R DIAGRAM

E-R DIAGRAM

System Flowcharts:

System Flowcharts:

SHAPE \* MERGEFORMAT

USE CASE DIAGRAMSUSE CASE DIAGRAMS:

These are used to explain the behavior of actors and use cases which are used in our System.

These diagrams consist of:

Use cases

Actors

A use case is the specification of sequences of actions, including variant sequences and error sequences, which a system, subsystem or a class can perform by interacting with outside actors.

An actor may be any thing that interact with the system, human, hardware device or another system etc.

Use case ID:

001

Article I. Use Case Name:Article II. Registration and Verification of Distributor

Version

1.0

Source:Impact

Date:01-03-09

Summary:

This Use case takes the details of distributor and verifies whether these

details are correct or not. If yes then registers it and issues ID and

Password Otherwise discards.

Priority:

High priority.

Preconditions:

Already the distributor must be registered with the client.

Actors:

Distributor, Administrator.

Basic course

of events

`

Actor Interactions: Distributors visits the IRC website. Request for registration. Enters personal details.

System Response: Asks for service type. Asks the distributor to enter

the details. Verifies Distributor details with respect to clients database.

Issues ID and Password.

Conclusion:

Getting registered with IRC.

Post Conditions:

Ready to interact.

Business Rules:

The actor must be a distributor of any of the IRCs clients.

Use case ID:

002

Article III. Use Case Name:

Article IV. Registration and Verification of Client details

Version

1.0

Source:

Impact

Date:01-03-09

Summary:

This Use case takes the details of Client and registers with

IRC then IRC issues ID and Password to the client

Priority:

High priority.

Preconditions:

Trigger:

Actors:

Client, Administrator.

Basic course

of events: `

Actor Interactions: Client visits the IRC website. Request for registration. Enters personal details.System Response: Asks for service type. Asks the Client to enter the details. Verifies client details. Issues ID and Password.

Alternative Paths:

Conclusion:


Post Conditions:

Ready to interact.

Business Rules:

The actor must be a distributor of any of the IRCs clients.

Assumptions:

Author: NNV001

Remarks:

Use case ID:

003

Article V. Use Case Name:

Article VI. Creating Distributors Information.

Version

1.0

Source:

Impact

Date:01-03-09

Summary:

This Use case gathers the information of distributors while registration and stores this information in a database.

Priority:

High priority.

Preconditions:

Trigger:

Actors:

Distributor, Administrator.

Basic course

of events:

Actor Interactions: Client visits the IRC website. Request for registration. Enters personal details.

System Response: Asks for service type. Requests the client to enter the personal details and the list of distributors. Issues ID and Password.

Alternative Paths:

Conclusion:


Post Conditions:

Ready to interact.

Business Rules:

The Client must provide the distributors list to IRC.

Assumptions:

Author: NNV

Remarks:

Use Case ID: 004Use Case Name: Applying for cards

Version: 1.01Date:01-03-09

Source:Impact

Summary:

To be a member of the ISP we need to select the card from the card type list and we

have to apply for that card by paying a specified amount. After the payment we will

be provide with the Card No and Pin through which distributor can buy the

products.

Preconditions:

Priority:High

Trigger:After applying for card ,distributor get the Card No and PIN.

Actors:Distributor, ISP.

Basic Course

of Events:

Actors Interactions System Response

1. Distributor visits ISP. 1. Ask for ID and Password .

2. Actor submits ID and Password. 2.Accepts the details and displays the

cards list.

3.Select the type of the card and apply

for it. 3. Accepts the application and provides

the Card No and PIN.

Alternative

Paths:If distributor wants to change his Password and Id he can consult with the ISP.

Conclusion:

After applying for card distributor should be provided with the Card No and

Pin which is unique.

Post conditions:

Distributor should delete the Card No and PIN to avoid the misuse of these

by other members

Business Rules:

1.Distributor should be the member of the any ISP client.

2. Distributor should be provided with the unique ID, Password, Card No and

Pin.

Assumptions:Distributor is responsible for any misuse of the Card No and Pin by others.

Author:NNA

Remarks:

Use Case ID: 005

Use Case Name: Payment for Card Selecting

Version: 1.01

Date:02-03-09

Source:IMPACT

Summary:

After submitting the application form by the distributor, ISP provides

details of the payment mode for a particular selected card. There

are two types of payment mode. They are 1. Type DD(Demand Draft)

and 2. Account Transfer.

Preconditions:

Priority:High

Trigger:


Basic Course

of Events:


1. Distributor visits ISP. 1. Ask for ID and Password.

2. Actor submits ID and Password. 2.Accepts the details and displays

the cards list.

3.Select the type of the card and apply

For it. 3.System gives the details

of the Payment type for the selected

card

Alternative Paths: Distributor can pay the amount by selecting the payment mode as

Account transfer.

Conclusion:After applying for card distributor has to pay the amount for that card .

Post conditions:Distributor has to select the any of the payment mode

Business Rules:

Assumptions:

Author: NNV

Remarks:

Use Case ID: 009

Use Case Name: Shopping Cart


Summary:

Shopping Cart is the site where the list of the products is given and distributor has to select the product and click the button Add Cart i.e., whenever the new product is selected it is added to the order list. And distributor has to mention the quantity of the product.

Preconditions:

Priority:High

Trigger:


Basic Course

of Events:


1.Distributor visits the ISP by 1. Gives the list of the products.

giving his Id and Password.

2. Select the products and add to

the cart.

Alternative Paths:

Conclusion:

Distributor has to select the products from the products lists and add the

products to the cart.

Post conditions:

1. Distributor has to select the products from the list given by the ISP.

2. Distributor has to select the products in such a way that the payment amount should be minimum 500 it should not be less than this amount.

Business Rules:

1.whenever distributor visit the ISP, he should give his ID and

Password.

2.He has to select the product from the list given by the ISP.

Assumptions:

Author:

Remarks:

Use Case ID: 007Use Case Name: Issuing the Card No and Pin


Source: Impact

Summary:

After applying for card, ISP provides the payment mode to the distributor and after the payment distributor is provided with his own Card No and Pin through which he is identified as the member of the ISP.

Preconditions:

Priority:High

Trigger:

Actors :Distributor, ISP.

Basic Course

of Events:


1. Distributor visits ISP . 1. Ask for ID and Password .

2. Actor submits ID and Password. 2.verifies and accepts the details

3. He pays the amount for the card. 3.Issue the Card No and Pin.

Alternative Paths:If distributor wants to change his card.

Conclusion:Distributor should be provided with the Card No and Pin which is unique.

Post conditions:

Distributor should delete the Card No and PIN to avoid the misuse of

these by other members

Business Rules:

1.Distributor should be the member of the any ISP client.

2. Distributor should be provided with the unique ID, Password, Card

No and Pin.

Assumptions:

Distributor is responsible for any misuse of the Card No and Pin

by others.

Author: NNV

Remarks:

Use Case ID: 008 Use Case Name: Reporting

Version: 1.01 Date:02-03-09

Source:

Summary:

ISP is responsible for giving the details of accounting balance to their clients as well as to their distributors.

Preconditions:

ISP has to check the card limit balance and should inform the distributor before

the limit balance has finished.

Priority:High

Trigger:

Actors:Distributor, ISP, client.

Basic Course

of Events:


Alternative Paths:

Conclusion:

After receiving the payment for the order ISP has to provide a

statement to their clients and distributors.

Post conditions:

Business Rules:

Assumptions:

Author: NNV

Remarks:

Business Rules:

The Client must provide the distributors list to IRC.

Assumptions:

Author: NNV

Remarks:

Use Case ID: 009 Use Case Name: Clearance for Order

Version: 1.01 Date:09-03-09Source: IMPACT

Summary: After the selection of the products distributor has to place an order to those products.

Preconditions: Verifies

Priority: High

Trigger:

Actors: Distributor, ISP.

Basic Course of Events:


1. The Distributor places an order. 1. System needs to verify the stock details.

2. The Distributor need to pay. 2. System updates the payment details.

3. Waits for the acknowledgement. 3. System Clears the Order.

Alternative Paths: Distributor needs to wait for the system to update the stock.

Conclusion: The System Clears the order transaction.

Post conditions: Distributor will get the products delivered.

Business Rules: Only stock details have to be verified by the System.

Assumptions:

Author:

Remarks:

Use Case ID: 010 Use Case Name: Renewals


Summary: By issuing a Card No and Pin to the distributor, he will be the member of the ISP. ISP provides a facility to distributors to renewal the card by paying the amount to it before the card limit is finished.

Preconditions:

Priority: High

Trigger:

Actors: Distributor, ISP.



1. Distributor has to apply for card 1. System issues the card to him.

2. He has to check the balance of the card. 2. Gives the details of the card limit.

3. He has to renewal the card 3. Gives the facility of renewal of the card

Alternative Paths:

Conclusion: Distributor is responsible for the card renewal.

Post condition:

Business Rules: The Card must be validated by the ISP.

Assumptions:

Author:

Remarks:

Use Case ID: 011 Use Case Name: Editing Customer Clients Personal

Information.


Summary: This use case provides a facility, which enables the client or the distributor to edit their personal information.

Preconditions:

Priority: Low.

Trigger:

Actors: Distributor, Clients



1. Actor requests for changing their personal details 1.System asks the actor to enter the new details.

2. Actor requests the IRC to update the new details. 2. IRC takes this details and gives an

Acknowledgement for updating.

Alternative Paths:

Conclusion: Updating the personal info database with the new details provided by the client/Distributor

Post conditions:

Business Rules: 1.Distributor should be the member of the any ISP client.

2. Distributor should be provided with the unique ID, Password, Card No and Pin.

Assumptions:

Author: SSA

Remarks:

SYSTEM FLOW:

PERFORMANCE REQUIREMENTS:

This part of the SRS specifies the performance constraints on the software system, specifying the requirements relating to the performance characteristics of the system.

Two types of performance requirements: -

1. Static Requirements

2. Dynamic Requirements

Static requirements are those that do not impose constraint on the execution characteristics of the system. These include requirements like the number of terminals to be supported, the number of simultaneous users to be supported, and the number of files that the system has to process and their sizes.

Dynamic requirements are which specify constraints on the execution behavior of the system. These typically include response time and throughput constraints on the system. Response time is the expected time for the completion of an operation under specified circumstances. Throughput is the expected number of operations that can be performed at a time.

Security Requirements :-

Specify any requirements regarding security or privacy issues surrounding use of the product or protection of the data used or created by the product. Define any user identity authentication requirements. Refer to any external policies or regulations containing security issues that affect the product. Define any security or privacy certifications that must be satisfied.

Under the E-Transaction project the security is required for both the Distributors and Clients. These security issues such as hiding distributor information from another distributor and other clients in the system and other issues has to be completely provided by the E-Transaction system (ISP). One such solution is by providing the IDs and Passwords to them. As the newly distributor wants to join the system, he/she has to register with the ISP, while registering with the system the distributor information is collected and that is verified with the clients data base.

If the distributor information is successfully validated then only he/she will gets registered with the system and gets an ID and Password with the ISP. This ID and Password provides a means of security to the distributors.

The same is true for the Clients, the above process also applicable to clients and hence they also can get security.

Encryption is another means of security. Since all the transactions with respect to distributors and clients are done online using the Internet, there is a huge Risk of information may be stolen, information can be your card number or any your password. E-Transaction system uses the concept of Debit cards instead of credit cards, therefore while purchasing over the Internet the distributors can pay the amount even from their savings account or bank account. So when distributors uses the internet to pay using their banks account they require much security to be provided, this can be done using encryption. When they enter their account number or PIN those are send using the cryptographic techniques. Since it is hard to detect and know the encrypted data than the normal text, and only the authorized user can decrypt the data.

Reliability Requirements:- Specifies persistence data storage. As moving or forwarding the information is important then storing that data efficiently is also very important. Depending upon the type of the database management system (DBMS) being used different reliability issues are provided.

In E-Transaction system, the DBMS being used is the Oracle 8I and it provides complete reliable data storage. Data such as distributor name or client name, their addresses, card number, pin number, and so on, when accepted in registration must be stored efficiently in database so that later time it can be retrieved efficiently as well.

Reliability can be defined as the probability that an item will continue to perform its intended function without failure for a specified period of time under stated conditions. This means that the E-Transaction should continue to work in any conditions, no failures should occur, suppose while doing the transaction the distributor sends his card number and the specified amount is detected from his account and transferred in the ISP then suddenly if there is a crash, may be hardware or software, in that situation there should not be a loss to the distributor. That is without buying the product the amount should not be detected from the system and if the amount is detected and before continuing further the crashes occurred then this information must be known to the ISP so later the ISP can fulfill the required task.

Scalability: - The E-Transaction system should be totally dynamic in nature, means if at dynamic time the changes takes place it should be effected at dynamic time only. Scalability refers to extending the existing features. This feature is important and has to be thinking in advance because it can be created later after the system is developed. Application scalability requires a balanced partnership between two distinct domains, software and hardware.

In the E-Transaction system if initially n number of clients/distributors are registered and connected with them then more distributors/clients must allow to registered with the system, like that there should not be limit in the number of clients or number of distributors that can be connected to the system.

The system can also be extended with respect to the hardware. If presently one data base server if connected to the E-Transaction system then the system should allow the second data base (or multiple data base servers) to be connected/added. This is known as Hardware scalability.

From the clients point of view in the E-Transaction system, initially they can registered with some number of products (say n), then later if the clients want to add new products to the system, they should allow to do so. Here also there should not be any number of product restrictions.

Accuracy of Data :-

The information stored of the distributors and clients must be accurately and correctly stored and maintained in the database.

Data accuracy becomes an issue, especially when important decisions are being made based on database results. The system has stored lots of information regarding their distributors and clients, and all the transaction is carried out according to this information only, that is, if the distributor is having the balance less than that of the price of the product then he/she should not be allowed to buy the product. This balance information is stored and should be efficiently. Say by some other means if this information is altered or was stored wrongly, then the distributors account is wrong.

To support this, lots of Reports are created and one of them is the Balance report, in which if the distributor requests the sales record, then according to it the balance report will be sending to them which consists of the dates of purchases, amounts paid and other information.

The distributor owns the IRC card and using which they pay to buy some product. As soon as they pay and if they have balance then immediately the successful transaction should be taken care and at that time only that many rupees has to be detected from the account and the new values has to be stored in the database.

Article VII. Safety: IRC is safe and secure

IRC provide the users with safe payment structure without any misuse of other amount

The IRC is safe enough to see that only authorized persons must able to access it

Privacy:

Privacy is important issue in E-transaction data transfer between customer and administrator over the Internet is in encrypted form and due to miss use of the credit numbers many online users can use that facility

Portability:

IRC is portable and easily moveable convenient for carrying small in size and come in your packet wherever you go you can purchase the products and pay using this card

Modify and extensibility:

We can modify and our IRC any other requirement in addition modify to planed software feature. Such as we can add international money card features customer can pay in international currency such as dollars also we can add and remove the clients from our system

SYSTEM ANALYSIS

REQUIREMENT COLLECTION

Data collection represents how the client requirement information is retrieved. This will lead to the proposed system i.e. how far the current problems in the application are overcome. To know the client requirement there are mainly 4 fact-finding techniques are used. They are frequently asked questions observation. QUESTIONNAIRES

Questionnaire method allows the collection of information from the different groups and users and from some experienced persons. The use of standardized question format can yield more reliable data than other fact-finding techniques and the wide distribution ensures greater anonymity for respondents, which can lead to more honest responses. Thus this method can be used in this project to gather information about the process of the project

SOFTWARE DEVELOPMENT METHODOLOGY

The methodology used to develop this project is object-oriented methodology is based on function and procedures. It can be said as the development of software by building self-contained modules as objects that can be easily replaced, modified and reused. In this environment software is a collection of discrete objects that encapsulate their data as well as the functionality to model real world objects. Each object has attribute and methods. Objects are grouped into classes. Here each object is responsible for itself.

This environment emphasizes its cooperative philosophy by allocating tasks among the objects of the applications. Instead of writing a lot of code we can create a lot of code we can create a lot of helps to take in an active role.

Object oriented methodology involves mainly

1. Analysis

2. Design

3. Prototyping and testing.

REQUIREMENT ANALYSIS:

There are 5 important steps in the analysis. They are

1. Identification of the users/actors.

2. Development a simple business process model.

3. Developing the use cases.

4. Developing the interaction diagrams.

5. Classifications.

SOFTWARE METHDOLOGY:

Using JACOBSON METHDOLOGIES we can develop the proposed system.

INTRODUCTION:

In 1986 BOOCH developed the Object Oriented Design concept is called as BOOTCH METHOD. It covers both analysis and Design phases of the Object Oriented System, The BOOTCH METHOD consists o following diagrams:

Class diagrams

Object diagrams

State transition diagram

Module diagram

Process diagram

Interaction diagram

OBJECT ORIENTED SOFTEWARE ENGINEERING

Object oriented software engineering also called, as the objectory. It is build around several models:

USE CASE MODEL: The use-case model defines the outside (actor) and inside (use case) of the systems behavior.

DOMAIN OBJECT MODEL: The objects of the real world are mapped in to the main object model.

ANALYSS OBJECT MODEL: The analysis object model presents how the source code (implementation) is carried out and written.

IMPLIMENTATON MODEL: The implementation model represents the implementation of the system.

TEST MODEL: The test model constitutes the test plan, specification and reports.

JACOBSON METHDOLOGY consists of following diagrams:

Use case Diagrams

UML activity diagram

UML use Case Diagram

Sequence diagrams

Class diagrams

Business class diagrams

USE CASE DIAGRAMS:

A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse An actor is a person, organization, or external system that plays a role in one or more interactions with your system.

UML ACTIVITY DIAGRAM:

Activity diagrams are used to document workflows in a system, from the business level down to the operational level. When looking at an Activity diagram, you'll notice elements from state diagram, the Activity diagram is a variation of the state diagram where the "states" represent operations, and the transitions represent the activities that happen when the operation is complete. The general purpose of Activity diagrams is to focus on flows driven by internal processing vs. external events.

SEQUENCE DIAGRAMS:

UML sequence diagrams model the flow of logic within your system in a visual manner, enabling you both to document and validate your logic, and are commonly used for both analysis and design purposes. Sequence diagrams are the most popular UML artifacts for dynamic modeling, which focuses on identifying the behavior within your system.

CLASS DIAGRAMS:

A class diagram describes the static structure of the symbols in your new system. It is a graphic presentation of the static view that shows a collection of declarative (static) model elements, such as classes, types, and their contents and relationships. Classes are arranged in hierarchies sharing common structure and behavior, and are associated with other classes

SYSTEM ENVIRONMENT

SYSTEM DESIGN

INTRODUCTION

The main focus of the analysis phase of Software development is on What needs to be done. The objects discovered during the analysis can serve as the framework or Design. The classs attributes, methods and association identified during analysis must be designed for implementation language. New classes must be introduced to store intermediate results during the program execution.

Emphasis shifts from the application domain o implementation and computer such as user interfaces or view layer and access layer. During analysis, we look at the physical entities or business objects in the system, that is, which players and how they cooperate to do the work of the application. These objects represent tangible elements of the business.

During the Design phase, we elevate the model into logical entities, some of which might relate more to he computer domain as people or employees. Here his goal is to design the classes that we need to implement the system the difference is that, at this level we focus on the view and access classes, such as how to maintain information or the best way o interact with a user or present information.

Design process:

During the design phase the classes identified in object-oriented analysis Must be evisited with a shift focus to their implementation. New classes or attribute and Methods must be an added for implementation purposes and user interfaces.The object-oriented design process consists of the following activities:

1. Apply design axioms to design classes, their attributes, methods, associations, structure

and protocols Refine and complete the static UML class diagram by adding details to the UML diagram. This step consists of following activities. *Refine attributes *Design methods and protocols by utilizing a UML activity diagram to represent the methods algorithms.

*Refine associations between classes

*Refine class hierarchy and design with inheritance

*Iterate and refine again

2. Design the access layer

Create mirror classes: For every business class identified and created. For

example, if there are three business classes, create three access layer classes.

Identify access layer class relationships.

Simplify classes and their relationships: The main goal here is to eliminate

redundant classes and structures.

*Redundant classes: Do not keep two classes that perform similar translate results

activities. Simply select one and eliminate the other.

*Method classes: Revisit the classes that consist of only one or two methods to see if they

can be eliminated or combined with existing classes.

Iterate and refine again.

3. Design the view layer classes

Design the macro level user interface, identifying view layer objects.

Design the micro level user interface, which includes these activities:

* Design the view layer objects by applying the design axioms and corollaries.

* Built a prototype of the view layer interface.

i. Test usability and user satisfaction

ii. Iterate and refine.

4. Iterate refine the whole design process.

From the class diagram, you can begin to extrapolate which classes you will have to

built and which existing classes you can reuse. As you do this, also begin this, also

begin thinking about the inheritance structure. If you have several classes that seem

relates but have specific differences.

Design also must be traceable across requirements, analysis, design from the

Requirements model.

operations of the class. Where as the private visibility indicates that the accessibility can be given only to the operations of the class only.

Type expression is a language dependent specification of the implementation type of an attribute. Initial value is a language dependent expression for the initial value is optional.

SEQUENCE DIAGRAM & COLLBOATION DIAGRAM

SEQUENCE DIAGRAM & COLLBOATION DIAGRAM

DISTRIBUTOR REGISTRATION:

CLIENT REGISTRATION

LOGON

LOGON Collaboration Diagram :

APPLY FOR CARDS

APPLY FOR CARDS COLLABORATION:

PRODUCTS

Products

SHOPPING CART

SHOPPING CART:

TRANSACTION DETAILS

TRANSACTION DETAILS

CLASS DIAGRAM

Activity Diagrams

Activity Diagrams:

It is a flowchart, showing flow of control from activity to activity. It is used to model the dynamic accepts of system. It also models the flow of an object as it moves from state to state at different points in the flow of control. It may stand alone to visualize, specify, construct, and document the dynamics of society of objects, or they may be used to model the flow of control.

Source : :Distributor Registration

& Login Use Case Diagram Use Case ID :ISPUC001

Activity ID :ISPA001Activity Diagram :Distributor Registration

& Login

Activity Flows :

1. The Distributor login to the system.

2. Distributor furnish his details and the tie-ups he has with the one of the clients and applies for registration

3. The Administrator will authenticates and validate the distributor

by comparing the information the distributor provided and

the information that ISP has regarding clients.

4. Based on the result the administrator registers the client and

confirms as valid distributor and allows to utilize the system..

Source : :Client Registration

& Login Use Case DiagramUse Case ID :ISPUC002

Activity ID : ISPA002Activity Diagram :Client Registration

& Login

Activity Flows :

1. The Client login to the system.

2. Client provides his information and applies for registration.

3. The Administrator authenticates and validates the client

by comparing the information he(client) provided and the

information the ISP has about client.4. Based on the verification result the administrator registers the

client and confirms as valid distributor and allows to utilize the

system.

Source :Apply for IRCUse Case ID :ISPUC004

Activity ID : ISPA004Activity Diagram :Apply for IRC

Activity Flow :

1. The distributor login to the system by entering login id and password.

2. The administrator validates the login id and password and displays the information about the IRC.

3. Now the distributor can select the IRC which he prefers by going thru IRC information.

4. Then the distributor can apply for the IRC by clicking on the button (Apply for the IRC) in the form.

Source : Issuing the IRC Use Case DiagramUse Case ID :ISPUC05

Activity ID : ISPA05Activity Diagram : Issuing the IRC

Activity Flow :

1. Distributor logins to the system.

2. IRC information is displayed as he clicks the IRC information button in the form displayed after login.

3. The distributor can select the IRC ,apply for that IRC and can purchase it if required by paying money thru D.D or A/c transfer into ISP account.

4. The Administrator verifies whether money paid by the distributor has transferred into ISP account.

5. If the money is transferred into ISP A/c then IRC is allotted to the

distributor else the distributor is informed about the failure.

. 6. The Administrator issues the IRC no, PIN thru mail or post

to the distributor.

Source :IRC Renewal Use Case DiagramUse Case ID :ISPUC09

Activity ID : ISPA09Activity Diagram : IRC Renewal

Activity Flow :

1. The distributor login to the system .

2. Distributor can check his card status by simply clicking on card status button.

3. The card status displayed i.e. card expiry and card balance.

4. If the distributor want to go for renewal he has to deposit amount into the ISPs A/c.

5. If the amount is transferred into the ISPs A/c the card is renewed.

Source :Posting Shopping Details to Client

Use Case Diagram.Use Case ID :ISPUC08

Activity ID : ISPA08Activity Diagram : Posting Shopping Details to Client

Activity Flow :

1. The distributor places the order to the administrator.

2. The order details are furnished to the administrator i.e. products selected and quantity.

3. The Administrator approves the transaction after its verification .

4. The complete details of the transaction are furnished to the client by the Administrator.

Data DictionaryDATA BASE DESIGN

INTRODUCTION

A database model is a collection of logical constructs used to represent the data in data structures and data relationships with in the database. Basically, the database models may be grouped into two categories: conceptual model and implementation models. The conceptual model focuses on the logical nature of that data presentation. Therefore the conceptual model is concerned with what is representing in the database and the implementation model is concerned with how it is represented.

1. Conceptual Model:

The conceptual model represents data present in the entities as well the relations present is the entities. All the strong entities and weak entities are identified here and it mainly focuses on the logical nature of that data presentation.

2. General Access Model:

General access model is used to convert the ER model into the relation model. Here we can identify the references to the other entities and the nature of the each attribute. But, A network models record can have more then one parent.

3. Relation Model:

The relational model is represented as tables. The columns of each table are attributes that define the data or value domain for entities in that column. The rows of each table are tuples representing individual data objects being stored. A relational table should have only one primary key. A primary key is a combination of one or more attributes whose value unambiguously locates each row in the table.

DATA DICTIONARY

Entities

tc \l 1 "2. 'Entities' section"

tc \l 2 "Entity Table"Entity

NameDefinitionLogical Only

ACCOUNT_DETAILSNo

ADDRESSNo

Bonus_pointsNo

ClearenceNo

CUSTOMERNo

DD_DETAILSNo

DistributorListNo

IRC_CARDNo

IRC_USER_CARD_DETAILSNo

ISP_AccountsNo

ITEMNo

LOGINNo

MANUFACTURERNo

PAYEMENTNo

PAYEMENT_MASTERNo

RENWALNo

TRANSACTIONNo

TRANSACTIONDETAILSNo

tc \l 2 "Attribute(s) of \"ACCOUNT_DETAILS\" Entity"Attribute(s) of "ACCOUNT_DETAILS" Entity

NameDefinitionIs PKIs FKRequired

A_IDYesNoYes

ACC_NONoNoNo

ACC_TYPENoNoNo

ACC_BANKNoNoNo

P_IDNoYesNo

Account_NoNoYesNo

tc \l 2 "Attribute(s) of \"Bonus_points\" Entity"Attribute(s) of "Bonus_points" Entity


Sl_noYesNoYes

CARD_IDNoYesNo

PointsNoNoNo

AmountNoNoNo

tc \l 2 "Attribute(s) of \"Clearence\" Entity"Attribute(s) of "Clearence" Entity


cl_noYesNoYes

TRANS_DETAIL_NONoYesNo

c_dateNoNoNo

StatusNoNoNo

tc \l 2 "Attribute(s) of \"CUSTOMER\" Entity"Attribute(s) of "CUSTOMER" Entity


DIST_IDYesNoYes

DIST_FIRSTNAMENoNoNo

DIST_LASTNAMENoNoNo

DIST_ADD1NoNoNo

DIST_ADD2NoNoNo

DIST_CITYNoNoNo

DIST_STATENoNoNo

DIST_CUNTRYCODENoNoNo

DIST_ZIPNoNoNo

DIST_PH1NoNoNo

DIST_PH2NoNoNo

DIST_FAX1NoNoNo

DIST_FAX2NoNoNo

DIST_DOBNoNoNo

DIST_OCCUPATIONNoNoNo

DIST_MAILIDNoNoNo

DIST_WEBSITENoNoNo

Client_IDNoYesNo

tc \l 2 "Attribute(s) of \"DD_DETAILS\" Entity"Attribute(s) of "DD_DETAILS" Entity


D_IDYesNoYes

DD_NONoNoNo

DD_BANKNoNoNo

DD_BRANCHNoNoNo

DD_DATENoNoNo

P_IDNoYesNo

tc \l 2 "Attribute(s) of \"DistributorList\" Entity"Attribute(s) of "DistributorList" Entity


sl_noYesNoYes

Client_IDNoYesNo

check_idNoNoNo

dist_nameNoNoNo

tc \l 2 "Attribute(s) of \"IRC_CARD\" Entity"Attribute(s) of "IRC_CARD" Entity


CARD_IDYesNoYes

CARD_NAMENoNoNo

CARD_DESCRIPTIONNoNoNo

CARD_LIMITNoNoNo

tc \l 2 "Attribute(s) of \"IRC_USER_CARD_DETAILS\" Entity"Attribute(s) of "IRC_USER_CARD_DETAILS" Entity


IRC_CARDNOYesNoYes

IRC_ISSUE_DATENoNoNo

IRC_EXPIRY_DATENoNoNo

IRC_CARD_PINNoNoNo

BALANCENoNoNo

CARD_IDNoYesNo

DIST_IDNoYesNo

TRANS_AMTNoNoNo

BonusPointsNoNoNo

tc \l 2 "Attribute(s) of \"ISP_Accounts\" Entity"Attribute(s) of "ISP_Accounts" Entity


Account_NoYesNoYes

BankNoNoNo

TypeNoNoNo

BranchNoNoNo

PlaceNoNoNo

tc \l 2 "Attribute(s) of \"ITEM\" Entity"Attribute(s) of "ITEM" Entity


ITEM_IDYesNoYes

ITEM_DESCNoNoNo

ITEM_PRICENoNoNo

ITEM_QTYNoNoNo

ITEM_CATEGORYNoNoNo

ITEM_IMAGEURLNoNoNo

Client_IDNoYesNo

ITEM_DELIVERYTIMENoNoNo

tc \l 2 "Attribute(s) of \"LOGIN\" Entity"Attribute(s) of "LOGIN" Entity


IDNoNoYes

PASSWORDNoNoNo

STATUSNoNoNo

tc \l 2 "Attribute(s) of \"MANUFACTURER\" Entity"Attribute(s) of "MANUFACTURER" Entity


Client_IDYesNoYes

Client_NAMENoNoNo

Client_ADD1NoNoNo

Client_CITYNoNoNo

Client_COUNTRYCODENoNoNo

Client_SATENoNoNo

Client_ADD2NoNoNo

Client_PH1NoNoNo

Client_PH2NoNoNo

Client_MOBILENONoNoNo

Client_EMAILIDNoNoNo

Client_WEBSITENoNoNo

Client_DOBNoNoNo

Client_ACCOUNTNONoNoNo

Client_ACCTYPENoNoNo

Client_BANKNoNoNo

Client_EXPNoNoNo

client_statusNoNoNo

tc \l 2 "Attribute(s) of \"PAYEMENT\" Entity"Attribute(s) of "PAYEMENT" Entity


PAY_IDYesNoYes

PAY_AMOUNTNoNoNo

PAY_DATENoNoNo

DIST_IDNoYesNo

Client_IDNoYesNo

TRANS_IDNoYesNo

tc \l 2 "Attribute(s) of \"PAYEMENT_MASTER\" Entity"Attribute(s) of "PAYEMENT_MASTER" Entity


P_IDYesNoYes

P_TYPENoNoNo

P_AMOUNTNoNoNo

P_DATENoNoNo

CARD_IDNoNoNo

DIST_IDNoYesNo

DescNoNoNo

tc \l 2 "Attribute(s) of \"RENWAL\" Entity"Attribute(s) of "RENWAL" Entity


SL_NOYesNoYes

IRC_CARDNONoYesNo

RENEWALDATENoNoNo

DIST_IDNoYesNo

AMOUNTNoNoNo

P_IDNoYesNo

tc \l 2 "Attribute(s) of \"TRANSACTION\" Entity"Attribute(s) of "TRANSACTION" Entity


TRANS_IDYesNoYes

TRANS_DATENoNoNo

TRANS_AMOUNTNoNoNo

DIST_IDNoYesNo

tc \l 2 "Attribute(s) of \"TRANSACTIONDETAILS\" Entity"Attribute(s) of "TRANSACTIONDETAILS" Entity


TRANS_DETAIL_NOYesNoYes

ITEM_IDNoNoNo

ITEM_QTYNoNoNo

ITEM_TOTALNoNoNo

ITEM_DELIVERYDATENoNoNo

Client_IDNoYesNo

TRANS_IDNoYesNo

tc \l 1 "3. 'Attributes' section"

tc \l 2 "Attribute Table"Attribute

NameDefinitionRequiredIs PK

A_IDYesYes

ACC_NONoNo

ACC_TYPENoNo

ACC_BANKNoNo

P_IDNoNo

Account_NoNoNo

D_ADDRESSNoNo

TRANS_DETAIL_NONoNo

DIST_IDYesYes

DIST_FIRSTNAMENoNo

DIST_LASTNAMENoNo

DIST_ADD1NoNo

DIST_ADD2NoNo

DIST_CITYNoNo

DIST_STATENoNo

DIST_CUNTRYCODENoNo

DIST_ZIPNoNo

DIST_PH1NoNo

DIST_PH2NoNo

DIST_FAX1NoNo

DIST_FAX2NoNo

DIST_DOBNoNo

DIST_OCCUPATIONNoNo

DIST_MAILIDNoNo

DIST_WEBSITENoNo

Client_IDNoNo

D_IDYesYes

DD_NONoNo

DD_BANKNoNo

DD_BRANCHNoNo

DD_DATENoNo

P_IDNoNo

CARD_IDYesYes

CARD_NAMENoNo

CARD_DESCRIPTIONNoNo

CARD_LIMITNoNo

IRC_CARDNOYesYes

IRC_ISSUE_DATENoNo

IRC_EXPIRY_DATENoNo

IRC_CARD_PINNoNo

BALANCENoNo

CARD_IDNoNo

DIST_IDNoNo

TRANS_AMTNoNo

BonusPointsNoNo

ITEM_IDYesYes

ITEM_DESCNoNo

ITEM_PRICENoNo

ITEM_QTYNoNo

ITEM_CATEGORYNoNo

ITEM_IMAGEURLNoNo

Client_IDNoNo

ITEM_DELIVERYTIMENoNo

IDYesNo

PASSWORDNoNo

STATUSNoNo

Client_IDYesYes

Client_NAMENoNo

Client_ADD1NoNo

Client_CITYNoNo

Client_COUNTRYCODENoNo

Client_SATENoNo

Client_ADD2NoNo

Client_PH1NoNo

Client_PH2NoNo

Client_MOBILENONoNo

Client_EMAILIDNoNo

Client_WEBSITENoNo

Client_DOBNoNo

Client_ACCOUNTNONoNo

Client_ACCTYPENoNo

Client_BANKNoNo

Client_EXPNoNo

client_statusNoNo

PAY_IDYesYes

PAY_AMOUNTNoNo

PAY_DATENoNo

DIST_IDNoNo

Client_IDNoNo

TRANS_IDNoNo

P_IDYesYes

P_TYPENoNo

P_AMOUNTNoNo

P_DATENoNo

CARD_IDNoNo

DIST_IDNoNo

DescNoNo

SL_NOYesYes

IRC_CARDNONoNo

RENEWALDATENoNo

DIST_IDNoNo

AMOUNTNoNo

P_IDNoNo

TRANS_IDYesYes

TRANS_DATENoNo

TRANS_AMOUNTNoNo

DIST_IDNoNo

TRANS_DETAIL_NOYesYes

ITEM_IDNoNo

ITEM_QTYNoNo

ITEM_TOTALNoNo

ITEM_DELIVERYDATENoNo

Client_IDNoNo

TRANS_IDNoNo

Account_NoYesYes

BankNoNo

TypeNoNo

BranchNoNo

PlaceNoNo

sl_noYesYes

Client_IDNoNo

check_idNoNo

dist_nameNoNo

Sl_noYesYes

CARD_IDNoNo

PointsNoNo

AmountNoNo

cl_noYesYes

TRANS_DETAIL_NONoNo

TECHNOLOGY DESCRIPTIONHTMLHTML, an initialism of Hypertext Markup Language, is the predominant markup language for web pages. It provides a means to describe the structure of text-based information in a document by denoting certain text as headings, paragraphs, lists, and so on and to supplement that text with interactive forms, embedded images, and other objects. HTML is written in the form of labels (known as tags), surrounded by angle brackets. HTML can also describe, to some degree, the appearance and semantics of a document, and can include embedded scripting language code which can affect the behavior of web browsers and other HTML processors.

HTML is also often used to refer to content of the MIME type text/html or even more broadly as a generic term for HTML whether in its XML-descended form (such as XHTML 1.0 and later) or its form descended directly from SGML

Hyper Text Markup Language

Hypertext Markup Language (HTML), the languages of the World Wide Web (WWW), allows users to produces Web pages that include text, graphics and pointer to other Web pages (Hyperlinks).

HTML is not a programming language but it is an application of ISO Standard 8879, SGML (Standard Generalized Markup Language), but specialized to hypertext and adapted to the Web. The idea behind Hypertext is that instead of reading text in rigid linear structure, we can easily jump from one point to another point. We can navigate through the information based on our interest and preference. A markup language is simply a series of elements, each delimited with special characters that define how text or other items enclosed within the elements should be displayed. Hyperlinks are underlined or emphasized works that load to other documents or some portions of the same document.

HTML can be used to display any type of document on the host computer, which can be geographically at a different location. It is a versatile language and can be used on any platform or desktop.

HTML provides tags (special codes) to make the document look attractive. HTML tags are not case-sensitive. Using graphics, fonts, different sizes, color, etc., can enhance the presentation of the document. Anything that is not a tag is part of the document itself.

Basic HTML Tags:

specifies comments

.Creates hypertext links

.Formats text as bold

. Formats text in large font.

Contains all tags and text in the HTML document

... Creates text

Definition of a term

...

Creates definition list

Formats text with a particular font

...Encloses a fill-out form

... Defines a particular frame in a set of frames

Creates headings of different levels( 1 6 )

... Contains tags that specify information about a document

...Creates a horizontal rule

Contains all other HTML tags

...Provides meta-information about a document

Contains client-side or server-side script

Creates a table

Indicates table data in a table

Designates a table row

Creates a heading in a table

Attributes

The attributes of an element are name-value pairs, separated by "=", and written within the start label of an element, after the element's name. The value should be enclosed in single or double quotes, although values consisting of certain characters can be left unquoted in HTML (but not XHTML).Leaving attribute values unquoted is considered unsafe.

Most elements take any of several common attributes: id, class, style and title. Most also take language-related attributes: lang and dir.

The id attribute provides a document-wide unique identifier for an element. This can be used by stylesheets to provide presentational properties, by browsers to focus attention on the specific element or by scripts to alter the contents or presentation of an element. The class attribute provides a way of classifying similar elements for presentation purposes. For example, an HTML document (or a set of documents) may use the designation class="notation" to indicate that all elements with this class value are all subordinate to the main text of the document (or documents). Such notation classes of elements might be gathered together and presented as footnotes on a page, rather than appearing in the place where they appear in the source HTML.

An author may use the style non-attributal codes presentational properties to a particular element. It is considered better practice to use an elements son- id page and select the element with a stylesheet, though sometimes this can be too cumbersome for a simple ad hoc application of styled properties. The title is used to attach subtextual explanation to an element. In most browsers this title attribute is displayed as what is often referred to as a tooltip. The generic inline span element can be used to demonstrate these various non-attributes.

The preceding displays as HTML (pointing the cursor at the abbreviation should display the title text in most browsers).

Advantages

A HTML document is small and hence easy to send over the net. It is small because it does not include formatted information.

HTML is platform independent.

HTML tags are not case-sensitive.

JavaScript

JavaScript is a script-based programming language that was developed by Netscape Communication Corporation. JavaScript was originally called Live Script and renamed as JavaScript to indicate its relationship with Java. JavaScript supports the development of both client and server components of Web-based applications. On the client side, it can be used to write programs that are executed by a Web browser within the context of a Web page. On the server side, it can be used to write Web server programs that can process information submitted by a Web browser and then update the browsers display accordingly

Even though JavaScript supports both client and server Web programming, we prefer JavaScript at Client side programming since most of the browsers supports it. JavaScript is almost as easy to learn as HTML, and JavaScript statements can be included in HTML documents by enclosing the statements between a pair of scripting tags

.. .

JavaScript statements

Here are a few things we can do with JavaScript:

Validate the contents of a form and make calculations.

Add scrolling or changing messages to the Browsers status line.

Animate images or rotate images that change when we move the mouse over them.

Detect the browser in use and display different content for different browsers.

Detect installed plug-ins and notify the user if a plug-in is required.

We can do much more with JavaScript, including creating entire application.

JavaScript Vs Java

JavaScript and Java are entirely different languages. A few of the most glaring differences are:

Java applets are generally displayed in a box within the web document; JavaScript can affect any part of the Web document itself.

While JavaScript is best suited to simple applications and adding interactive features to Web pages; Java can be used for incredibly complex applications.

There are many other differences but the important thing to remember is that JavaScript and Java are separate languages. They are both useful for different things; in fact they can be used together to combine their advantages.

Advantages

JavaScript can be used for Sever-side and Client-side scripting.

It is more flexible than VBScript.

JavaScript is the default scripting languages at Client-side since all the browsers supports it.

Java Technology

Initially the language was called as oak but it was renamed as Java in 1995. The primary motivation of this language was the need for a platform-independent (i.e., architecture neutral) language that could be used to create software to be embedded in various consumer electronic devices.

Java is a programmers language.

Java is cohesive and consistent.

Except for those constraints imposed by the Internet environment, Java gives the programmer, full control.

Finally, Java is to Internet programming where C was to system programming.

(i) Importance of Java to the Internet

Java has had a profound effect on the Internet. This is because; Java expands the Universe of objects that can move about freely in Cyberspace. In a network, two categories of objects are transmitted between the Server and the Personal computer. They are: Passive information and Dynamic active programs. The Dynamic, Self-executing programs cause serious problems in the areas of Security and probability. But, Java addresses those concerns and by doing so, has opened the door to an exciting new form of program called the Applet.

(ii) Java can be used to create two types of programs

Applications and Applets: An application is a program that runs on our Computer under the operating system of that computer. It is more or less like one creating using C or C++. Javas ability to create Applets makes it important. An Applet is an application designed to be transmitted over the Internet and executed by a Java compatible web browser. An applet is actually a tiny Java program, dynamically downloaded across the network, just like an image. But the difference is, it is an intelligent program, not just a media file. It can react to the user input and dynamically change.

(iii) Features of Java Security

Every time you that you download a normal program, you are risking a viral infection. Prior to Java, most users did not download executable programs frequently, and those who did scan them for viruses prior to execution. Most users still worried about the possibility of infecting their systems with a virus. In addition, another type of malicious program exists that must be guarded against. This type of program can gather private information, such as credit card numbers, bank account balances, and passwords. Java answers both these concerns by providing a firewall between a network application and your computer.

When you use a Java-compatible Web browser, you can safely download Java applets without fear of virus infection or malicious intent.

(iv) Portability

For programs to be dynamically downloaded to all the various types of platforms connected to the Internet, some means of generating portable executable code is needed .As you will see, the same mechanism that helps ensure security also helps create portability. Indeed, Javas solution to these two problems is both elegant and efficient.

(v) The Byte code

The key that allows the Java to solve the security and portability problems is that the output of Java compiler is Byte code. Byte code is a highly optimized set of instructions designed to be executed by the Java run-time system, which is called the Java Virtual Machine (JVM). That is, in its standard form, the JVM is an interpreter for byte code.

Translating a Java program into byte code helps makes it much easier to run a program in a wide variety of environments. The reason is, once the run-time package exists for a given system, any Java program can run on it.

Although Java was designed for interpretation, there is technically nothing about Java that prevents on-the-fly compilation of byte code into native code. Sun has just completed its Just In Time (JIT) compiler for byte code. When the JIT compiler is a part of JVM, it compiles byte code into executable code in real time, on a piece-by-piece, demand basis. It is not possible to compile an entire Java program into executable code all at once, because Java performs various run-time checks that can be done only at run time. The JIT compiles code, as it is needed, during execution.

(vi) Java Virtual Machine (JVM)

Beyond the language, there is the Java virtual machine. The Java virtual machine is an important element of the Java technology. The virtual machine can be embedded within a web browser or an operating system. Once a piece of Java code is loaded onto a machine, it is verified. As part of the loading process, a class loader is invoked and does byte code verification makes sure that the code thats has been generated by the compiler will not corrupt the machine that its loaded on. Byte code verification takes place at the end of the compilation process to make sure that is all accurate and correct. So byte code verification is integral to the compiling and executing of Java code.

Overall Description

(vii) Picture showing the development process of JAVA Program

Java programming uses to produce byte codes and executes them. The first box indicates that the Java source code is located in a. Java file that is processed with a Java compiler called javac. The Java compiler produces a file called a. class file, which contains the byte code. The .Class file is then loaded across the network or loaded locally on your machine into the execution environment is the Java virtual machine, which interprets and executes the byte code.

(viii) Java Architecture

Java architecture provides a portable, robust, high performing environment for development. Java provides portability by compiling the byte codes for the Java Virtual Machine, which is then interpreted on each platform by the run-time environment. Java is a dynamic system, able to load code when needed from a machine in the same room or across the planet.

(ix) Compilation of c

Document e Transactions

Documents

Transcript of Document e Transactions