Escolar Documentos
Profissional Documentos
Cultura Documentos
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,
5.3 - HIERARCHY DIAGRAM 5.4 - DATA DICTIONARY 5.5- TABLE LAYOUT 6. OUTPUT DESIGN....................................................... 6.1 FORM LAYOUT
2 | Page
6.2-
REPORT LAYOUT
7. BIBLOGRAPHY..............................................................
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 their curriculum 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 25feb-2011. We give them all the best for their future with regards.
Signature:-
3 | Page
Computer is an inherent part of the life body.virtually,in every walk of life.a person in expected to be able to use computers.The impact of computer technology in several aspect of accouting profession and practice has been pronounced over the last two decades in India. Now,We are in hyper technology era.there are several revolution in any field.We have got more and more machine support in any kind of work in the world.In the medical science.We have more efficient equipments available having all more facility.so,computerization becomes a painful factor behind this technology.And We can do any work faster, and time consumed all this process become very less than ancient era. We are doing a project named ONLINE MOBILE SHOP. 4 | Page
The project has maintained All types about the admission process.
First Of All, We are Thankful to Hemchandracharya North Gujarat 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 to Mr. jagdishbhai barot Owner of and And Their Staff to Co-operate Us at the Time of Information Gathering for System Development.
5 | Page
: Online Mobile Shop : 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. : Jay Shree Chamunda Mobile Shop : Intel Pentium Dual-Core, 1 GB, 128 GB Hard Disk
: Microsoft Visual Studio 2008 : Microsoft SQL server 2005 : .NET 3.5 : Windows XP or later : Barot Saroj v. Kandoi Roshani j.
6 | Page
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 for purchase 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
SCOPE:
Online Mobile Shop System is designed for search, purchase various 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.
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
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 | P a g e
Basic Compiler
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 | P a g e
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 | P a g e
13 | P a g e
14 | P a g e
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 project as operational Feasible.
1. Sufficient support from the user. 2. Acceptance from the user side for active involvement and interest in project
15 | P a g e
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 as front end and MySQL as back end. The softwares are available in the development company.
3)
Request approval:
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 | P a g e
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 | P a g e
NOTATIONS:
There are several notations available for use in flowcharting. Some used in the described system are listed below:
18 | P a g e
Computational steps
19 | P a g e
Start
Login
yes Adm in
C usto m er
U pdate m o bile in fo
C h ek order info
G enerat e report
Search m obile
Purchas e m obile
or der
End
20 | P a g e
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
Feture_id
feture
description
feature
Company master
has
has
Model_id
Model feature
has
Model_ma ster
Model name
name
phone E-mail
has
city
sale
Client order
Order date
21 | P a g e
22 | P a g e
Client
Request/Search
Confirm/Results
Send request/Search
Client _order
Fetch detail
23 | P a g e
Admin
response
1.0 Log in
5.0 Reports
Check report
Model _master
Retrieve info
Model _master
Retrieve info
Client_order
Report
24 | P a g e
Client
Search mobile
Give order
3.0 order
Give payment
4.0 Payment
Retrieve info
Model_master
Retrieve data
Product
Retrieve info
Reply
Client_order
Payment
25 | P a g e
5.4:Data Dictionary:
1. Table Name:-Company_master
Description:- It stores the company id and name . Field name Company_ id Company_name Data type Int Varchar(50) Description Id of company Constraints Primary key
2. Table Name:-Admin
Description:-.It stores the admin id, username and password.
Description Id of Admin
Admin login name Not null Password belongs Not null to admin
3. Table Name:-model_master
Description:- It stores the details of models or mobiles.
26 | P a g e
Retail price of Allow null mobile Less price from the Allow null MRP Provide discount Allow null Name of image Path of image Description of model Allow null Allow null Allow null
4. Table Name:-Client_order
Description:-It stores order details. Field name Order _id First name Middle name Last name Address1 Address2 City State Country Email Mobile no Phone no Data type int Varchar(15) Varchar(15) Varchar(15) Varchar(20) Varchar(20) Varchar(15) Varchar(15) Varchar(15) Varchar(20) Int Int Description Id of order First name Middle name Last name Address of client Address of client Name of city Name of state Name of country Email of client Constraints Primary key Not null Not null Not null Not null Not null Not null Not null Not null Allow null
Mobile number of Allow null the client Phone number of Allow null
27 | P a g e
client Credit card no. Mobile_ id MRP Discount Sale Order date Int Int Numeric Numeric Numeric Datetime Credit card no. of Not null the client Id of mobile Foreign key of model_master Retail price of Not null mobile Provide discount Not null Less price from MRP Date of order Not null Not null
5. Table Name:-Product_master
Description:-It stores the information of product.
Field name
Product _id Product name Price
Data type
Int Varchar(15) Float
Description
Id of product Name of product Price of product
Constraints
Primary key Allow null Allow null
Product company Varchar(20) name Color Varchar(10) Photo Feature Description Varchar(20) Varchar(25) Varchar(30)
Company name of Allow null product Color of mobile Allow null Photo of mobile Feature of mobile Description of mobile Allow null Allow null Allow null
28 | P a g e
6. Table Name:-Model_feature
Description:-It stores the information about feature of model. Field name Data type Description Constraints
Id of model feature Primary key Id of model Id of feature Description of mobile Foreign key of model_master Foreign key from feature Allow null
7. Table Name:-Feature
Description:-It stores the info of feature of model accordingly client requirements. Field name Feature_id Feature Description Data type Int Varchar(50) Varchar(50) Description Id of feature Feature of mobile Description of mobile Constraints Primary key Not null Not null
8. Table Name:-User_table
Description:-It stores the username and password of client. Field name Id User name Password Data type Int Varchar(20) Varchar(20) Description Id of client User login name Constraints Primary key Not null
29 | P a g e
9. Table Name:-Payment
Description:-It stores the information about payment.
Field name Id First name Last name Company Address City State Zip code Telephone no Mobile no Fax
Data type Int Varchar(20) Varchar(20) Varchar(20) Varchar(30) Varchar(20) Varchar(20) Int Int Int Int
Store the first name Not null Store the last name Not null Store the company Not null name Store the address Allow null Store the city Store the state Store zip code Store telephone number Store mobile number Store fax number Not null Not null Not null Not null Not null Allow null
30 | P a g e
Store email address Not null Store website name Not null Store mode of inquiry Store comments Not null Allow null
10.Table Name:-Query
Description:-It stores the query details which are given by the user. Field name Cust _no First name Middle name Last name Address Phone no Fax no E-mail Query description City State Data type Int Varchar(20) Varchar(20) Varchar(20) Varchar(30) Int Int Varcahr(20) Varchar(30) Varchar(15) Varchar(15) Description Store client no. Store first name Store middle name Store last name Store address Store phone no Store fax no Constraints Primary key Not null Not null Not null Not null Allow null Allow null
Store email address Not null Store query description Store city name Store state name Not null Allow null Allow null
31 | P a g e
Field name Id First name Middle name Last name Address1 Address2 City State Country Email Phone no Mobile no Feedback
Data type Int Varchar(15) Varchar(15) Varchar(15) Varchar(25) Varchar(25) Varchar(15) Varchar(15) Varchr(15) Varchar(20) Int Int Varchar(30)
Description Id of client Store first name Store middle name Store last name Store address Store address Store city name Store state name
Constraints Primary key Not null Not null Not null Not null Not null Not null Not null
Store country name Not null Store email address Not null Store phone number Allow null Store mobile numberAllow null Store feedback Allow null
32 | P a g e
33 | P a g e
34 | P a g e
35 | P a g e
6.3 Feedback:--
36 | P a g e
6.4 Query:-
37 | P a g e
7.2.1
www.themobilestore.in
7.2.2 www.w3schools.com
38 | P a g e
39 | P a g e