Miniprjctreport

Online Bookshop Project Report 2012
INTRODUCTION
Centre Of Computer Science CCSIT,CU
1. INTRODUCTION
As said earlier Online Bookshop is a website that provide book shopping service.This shopping website can market the products of any seller through the internet.The services going to be provided in this website will not be free.The sellers have to make payment to us if they need to market their books in our website.The website will contain a list of books of various sellers.The features and prices of these books are also be given.When a user enters our site he can buy the books that he want by checking the features.After purchasing the books the total amount will be displayed.The purchaser can make his payment and the products will be delivered.There will also be a provision for advertisement.The sellers can add their advertisement by making a payment.And these advertisement are displayed on the advertisement page.The administrator is the controller of this site.And three modules involved are buyer,seller,administrator. .
SYSTEM ANALYSIS
2. SYSTEM ANALYSIS
Centre Of Computer Science CCSIT,CU 3
2.1 INTRODUCTION
A system is an orderly grouping of interdependent components linked together according to a plan to achieve a specific objective. Analysis is a detail study of the various operations performed by a system and their relationships within and outside the system .During analysis, data are collected on the available files decision points and transactions handled by the present system. System analysis is concerned with analyzing, designing, implementing and evaluating information system in our organization. It is carried out to make the system more effective either by modification or by substantial redesign. In system analysis we identify the problem, study the other possible solutions and select the most suitable solution, which will meet the technical, economical and social demands for analysis. Various tools such as dataflow diagrams, interviews, on site observations, questionnaires etc are used. System analysis process is also called life cycle methodology since it relates four significant phases in life cycle of all information system. They are: The Study phase The design phase The development phase The operation phase All the activities associated with each life cycle phase must be performed, managed and documented. So system analysis is the performance, management and documentation of the activities related to the four life cycle phases of a computer based business system.
2.2 IDENTIFICATION OF THE NEED 2.2.1 EXISTING SYSTEM

In the present system of business the customer go to shops to purchase books. This method has several limitations such as1) Wastage of time
2) Has to find the shops which provide books 3) Carry books to home 4) Shops may be in short of books.
In this world of technology computerization in the field of business is an inevitable fact to overcome these problems. This fact is what we aim through this project. The purchaser can purchase the books from his home through his system. This makes life more easier. This is already a realized fact. So also many other shopping websites are now available. Some of the most popular are rediff,ebay, manorama e-mart. So what we intend is to develop a website that include almost all the features of the existing others and at the same time solving the problems that prevail in these portals. So our preliminary task was to identify the problems of these websites. Based on the study of these portals we could identify some problems. They are1) Does not consider the feelings of the customer. What most shopping website do is sell their product, obtain the cash and then afterwards no attention is given on the part of customer. They does not see whether the product is delivered or not. So also sometimes the customer may be urgently in need of a product. In these portals they are no provisions to check the urgency of customer and to provide the item needed in time. 2) Does not consider the feelings of the seller
In most shopping websites the sellers has to make face to face contract with site owners to market their products in these portals. In this busy world, most sellers find it difficult to have a face to face conversation with the site members.
3) No options for already registered sellers to quickly add new products There is no options for an already registered sellers to add new products to the sites quickly. If new products are to be added the seller has to arrange a new meeting with the site members. 4) No options for the customer to reveal his problems Customer may find many problems dealing with our site. There are no options at present to collect their feedbacks, complaints etc. 5) No possibilities for a communication between administrator and companies The communication between the companies and administrator is a must in certain cases like agreement renewal,quantity scarcity etc. Theses provisions are lacking in an existing system.
2.2.2 PROPOSED SYSTEM

Through our project ie, the e-commerce portal we will overcome these problems. So the advantages of this portal are1) Consider the feelings of the customer The customer satisfaction is given primary importance. The customer have the option to mark their urgency ie, the customer has the option to select the number of days with which the product has to be delivered. The customer also have the option to inform the site if the products are not delivered in time.
2) Consider the feelings of companies Our site take into consideration the feelings of companies and saves their precious time. The agreements are signed from the system itself and all they need to do is to enter their details in our site and the products that they wish to sell. The genuineness of the company is checked and the site will not register the company if the details are not valid. 3) Option for already registered companies to add new products The companies which are already in contract with our site can add new products after the payments very easily. All they need to do is to send the details of that product to us. 4) Customer can provide his feedbacks The site considers the feedback of the customer important. The site can improve only from their opinions. The customers can post their complaints if they are dissatisfied with the services of the site. 5)Direct mail service between companies and administrator A direct communication between the admin and companies is made possible through a local mailing system provided in our site. Similar to a global system, messages can be sent between them and communicated within no time.
The advantages and facilities of the existing site are retained; at the same time new facilities are added which will make this e-commerce portal more useful.
2.3 PRELIMINARY INVESTIGATION

The preliminary investigation is an investigation performed to clarify the business information system. After the need of the new system has been identified an initial
investigation is conducted to identify the real problems of the existing system. Information is gathered through interviews and enquiry. We interviewed several persons to know what they expect from an e-commerce portal. Next we made a deep enquiry on the already present e-commerce portals and checked whether they satisfy these needs. Most of the needs are satisfied in the present systems. But they lack several qualities which is already pointed out. The next step was to determine what exactly the new system is to do to solve these problems. The outcome of initial investigation was the alternatives to solve these problems.
2.4 FEASIBILITY STUDY
Feasibility is a test of the proposed system according to workability, impact on the organization ability to meet user needs, and effective use of resources. Following are the feasibility studies employed: Technical Feasibility Operational Feasibility Economic Feasibility
2. 4.1 TECHNICAL FEASIBILITY The system requires a higher configuration computer system, but it is already available at the organization. The Hardware requirements are:

Processor : Core 2 Duo Main memory : 256 MB Monitor : LCD Display Mouse : Microsoft series or compatible
The Software requirements are:

Operating system : Windows XP Front end : C#.NET Technology : ASP.NET Backend : SQL Database
Thus the proposed system is technically feasible. 2.4.2 OPERATIONAL FEASIBILITY The proposed system offers: 1) Greater customer friendliness. 2) Greater understandability. 3) Less restrictions on companies.
4) Simplicity. The operations of this site are absolutely simple. Handling this site does not need much training. So the system is operationally feasible.
2.4.3 ECONOMIC FEASIBILITY There is no need of any initial investment for software or hardware. The e-commerce portal can be considered as a shop which can sell variety of products. In the case of a shop the shopkeeper needs a lot of initial investment. But in the case of an e-commerce portal there is no such investments; making it economically feasible.
2.5 DEVELOPMENT TOOLS

1. LANGUAGE: C#. Net 2. TECHNOLOGY: ASP 3. BACKEND: SQL
11
2.6 PROJECT SCHEDULING

START SLNO PHASES DATE END DATE NO. OF DAYS
STUDY PHASE
18-02-09
23-02-09
6 days
DESIGN PHASE
24-02-09
09-03-09
13 days
DEVELOPMENT PHASE
10-03-09
31-03-09
20 days
TESTING
01-04-09
03-04-09
3 days
IMPLEMENTATION
04-04-09
06-04-09
3 days
12
SYSTEM DESIGN
13
3. SYSTEM DESIGN
3.1 MODULARIZATION DETAILS
Our project The E-commerce Portal is divided into three modules namely1) The Administrator 2) The Purchaser 3) The Company.
1) The Administrator The administrator is the central controller of the operations performed by the website. He has different functions that cater to the overall supervision of the e-commerce website.He can view companies;at the sametime modify or delete their account.Similarly he can view products,modify and delete them. Only admin has the right to delete the account of a company if the details are not true and delete the products of the company in case a problem occurs. Moreover,only after the admin approves the products of a company it will be published on the site for the buyers.The admininistrator has mailbox provisions through which he can communicate with the companies in case of agreement expiry or other problems that may occur.He can also read the feedbacks of the customers and take necessary actions.The admin can also view purchaser details which include the products purchased by a customer on a particular date and thereby the company details of the concerned products. He can see whether the products are delivered to the concerned customers on the requested date. The admin can also read the problems revealed by the customers and take necessary actions. 2) The Purchaser The purchaser is any user who approaches our site with an intention to buy the products marketed by the companies. Every user will be provided with a unique username and password at the time of sign up. For this he need to submit his details into our database. If he is an already registered customer with an existing username and password he can directly sign in. The purchaser has the provision to view the commodities
available in our site before logging in. This saves his time so that he needs not login if the required product is not there. Selected products are put into a shopping cart. The cart implementation helps to deduce the quantity of the purchased product from the database. The quantity purchased will be multiplied by the unit price and added to get the total bill of a customer. The purchaser can select the period within which he needs the product. The product will be sent to the concerned person within that period. These processes will be looked after by the admin. Bill payment is performed through the credit card system Customers can also provide his valuable feedbacks about our site. 3) The Company Different companies can use the site for selling and advertising their products. Companies log on to our site using the username and password given to them. To get the username and password for the first time there are a series of steps that include accepting our agreement, submitting details and so on. Later they can enter the products. An amount has to be paid before company can upload the products to our site. The products are uploaded by company itself. But these will be verified by the admin and can be deleted if they are not worth. The company can also add another set of items acceptable to the site on further payment. Quantity upload is also allowed .The companies can also upload advertisements based on payments. The company also has a provision for mailbox through which the company can directly communicate with the administrator. He can also view their customers.
3.2. DATA FLOW DIAGRAM

3.2.1 HIGH LEVEL

PERFORM OPERATIO NS OF ADMIN
LOGIN ADMIN LOGOUT
DATABAS
LOGIN COMPAN Y LOGOUT
PERFORM OPERATIO NS OF COMPANY
DATABAS
LOGIN PURCHA SER LOGOUT
PERFORM OPERATIO NS OF PURCHAS ER
DATABAS
3.2.2 INTERMEDIATE LEVEL

Online Bookshop Project Report 2012 VIEW COMPAN IES VIEW PRODUC TSOMPA NIES READ CUSTOM ER FEEDBA CKS VIEW UNREGIST ERED PRODUCTS MESSA GE SERVIC ES
CDETAILS
ADMI N
PRODUCT1
FEEDBACKS
PRODUCT1
MAILBOX1
VIEW CUSTOM ERS
PURCHASE_BACK UP
VIEW ADVERTISEM ENTS READ CUSTOM ER PROBLE MS
ADVERTISEMENTS
PROBLEMS
17
Online Bookshop Project Report 2012 ADD PRODUC TS UPDATE PRODUC T QUANTI TY PRODUCT1
COMPA NY
PRODUCT1
ADD ADVERTISEM ENTS MESSA GE SERVIC ES
ADVERTISEM
MAILBOX1
VIEW CUSTOM ERS
PURCHASE
18
Online Bookshop Project Report 2012 SELECT PRODUC TS WRITE PROBLE MS PRODUCT1
PURCHA SER
PROBLEMS
WRITE FEEDBACKS
FEEDBACKS
3.2.3 LOW LEVEL

CDETAIL VIEW COMPA NIES PRODUC Centre Of ADMI Computer Science CCSIT,CU N 19 DELE TE DELE TE EDIT
APPRO VE
Online Bookshop Project Report 2012 VIEW PRODUC TSOMPA NIES FEEDBAC READ CUSTOM ER FEEDBA CKS PRODUC VIEW UNREGIST ERED PRODUCTS MAILBOX MESSA GE SERVIC ES PURCHASE_BAC KUP VIEW CUSTOM ERS ADVERTISEMEN VIEW ADVERTISEM ENTS PROBLEMS READ CUSTOM ER PROBLE MS DELE TE DELE TE DELE TE DELE TE INBO X APPRO VE DELE TE EDIT
EDIT
COMP OSE
20
PRODUC ADD PRODUC TS PRODUC COMPA NY UPDATE PRODUC T QTY
PAYME NT
ADVERTISEM ADD ADVERTISEM ENTS MAILBOX MESSA GE SERVIC ES PURCHASE VIEW CUSTOM ERS PRODUC PURCHA SER SELECT PRODU CTS BUY PAYME NT
PAYME NT INBO X COMP OSE MARK DELIVE RED DELE TE
PROBLEMS WRITE PROBLEMS Centre Of Computer Science CCSIT,CU 21
Online Bookshop Project Report 2012 FEEDBAC WRITE FEEDBAC KS
3.3. FLOW CHART

START
ADMI N?
LOGIN
YES PERFORM
ACTIONS OF ADMIN
NO NO YES PURCHASE R?
CONTIN UE? NO
YES
Centre COMPAN Of Computer Science CCSIT,CU Y?
LOGIN
22

NO LOGOUT
YES LOGIN
PERFORM ACTIONS OF
PERFORM ACTIONS OF
CONTINU E?
YES
NO YES CONTINU E? NO LOGOUT
LOGOUT
STOP
SYMBOLS USED START / STOP PROCESS
DECISION BOX
3.4 DATA BASE DESIGN

A Database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and efficiently. Database design runs in parallel with the application design. As we collect information about what is to be done, we will obviously collect information about what data needs to be entered, stored, message and printed on reports. One of the main tasks in building a new system is determining the contents and structure of the database. The type of retrieval and recording required by the user and availability of inputs determine what data has to be stored. A comprehensive database should contain all the information necessary to manage the enterprise. Database can be implemented directly using file management program or a
database management system. The objectives in establishing a database can be summarized as: Eliminate redundant data as much as possible. Integrate data files. Incorporate changes easily and quickly. Lower the cost of storing and retrieving data. Improve accuracy, integrity and consistency. Data independence. Privacy and security.
The various steps involved in database design are given below: Organizing the data As we gather the data, we will organize it into tables and begin to work out its connections. Our first goal is to identify the tables and the columns within the tables. Identify the keys The next step in database design is to identify the key that is used as a primary key. A primary key is a column, which uniquely identifies a row in a table. Uniqueness is the key property of a primary key, so we have to choose it carefully. Then identify the foreign keys that are used. A foreign key is a row or a column in a table, which acts as a primary key for another table. So after identifying the primary keys and the foreign keys, go to the next step of database design. Normalization Normalization is the process of decomposing the attributes in an application, which results in asset s of tables with very simple structure or in simple words it is a process of simplifying the relationship between the data elements in a file.
24
The goal of a relational database design is to generate a set of relational schemes that allows us to store information without unnecessary redundancy and yet allows us to retrieve information easily. The purpose of normalization is to make tables as simple as possible. The normalization deals with the process of gathering data into relations. The normalizing provides, The data needed to construct the user objects, It is robust enough to allow rows to be inserted, deletes and modified without resulting in anomalies and errors. First normal Form (1NF) Here the tables are analyzed for repeating or redundant data and these are eliminated. Second Normal Form (2NF) To be in second normal form, a table must be in first normal form and no attributes of the table should be functionally dependent on only one part of a concatenated primary key. Third Normal Form (3NF) To be in third normal form, a table must be in 2NF and no attribute of the table should be transitively functionally dependent on the primary key.
The various tables used in our project are:
Advertisement
Approvedcomid
Cagreement
Cdetails
Clogin
Companyname1
Feedbacks
Mailbox1
26
Mailbox2
Problemstable
Product1
27
Pur_login
Pur_amount
Pur_product
28
Online Bookshop Project Report 2012 Purchaser_backup
Purchase
Purchaser
Temp_purchase
29
3.5 USER INTERFACE DESIGN
30
3.5.1 INPUT DESIGN:

The input design is the process of converting the user-oriented inputs into the computer-based format. It also includes determining the record media, method of input, speed of capture and entry into the system. Inaccurate input data are the most common cause of errors in data processing. Errors entered by the data entry operator can be controlled by input design. The goal of designing input data is to make the processing easy and free from errors. Input screen: Home Productview Pur_buy Pur_details Companylogin Agreement Details Product Admin Admin_login_enter
31
3.5.2 OUTPUT DESIGN:

A quality output is the one, which meets the requirements of the end user and present the information clearly. In any system, the results of processing are given to the users through the outputs. In the output design it is determined how the information is to be displayed for the immediate needs. Output design should improve the relationship of the system with the user and help in decision making. The objective of the output design is to define the format of all printed documents and of the screens that will be produced by the system. The output has been designed as per the needs of the institution. The suggestions of the users are also taken into consideration while designing the layouts and the fields that are to be included in the project.
Output screen: cid
32
SYSTEM DEVELOPMENT
33
4. SYSTEM DEVELOPMENT
4.1 PSEUDO CODE
PROCEDURE homepage() BEGIN CASE OF: customer login(); CALL: customer login(); CASE OF : company login(); CALL : company login(); CASE OF : contact us(); CALL : contact us(); CASE OF: about us(); CALL : about us(); END PROCEDURE customer login() BEGIN IF old user INPUT username and password IF username and password valid CALL : productbuy(); ELSE PRINT: Invalid Username or password; ELSE IF new user CALL custsign up(); END
PROCEDURE :
BEGIN
company login()
IF old company INPUT username and password IF username and password valid CALL : companytasks(); ELSE PRINT: Invalid Username or password; ELSE IF new company CALL compsign up(); END PROCEDURE :productbuy() BEGIN SELECT The required products ENTER The required quantity of each product purchased SELECT The number of days within which you need the products CALL creditcard(); SELECT The feedback link if required END PROCEDURE :custsign up() BEGIN
INPUT Customer name INPUT address INPUT phone number INPUT E-mail id INPUT account number IF all details are valid Provide the username and password END PROCEDURE :compsign up() BEGIN INPUT Company name INPUT address INPUT phone number INPUT E-mail id INPUT account number IF all details are valid Provide the username and password END PROCEDURE: companytasks() BEGIN IF new product registration
CALL addproducts(); ELSE IF product quantity updation CALL qty updation(); ELSE IF advertisement registration CALL: addadvertisement() ELSE IF customers details CALL: viewcustomers(); ELSE CALL : mailbox(); END PROCEDURE: creditcard() BEGIN ENTER Your credit card number IF valid RETURN payment receipt END PROCEDURE: addproducts() BEGIN ENTER productname ENTER features ENTER price
ENTER quantity UPLOAD image IF details valid UPLOAD details to the database ELSE PRINT Invalid; END PROCEDURE qty updation() BEGIN INPUT productname INPUT The quantity to be uploaded SUBMIT END PROCEDURE addadvertisement() BEGIN INPUT advertisement text SUBMIT END PROCEDURE viewcustomers() BEGIN IF view customers of the day
SELECT customers of the day link ELSE IF view all customers SELECT all customers link END PROCEDURE mailbox() BEGIN IF view incoming messages SELECT inbox option ELSE IF compose new messages SELECT compose option END PROCEDURE adminlogin() BEGIN INPUT admin username and password IF valid GO TO admintasks(); ELSE PRINT Invalid username and password END PROCEDURE admintasks() BEGIN
IF view companydetails SELECT companydetails link ELSE IF view productdetails SELECT productdetails link ELSE IF read customer feedback SELECT customer feedback link ELSE IF view unregistered products SELECT unregistered products link ELSE IF mailbox SELECT mailbox link ELSE IF view site customers SELECT site customers link ELSE IF advertisement of the site SELECT advertisement link ELSE IF view customer problem SELECT customer problem link END
40
4.2 VALIDATION CHECKS

Validation checks are performed on the following field
Text Field:
The text field can contain only the number of characters lesser than or equal to its size. The text fields are alphanumeric in some tables. Incorrect entry always results in an error message.
Numeric Field:
The numeric field can contain only numbers from 0-9. An entry of any characters flashes an error message. The individual modules are checked for accuracy and what it has to perform. Each module subjected to test run along with the sample data. The individually tested modules are integrated into single system. Testing involves executing the real data information used in the program. The existence of any program defect is inferred from the output. The testing should be planned so that all the requirements are individually tested. In addition validation checks are also implemented for certain formatted entries like the email-id.Any other entry in the mail-id field results in an error message. Also blank entries in all fields are dealt with appropriate error messages.
41
TESTING AND IMPLEMENTATION
5. TESTING AND IMPLEMENTATION

5. 1 TESTING
5.1.1 SYSTEM TESTING
System testing is actually a series of different testing whose primary purpose is to fully exercise the computer based system. Software testing is critical element of software quality assurance and represent the ultimate review of the specification, design and coding. System testing makes a logical assumption that all the part of the system is correct; the goal will be successfully achieved. Testing is the final verification and validation activity within the organization itself. During testing the major activities are concerned on the examinations and modification of the source code. Testing objectives are:
Testing is a process of executing a program with the intend of finding an error. A good test is one that uncovers an as yet undiscovered error.
Unit testing Integration testing System testing Validation testing User acceptance testing
5.1.1.1 UNIT TESTING

Unit testing enables a programmer to detect error in coding. A unit test focuses verification of the smallest unit of software design. This testing was carried out during the coding itself. In this testing step, each module is going to be work satisfactorily as the expected output from the module. Project aspect:
The front-end design consists of various forms. They were tested for data acceptance. Similarly, the back-end also tested for successful acceptance and retrieval of data.
5.1.1.2 INTEGARTION TESTING

Through each program work individually, they should work after linking together. This is referred to as interfacing. Data may be lost across the interface; one module can have adverse effect on the other. Subroutines after linking may not do the desired function expected by the main routine. Integration testing is the systematic technique for constructing the program structure while at the same time conducting test to uncover errors associated with the interface. Using integrated test plan prepared in the design phase of the system development as a guide, the integration test was carried out. All the errors found in the system were corrected for the next testing step. Project aspect: After connecting the back-end and the front-end as whole module, the data entered in the front-end once submitted were successfully entered in the database. On request, data were successfully retrieved in to forms.
5.1.1.3 SYSTEM TESTING

After performing the integration testing, the next step is output testing of the proposed system. No system could be useful if it doesnt produce the required output in a specified format. The output generated are displayed by the system under consideration and then tested by comparing with the format require by the user. Here the output format is considered in to two ways, one in on-screen and other in printed format.
Project aspect:
The entire project was tested and found successful.
5.1.1.4 VALIDATION TESTING

The user has to work with the system and check whether the project meets his needs. In the validation checking, the user works with the beta version of the software. Project aspects: User enters the appropriate data and results was checked and validated
5.1.1.5 USER ACCEPTANCE TESTING

User acceptance of a system is a key factor of the success of any system. The system under consideration was tested for user acceptance by running a prototype of the software. Project aspects: An alpha version is demonstrated to the users. Their suggestions are recorded.
5.1.2 TEST CASE DESIGN METHODS

The primary objectives of test case design methods are to derive a set of test that has of highest likelihood of uncovering the defects. To accomplish this objective, two categories of test case design techniques are used. Black box testing and White box testing.
5.1.2.1 White Box Testing

White box testing is a test case design method that uses the control structure of the procedural design to derive test cases. Using white box testing methods, we can derive test cases that 1 2 3 Guarantee that all independent paths within a module have been exercised at least once Exercise all logical decisions on their true and false sides Execute all loops at their boundaries and within their operational bounds 45
Online Bookshop Project Report 2012 4 Exercise internal data structures to ensure their validity.
5.1.2.2 Black Box Testing

Black box testing methods focus on the functional requirements if the software. That is, black box testing enables us to derive sets of input conditions that will fully exercise all functional requirements of the program. Black box testing attempts to find errors in the following categories: 1. 2. 3. 4. 5. Incorrect or missing functions Interface errors Errors in data structure or external database access Performance errors Initialization and termination errors
46
5.2 IMPLEMENTATION
The implementation phase of the software design consists of different tasks to be done sequentially for obtaining the desired results. Here we do not implement parallel; instead we first implement admin and then the user module. The different phases are:
5.2.1 CREATING A DATABASE

A Database is created, in which all the tables are defined which are required to do the different operations such as storage and retrieval of information. Databases are designed in such a way it can handle the different database queries. User and admin can retrieve required details from the system on clicking on the links and buttons.
5.2.2 CREATING GRAPHICAL USER INTERFACE

Graphical User Interface is created in Visual Studio 2005 Express Edition under .NET framework 2.0 for a user friendly interface. It is intended for two purposes. First is to create a user friendly interface for the software. Having a good user interface makes it easier for the user to use and understand the different functionalities of the software. Secondly, the user interface hides the end users from the complexities in the working of the software. So the user is made unaware of how a task is performed when he chooses to perform it.
5.2.3 CREATING SYSTEM ENVIRONMENT:

For the intended project to work on, we need to implement its required hardware and software requirements. This system is build using Visual Studio 2005 under .NET framework and based on Windows Operating System. Memory and Hard disk should confirm according to hardware requirements mentioned above.
5.2.4 PERFORMING FUNCTIONS

Initially we implement the admin module because the operation made in admin reflects in the user module. After implementing this, we check whether all the operations and reports are up to the specification. Only after ensuring this we go for user module. With the help of a user-friendly visual interface, the end users can perform the desired operations. Upon selecting any operation, the corresponding link commands will be passed to database and the response is also received. The responses are then retrieved and displayed in screen.
48
6. FUTURE SCOPE AND ENHANCEMENT OF PROJECT

In this world of computerization this project has high scope. The nearby future will be an era of e-commerce portals. As people are getting more busy day by day there is no enough time for them to go out shopping. So they will buy things through the easiest paths like e-commerce portals. Normally in e-commerce portals the companies has to sign a face to face contract with site owners to sell their products in the site. This is difficult for companies as they are highly busy people. But in our site there is no such formalities. The registration of products is through site itself. Hence the future scope of our project is very high.
49
7. CONCLUSION
We are glad to say that we were successful in implementing all the features we intended in this e-commerce portal. Although we could not implement the exact credit card system by accessing the gateway of banks we could implement the concept behind that. So in overall we can proudly say that it was a successful project.
50
8. BIBLIOGRAPHY
1) http://www.rediff.com 2) http://www.ebay.com 3) Elements of SystemAnalysis - Marvin Gore & John Stubbe 4) Data Base System Concepts- Abraham Silberschatz, Henry F Korth, S Sudarshan
51
SCREEN SHOTS
52

Miniprjctreport

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Miniprjctreport

Caricato da

Copyright:

Formati disponibili

Online Bookshop Project Report 2012

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

Online Bookshop Project Report 2012

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

2.2 IDENTIFICATION OF THE NEED 2.2.1 EXISTING SYSTEM

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

2.2.2 PROPOSED SYSTEM

Online Bookshop Project Report 2012

Online Bookshop Project Report 2012

2.3 PRELIMINARY INVESTIGATION

Online Bookshop Project Report 2012

2.4 FEASIBILITY STUDY

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

The Software requirements are:

Online Bookshop Project Report 2012

2.5 DEVELOPMENT TOOLS

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

2.6 PROJECT SCHEDULING

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

Online Bookshop Project Report 2012

3.2. DATA FLOW DIAGRAM

Online Bookshop Project Report 2012

3.2.1 HIGH LEVEL

LOGIN ADMIN LOGOUT

LOGIN COMPAN Y LOGOUT

PERFORM OPERATIO NS OF COMPANY

LOGIN PURCHA SER LOGOUT

PERFORM OPERATIO NS OF PURCHAS ER

3.2.2 INTERMEDIATE LEVEL

VIEW CUSTOM ERS

VIEW ADVERTISEM ENTS READ CUSTOM ER PROBLE MS

Centre Of Computer Science CCSIT,CU

ADD ADVERTISEM ENTS MESSA GE SERVIC ES

VIEW CUSTOM ERS

Centre Of Computer Science CCSIT,CU

3.2.3 LOW LEVEL

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

PRODUC ADD PRODUC TS PRODUC COMPA NY UPDATE PRODUC T QTY

PAYME NT INBO X COMP OSE MARK DELIVE RED DELE TE

PROBLEMS WRITE PROBLEMS Centre Of Computer Science CCSIT,CU 21

Online Bookshop Project Report 2012 FEEDBAC WRITE FEEDBAC KS

3.3. FLOW CHART

Centre COMPAN Of Computer Science CCSIT,CU Y?

Online Bookshop Project Report 2012

NO YES CONTINU E? NO LOGOUT

SYMBOLS USED START / STOP PROCESS

3.4 DATA BASE DESIGN

Online Bookshop Project Report 2012

Centre Of Computer Science CCSIT,CU

Online Bookshop Project Report 2012

Online Bookshop Project Report 2012