mobile document1

8/2/2019 Mobile Document1

1/39

THIS REPORT IS SUBMITED AS PROJECT IN PARTIAL

FULFILMENT OF THE ACADEMIC CURRICULUM OF GRADUATE IN

COMPUTER SCIENCE & APPLCATION

2010-2011

Developed at JAY SHREE CHAMUNDA MOBILE VIJAPUR

***INTERNAL GUIDE***

MR.JAYDEEP TRIVEDI

MR .SUNIL THHAKAR

***SUBIMITTED TO***

MERCHANT COLLEGE OF MANAGEMENT

STUDIES&RESERCH

VISNAGAR-384315

***AFFILIATED TO***

HEM . NORTH GUJARAT UNIVERSITY, PATAN,

***SUBMITTED BY***

BAROT SAROJ.V. [EXAM NO: ]

KANDOI ROSHANI.J. [EXAM NO: ]

1 | Page


2/39

1. PREFACE.............

2.

ACKNOWLEGEMENT..............................

3. DRAWBACK OF EXISTING

SYSTEM...........

4. TOOLS AND

TECHNOLOGY..............................................

4.1- HARDWARE REQUIREMENT

4.2- SOFTWARE REQUIREMENT

5. SYSTEM DESIGN............................................................

5.1 - DATA FLOW DIAGRAM

5.2 - E-R DIAGRAM

5.3 - HIERARCHY DIAGRAM

5.4 - DATA DICTIONARY

5.5- TABLE LAYOUT

6. OUTPUT DESIGN.......................................................

6.1 - FORM LAYOUT

2 | Page


3/39

6.2- REPORT LAYOUT

7. BIBLOGRAPHY..............................................................

TO WHOM IT MAY CONCERN

This is to Certificate that Miss Barot Saroj v.&

kandoi roshani j.of B.C.A of Merchant Institute of

Post Bechelar of Computer Application, Visnagar

has completed the project report of Mobile Shop

Management System as an integral of theircurriculum project is successfully completed & up

to mark during the project at our Visat mobile

Stores, Vijapur.They taken interest in the related

field of their student.

The duration of project was 1-jan-2011 to 25-

feb-2011. We give them all the best for theirfuture with regards.

Signature:-

3 | Page


4/39

Computer is an inherent part of the lifebody.virtually,in every walk of life.aperson in expected to be able to usecomputers.The impact of computertechnology in several aspect of accoutingprofession and practice has beenpronounced over the last two decades in

India. Now,We are in hyper technology era.there

are several revolution in any field.Wehave got more and more machine supportin any kind of work in the world.In themedical science.We have more efficientequipments available having all more

facility.so,computerization becomes apainful factor behind this technology.AndWe can do any work faster, and timeconsumed all this process become veryless than ancient era.

We are doing a

project named ONLINE MOBILE SHOP.

4 | Page


5/39

The project has maintained All typesabout the admission process.

5 | Page

First Of All, We are Thankful to Hemchandracharya NorthGujarat University for Giving Me Opportunity to develop The

system. Secondly we are Thankful to MERCHANT COLLEGE OF

MANAGEMENT STUDIES &RESEARCH, VISNAGAR to Provide the

Excellent Environment to Me for Develop the Project.

We are Also Greatly Thankful to gs JAY SHREE CHAMUNDA

MOBILESHOP for Giving Chance to Develop the Project in Their

Organization.

We Express My Deep Sense of Gratitude towards

OurGuides,PROF. Mr. JAYDEEP SIR, Mr. SUNILSIR For Their Precious

Guidance Encourages Me To Developing The Project In The

Right Way. We are Also Thankful toMr.jagdishbhai barotOwner of and And Their Staff to Co-operate Us at the Time of

Information Gathering for System Development.

MISS BAROT SAROJ V.

MISS KANDOI ROSHANI J.


6/39

6 | Page

Project Title : Online Mobile Shop

Project Objective : Create a Web application to be used in place of old

paper based user mobile purchase process.

ASP.NET and SQL Server technology to create strong

and secured database connectivity.

Runtime package and deployment instructions are

given.

Developed for : Jay Shree Chamunda Mobile Shop

Hardware Configuration : Intel Pentium Dual-Core, 1 GB, 128 GB Hard Disk

Front End : Microsoft Visual Studio 2008

Back End : Microsoft SQL server 2005

Technology : .NET 3.5

Operating System : Windows XP or later

Developed by : Barot Saroj v.

Kandoi Roshani j.


7/39

INTRODUCTION:Online Mobile Shop system is built on Asp.net and SQL

Server 2005. The web application is built to serve the following

areas.

-To make the mobile search process is fast, reliable and error

free.

- Hosting on the Internet can provide a secured channel forpurchase the mobile.

- Real time report generation gives quick results of given order of

mobile by User.

-User can also purchase the mobile by online payment facility.

7 | Page


8/39

SCOPE:

Online Mobile Shop System is designed for search, purchasevarious companies mobile. The system handles all the operations

and generates reports as soon as the order is given by the

Customer which saves the precious time of Customer as well as

company. The existing system is weak when we want to purchase

mobile instantly. We can also search for the new arrival mobile

models.

Study & weakness of Current System

Weaknesses in Current System

The current system is as mentioned earlier very complicated and

expensive as compared to the new system. It also wastes the precious time

of the customer.

In current system customer must go to the Mobile Store and then only

purchase the mobile.

In current system customer see only limited companys mobile as well

as limited models of mobile.

In current system customer cant see the new arrivals of mobile in the

market.

8 | Page


9/39

Requirements of the new system

User Requirements

The user requirements for the new system are to make the system fast,

flexible, less prone to errors and reduce expenses and save time.

- Time can be saved in purchasing mobile at a time.

- Systems that can automate update new arrivals of the mobile

in the market.

- An admin can generate the report according to the order of

the customer.

- The new system should be more secure in managing user

records and reliable enough to be used in any condition.

- Finally, it should prove cost effective and easy as compared to

the current system.

9 | Page


10/39

3.1 INTRODUCTION TO .NET TECHNOLOGY3.1.1. What is .NET Framework?

Applaid .net frame work programing.

10 | Page


11/39

If you use the .NET Framework, your code targets the common

language runtime (CLR), which affects your decision about a programming

language. The common language runtime is just what its name says it is: A

runtime that is usable by different and varied programming languages.

The features of the CLR are available to any and all programming

languages that target it-period. If the runtime uses exceptions to report

errors, then all languages get errors reported via exceptions. If the runtime

allows you to create a thread, then any language can create a thread. In

11 | Page

Basic Compiler

Managed module

(IL and Metadata)

Basic souece Code File(s)


12/39

fact, at runtime, the CLR has no idea which programming language the

developer used for the source code. You may develop your code in any

programming language you desire as long as the compiler you use to

compile your code targets the CLR. Microsoft is creating several language

compilers that target the runtime: C++ with managed extensions, C#

(pronounced C sharp), Visual Basic.NET, JScript, Java, and an

intermediate language (IL) Assembler. In addition to Microsoft, there are

several other companies creating compilers that produce code that targets

the CLR. At this writing, I am aware of compilers for Alice, APL, COBOL,

Component Pascal.

As per our requirement we have also used some AJAX tools and

AJAX extensions.

12 | Page


13/39

3.1.2 What is AJAX?

AJAX web applications, made famous by GMail and Google Maps,

seem to be the flavour of the month in some circles. Using a combination

of HTML/XHTML, XML, CSS, DOM scripting via JavaScript, and

XMLHttpRequest (for exchanging data with a server asynchronously),

AJAX allows you to do many interactive things with your website,

making it appear almost like a native application running on your

system. Incidentally, in case you were wondering, AJAX is an acronym

for "Asynchronous JavaScript and XML".

13 | Page


14/39

4.1 What is system analysis?

The collection of notations, methodologies & tools used to gather details

&analyse a problem situation prior to information system design &

implementation is called system analysis.

Record inspections:

In this method analyst examines information that has been recorded

earlier about system & users. It can be applied at the beginning or

end as required.

Observations:

Observation allows analyst to gain information they cant by any other

fact finding technique. Experienced observers know what to look for &

how to access the significance of what they observed.There are distinct

approaches to the development of computer information system.

Here described is the method called as SDLC(System Development Life

Cycle).

4.2 SDLC(System Development Life Cycle)

Itconsists of following 6 activities:-

1. Preliminary Investigation :

This activity has three parts:

1) Request clarification

It deals with clarity of requests from users.

14 | Page


15/39

2) feasibility study:

Feasibility study is a stage in the system development life cycle

following the information phase. In this phase, it is decided

whether it is worth automating/computerizing the problem. The

information collection that occurs during preliminary

investigation examines system feasibility, and find out whether

system will be beneficial to the organization or not.

Technical feasibility:

The following factors suffice for considering the given

project as

Technically Feasible.

1. The system developed in .net technology which is well

known and today we can easily get the technical help of .net

technology from the internet.

2. The system development in .net technology is specified by

client.

Operation Feasibility:

The following factors suffice for considering the given projectas operational Feasible.

1. Sufficient support from the user.

2. Acceptance from the user side for active involvement and

interest in project

15 | Page


16/39

Economic feasibility :

The following factors suffice for considering the given project

as Economically Feasible.

1. The system does require investment which provided by client.

2. The system will perform according to client requirement and

Economical will not much expensive.

Implementation Feasibility:

This system is developed using Visual Studio .NET 2008 asfront end and MySQL as back end. The softwares are

available in the development company.

3) Request approval:

It deals with selection of feasible projects among various

projects.

2. Determination of system requirements:

Detailed understanding of all important facts of business area under

investigation.

3. Design of System:

The design of system consists of logical & physical types of designs.

The design that produces the details stating how a system will meet the

requirements identified during system analysis. This stage is referred as

logical design. The process of developing application is referred as physical

design.

16 | Page


17/39

4. Development of software

This part refers to the coding of the system.

5. System testing

The system is used experimentally to ensure that the application does

not fails.It should run according to its specifications & in the way users

expect.

6. Implementation & Evaluation:

Implementation is the process that checks the system & put it into use.

Evaluation is performed to identify its strength & weaknesses. Dimensions

in which evaluation may occur are:

1) Operation Evaluation

2) Organizational Impact

3) User management assessment

4) Development performance

17 | Page


18/39

5.1 SYSTEM FLOWCHART

A flowchart is a diagrammatic representation that illustrates

the sequence of operations to be performed to arrive at a

particular solution.

NOTATIONS:

There are several notations available for use in flowcharting.

Some used in the described system are listed below:

18 | Page


19/39

Start or end of program

Computational steps

Decision making & Branching

19 | Page


20/39

5.1.1 Flow Chart:

Start

Login

Updatemobile

company

Update

mobile

info

Update

mobilefeature

Searchmobile

Generate repor t

Chek

order info

Seach

mobileinfo

Purchase m obile

En d

Ad m in C us to m er

ye

s

order

20 | Page


21/39

5.2:E-R DIAGRAM:-

After carefully analysing the requirements and functionality of the

webapplication, We had two important diagrams by the end of the analysis

phase for documentation.They are the ER diagram and data flow diagram

which were the basis for finding out entities and relationships between

them,the flow of information

feature

Feture_id feture description

Companymaster

Company_name

Company_id

hashas

Model_master

Modelfeature

has

Model_idModel feature

Model name

Company_id

Model_id

has

Clientorder

Order date

E-mail

Creditcardstate

sale

Address

phonename

city

21 | Page


22/39

5.3:Data Flow Diagram

A Data-Flow Diagram (DFD) is a graphical representation of the

flowof data through an information system. A data-flow diagram can

also be used for the visualization of data processing. DFD is also a virtually

designable diagram that technically or diagrammatically describes the

inflow and outflow of data or information that is provided by externalentity.

DFD levels

Context(Zero) level diagram

First level diagram

Second level diagram

5.3.1 Context Level Diagram:

22 | Page


23/39

Client

Online mobile

shop

Client_order

Request/Search

Send request/Search

Fetch detail

Confirm/Results

5.3.2 1st level Data flow Diagram for Admin

23 | Page


24/39

User_table

1.0

Log inAdminUsername,password

response

2.0Mobile

information

3.0Mobile

feature

4.0Order

information

5.0

Reports

Addmobileinfo

Addmobilefeature

Checkorderinfo

Generatesreports

Updatemobileinfo

Retrieveinfo

Updatemobilefeature

Retrieveinfo

Checkorderinfo

Giveresponse

Model_master Model_master Client_order Report

Confirm re

sponse

Checkreport

Displayinfo

24 | Page


25/39

5.3.3 1st level Data flow Diagram for client

Client

Confirm

username,password

Reply

User_table

2.0

Search

mobile

3.0

Select

product

3.0

order

Searchmobile

Select product/mobile Give order

Model_master Product Payment

Storemobileinfo R

etrievedata

Storeproductmobile

Retri

eveinfo

Storepaym

entinfo

R

eply

4.0

Payment

Client_order

Give payment

Storeord

erinfo

Retriev

einfo

25 | Page


26/39

5.4:Data Dictionary:

1. Table Name:-Company_masterDescription:- It stores the company id and name .

Field name Data type Description Constraints

Company_ id Int Id of company Primary key

Company_name Varchar(50) Name of company Allow null

2. Table Name:-AdminDescription:-.It stores the admin id, username and password.


Id Int Id of Admin Primary key

User name Varchar(20) Admin login name Not null

Password Varchar(20) Password belongs

to admin

Not null

3. Table Name:-model_masterDescription:- It stores the details of models or mobiles.


Model_id Int Id of mobile Primary key

Company _id Int Id of company Foreign key from

company_master

Model_name Varchar(50) Name of model Allow null

26 | Page


27/39

MRP Numeric(18,0) Retail price of

mobile

Allow null

Sale Numeric(18,0) Less price from the

MRP

Allow null

Discount Numeric(18,0) Provide discount Allow null

Image name Varchar(100) Name of image Allow null

Imagepath Varchar(500) Path of image Allow null

Description Varchar(200) Description of

model

Allow null

4. Table Name:-Client_orderDescription:-It stores order details.


Order _id int Id of order Primary key

First name Varchar(15) First name Not null

Middle name Varchar(15) Middle name Not null

Last name Varchar(15) Last name Not null

Address1 Varchar(20) Address of client Not null

Address2 Varchar(20) Address of client Not null

City Varchar(15) Name of city Not null

State Varchar(15) Name of state Not null

Country Varchar(15) Name of country Not null

Email Varchar(20) Email of client Allow null

Mobile no Int Mobile number of

the client

Allow null

Phone no Int Phone number of Allow null

27 | Page


28/39

client

Credit card no. Int Credit card no. of

the client

Not null

Mobile_ id Int Id of mobile Foreign key of model_master

MRP Numeric Retail price of

mobile

Not null

Discount Numeric Provide discount Not null

Sale Numeric Less price from

MRP

Not null

Order date Datetime Date of order Not null

5. Table Name:-Product_masterDescription:-It stores the information of product.


Product _id Int Id of product Primary key

Product name Varchar(15) Name of product Allow null

Price Float Price of product Allow null

Product company

name

Varchar(20) Company name of

product

Allow null

Color Varchar(10) Color of mobile Allow null

Photo Varchar(20) Photo of mobile Allow null

Feature Varchar(25) Feature of mobile Allow null


mobile

Allow null

28 | Page


29/39

6. Table Name:-Model_featureDescription:-It stores the information about feature of model.


Model feature_id Int Id of model feature Primary key

Model_id Int Id of model Foreign key of

model_master

Feature_id Int Id of feature Foreign key from

feature


mobile

Allow null

7. Table Name:-FeatureDescription:-It stores the info of feature of model accordingly client

requirements.


Feature_id Int Id of feature Primary key

Feature Varchar(50) Feature of mobile Not null


mobile

Not null

8. Table Name:-User_table

Description:-It stores the username and password of client.


Id Int Id of client Primary key

User name Varchar(20) User login name Not null

Password Varchar(20) Password belongs

to client

Not null

29 | Page


30/39

9. Table Name:-Payment

Description:-It stores the information about payment.


Product_id Int Id of product Foreign from

product

Login_id Int Login id of client Foreign key from

10. Table Name:-Contact_us

Description:-It stores the contact detail.


Id Int Store the id Primary key

First name Varchar(20) Store the first name Not null

Last name Varchar(20) Store the last name Not null

Company Varchar(20) Store the company

name

Not null

Address Varchar(30) Store the address Allow null

City Varchar(20) Store the city Not null

State Varchar(20) Store the state Not null

Zip code Int Store zip code Not null

Telephone no Int Store telephone

number

Not null

Mobile no Int Store mobile

number

Not null

Fax Int Store fax number Allow null

30 | Page


31/39

E-mail Varchar(30) Store email address Not null

Website Varchar (30) Store website name Not null

Mode of inquiry Varchar(15) Store mode of

inquiry

Not null

comments Varchar(50) Store comments Allow null

10.Table Name:-Query

Description:-It stores the query details which are given by the user.


Cust _no Int Store client no. Primary key

First name Varchar(20) Store first name Not null

Middle name Varchar(20) Store middle name Not null

Last name Varchar(20) Store last name Not null

Address Varchar(30) Store address Not null

Phone no Int Store phone no Allow null

Fax no Int Store fax no Allow null

E-mail Varcahr(20) Store email address Not null

Query description Varchar(30) Store query

description

Not null

City Varchar(15) Store city name Allow null

State Varchar(15) Store state name Allow null

11. Table Name:- feedback

Description:- It stores the feedback details.

31 | Page


32/39


Id Int Id of client Primary key

First name Varchar(15) Store first name Not null

Middle name Varchar(15) Store middle name Not null

Last name Varchar(15) Store last name Not null

Address1 Varchar(25) Store address Not null

Address2 Varchar(25) Store address Not null

City Varchar(15) Store city name Not null

State Varchar(15) Store state name Not null

Country Varchr(15) Store country name Not null

Email Varchar(20) Store email address Not null

Phone no Int Store phone number Allow null

Mobile no Int Store mobile numberAllow null

Feedback Varchar(30) Store feedback Allow null

32 | Page


33/39

6.1 Home page:--

33 | Page


34/39

34 | Page


35/39

6.2 Admin Login Page:--

35 | Page


36/39

6.3 Feedback:--

36 | Page


37/39

6.4 Query:-

37 | Page


38/39

7.1. Books referred:

7.1.1 ASP.net complete reference

7.2 Websites referred:

7.2.1 www.themobilestore.in

7.2.2 www.w3schools.com

38 | Page
http://www.themobilestore.in/http://www.w3schools.com/http://www.themobilestore.in/http://www.w3schools.com/


39/39

mobile document1

Documents