TITLE OF THE PROJECT

Mobile Shop Manager 1.0

INTRODUCTION
About Project:
The project Mobile Shop M ! "er #$% is to develop software based information of Mobile shopping. In global business market the mobile is most important accessory in real life. Visualizing the huge opportunity, this is an effort to ma imize the business through the development of this software and keeping the data and thus increasing the customer base from the local as well as global markets around the world. My ongoing project is a software application because nowadays software is a prominent tool of marketing mantra. !ith the advent of the software technologies, world has become a global village. "very year, millions more people around the world are added to the e isting customer base. #o considering a big hike in the revenue in this booming sector and one of the successful businesses through this software one should be proud to have such a technical deal.

These are the modules we are going to develop in my proposed project.

Tot l !u&ber o' &o(ule): * #%

#$ LO+IN S,STEM -$ CUSTOMER INFORMATION .$ EMPLO,EE INFORMATION /$ SUPPLIER INFORMATION 0$ ITEM INFORMATION 1$ SALES DETAIL 2$ STOC3 DETAIL 4$ PURCHASE INFORMATION 5$ REPORT #%$ CHAN+E PASS6ORD

O7JECTI8ES
The main objective of this project as its title reflects is to developed time distributed software for &Mobile Shop M ! "er #$%'. The proposed automated system will provide the needed ability to support future growth and e pansion and ensure the capability to determine the status of any sales order and purchase order at any given time. It will also integrate sales order activities with account receivable and purchase order activities with account payable management.

Thi) project i!clu(e) the 'ollo9i!" cti:itie) o' it) p rt):

$. %. *. +. ,. (andling sales order information and show current status of re)uirement for the orders. Maintaining receivable accounts. (andling purchase order information and show current status of re)uirement to purchase. Maintaining payable accounts. -eport generation of related information.

Co!trol. /
Improve accuracy and reliability. 0etter security. It provides an interactive interface for the customer and vendor, using the flavors of Java 2.0. 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. roviding !ecured "nvironment for secured data access wherever necessary.

#etrieval of data from database using easy buttons and interfaces in a very fast and efficient manner. $pdating of all type of data. $pdating %ata using software based interfaces and with the help of buttons in an easy & convenient way.

PROJECT CATE+OR,
The undergoing project falls under SOFT6ARE TECHNOLO+IES 1 RD7MS ;Rel tio! l D t b )e M ! "e&e!t S<)te&= category. . 2ava %.3 is a rich programming framework for building software/based applications. It offers outstanding support for both developers and administrators, providing improved ease/of/use, tool support, reliability, scalability, administration and security.

Ho9 it 9or>)?
2ava %.3 is a programming framework built on the common language runtime that can be used on a server to build applications. 2ava %.3 offers several important advantages over previous software development models.
ENHANCED

PERFORMANCE: * 2ava %.3 is compiled and then converted

into bytecode or object code. 4nlike its interpreted predecessors, 2ava %.3 can take advantage of early binding, just/in/time compilation, native optimization, and caching services right out of the bo . This amounts to dramatically better performance before you ever write a line of code.
6ORLD*CLASS

TOOL SUPPORT: * The 2ava %.3 and 2%""/ framework

is complemented by a rich toolbo and designer in the sun Microsystems which is supported in any editor like edit plus, te t pad, notepad etc. PO6ER AND FLE@I7ILIT, : * 0ecause 2ava %.3 is based on the 0yte code and then interpreted either machine language e)uivalent or object code .These are the power and fle ibility of that platform independence that are run in any platform. The 2ava %.3 class library, Messaging, and 5ata 6ccess solutions are all seamlessly accessible from the software. 2ava %.3 is also language/ independent, so you can choose the language that best applies to your application or partition your application across many languages. SIMPLICIT,: / 2ava %.3 makes it easy to perform common tasks, from simple form submission and client authentication to deployment. 7or e ample, the 2ava %.3 page allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple, Visual 0asic like forms processing model. 2ava support garbage collection that is generally used in deinitialisation of object references. MANA+EA7ILIT,: * 2ava %.3 employs a te t/based, hierarchical configuration system, which simplifies applying settings applications, because configuration information is stored as plain te t, new settings may be applied without the aid of local administration tools. This 8zero local administration8 philosophy e tends to deploying 2ava %.3 applications as well as in 2ava

application is deployed to a server simply by copying the necessary files to the server. SCALA7ILIT, AND A8AILA7ILIT, : * 2ava %.3 has been designed with scalability in mind, with features specifically tailored to improve performance in clustered and multiprocessor environments. 7urther, processes are closely monitored and managed by the 26V6% runtime, so that if one misbehaves 9leaks, deadlocks:, a new process can be created in its place, which helps to keep your application constantly available to handle re)uests. CUSTOMISA7ILIT, AND E@TENSI7ILIT, : / 2ava% delivers a well/ factored architecture that allows developers to 8plug/in8 their code at the appropriate level. In fact, it is possible to e tend or replace any subcomponent of the 26V6% runtime with your own custom/written component, implementing custom authentication or state services has never been easier SECURIT,: * !ith built in !indows authentication and per application configuration, you can be assured that your applications are secure. The byte code provides a complete set of managed data access 6;Is for data/intensive application development. These 6;Is help to abstract the data and present it in a consistent way regardless of its actual source 9#<= #erver, 2ava %.3, and so on:. There are essentially three objects we will work with most often. connections, commands, and datasets. 6 connection represents a physical connection to some data store such as #<= #erver or >racle ?i 5atabase Through 2ava %.3. 6 command represents a directive to retrieve from 9select: or manipulate 9insert, update, delete: the data store. 6 dataset represents the actual data an application works with. @ote that datasets are always disconnected from their source connection and data model and can be modified independently. (owever, changes to a dataset can be easily reconciled with the originating data model. 6s 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 9or 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. 6 database is a collection of interrelated data stored with minimum redundancy to serve many users )uickly and effectively. The general objective is to make information easy, )uick, e pressive, and fle ible for the user. In database design specific objectives are considered. /

E )e o' le r!i!" !( u)e$ More i!'or& tio! t lo9 co)t$ Accur c< !( i!te"rit<$ Reco:er< 'ro& ' ilure$ Per'or& !ce$ In this way, S.Q.L server 2000 is one of the leading -.5.0.M.#. software in the world. It is characterized by the )uick retrieval of information from huge tables. This )uality allows it to cater to the ever/changing business needs of the present age. It supports fourth generation language, #<=, thereby making it easier for the customers to grasp it, a development language where complicated procedures, functions etc. can be used. The S.Q.L server 2000 include following features:

Auerie) Co!)tr i!t) Proce(ure) Tri""er) 7 tch i&ple&e!t tio! Fu!ctio!) 7ull cop< utilit< Cur)or) Store( proce(ure)

DATA FLO6 DIA+RAM

D t Flo9:
6n arrow represents a data flowC it represents the path over which data travels in the system. 6 data flow can move between processes, flow into or out of data stores, to and from e ternal entities.

7ubble) ;Proce))=:
6 circle or bubble represents that transforms data from once form to another by performing some tasks with the data.

D t )tore:
6 data store is a place where data is held temporarily from one transaction to the ne t or is stored permanently.

EBter! l E!tit<.
!hich defines a source or destination of system data also called an e ternal entity. 0ased on the working process of the proposed system 5ata 7low 5iagram 9575: is a model, which gives the insight into the information domain and functional domain at the same time can be drawn using >MT symbols. 575 is refined into different levels. The more refined 575 is more details of the system are incorporated. In the process of creating a 575, we decompose the system into different functional subsystems. The 575 refinement results in a corresponding refinement of data. The DFD o' the CMobile Shop M ! "er #$%D "ach break/up has been numbered as per the rule of 575. (ere we attempted to incorporate all the details of the system and still it re)uires further improvement since the entire system is under study.

O8ER8IE6 OF PROJECT
;ayment ;urchase order

5istributor

#lip #ales >rder

Vendor
Invoice

Mobile Shop M !"er #$%

7inance Eharge

;urchase >rder

6ccount -eceivable

Vendor

Invoice ;ayment

6ccount ;ayable

ANAL,SIS ;DFD=

5istributor

6pprovalF5isapproval ;acking #lip

6ccount -eceivable
5istributor 6ccount #tatus

#ales >rder ;roduction >rder -eady to 5ispatch details

Mobile Shop M !"er #$%

;ayment FEheck 7inance Eharge

5istributor

Vendor

7ig. Co!teBt D t Flo9 Di "r &

$3

FIRST LE8EL DFD

5istributor
#ettlement

6pprovalF ;ermit 5isapproval Verified #$% permit data E!ter 6pproval ;ermit Mang. 6pproval or(er Fdisapproval >rder 5etail

Management

;ermit log

-$% Proce)) Per&it

6djustment

6ccount -eceivable
Invoice 4npaid 0alance 6djustment

/$% Po)t P <&e!t

;roduction >rder

;roduction
-eady to dispatch detail .$% Pro(uct I!:oice

0$% M i!t i! Accou!t Recei: ble

7inance Eharges ;acking slip

5istributor

$$

6ccount -eceivable -eport

Vendor 6ccount #tatus

PROCESS LO+IC
MODULE : INTER PERMIT
>rder 5etails #$# 8eri'< b< uthorit < 6uthority Verified order 5istributor 6ccount #tatus

#tate Verified order #$. Appro:e or(er 6pproved order

Management 6pprovalF 5isapproval

$%

Management

Verified order 5ata

6ccount -eceivable

#$8eri'< Accou!t St tu)

PROCESS LO+IC
MODULE : PROCESS ORDER
6pproved order -$# Sep r te St te 6i)e #tate wise order detail >rder 5etail

Group wise order detail

#tock 5etail

;urchase Information

;urchase >rder

;roduction
-eady to 5ispatch detail
$*

#tock 7ile

-$. Prep re or(er c r(

order log

-$Sep r te M r>eti!" +roup

#tock 7ile

PROCESS LO+IC
MODULE : PRODUCED IN8OICE

;roduction
-eady to 5ispatch detail

5istributor

;acking #lip

.$# Prep re I!:oice

Invoice

Invoice

@umbered Invoice

$+

-$. Prep re Per&it c r(

Invoice log

.$A))i"! I!:oice Nu&ber

PROCESS LO+IC
MODULE : POST PA,MENT 5istributor
#ettlement 5ata ;ayment /$# Prep re I!:oice Eredit

/$Prep re I!:oice

/$. Prep re I!:oice 6pproved Eredit

/$/ Prep re I!:oice 6djustment

6djustment

6ccount -eceivable
6ccount -eceivable -eport 7inance Eharge Invoice

Management

5istributor

$,

PROCESS HIERARCH, CHART

Verify by 6uthority "nter purchase order Verify account status 6pprove >rder #tate wise order separation ;rocess order ;repare order card ;repare open order card ;rovide Invoice ;repare invoice 6ssign invoice number ;ost ;ayment "nter settlement Ereate account balance Maintain 6ccount -eceivable 6pprove Eredit 5ebit account balance

S l e) M ! " e& e!t

ER*DIA+RAM FOR SALSE E PURCHASE IS +I8EN ON THE NE@T PA+E

$A

"id Mobile

"@ame

"6ddres s

0sa

"mployee

;hone

5>0 5oj
=ogin id 4ser @ame
=ogi n

;asswor d

;hone 6ddres s =ocation Eid

;hone
=ocation

Mobile

Vendor

"mai l

Vid Vname
5escriptio n Mobil e

Eustomer

"mai l

Ename

6ddres s ;dat e
Item Eode

cid
;urchas e

vid ;no
#ales

Icode

Item Eid Icod e $B Itemdate

#date

6or>i!" Proce)) o' Propo)e( S<)te&:

To be the user of the system you need a registration. >n each Mobile phone a fi ed commission is charged by the company, which is being deducted from the rate as the product was sold. The user information is kept secret from other users as a company policy because the whole business is the game of contract. !hen user visits the shown with different offers and advertisements through which he can update his knowledge regarding the Mobile phone available for sale. 0esides that he can search for specified Mobile phone in our database, if he is interested and needs to book a Mobile phone or to sale on then he needs a registration to be the member.

MODULES DESCRIPTION
#$ LO+IN S,STEM:*

=>GI@ #H#T"M is the module which checks for a valid candidate when the user enters his loginid, user/id, password and link to the main page. 6s user id rules the system so a person is known by his uni)ueness of his user id. 6s it is to provide the viable candidate system, so the user id is being validated with password in different cases to validate the genunity of the candidate. This module keeps the status of who and when logged in and for which purpose and how much time.
-$ CUSTOMER INFORMATION:*

This module define customer information in purchase of mobile .Eustomer id, Eustomer @ame, Eustomer address, customer phone number and customer company address are the important attribute in this modules.
.$ SUPPLIER INFORMATION:*

This module defines the supplier information in all kings of mobile sets. The main feature of this module is e plained clearly supplier id, supplier name, supplier address, supplier phone number and type of mobile set.
/$ EMPLO,EE INFORMATION:*

This module defines "mployee information like employee uni)ue id, name, address, phone, salary, date of joining and salary information.

$?

0$ ITEM INFORMATION:*

This module defines the item information on all the mobile companies those are manufacturing the mobile .The main features of this module clearly e plains all the item code that are uni)uely identified by the item and supplier information.
1$ SALES DETAIL:*

This module defines the sales information of item .The main features of these modules are uni)ue identity the salesid and itemcode. Item code is the references of item information table and customer id is the references in customer table.
2$ STOC3 DETAIL:*

This module defines all the information of stock of mobile sets. 6ll the information of issue stock and item stock are clearly defined.
4$ PURCHASE DETAIL:*

This module defines the purchase detail of customer .6ll the information of mobile sets and customer as well as supplier is given here.
5$ REPORT:*

These module define all the individual report of customer information, employee information, stock information, issue information as well as detail description of mobile company.
#%$ CHAN+E PASS6ORD:*

This module provides forgotten password. If password is forgotten then we can change another password.

T ble Structure:
There will be A tables in the &Mobile #hop Manager $.3' the normalized form of the table with their structure is described as under. /

T ble #: U)er Lo"i!

Field Name
=oginId 4#"-@6M" ;6##!>-5

Type
V6-E(6-9%3: V6-E(6-9%3: V6-E(6-9%3:

Description
4ser id 4ser name ;assword

Constraint
;rimary key

$D

7ield @ame
E4#TI5 E@6M" E655-"## E;(>@"

T ble -: Cu)to&er Det il Type De)criptio!

V6-E(6-9%3: V6-E(6-9+3: V6-E(6-9$33: @4M"-IE9$%: Elient I5 Eustomer name Eustomer 6ddress ;hone @umber

Co!)tr i!t
;-IM6-H I"H

T ble .: S le) (et il

FIELD NAME #@> IT"ME>5" E4#TI5 <46@TITH -6T" PRICE T,PE V6-E(6-9%3: V6-E(6-9%3: V6-E(6-9%3: I@T"G"-9+: 7=>6T INTE+ER;/= DESCRIPTION #ales id Item code Eustomer id <uantity -ate Tot l Price CONSTRAI NT PRIMAR, 3E, FOREI+N 3E,

T ble /: Purch )e Det il

FIELD NAME ;@> #4;I5 IT"ME>5" <46@TITH -6T" PRICE T,PE I@T"G"-9+: V6-E(6-9%3: V6-E(6-9%3: I@T"G"-9+: I@T"G"- 9+: INTE+ER ;/= DESCRIPTION Item number Item code Eustomer id <uantity -ate Tot l Price CONSTRAI NT PRIMAR, 3E, FOREI+N 3E, FOREI+N 3E,

T ble 0: Ite& Det il

FIELD NAME IT"ME>5" IT"M@6M" ITT"M;-IE" <46@TITH TOTAL T,PE V6-E(6-9%3: V6-E(6-9*3: I@T"G"-9+: I@T"G"-9+: INTE+ER ;/= DESCRIPTION Item Eode Item @ame Item ;rice <uantity R te CONSTRAI NT PRIMAR, 3E,

T ble 1: E&plo<ee Det il

FIELD NAME "I5 "@6M" "655-"## ;(>@" 5>0 5>2 0#6= +SAL T,PE V6-E(6-9%3: V6-E(6-9%3: V6-E(6-9,3: @4M"-IE9$%: 56T"TIM" 56T"TIM" I@T"G"-9+: INTE+ER ;/= DESCRIPTION "mployee id "mployee @ame "mployee address ;hone 5ate of 0irth 5ate of 2oining 0asic #alary +ro)) S l r< CONSTRAI NT PRIMAR, 3E,

%3

TOOLSF PLATFORM USED

For the u!(er"oi!" projectG 'ollo9i!" tool) re u)e( : /
;latform The >perating #ystem 7ront/"nd Tool "diting Tool 0ack/"nd Tool . !indows . !indows %333 ;rofessionalFJ; . 2ava %.3 . MIE->#>7T VI#46= I@T"-5"V, @>T";65 . #.<.= #"-V"- %333

HARD6ARE :*
;rocessor Memory @etwork 6daptor Modem #econdary #torage . I@T"= ;"@TI4M/IV %.$ G(K . %,A M.0., 5.5.-. -6M . "thernet 6daptor . ,A I0;# V>IE" 76J 56T6 . #6M#4@G F #"6G6T" (6-5 5I#I 9?3 G0:

SOFT6ARE REAUIREMENT SPECIFICATION:*

The software re)uirement specification is produced at the culmination of the analysis task. The function and performance allocated to software as part of system engineering are refined by establishing a complete information description, a detailed functional description, a representation of system behavior, an indication of performance re)uirement and design constraint, appropriate validation criteria, and other information pertinent to re)uirements. #oftware re)uirement specification 9andFor prototype: is conducted by both the software developer and the customer. 0ecause the specification forms the foundation of the development phase, e treme care should be taken in conducting the review. The review is first conducted at a macroscopic levelC that is reviewers attempt to ensure that the specification is complete, consistent, and accurate when the overall information, function. and behavioral domains are considered.

%$

>nce the review is complete, the software re)uirement specification is &signed/off' by both the customer and the developer. The specification becomes a &contract' for software development. -e)uest for changes in re)uirement after the specification is finalized will not be eliminated. $. I!tro(uctio! o' the )o't9 re: * It specifies the goals and objectives of the software. %. I!'or& tio! (e)criptio!: * It provides the detailed description of the problem that the software must solve. *. Fu!ctio! l De)criptio!: * It deals with the each function design constraints are stated and justified performance 1 characteristics are stated one and more diagrams are included to graphically represent the overall structure of the software. +. 7eh :ior l De)criptio!: * 0ehavioral description e amines the operation of the software as a conse)uence of e ternal events and internally generated control characteristics. ,. 8 li( tio! Criteri : * It is probably the most important and ironically the most often neglected section of software re)uirement specification validation criteria acts as an implicit review of all the re)uirements. A. 7iblio"r ph<: * The bibliography contains references to all documents that relate the software. These include other software engineering documentation, technical references, vendor literature and standards. B. Appe!(iB: * The appendi contains information that supplements the specifications. Tabular data, detailed description of the algorithms, charts, graphs and other material are presented as appendi .

SCOPE OF FUTURE APPLICATION: *

#oftware scope describes the data and control to be processed, function performance, constraints, interfaces and reliability. 7unction describes in the statement of scope are evaluated and in some case refined to provide more detail prior to the beginning of the estimation. 0ecause both cost and schedule estimates are functionally oriented, some degree of decomposition is often useful. !e can implement easily this application. -eusability is possible as and when we re)uire in this application. !e can update it ne t version. !e can add new features as and when we re)uire. There is fle ibility in all the modules. #cope of this document is to put down the re)uirements, clearly identifying the information needed by the user, the source of the information and outputs e pected from the system.

%%