Table of Contents

Serial no.                Contents                              Page no.

1.                          Title of the project--------------------------       2

2.                          Introduction----------------------------------      3
                                 * About Project

3.                          Objective of the project--------------------       5

4.                          Project Category----------------------------       7

                                 * Internet Technologies & RDBMS

5.                          Data Flow Diagram------------------------       11

6.                          Program Structure-------------------------       14

                                 * Project Description
                                 * Database Table

7.                          Tools/ Platform used-----------------------       29

                                 * Software requirement specifications

8.                          Security Mechanisms-----------------------      31

                                 * Testing & Validation

9.                          Future Scope----------------------------------     33

                                 * Project Overview

THE TITLE OF THE PROJECT

ONLINE MOBILE PHONE SHOP

 INTRODUCTION
About Project:

The project ONLINE MOBILE PHONE SHOP  is to develop an Internet

based sale and purchase system for mobile. As mobile market is
increasing very sharply and will increase with boom in near future.
Visualizing the huge opportunity this is an effort to internationalize
the business through Internet. By developing of this portal and
keeping the site searchable on Google hence increasing the
customer base from a local market to all around the globe.

My ongoing project is a web application because nowadays Internet

is a prominent tool of marketing mantra. With the advent of the
Internet technologies, world has become a global village. Every year,
millions of people around the world use the Internet to interact in
more ways then ever before till date. People, who surf on Internet,
are thinking about the online purchase because it is very easy and
comfortable to order online than going to market and purchase their
required goods. So considering a big hike in the revenue in this
booming sector and one of the successful businesses through
Internet one should be proud to have such a technical deal.

With the fast growing of communications network like optical fiber,

making way to   broadband it will be now easy and economical also
to access the Internet, whether in monetary or information retrieval
term.

The mere existence of   the web has been enriching, as it provides a
huge diversity of views, take web logs, or blogs, which can assume
the form of online diary or message board. The gist of all these is
that if the data access retrieval and the goal are placed in a well
order on the net by using its technologies, we are not going to loose
in any way whether it is the user or the service provider. So a
computer has now become helpful in many other cases too:
ormation around the globe by browsing the net.

ating at home to most of the work places

     Easy database access with the invaluable functions of online entertainment and jobs
and placement.

These are the modules that I am going to develop in my proposed project.

Total no. of modules:- 10

1.     LOGIN SYSTEM
2.     REGISTRATION MASTER
3.     THE SEARCH MASTER
4.     ITEM MASTER
5.     ORDER MASTER
6.     THE SITE MASTER (CONTROL PANEL)
7.     SHOPPING CART

8.     THE VALIDATION MASTER

9.      PRODUCT SALE PURCHASE MAILER
               10. ADVERTISEMENT HANDLER

              
OBJECTIVES - MOBILE SHOWROOM MANAGEMENT SYSTEM

  Project Objectives:

The objective of the project “ONLINE MOBILE PHONE SHOP” is to develop a

viable e-marketing system for the purchase and sale of mobile phones.

The major objectives of this project are as follows: -

        Providing an interactive interface for the customer for online sale and purchase
of Mobiles, purchase details input, sales details input, search of the MOBILE type
available on the given criteria, online booking of the MOBILE to be purchased,
with the facility of the shopping cart using the flavors of H.T.M.L, X.M.L. blended
with the power of V.B.NET under the framework of A.S.P.NET. After all interface
has a lot to do when proper interaction and attraction is necessary.

        Helping the customer to search his specific MOBILE with a robust search tool.
  
        Online booking of Mobiles with the delivery status notification system.

        Providing Secured Environment for secured data access wherever necessary.

        Retrieval of data from database using easy buttons, links and interfaces in a very
fast and efficient manner.

        On-line updating of all types of data. Updating Data using web based interfaces
and with the help of buttons & links in an easy & convenient way.

Developing a viable candidate system that fulfills the following  requirements: -

  Faster and accurate information retrieval.

  Easy registration.

  Login dependent information retrieval and updating.

  Correct and consistent maintenance of data and its

     quick retrieval.
                   
        Minimizing the page download time and hence less Investment.

        Improving the switches   button and hyperlink so that the candidate shall find all
the queries they need at first sight.

        Maintaining the fast download of the page by using the flavors of cookies.
        Smooth transition and easy access to the pages not requiring much training to
the end user.

The overall objective of the system is to bring the MOBILE sellers and
purchasers round the globe closer to each other so that one can have the perfect
buy.

PROJECT CATEGORY - MOBILE SHOWROOM MANAGEMENT SYSTEM

The undergoing project falls under INTERNET TECHNOLOGIES & RDBMS (Relational

Database Management System) category. Since the project is mainly responsible for
creation of the portal with the online database at backend. As we know that, the Internet is
huge client server architecture. The client is the web browser, it is requesting a web based
data, a file, or whatever, from some computer somewhere – anywhere – in the world. The
server is that computer that holds the information you want.ASP.NET is a rich programming
framework for building web-based applications. It offers outstanding support for both
developers and administrators, providing improved ease-of-use, tool support, reliability,
scalability, administration and security.

How it works?

ASP.NET is a programming framework built on the common language runtime

that can be used on a server to build powerful Web applications. ASP.NET offers
several important advantages over previous Web development models:
  ENHANCED PERFORMANCE: - ASP.NET is compiled common language
runtime code running on the server. Unlike its interpreted predecessors,
ASP.NET can take advantage of early binding, just-in-time compilation, native
optimization, and caching services right out of the box. This amounts to
dramatically better performance before you ever write a line of code.
  WORLD-CLASS TOOL SUPPORT: - The
ASP.NET framework is
complemented by a rich toolbox and designer in the Visual Studio integrated
development environment. WYSIWYG editing, drag-and-drop server controls,
 and automatic deployment are just a few of the features this powerful tool
provides.
  POWER AND FLEXIBILITY: - Because ASP.NET is based on the common
language runtime, the power and flexibility of that entire platform is available to
Web application developers. The .NET Framework class library, Messaging, and
Data Access solutions are all seamlessly accessible from the Web. ASP.NET is
also language-independent, so you can choose the language that best applies to
your application or partition your application across many languages. Further,
common language runtime
Interoperability guarantees that your existing investment in COM-based
development is preserved when migrating to ASP.NET.
  SIMPLICITY: - ASP.NET makes it easy to perform common tasks, from simple
form submission and client authentication to deployment and

Site configuration. For example, the ASP.NET page framework allows you to
build user interfaces that cleanly separate application logic from presentation
code and to handle events in a simple, Visual Basic- like forms processing
model. Additionally, the common language runtime simplifies development, with
managed code services such as automatic reference counting and garbage
collection.
  MANAGEABILITY: - ASP.NET employs a text-based, hierarchical configuration
system, which simplifies applying settings to your server environment and Web
applications, because configuration information is stored as plain text, new
settings may be applied without the aid of local administration tools. This "zero
local administration" philosophy extends to deploying ASP.NET applications as
well as in ASP.NET application is deployed to a server simply by copying the
necessary files to the server. No server restart is required, even to deploy or
replace running compiled code.
  SCALABILITY AND AVAILABILITY: - ASP.NET has been designed with
scalability in mind, with features specifically tailored to improve performance in
clustered and multiprocessor environments. Further, processes are closely
monitored and managed by the ASP.NET runtime, so that if one misbehaves
(leaks, deadlocks), a new process can be created in its place, which helps keep
your application constantly available to handle requests.
  CUSTOMIZABILITY AND EXTENSIBILITY: - ASP.NET delivers a well-
factored architecture that allows developers to "plug-in" their code at the
appropriate level. In fact, it is possible to extend or replace any subcomponent of
the ASP.NET runtime with your own custom-written component, implementing
custom authentication or state services has never been easier.

  SECURITY: - With built in Windows authentication and per application

configuration, you can be assured that your applications are secure.
The common language runtime provides a complete set of managed data access
APIs for data-intensive application development. These APIs help to abstract the
data and present it in a consistent way regardless of its actual source (SQL
Server, OLEDB, XML, and so on). There are essentially three objects you will
work with most often: connections, commands, and datasets.
  A connection represents a physical connection to some data store; such as SQL
Server or an XML file Through ADO.NET.
  A command represents a directive to retrieve from (select) or manipulate (insert,
update, delete) the data store.
  A dataset represents the actual data an application works with. Note that datasets
are always disconnected from their source connection and data model and can
be modified independently. However, changes to a dataset can be easily
reconciled with the originating data model.

As we know that the database is a repository for stored, operational data in a

database environment and common data are available and used by several
users. Instead of each program (or user) to manage its own data, the data across
applications are shared by all authorized users with the help of database
software managing the data as an entity.

The general concept behind a database is to handle information as an integrated

whole. A database is a collection of interrelated data stored with minimum
redundancy to serve many users quickly and effectively. The general objective is
to make information easy, quick, expressive, and flexible for the user.

 In database design specific objectives are considered: -

        Ease of learning and use. 
        More information at low cost.
        Accuracy and integrity.
        Recovery from failure.
        Performance.                            

In this way, S.Q.L server 2000 is one of the leading

R.D.B.M.S. software in the world. It is characterized by the quick retrieval of
information from huge tables. This quality allows it to cater to the ever-changing
business needs of the present age. It supports fourth generation language, SQL,
thereby making it easier for the customers to grasp it, a development language
where complicated procedures, functions etc. can be used. In the S.Q.L server
2000 include following features:
   Queries
   Constraints
   Procedures
   Triggers
   Batch implementation
   Functions
   Bulk copy utility
   Cursors
   Stored procedures

DATA FLOW DIAGRAM - MOBILE SHOWROOM MANAGEMENT SYSTEM

Data Flow:

An arrow represents a data flow; it represents the path over which data travels in
the system. A data flow can move between processes, flow into or out of data
stores, to and from external entities.

Bubbles (Process):

A circle or bubble represents that transforms data from once form to another by
performing some tasks with the data.
                       
Data store:
A data store is a place where data is held temporarily from one transaction to the
next or is stored permanently.

External Entity:

Which defines a source or destination of system data also called an external

entity. Based on the working process of the proposed system Data Flow Diagram
(DFD), is a model, which gives the insight into the information domain and
functional domain at the same time can be drawn using OMT symbols. DFD is
refined into different levels. The more refined DFD is more details of the system

are incorporated. In the process of creating a DFD, we decompose the system

into different functional subsystems. The DFD refinement results in a
corresponding refinement of data.
 The DFD of the “ONLINE MOBILE PHONE SHOP”

Each break-up has been numbered as per the rule of DFD. Here we attempted to
incorporate all the details of the system and still it requires further improvement since the
entire system is under study.
  
0 LEVEL D.F.D.:-

This is the context level D.F.D. of the proposed system the whole system has
been depicted in a single bubble, primary input and output has been carefully
noted and depicted in the way so that information flow continuity should not be
lost in the next level. The purposed system is shown as a whole process and the
inputs and outputs are shown with incoming and outgoing arrow from the system.

0 LEVEL D.F.D. FOR “ONLINE MOBILE PHONE SHOP”

1ST LEVEL D.F.D.:-

This D.F.D. shows all the processes together with all the data stores (tables). It
shows the true data flow i.e. how data is actually flowing in the system. Data is
 coming from which table and going into which table is clearly shown by this DFD.
This DFD is the main reference for the development of the system. After
understanding the whole system, the application developer will fall back upon this
DFD during the Development phase.

1st LEVEL D.F.D.

Program structure - MOBILE SHOWROOM MANAGEMENT SYSTEM

Analysis Report:

System analysis is the first step towards the software building process. The
purpose of system analysis is to understand the system requirements, identify
the data, functional and behavioral requirements and building the models of the
system for better understanding of the system.

In the process of system analysis one should first understand that, what the
present system, what it does, is how it works (i.e. processes). After analyzing
these points we become able to identify the problems the present system is
facing. Upon evaluating current problems and desired information (input and
output to the system), the analyst looks towards one or more solutions. To begin
with, the data objects, processing functions, and behavior of the system are
defined in detail. After this models, from three different aspects of the system-
data, function and behavior. The models created during the system analysis
process helps in better understanding of data and control flow, functional
processing, operational behavioral and information content.

WORKING PROCESS OF PROPOSED SYSTEM:

        To be the user of the site you need a registration.

        After that one can use the site for to sell or purchase of different mobiles.
        On each mobile a fixed commission is charged by the company, which is being
deducted from the rate the product was sold.
        The user information is kept secret from other user as a company policy because
the whole business is the game of contact.
        When user visits the portal main page he is shown different offers and
advertisements through which he can update his knowledge regarding the
MOBILE available for sale. Besides that he can search for specified MOBILE in
our database, if he is interested and needs to book a MOBILE or to sale then he
needs a registration to be the member of the site.

The proposed system contains the following main processes: -

The candidate registration & login: -

LOGIN

        As the system is candidate dependent so proper user-id and password based
candidate system is necessary to accomplish the fact. Whatever and however
the system is to maintain the candidate status and specific user enabled services
as well as to track the candidates surfing for security and privacy reason.
        Based on the login he is linked to the appropriate page. If the user is not
registered on the site, he is linked to the Registration page.
        A login status and log is maintained to find who and from where login for which
purpose and also to find the number of time a user logins.

 REGISTRATION
      
        A candidate registration asking for name, address and other credential for further
interaction is taken.
        He is asked to register with the unique id and password as well some initial
information is taken such as e-mail id, address and date of birth etc.
         At the end of registration the user is confirmed.

PRODUCT SEARCH

The user can search freely on different products on our site by simply putting a
search if the item is present then he is returned with the matched criteria else he
is requested to follow the registration process to keep his searchable product in
 the database so that if further updating of that product takes place he can be e-
mailed.

SHOPPING CART SYSTEM

If a user navigates through the site and finds different things to purchase and
books that, this shopping cart simply keeps all his purchased item rate
maintained on the server so that their should be no ambiguity of what the user
bought and what he left.

ORDER MASTER

After selecting different products in shopping cart users confirm their order to the
site. All information related to the product, users and their shipping details must
be saved in database so that the product will ship on right time and right place.

PAYMENT MASTER

All payment related information are handled after the order confirmation. User must
pay either online through credit card or in cash at the time of delivery of product.

SELL & PURCHASE MAINTENANCE SYSTEM

As this site is mainly associated with the sale and purchase so, a robust sale and
purchase maintenance system is always needed to maintain the data.

PROJECT DESCRIPTION - MOBILE SHOWROOM MANAGEMENT

SYSTEM

PROJECT MODULES:

The proposed website will have its main page and will be mainly divided into
partially dependent and partially independent modules as: -

1.     LOGIN SYSTEM
2.     REGISTRATION MASTER
 3.     THE SEARCH MASTER
4.     ITEM MASTER
5.     ORDER MASTER
6.     THE SITE MASTER (CONTROL PANEL)
7.     SHOPPING CART
8.     THE VALIDATION MASTER
9.      PRODUCT SALE PURCHASE MAILER
               10. ADVERTISEMENT HANDLER

These modules with their sub module are described below: -

1.    LOGIN MASTER: -

Login master is the module which checks for a valid candidate when the user
enters his user-id, password and link to the correct page or denies and link to the
registration page.
      As user id rules the system so a person is known by his uniqueness of his user id. As it is to
provide the viable candidate system .so the user id is being validated with password in different cases
to validate the genuine ness of the candidate. This module keeps the status of who and
when logged in and for which purpose and how much time.

2. REGISTRATION MASTER:-

This module deals with the different states of registration as:

A.    Registration form display.
B.     Client side validations being handled by validation master.
C.     Unique user id checker (checks that the user id being entered by the candidate
is unique or not.)
D.    Auto user id generator (generate auto user id in user id field by taking the e-mail
id of the user if it is unique or suggest by combining it with some number.)

3. SEARCH MASTER: -
                       
This module is the main module of the project. An enhanced search tool is made
to search item of different categories on the basis of item type, item name or the
difficult one on the basis of description and criteria given by the visitor of the site.
4. ITEM MASTER: -

This module specially relates with item being searched on the site and are not
available, such item and their description are being sent to all the members of the
site, which is being handled by product sale purchase mailer module. A special
database is maintained for such items which when uploaded on the site being
informed to the party through e-mail.

5. ORDER MASTER: -

It deals with orders being booked and transaction related to a candidate that first
books the MOBILE that he wants to purchase and he is asked to send the
amount through suitable media to the company account if the transaction
succeeds, the booking detail is being deleted from the database and the data is
being transferred to the purchase detail or after a limited period the booking
detail expires.

6. SITE  MASTER:-

The site maintenance master deals with the work related to direct updating of the
site. The data necessary to keep the site working, a menu is displayed asking for
updation the instance of the site a user wants. As the size of the module directly
depend upon the table design and updating. A special control panel is designed
for the use of uploading of data in different tables. This is done through a site
master account.

IT INCLUDES THE FOLLOWING SUB MODULES: -

1. COUNTRY SERVICES ENTRY

2. STATE ENTRY
3. CARGO COMPANY DETAIL ENTRY
4. MOBILE COMPANY ENTRY
5. MOBILE TYPE ENTRY
6. ENTRIES RELATED TO UPDATION AND MAINTENANCE OF MOBILE
BOOKED, SOLD, ACCOUNT MAINTENANCE OFF LINE (SOME OF THE
INSTANCES ARE NOT THE PART OF THIS PROJECT)
7. SHOPPING CART SYSTEM:-

If a user navigates through the site and WANTS TO BOOK MORE THEN ONE
MOBILE, THEN this SHOPPING CART IS VERY MUCH HELPFUL FOR SUCH
CASES. This shopping cart simply keeps his entire purchased MOBILE rate
maintained on the server so that there should be no ambiguity of what the user
bought and what he left. This is done through maintaining virtual table for each
user and a unique session id generated by the system that remains same with
the current user session based on that uniqueness is maintained and whatever
the person purchase is updated in to the shopping cart, which is being displayed
with the amount entered.

8. THE VALIDATION MASTER: -

This basically deals with the validation of different entries done during resume
building process. This module specially uses the Clint side validation scripting
from JavaScript and server side scripting from vb.net to make the system robust
reliable and error free. This module as specially integrated with the different
pages and forms checks all the discrepancies such as incorrect e-mail, date of
birth, address, etc to finally deal with any wrong entry being done by the user it
validates as well as suggests for correct input.
                                                                                      
This has different sub modules depending upon the above module.

A). MOBILE UPDATE VALIDATION MASTER

    
Deals with the validations regarding the updating of product.
  
B). REGISTERATION VALIDATION MASTER
    
Deals with the discrepancies in the registration process etc.

9. PRODUCT SALE PURCHASE MAILER:-

This module basically deals with mailing of data to all the members whenever
and wherever the module gets called to take the data and mail it to specific
 suggested or all the members of the portal by using their e-mail addresses from
the database.

10. ADVERTISEMENT HANDLER:-

This module deals with add display on our site.

This has following sub modules:

(i) ADD DISPLAY

This sub module displays the addition on the pages on pre-assigned format. This
checks for the add being paid as well as the expiration of that add after that it is
being automatically removed from the data base.

(ii) ADD ROTATOR (ADD RANDOMIZER)

This randomizes the addition on the basis of priority.

  
(iii) ADD MAINTENANCE MASTER

This deals with updating deletion and maintenance of add a unique user id is
provided after a fixed amount is paid to the company and the company can
update delete or maintain the on the basis of the amount a priority is fixed by us
for the no. of time an add should be displayed.

(iv) ADD PAYMENT DETAIL MASTER

This maintains and manages the payment detail related to company displaying
the addition.

* Since the project is under study and creation. To accomplish all the purposes of
sub module functions may increase.

    

     Site summary
The main group of pages on site will be: -
1.   MAIN PAGE: - home page of the site
2.   Registration page: - user registration page
3.   Login page: - used for login to use the service provided by the site
4.   Old MOBILE entry forms
6.  Search forms
7.  MOBILE details display
8.  Shopping cart frame
9.   Control panel pages (site updating and maintenance)
10. Payment details pages and forms
11. MOBILE booking pages
12. Delivery status information pages.

*Most of the pages which are dynamically created when the client
requests for the page using the robustness of ASP.NET framework
(V.B.NET) blended with the simplicity of H.T.M.L and versatility of
X.M.L have dynamically generated pages.

2. DATABASE TABLE - MOBILE SHOWROOM MANAGEMENT SYSTEM

Table Structure:

There will be 17 tables in the ONLINE MOBILE PHONE SHOP. The normalized

form of the table with their structures is described as under: -

Table 1: Login

Field Name Type Description Constraint

USER_ID NVARCHAR User id (unique) PRIMARY KEY

PASSWORD NVARCHAR Password
NAME VARCHAR Candidate name
ADDRESS1 VARCHAR Permanent address
ADDRESS2 VARCHAR Temporary address
PHONE1 VARCHAR Phone(r)
 PHONE2 VARCHAR Phone (o)
CELL VARCHAR Mobile
E-MAIL VARCHAR Email id
COUNTRY_ID INTEGER Country to which FOREIGN KEY
belongs
STATE_ID INTEGER State FOREIGN KEY
REGIS_DATE DATE Registration date

                                                            

Table 2: Mobile Details

 
Field Name Type Description Constraint
USER_ID VARCHAR User id FOREIGN KEY
ITEM_NO INTEGER Item no PRIMARY KEY
MOBILE_NAME VARCHAR MOBILE name
QOTED_PRICE INTEGER Price
ABOUTMOBILE VARCHAR About item
ALTERNATIVE_PRESENTATION VARCHAR Web address
KEYPOINTS VARCHAR Summary
MOBILE_COMPANY_ID NUMERIC Manufacturer id FOREIGN KEY
MOBILE _MODEL_ID NUMERIC Model detail
MOBILE DATE Date
_MANUFACTURED_DATE manufactured
MOBILE _TYPE VARCHAR Petrol/Diesel
WHETHER_PAID INTEGER Yes/no

                                               
Table 3: Mobile Booked

Field Name Type Description Constraint

USER_ID VARCHAR User id FOREIGN KEY
ITEM_ID INTEGER Item id FOREIGN KEY
 NO_OF_ITEM INTEGER No of item
RATEOF NUMERIC Unit rate
BOOKING_DATE DATE Booking date
BOOKED_ID INTEGER Booking id (unique) PRIMARY KEY

Table 4: MOBILE Picture

Field Name Type Description    Constraint

ITEM_ID NUMERIC Item id FOREIGN KEY

PICTURE_ID NUMERIC Picture id (unique) PRIMARY KEY
PICTURE PICTURE Picture
PICTURE_NAME VARCHAR Picture name
PICTURE_DETAILS VARCHAR Picture
DATE DATE Date of upload

Table 5: MOBILE Enquiry

Field Name Type Description Constraint

USER_ID VARCHAR Id FOREIGN KEY
MOBILE_TYPE_ID INTEGER Id FOREIGN KEY
MOBILE _NAME VARCHAR Item enquired
name
MOBILE _DETAIL VARCHAR Item detail
UNIQUE_ID INTEGER Unique id for PRIMARY KEY
each enquiry
PRICE_RANGE VARCHAR Price
KEYPOINTS VARCHAR Summary
MOBILE _COMPANY_ID NUMERIC Manufacturer id FOREIGN KEY
MOBILE _MODEL_ID NUMERIC FOREIGN KEY
MOBILE _COLOUR VARCHAR
MOBILE DATE Date
_MANUFACTURED_DT
MOBILE _TYPE VARCHAR
WHETHER_INSURED INTEGER Yes/no
WHETHER_INSURANCE_PAID INTEGER Yes/no
DOES_LOAN_REMAINS INTEGER Yes/no

Table 6: Response

Field Name Type Description Constraint

USER_ID VARCHAR User Id FOREIGN KEY
UNIQUE_ID INTEGER Id FOREIGN KEY
RESPONSE_USER_ID VARCHAR User id who response FOREIGN KEY
RESPONSE_DETAILS VARCHAR Details FOREIGN KEY
ITEM_PICTURE_ID PICTURE FOREIGN KEY
RES_DATE DATE Date responded
ITEM_ID INTEGER Item id

Table 7: Item Payment

Field Name Type Description Constrai

nt
USER_ID VARCHA User id FOREIGN
R KEY
PAYMENT_ID NUMBE Payment (unique) PRIMARY
R KEY
ITEM_ID NUMBE Item FOREIGN
R KEY
BOOKED_ID INTEGE Booked id FOREIGN
R KEY
ITEM_NO INTEGE Item no FOREIGN
R KEY
RATEOF NUMERI Rate
 C
TOTAL_PAYMENT NUMERI Payment
C
BYMODE VARCHA Bankcheque/draft/cash/transa
R ction
NO VARCHA Transaction no. /cheque/ draft
R no.
DATE_ISSUED DATE Issuing date
ISSUING_ORGANISATI VARCHA Bank name
ON R
DATE_EXPIRED DATE Date of expiry of draft/ cheque
CREDIT_ID NUMERI Unique (id) PRIMARY
C KEY
DATE_RECEIVED DATE Date

Table 8: Sales Payment

Field Name Type Description Constraint

USER_ID VARCHAR User id FOREIGN KEY
ITEM_ID INTEGER Item id
NO_OF_ITEM INTEGER No of item
RATEOF NUMERIC Rate
BYMODE VARCHAR Cheque /draft /
transaction
NO INTEGER FOREIGN KEY
ORGANISATION VARCHAR Bank name FOREIGN KEY
DATE_SEND DATE
WHETHER_RECEIVED CHAR FOREIGN KEY
DEBIT_ID INTEGER Debit PRIMARY KEY

                                     
Table 9: Login Status Manager

Field Name Type Description Constraint

LOGIN_ID VARCHAR User id FOREIGN KEY
LOGIN_TIME DATE/TIME Login time
LOGOUT_TIME DATE/TIME Logout time

Table 10: Country Services

Field Name Type Description Constraint

COUNTRY_ID NUMERIC Country ID PRIMARY KEY
COUNTRY VARCHAR Country

Table 11: State

Field Name Type Description Constraint

STATE_ID NUMERIC Country ID PRIMARY KEY
COUNTRY_ID NUMERIC
STATE VARCHAR FOREIGN KEY

Table 12: Mobile Manufacture

Field Name Type Description Constraint

MANUFACTURE_ID INTEGER Item Type ID PRIMARY KEY
MANUFACTURE_NAME VARCHAR

Table 13: Mobile Model

Field Name Type Description Constraint

MANUFACTURE_ID INTEGER Manufacturer id FOREIGN KEY
MODEL_ID INTEGER Model id PRIMARY KEY
MODEL_NAME VARCHAR Model name
QUALITIES INTEGER Qualities
                                                                      

Table 14: Delivery Status

Field Name Type Description Constraint

USER_ID VARCHAR User id FOREIGN KEY
BOOKED_ID VARCHAR Booking id FOREIGN KEY
C_BOOK_DATE DATE Cargo booked in transport
BOOKING_NO VARCHAR Unique booking no by cargo
company
C_C_SITE_ADD VARCHAR Cargo company web site
C_ADD VARCHAR Cargo Address
C_C_PHONE VARCHAR Phone of the cargo company

Table 15: Add Details

Field Name Type Description Constraint

USER_ID VARCHAR User id FOREIGN KEY
ADD_ID INTEGER Add id
ADD_LINK VARCHAR Linked page
ADD_LINK2 VARCHAR Alternative linked pages
PICTURE PICTURE Picture
PRIORITY CHAR Priority level
DATE_UPLOADED DATE Date
EXPIRY_DATE DATE Expiry date

Table 16: Payment Details

Field Name Type Description Constraint

USER_ID VARCHAR User id FOREIGN KEY
AMOUNT_PAID VARCHAR Amount paid
ORGANIZATION VARCHAR Organization name
DD_NO INTEGER DD no.
 DATE_RECEIVED DATE Date of received
DATE_EXPIRY DATE Expiry date
WHETHER_RECEIVED CHAR Received information
CREDIT_ID INTEGER Credit id

                                                  
Table 15: Shopping Cart

Field Name Type Description Constraint

USER_ID VARCHAR User ID  PRIMARY KEY
SESSION_ID NVARCHAR
ITEM_ID NUMERIC
QUANTITY INTEGER
RATE_LOCKED NUMERIC
DATE DATETIME

TOOLS/ PLATFORM USED - MOBILE SHOWROOM MANAGEMENT

SYSTEM

For the undergoing project, following tools are used :

Platform                                  : Windows
The Operating System             : Windows 2000 Professional/XP
Framework                              : ASP.NET FRAMEWORK
Front-End Tool                       : ASP.NET With VB.NET
ol                            : MICROSOFT VISUAL INTERDEV,
                                   NOTEPAD, DREAMWEAVER MX6.0
                     : VB.NET, JAVASCRIPT, JAVASCRIPT.NET
                      : H.T.M.L, X.M.L (STYLE SHEET (.XSL))
                       : INTERNET INFORMATION SERVER
Tool                        : S.Q.L SERVER 2000                          

HARDWARE: -
 
 Processor                                           : INTEL PENTIUM-IV 2.1 GHZ

Memory                                             : 256 M.B., D.D.R. RAM

Network Adaptor                             : Ethernet Adaptor

Modem                                               : 56 KBPS VOICE FAX DATA

e                           : SAMSUNG / SEAGATE HARD

DISK                                                                                                                          
         
                                                         (80 GB)

SOFTWARE REQUIREMENT SPECIFICATIONS - MOBILE SHOWROOM

MANAGEMENT SYSTEM

The software requirement specifications (SRS) is a very important part of the

software building process, which describes the actual user level requirement
from technical point of view. I.e. what the user exactly wants? The objective of
preparing the software requirement specification is to represent the requirements
of the software in such a manner that ultimately leads to successful software
implementation. It is the result of the analysis process of the software
development. It should contain all the data the software is going to process, the
function it will provide, and the behavior it will exhibit.

This Software Requirements Specifications (SRS) is defined in IEEE Std. 830-1993, IEEE
Recommended Practice for Software Requirements Specifications.
the synopsis is prepared in the way to fulfill almost all the points needed in S.R.S.

SECURITY MECHANISMS - MOBILE SHOWROOM MANAGEMENT

SYSTEM

TESTING & VALIDATION

 The approach of web application testing adopts the basic principle for all
software testing and applies a strategy and tactics that have been recommended
for object oriented system .the following steps summarizes the approach:

1.      The content model for the web application is reviewed to uncover errors.

2. The design model for the web application as reviewed to uncover

navigation error.                                          
Use cases derived as part of the analyst activity, allow a web Engineer           
exercise each usage scenario against the architectural and navigational design.
These non-executable test help uncover error in navigation.

3.  Selected processing component and web page is unit tested.

When web apps are considered, the concepts of the unit changes, each web
page encapsulated in itself content navigation link as well as script, form and

applet (processing element). It is not always possible or practical to test each of

these characteristics individually.

4. The architecture is constructed and integration tests are conducted.

The strategy for integration testing depends upon the architecture that has been
chosen for the web application.

5. The assembled web application is tested for overall functionality and

content delivery.

Like conventional validation, the validation of web based systems and application
focuses on user visible action and user recognizable output from the system. To
assist in the derivation of validation tests the tester should draw upon use cases
the use cases provides a scenario that has high likelihood of uncovering errors in
user interaction requirement
.
6. The web application is implemented in a variety of different                
environmental configuration and is tested for compatibility with each
configuration.
 7.  The web application is tested by the controlled and monitored
population of end users.
 
Finally with the modular concept inside the application it is being also tested for
its Reliability:

The system reliability will be insured through data integrity rules built into the
database at the backend and the system rules built into the front-end application.

The system will take assurance from the user before making any changes
permanent.

MAINTAINABILITY:

The system has been designed taking care of modularity. Faults in the system can be
traced to modules.

VALIDATION CHECKS

This will be as such to maintain consistent and persistent information on the web
when most of the time the project has to deal with uploads so a minor error will
down the impression of the company.

Therefore, validation checks by software itself using the flavors of JavaScript and
vb.net manual checks are also necessary as: -

1.      Correct entry of data in the form.

      2. Correct updating of question and with the most suitable answer etc.

FUTURE SCOPE - MOBILE SHOWROOM MANAGEMENT SYSTEM

SCOPE OF FUTURE APPLICATION: -

Software scope describes the data and control to be processed, function performance,
constraints, interfaces and reliability. Function describes in the
statement of scope are evaluated and in some case refined to provide more detail prior to
the beginning of the estimation. Because both cost and schedule estimates are
functionally oriented, some degree of decomposition is often useful.

We can implement easily this application. Reusability is possible as and when we

require in this application. We can update it next version. We can add new
features as and when we require. There is flexibility in all the modules. Scope of
this document is to put down the requirements, clearly identifying the information
needed by the user, the source of the information and outputs expected from the
system.

Future scope: MOBILE SHOWROOM MANAGEMENT SYSTEM

It is directly dependent on the lay stone of the project that is we will have to
design a system which when the time passes having a better system initially
should not become a joke later.

It is highly likely that the scope will change as the web application project moves
forward; the web process model should be incremental. This allows the development
team to “freeze” the scope for one increment so that an operational web application
release can be created. The next increment may scope changes suggested by a review of
the preceding increment, but once the second increment commences, scope is again
frozen temporarily. This approach enables the Web App team to work without having to
accommodate a continual stream of changes but still recognizes the continuous evolution
characteristics of most web application. Besides that, the following basic quality in the
software always safeguards the future scope of the software.

Re usability: -
Reusability is possible as and when we require in this application. We can update
it next version. Reusable software reduces design, coding and testing cost by
amortizing effort over several designs. Reducing the amount of code also

simplifies understanding, which increases the likelihood that the code is correct.
We follow up both types of reusability: Sharing of newly written code within a
project and reuse of previously written code on new projects. 
Extensibility: -

This software is extended in ways that its original developers may not expect.
The following principles enhance extensibility like Hide data structure, avoid
traversing multiple links or methods, avoid case statements on object type and
distinguish public and private operations.

Robustness: -

Its method is robust if it does not fail even if it receives improper parameters.
There is some facilities like Protect against errors, Optimize after the program
runs, validate arguments and avoid predefined limits.

Understandability: -

A method is understandable if someone other than the creator of the method can
understand the code (as well as the creator after a time lapse). We use the
method with small and coherent helps to accomplish this.

Cost-effectiveness: -
I
Its cost is under the budget and make within given time period. It is desirable to
aim for a system with a minimum cost subject to the condition that it must satisfy
all the requirements can be rectified easily. The entire source code is well
structured and commented to ensure clarity and readability.

Portability: -

Since it is an Internet based application so its portability and usability depends

upon the client connected with the Internet. The interface designed that is the
web page designing which is one of the major parts of web application because it
is the first impression regardless of the value of its contents interface should grab
a potential user immediately.

PROJECT OVERVIEW
This document contains the system and software requirements in terms of what
the system will be and what is expected from the system. This will also highlight
the system behavior in terms of queries and reports generated by the system. It
contains the user characteristics, access controls, assumptions and
dependencies on the system.

The benefit of the system:

Reduce in overheads paper works, zero delays in project completion, etc