accessories shop management system on advance java

Statement and Confirmation of Own Work

Programme/Qualification name:

Each NCC Education assessed assignment submitted by you must have this statement attached to the assignment as the cover page or it will not be accepted for marking. Please ensure that this statement is either firmly attached to the cover of the assignment or electronically inserted into the front of the assignment.

Student declaration

I have read and understood NCC Education’s Policy on Academic Dishonesty andPlagiarism.

I can confirm the following details:

Student ID/Registration number: 00120142

Name: Md. Mahbub Alam

Centre Name: Daffodil Institute of Information Technology

Module Name: Final Practical Project

Module Leader: Mr. Shamsuddin Ahammad

Number of words: 8,019

I confirm that this is my own work and that I have not plagiarized any part of it. I have also noted the assessment criteria and pass mark for assignments.

Due Date:

Student Signature:

Submitted Date:

2 Mobile Accessories Shop Management System

Acknowledgment:

I offer our heartfelt thanks to almighty Allah who has given me the strength and the knowledge to

complete this project in Accessories Shop Management System on Advance JAVA.

Thanks to NCC education that enable me to gain such a valuable education like Information Technology.

Thanks to DIIT that bring such education within our bounds.

I express us sincere thanks to Mr. Shamsuddin Ahammad, Lecturer of DIIT, who has shown deep

interest in our work throughout and help me with his rich and varied experience and co-operation in

various ways. He continues support, concentration & encouragement help me to complete this Practical

Project. Huge unknown things are now know to me by doing this Practical Project. In class room we

collect theoretical knowledge about Advance JAVA but practically I gather knowledge by doing this

Practical Project.

I have learned a lot while doing this project. This knowledge will help me enormously in future…

And also thanks to all the staff of DIIT, Especially Bablu Bhai, Zillur Bhai, Yusuf Bhai and Masum Bhai.

Finally I am grateful to our friends who give me inspiration to do the project. It was a glorious memory

by doing this project in my Life.

Last of all I like to thanks Nazrana Haque for his support.

Advance JAVA June 2011 Final @NCC Education 2011


Table of Contents

Stages Sub Stages Page Number

Initial Study

Introduction 6Company Background 7

Project Background 8System Boundary 9Current Operation 10

Limitations/Problems 11Possible Proposed Solution 11

Conclusion 12

Feasibility Study

Introduction 13Planning Issue 14

SDLC 16Methodology 16Gantt Chart 17Testing Plan 17

Feasibility Report 18Economical 18Technical 18

Operational 18Social 18

Conclusion 19

Current System Analysis

Introduction 21User Catalogue 21

Interview Schedule 22Discussion Record 23- 25Context Diagram 26

Current System Physical DFD 27Elementary Process Description 28

ERD of Current System 28Entity Description 29

BAM 30Requirement Catalogue 31

BSO 32Proposed Function 32

Cost/Benefit Analysis 33, 34TSO 35

Conclusion 35



Stages Sub Stages Page Number

New System Analysis

Introduction 37New System DFD 37

Elementary Process Description 38Normalization 39- 42

ERD 43DD of Entities 44- 45

ELH 46Conclusion 46

Design

Introduction 48User Interface Design 48

Form Design 49Report Design 50

Dialogue Design 50Coding 51- 61

Program Specification 61Flowchart/Pseudocode of Function 62, 63

Conclusion 64

Testing

Introduction 66Testing Strategy 66

Unit testing 66System Testing 67

Installing Testing 67Acceptance Test 67

Integration Testing 68Conclusion 68

System Implementation

Introduction 70Implementation Plan 70

Hardware Setup 70Network Setup 70User Training 71

Conclusion 71

Reference 72



Initial Study



Introduction:

Before any new system starts to work a decision is required on the basis of the initial study. An

initial study is used to determine what information systems are needed to support the needs of

the business of what Information Technology would be most appropriate. At the end of this

stage minimum outputs are:

A brief discussion of the proposed system.

An estimation of the project cost.

A possible completion date for the work.

Dhaka city is the busiest city here in Bangladesh. There are plenty of markets bazaars, shops

etc. Among all these “Mobile Corner” is the name of the mobile accessories shop which

contains various type of mobile related product for selling. The sales management system of

mobile corner is currently being maintained manually. There for according to other hi-fi shops

etc. Mobile Corner wants to implement a new sales system, which will be computerized.

Before entering to the details, it is important to know that what should be done to finish the

project successfully. Therefore I collect the following ideas before starting the project.

In the late nineties and millennium there were very few mobile or telecom stores in Dhaka City.

Most of them don’t have a computerized sales management system. But the system was not

very sufficient and could cover each and every problem.



Company Background:

The company was established in the year 2002. At that time mobile was first introduced in

Bangladesh. The name of the founder of the store is Md. Jewel Rana and the shop title is

“Deshprem”. Previously the shop had a different business, but they finally changed to this

mobile business in the year 2002.

The organization had one shop in Kanchpur, Sonargaon, Narayangonj. Previously they have no

computerized system. Already this organization has been achieved good reputation all over the

Narayangonj district providing good quality product, on time delivery of product and service to

customer and has been success in this business field. The main activities are still maintained

manually. The main activity of the shop is to buy mobile accessories and sell it to the

customers. Training about mobile servicing and download multimedia or application file for

customer requirements.

The company maintains basically 4 registry copies which are accordingly:

Sales registry book

Servicing registry book

Download registry book

Laser registry book

Mobile accessories are bought from the supplier or market. These accessories never booked in

any registry because there is no stock registry book. The sales registry is regularly maintained

and updated whenever new accessories are sold on the shop. Servicing and download registry

update every day like of sales registry. Then the accessories are displayed for sell. The sales

registry is maintained every time an accessory gets sold to a customer. This registry is updated

by the employees and is gradually signed out at the end of the day by the sales man. By

comparing all the information form the registers maintained, the shop takes decision of what to

do. They do this on every Friday of the week. They also maintain a “laser” registry which they

update regularly and this is their main backup registry. The total reports of all the transactions

and the registries are checked at the day’s end and are reported to the owner of the shop by

the manager.



Project Background:

Now a day’s global market oriented organization does not able to run without automation and

up-to-date system. It’s because the world is running in speedy network where everybody try to

overlapping others. As a matter of facts no one can survive here without bless of the

automation and up-to-date system for the organization specially the Mobile accessories sales

shops. But also this organization is going on by maintaintaing manual system. So hold the

organization in this business field in the world. Every organization must have better automation

system and others better system otherwise every organization does not keep the own position

on that’s business field, because present worlds is competition world. Everybody wants to

compete to each other in this world. This project will help to maintain the business of a Mobile

Accessories shop.

Mobile accessories shop is totally dominating by the others mobiles shops. So, to fight against

them, an organization from this third world must need to up to date and operate their internal

operation speedy. As a part of internal task of company Order processing and production

system must need to automate. To do so, Deshprem Telecom also tries to develop a computer

department from very beginning of the company. But that department was about conventional

in manner. It does not have much more contemporary facilities.

Now a days the company operating their order processing and all of order related task

manually. It takes a lot of time to check and handle order file from department to department.

For this reason sometimes it is unable to make a product in proper time and it will be late to

deliver.


Customer

ProductSupplier


System Boundary:

System Boundary: A major issue in determining requirements is distinguishing what the

system should do from what it should not do. It often difficult to make decisions about this

boundary, but it is also often difficult to communicate about this issue with all the people

involved. We have found that it is very helpful to apply an approach familiar in design. Here I

give a diagram for understanding the company’s existing system’s boundary. The diagram for

the Mobile Corner is below.

Fig: System Boundary



Current Operation:

This organization buy product from Gulistan underground market. All kind of accessories are

available there. Manager collects product for his organization. When he goes to market he

contain a list of product which is made on his shop before go to market. After buying he come

to the shop and display accessories for sale. If customers are come to the shop and they are

want to buy one or more product sales man make a money receipt for a customer. Sales

money receipt contain some data like date & time, Sl No:, Customer name, Address, Item

number, accessories detail, quantity, unit prize, Taka and authorized signature etc. after sale

product manager or sales man write sale information on sales registry book. If any customers

want to service his/her mobile from this shop than sales man makes a servicing money receipt

for customer. Servicing money receipt contain some data like date & time, Sl No:, Customer

name, Address, Item number, Mobile brand name, Mobile detail, Taka and authorized signature

etc. after sale product sales man write sale information on servicing registry book. Multimedia

expert download games, songs like audio, video and mobile application as like of customer

choice. He records his income on download registry book. Than at last manager manage all

kind of record in leaser registry book. Leaser registry book is the main backup file on the shop.

That’s mean everything or every operation is manually. That’s why take long time to calculate

Profit and error possibility is contain in the system.



Problems with the current system:

After visiting the company and talking to some of the employees, we identified that the

marketing strategy of Mobile’s accessories had caused different problems. These are below –

They follow a manual system for maintain their documents that are vulnerable.

Security is not strong

Document can be lost

Documents reservation is arduous.

Previous documents are not available.

Employee management is not

Sometimes product delivery cannot be possible on specific time

Their manual system is more time consuming.

Their full business process is lengthy.

Take long time to make decision about make decision

Report generate is not easy daily, weekly, monthly and yearly

If you need any necessary previous invoice, it is impossible to get.

Their manual business process is not user friendly.

For maintaining their business more staff is required that are costly.

Their current account supervision function is complicated.

Necessary data missing probability is high.

Possible Proposed Solution:

There are several ways to solve this kind of problems.

Apply automated system

Database will available in this system.

Possible to keep all type of information (business related).

Entire system will be user friendly.

The system will be more secure than their manual system.



Conclusion:

Finally we are satisfied to discuss with them about their business process, their history and so

on. They are agree with us for develop their manual system to automated by us. We observe

their problem with manual system and talk about with them how they can overcome from it. We

make them understand how all of you are benefited by using this software.



Feasibility Study



Introduction:

The term feasibility study is also used to pass on to the resulting document, it will illustrate the

feasible stage of our project with the situation of the current environment and changes that can

be made to progress the business feat over the next few years as well as the cost involve to

carry out the proposed system. We can make decision from the feasibility study against of any

project. What is the profit and risk?

A feasibility study is a preliminary investigation of a project, to decide whether it will cost –

effective, will realize the benefits that are expected and be technically feasible. A feasibility

study is essentially a mini-systems analysis with some additional systems design and

investigation work. Without feasibility study small – scale projects may be initiated but for larger

projects those, which require an amount of time and money the feasibility study is required.

Because it can reduce the risk of the wastage of money.



Planning Issue:

A plan is the backbone of every project and is essential for a successful outcome. Good

plans cover all aspects of the project, giving everyone involved a common understanding of

the work ahead. Here we are planning for an application. In this planning, we have tried to

define our products, major activities involved with the production of the product, timeslot

distribution for these activities and some other things.

i. Staff issues

After the successful development of this project all the works related with staffs will be

faster and easier the more appropriate the system the more sophisticated the works of

those staffs whose are fully or partially related with this system.

ii. Testing

Testing is a very important stage of implement a new system. If we implement our

system without testing, then it’s not work properly or its will failed. So we must be testing

our system with concisely.

iii. Implementation

After the successful development of a system, it needs to be implemented

appropriately. For this purpose an appropriate implementation plan should be prepared.

When all the things go through the plan it will be accomplished.



System Life Cycle Model:

A number of system development life cycle (SDLC) models have been created: waterfall, v-

model, fountain, and spiral, build and fix, rapid prototyping, incremental, and synchronize and

stabilize. The software development life cycle (SDLC) is the entire process of formal, logical

steps taken to develop a software product. Here we prefer to take Waterfall Lifecycle because of

the following reason:

Methodology:

There is few well define methods for system development are SSADM, UML, DSDM. We follow

the SSADM methodology. Because the SSADM method involves the application of a sequence

of analysis, documentation and design tasks concerned with the following:



Gantt Chart:

Gantt chart is a popular type of bar chart that illustrates a project schedule. Gantt charts

illustrate the start and finish dates of the terminal elements and summary elements of a project.

Terminal elements and summary elements comprise the work breakdown structure of the

project. The start and finish time and also the time duration.

SerialNo Name Of Stages Start Date Finish Date

Working Days2 2 3 4 5 10 3 3

1 Initial Study 24-03-11 25-03-11

2 Feasibility 26-03-11 27-03-11

3 Current System Analysis

28-03-11 30-03-11

4 New system analysis

31-03-11 03-04-11

5 Design 04-04-11 08-04-11

6 Developments 09-04-11 18-04-11

7 Testing 19-04-11 21-04-11

8 Implementation 22 24-04-11

Total 32 days and per day 4 hour32*4= 128 Hour

Testing Plan:

A test plan is a methodical approach to testing a system such as software. The plan typically

contains a detailed understanding of what the eventual workflow will be. First we have to

identify the objective of the plan in relation to the Software Project Plan that it relates to. These

are things we intend to test within the objective of the plan. Essentially, something we will test,

a list of what is to be tested. We able to turn every test run into a key contribution to our overall

development efforts. This can be developed from the software application inventories as well as

other sources of documentation and information. We keep our projects on schedule and on

speculation. Our team confident and the work 100% productive.



Feasibility Report:

Feasibility reports describe one or more design solutions to a specific problem and agree on if

the proposed solution is realistic and feasible. If possible, more than one solution is offered, in

which case the report compares the various designs and determines which option is best.

Feasibility reports emphasis placed on practical and economic viability of the design in

comparison with other possible solutions. Feasibility reports are vital for decision making. In our

project development, feasibility reports are based on few matters that are social, economical,

technical and operational. The detail discussions are as follows:

Economical: This involves the feasibility of the proposed project to generate economic

benefits. A benefit-cost analysis and a breakeven analysis are important aspects of evaluating

the economic feasibility of new industrial projects. The tangible and intangible aspects of a

project should be translated into economic terms to facilitate a dependable basis for valuation.

Cost benefit analysis is an important feature of economical feasibility. Here we try to illustrate

their cost analysis for build up their entire system.

Technical: This involves questions such as whether the technology needed for the system

exists, how difficult it is to build, and whether the organization has enough experience using

that technology. The assessment is based on an outline design of system requirements in

terms of Input, Output, Fields; this can be qualified in terms of volumes of data, frequency of

updating, etc. In order to give an introduction to the technical system, they are currently posses

the necessary technology. Our system fully supports their technical infrastructures.

Operational: Our systems modes of operation will afford adequate throughput and response

time. Our system will provide accurate and usefully formatted information. Our systems

operation offer effective controls to protect against fraud and to guarantee accuracy and

security of data and information. This systems mode of operation provides reliable service and

it flexible and expandable.

Social: Social feasibility concentrates on the control that a proposed project may have on the

social system in the project environment. The ambient social structure may be such that

certain categories of workers may be in short supply or absent. The effect of the project on the

social status of the project participants must be assessed to ensure compatibility. It recognized

that workers in certain company may have certain status symbols within the society.



Conclusion:

Conducting a feasibility study is a good project practice. The system is going to provide

service dynamically for their business. As we have already mentioned how they are

going to be benefited by this system. Finally they are understood and agree with us for

developing their manual system to automate.



Current System Analysis



Introduction:

Requirement analysis is concerned with discovering what the new system is required to do.

Some outline requirements are already discussed in the initial study and the feasibility

study, but there are not sufficient to build a new system. Requirements analysis will include

everything gleaned from interviews & observations which do not refer to the current system.

User Catalogue:

The report is constitutionally mandated for this company.

User Catalogue Activity

Job Title Tasks Comments

Chairman/Managing Director

Make executive

decisions.

SalesmanHandling and effective

sales of the products.

Servicing Expert

Service mobile as

customer

requirements

Multimedia ExpertReceive Update and

Monitor Store.



Interview schedule:

Name of interviewer:

Name Date Time PositionMr. Jewel Rana 28-03-2011 11.00 am Managing Director

Mr. Mahbubur Rahman 28-03-2011 3.00 am Salesman

Mr. Belal Hossain 29-03-2011 11.00 am Servicing Expert

Mr. Safiqul Islam Rony 29-03-2011 3.00 am Multimedia Expert



Discussion record:

Discussion Record

System:

Accessories shop management system

Name: Managing Director Sheet -1

Participants: Salesman Date: 28-03-2011

Objective/Agenda: Business Process infoLocation:Kanchpur,

Dhaka-1430

Duration: 2 hoursResult: The purpose of our discussion is understands their business

function and makes them understand what we are going to do. We

covers with the production of the business .How they conduct their

business and what sort of problem.

They are facing which problem. How can they remove their particular

problem by our system? As a result they agree with us for

developing a system and their business.

Cross reference



Discussion Record

System:


Name: Salesman Sheet -2

Participants: Servicing Expert Date: 29-03-2011


Dhaka-1430








Cross reference



Discussion Record

System:


Name: Salesman Sheet -3

Participants: Multimedia Expert Date: 29-03-2011


Dhaka-1430








Cross reference



Context Diagram:

This is the first method of depicting the system graphically. The context diagram does not show

enough detail to indicate exactly what happens. It defines the boundaries of the system. This is

usually drawn as a single process with all the inputs from sources and outputs to sinks

identified.

The context diagram is given below:

Fig: Context Diagram Representation


Processes

Product Info

Product

Customer

Place the Order

Viewinfo

Product info

Confirm

Supplier

Supply Product

Provide new Product Order new

Product


Data Flow Diagram (DFD):

A data Flow Diagram (DFD) is a graphical technique that depicts information flow

and the transforms that are applied as data moved from input to output.

A data flow diagram (DFD) which represents the data flows is given below:


Process Product info

Admin1

Product

Confirm

Product info

Process Supplier’s info

Admin2

ProductOrder New Product

Provide New Product

M2 Supplier’s Data

M1 Product Data

Process Customer’s Order

Admin3

Customer

Order new Product

Confirm M3 Order Data

M1 Product Data


Elementary Process Description:

ID Process Name Description

1.1 Analyzing Manager must analyses the confirm order, and then this

department maintain the model of product and make an

estimate of product. Take important decision for the

shop.

1.2 Planning Manager makes plan for product according to customer

demand. Produce daily report to the managing director.

1.3 Salesman Salesman follows the direction of the Manager. They

give the total sales information / report to the manager at

the end of the day.

1.4 Quality Control Salesman quality is responsible for maintain the quality

of product. This department checks the product and

maintains the quality of product.

Entity Relationship Diagram (ERD):


Product Supplier

Product Supplier

Customer


Entity Description:

Data Dictionary

Type Entity

NameProduct

Definition:Product ID + Product Name + product Price

Occurrence10,000

Data Dictionary

Type Entity

NameSupplier

Definition:Supplier ID + Supplier Name + Supplier Address + Supplier Phone

Occurrence10,000

Data Dictionary Type Entity

NameClient

Definition:Customer ID + Customer Name + Customer Address + Customer Phone

Occurrence10,000


Enquiry


Business Activity Model (BAM):

Figure: Sample product

Figure: Order product


Maneger Production Stock

Order product

Receive product

Confirmation

Confirmation

Maneger Show Room / Store


Requirement Catalogue:

Requirement ID R1Requirement Name Quality MaintainBusiness Activity On time quality checkingSource Quality managerPriority HighOwner Mr. Jewel RanaFunctional Requirement Users can get company information.Non-Functional Requirement System to be available 24 hours Benefits Customer gets quality full productComments It is provide securityRelated DocumentsRelated Requirements To be updated regularly.

Requirement ID R2Requirement Name Security maintainBusiness Activity Apply passwordSource Production managerPriority HighOwner Mr. Jewel RanaFunctional Requirement Users can get company information.Non-Functional Requirement System to be available 24 hours Benefits System security will not breakComments It is provide securityRelated DocumentsRelated Requirements Its provide high security

Requirement ID R3Requirement Name Better service provideBusiness Activity Work properlySource Production managerPriority HighOwner Mr. Jewel RanaFunctional Requirement Users can get basic information.



Non-Functional Requirement System to be available 24 hours Benefits Customer gets product on time Comments It is provide securityRelated DocumentsRelated Requirements Fast service



Business System Option (BSO) Catalogue:

Business System Option for IMS:

Development of business system option gives analyst and users the opportunity to explore

where the system boundary lies. It will provide a starting point for the specification of the

required system and the users with an initial over view of the system.

System Boundary:

In this section we define the section of working area; we will work with what and area.

Production:

When a product come to the production house, then it has been produced according to the

customer demand, then check the quality of product an delivery on due time.

Functionality:

As we have already identified the user for production management system. So levels of

functionality here must be different for both users.

Functionality to be performed by users in the production management System:

The admin will give the permission to the user by providing them their personal

ID and password.

After completing their registration process they are able to access product form

to record new products information or update records of existing records.

System must deny unauthorized user.

The user will add and delete necessary information about product.

They can produce report based on product information.

Proposed Function:

User Id and password.

Restricted unauthorized access.

Different authorization level.

Strong securities maintain.

Data will be saved in different place at the same time.

Its can have an opportunity to update.



Reports:

Report is very important part of our proposed system. So our system such as that is show

report against function.

Cost/ Benefits analysis:

Cost involved in this project (In Bangladeshi Taka-BDT)

Hardware peripheral:

Peripheral Name Description Quantity Price

Processor Intel core i3 2.21 GHz 1 8100

Motherboard Intel g41 1 4100

Hard disk(HDD) Samsung 500 GB 1 3500

RAM Transcend 1 GB 1 2000

Monitor LCD 15 inch 1 10000

Keyboard A4 tech 1 200

Mouse A4 tech 1 200

Printer Canon 1 3000

UPS Rahimafroz (600va) 1 3000

Total Cost = 34300

Software Purchase Cost:

Name of the software Description Quantity Price

Windows XP Service pack 2 1 100

Microsoft Office Office XP 1 200

iReport Java report tool 1 180

Sun JDK 1.6.0 Java Platform 1 150

JDBC Driver MSSQL 1 Free

Total cost – 630



Grand total cost:

Hardware Costs 34300

Software Costs 200

Total costs – 34500

Benefits:

They can be able to generate a report daily, weekly, monthly and yearly,

They can retrieve their data in any time.

They can preserve their customer’s information.

They can manage employee easily

They can keep information about worker of work and can easily retrieve information

within short time of need.

Account department will get an actual information worker working time and salary

calculation will be easy.

Decision making will be very easy.

Impact Analysis:

In every where or anywhere are has been implemented a new system .there will have some

change or impact after implement new system like this some impact are have to be faced.

Which impact can be show that is listed below - -

Need to take budget to established new system May need to train up some employee May need to take new rules May need to requirement for new employee which are experience in this field It can seems to that it is cost effective

If it is seems that cost effective but. Must have to take a budget just for one time then it will be

going on by one operator. After established this system customer service will very fast. Product

will be delivery on time that why customer will be satisfy. Then this organization can compete to

other organization. Established the accessories shop management system cost will come to

breakeven point in once time from this make profit by the production management system.



TSO:

Technical System Option for Accessories Shop Management System:

Technical environment of Production Management System:

External Hardware:

The Accessories Shop Management System will interact directly or indirectly, with the

following significant external hardware:

Backend hardware:

Employees workstation, which are the personal computers used by employees to

perform their task.

Mirroring of central database server:

Central server, which contains the main database that connects both users machine.

Conclusion:

From our point of view we would like to say that Accessories Shop Management System

would help Multipurpose. At present we must appear hard competition in most business

ground. Under these conditions it is precondition for Deshprem Telecom to provide the better

opportunity to their probable customers and employees. The new system entirely able to

provide better service and fast service, consequently it will help to gain their target within due

time. So we consider and hope that our developed system will increase their social and

business standing.



New System Analysis



Introduction:

Our proposed production management system is able to provide better service before previous

system. Just like this, it’s confirming the customer demand product quality, this system delivery

of product on time, this system provides high security, this system provide strong backup for

data.

New System Data Flow Diagram (DFD):


Process Supplier’s info

Admin2

SupplierOrder New Product

Provide New Product

D2 Supplier’s Data

Process Customer’s Order

Sales man3

Customer

Order new Product

Confirm D3 Purchase Data

D1 Product Data

Process Product info

Admin1

Product Product info

D1 Product Data


Elementary Process Description:


1.1 Login to the System There is some entry point for entry of product.

1.1 Create Product InformationIf any products buy, Admin entered in to the system. To

use those data in feature.


2.1 Client Order product Client order some product for buying.

2.2 Makes a Money receipt

Sales man makes a money receipt using this system.

Product data are collected from product data file.

2.3 Create operational file

Create operation file has been used to store of each

operation. Operation file contains information of each

operation in detail such as,

Create sales information of product

Quality checking

Delivery product report

2.3 Data maintain

Data maintain part is very important and it is very

sensitive case for the system. We maintain data about

product, sales, purchase etc.


3.1 Employee information Admin collect data from employee.

3.2Making ID card of

employee

Admin makes a ID card using this system. ID Card data

are collected from Employee record file.



Normalization:

Gather Data:

Customer ID

Customer phone

Customer name

Customer address

Sales ID

Sales Date

Sales price

Supplier ID

Supplier date

Supplier name

Product ID

Product price

Product quality

Product name

Sales ID

Sales quantity

Sales unit price

Purchase ID

Purchase Date

Purchase price

Purchase quantity

Purchase quality

Purchase unit price

Stock ID

Stock name

Stock date

Stock quantity

Category ID

Category name

Non Repetitive Data:

Customer ID

Customer phone

Customer name

Customer address

Sales ID

Sales Date

Sales unit price

Supplier ID

Supplier date

Supplier name

Product ID

Product price

Product quality

Product name

Purchase ID

Purchase Date

Purchase unit price

Purchase quality

Stock ID

Stock name

Stock date

Stock quantity

Category ID


Repetitive Data:

Sales quantity

Sales unit price

Purchase unit price

Purchase quality

Category name

Product ID

Product quality

Product name

1NF:

StockProduct IDProduct nameProduct quantity

2NF:

StockProduct IDProduct nameProduct quantity

3NF:

CustomerCustomer IDCustomer nameCustomer phoneCustomer Address

ERD:

Product

Product ID

Product name

Product Price

*Category ID

DD of Entities:

Data Dictionary

Type: Entity Name: Product

Description:

Product ID + Product unit price + Product Name + Product Price

Occurrence

400

Data Dictionary

Type: Entity Name: Customer

Description:

Customer ID + Customer Name + Customer Phone + Customer Address

Occurrence

400

Data Dictionary

Type: Entity Name: Sales

Description:

Sales ID + Sales date + customer ID

Occurrence

400

Data Dictionary

Type: Entity Name: Sales Detail

Description:

Sales ID + quantity + Sales unit price + Product ID

Occurrence

400

Data Dictionary

Type: Entity Name: Supplier

Description:

Supplier ID + Supplier name + supplier phone + supplier address

Occurrence

400

Data Dictionary Type: Entity Name: Purchase

Description:

Purchase ID + Purchase date + supplier ID

Occurrence

400

Data Dictionary

Type: Entity Name: Purchase Detail

Description:

Purchase ID + Product ID + Quantity + purchase unit price

Occurrence

400

Data Dictionary

Type: Entity Name: Stock

Description:

Product ID + Product name + Product Quantity

Occurrence

400

Data Dictionary

Type: Entity Name: Category

Description:

Category ID + Category name

Occurrence

400

ELH:

Figure: Entity Life History (ELH)

Conclusion:

This section contains the analysis of new system. These systems are able to perform for

customer better service of Accessories shop management system. The new system entirely

able to amplify the rate of operations, consequently it will help to gain their target within due

time. So we consider and hope that our developed system will increase their social and

business standing.

Design

Introduction:

This is the design part of proposed system. In this part I have been design User Interface, Form

Design, Report Design, Dialogue Design etc which is used for the system. It was designed to

solve certain set of problems.

User Interface Design:

Figure: Main Window of the system

Form Design:

Figure: Sales form

Report Design:

Figure: Stock Report

Dialogue Design:

Figure: Sale ID insertion dialogue box

Coding:

Coding of main user Interface under the below (MainUI.java):

package project.ui;

import java.awt.Toolkit;import java.util.HashMap;import javax.swing.JOptionPane;

public class MainUI extends javax.swing.JFrame { public MainUI() { initComponents(); setSize(Toolkit.getDefaultToolkit().getScreenSize()); }

@SuppressWarnings("unchecked") // <editor-fold defaultstate="collapsed" desc="Generated Code"> private void initComponents() {

desktopPane = new javax.swing.JDesktopPane(); jPanel1 = new javax.swing.JPanel(); saleReportiButton = new javax.swing.JButton(); stockReportButton = new javax.swing.JButton(); dailyReportButton = new javax.swing.JButton(); weeklyReportButton = new javax.swing.JButton(); yearlyReportButton = new javax.swing.JButton(); jPanel2 = new javax.swing.JPanel(); saleuiButton = new javax.swing.JButton(); customeruiButton = new javax.swing.JButton(); systemExit1 = new javax.swing.JButton(); categoryuiButton = new javax.swing.JButton(); supplieruiButton = new javax.swing.JButton(); purchaseuiButton = new javax.swing.JButton(); productui = new javax.swing.JButton(); menuBar = new javax.swing.JMenuBar(); fileMenu = new javax.swing.JMenu(); openMenuItem = new javax.swing.JMenuItem(); saveMenuItem = new javax.swing.JMenuItem(); saveAsMenuItem = new javax.swing.JMenuItem(); exitMenuItem = new javax.swing.JMenuItem(); helpMenu = new javax.swing.JMenu(); jMenuItem1 = new javax.swing.JMenuItem();

setDefaultCloseOperation(javax.swing.WindowConstants.EXIT_ON_CLOSE); setTitle("Mobile Accessories Shop Management System"); setBounds(new java.awt.Rectangle(0, 0, 0, 0)); setIconImage(Toolkit.getDefaultToolkit().getImage("src/others/icon.png"));

jPanel1.setBackground(new java.awt.Color(255, 255, 255)); jPanel1.setBorder(javax.swing.BorderFactory.createTitledBorder(null, "Print Options", javax.swing.border.TitledBorder.DEFAULT_JUSTIFICATION, javax.swing.border.TitledBorder.DEFAULT_POSITION, new java.awt.Font("Monotype Corsiva", 0, 14), new java.awt.Color(3, 101, 36))); // NOI18N

saleReportiButton.setText("Sales"); saleReportiButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { saleReportiButtonActionPerformed(evt); } });

stockReportButton.setText("Stock"); stockReportButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { stockReportButtonActionPerformed(evt); } });

dailyReportButton.setText("Daily Income"); dailyReportButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { dailyReportButtonActionPerformed(evt); } });

weeklyReportButton.setText("Weekly Report"); weeklyReportButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { weeklyReportButtonActionPerformed(evt);

} });

yearlyReportButton.setText("Yearly Profit"); yearlyReportButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { yearlyReportButtonActionPerformed(evt); } });

javax.swing.GroupLayout jPanel1Layout = new javax.swing.GroupLayout(jPanel1); jPanel1.setLayout(jPanel1Layout); jPanel1Layout.setHorizontalGroup( jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING) .addGroup(jPanel1Layout.createSequentialGroup() .addGroup(jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING) .addGroup(javax.swing.GroupLayout.Alignment.TRAILING, jPanel1Layout.createSequentialGroup() .addGap(1, 1, 1) .addComponent(stockReportButton, javax.swing.GroupLayout.DEFAULT_SIZE, 107, Short.MAX_VALUE)) .addGroup(jPanel1Layout.createSequentialGroup() .addGap(1, 1, 1) .addComponent(dailyReportButton, javax.swing.GroupLayout.DEFAULT_SIZE, 107, Short.MAX_VALUE)) .addGroup(jPanel1Layout.createSequentialGroup() .addGap(1, 1, 1) .addComponent(weeklyReportButton, javax.swing.GroupLayout.DEFAULT_SIZE, 107, Short.MAX_VALUE)) .addComponent(yearlyReportButton, javax.swing.GroupLayout.DEFAULT_SIZE, 108, Short.MAX_VALUE) .addGroup(jPanel1Layout.createSequentialGroup() .addGap(1, 1, 1) .addComponent(saleReportiButton, javax.swing.GroupLayout.DEFAULT_SIZE, 107, Short.MAX_VALUE))) .addContainerGap()) ); jPanel1Layout.setVerticalGroup( jPanel1Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING) .addGroup(jPanel1Layout.createSequentialGroup() .addContainerGap() .addComponent(saleReportiButton)

.addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED) .addComponent(stockReportButton) .addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.UNRELATED) .addComponent(dailyReportButton) .addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.UNRELATED) .addComponent(weeklyReportButton) .addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.UNRELATED) .addComponent(yearlyReportButton) .addContainerGap(56, Short.MAX_VALUE)) );

jPanel1.setBounds(130, 170, 130, 250); desktopPane.add(jPanel1, javax.swing.JLayeredPane.DEFAULT_LAYER);

jPanel2.setBackground(new java.awt.Color(255, 255, 255)); jPanel2.setBorder(javax.swing.BorderFactory.createTitledBorder(null, "Interface Buttun", javax.swing.border.TitledBorder.DEFAULT_JUSTIFICATION, javax.swing.border.TitledBorder.DEFAULT_POSITION, new java.awt.Font("Monotype Corsiva", 0, 14), new java.awt.Color(3, 101, 36))); // NOI18N

saleuiButton.setText("Sale"); saleuiButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { saleuiButtonActionPerformed(evt); } });

customeruiButton.setText("Customer"); customeruiButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { customeruiButtonActionPerformed(evt); } });

systemExit1.setText("Exit"); systemExit1.addActionListener(new java.awt.event.ActionListener() {

public void actionPerformed(java.awt.event.ActionEvent evt) { systemExit1ActionPerformed(evt); } });

categoryuiButton.setText("Category"); categoryuiButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { categoryuiButtonActionPerformed(evt); } });

supplieruiButton.setText("Supplier"); supplieruiButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { supplieruiButtonActionPerformed(evt); } });

purchaseuiButton.setText("Purchase"); purchaseuiButton.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { purchaseuiButtonActionPerformed(evt); } });

productui.setText("Product"); productui.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { productuiActionPerformed(evt); } });

javax.swing.GroupLayout jPanel2Layout = new javax.swing.GroupLayout(jPanel2); jPanel2.setLayout(jPanel2Layout); jPanel2Layout.setHorizontalGroup( jPanel2Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING) .addGroup(jPanel2Layout.createSequentialGroup()

.addContainerGap() .addGroup(jPanel2Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING) .addComponent(saleuiButton, javax.swing.GroupLayout.DEFAULT_SIZE, 80, Short.MAX_VALUE) .addComponent(systemExit1, javax.swing.GroupLayout.DEFAULT_SIZE, 80, Short.MAX_VALUE) .addComponent(productui, javax.swing.GroupLayout.DEFAULT_SIZE, 80, Short.MAX_VALUE) .addComponent(purchaseuiButton, javax.swing.GroupLayout.DEFAULT_SIZE, 80, Short.MAX_VALUE) .addComponent(supplieruiButton, javax.swing.GroupLayout.DEFAULT_SIZE, 80, Short.MAX_VALUE) .addComponent(categoryuiButton, javax.swing.GroupLayout.DEFAULT_SIZE, 80, Short.MAX_VALUE) .addComponent(customeruiButton, javax.swing.GroupLayout.Alignment.TRAILING, javax.swing.GroupLayout.DEFAULT_SIZE, 80, Short.MAX_VALUE)) .addGap(18, 18, 18)) ); jPanel2Layout.setVerticalGroup( jPanel2Layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING) .addGroup(jPanel2Layout.createSequentialGroup() .addComponent(saleuiButton) .addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED) .addComponent(customeruiButton) .addGap(5, 5, 5) .addComponent(categoryuiButton) .addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED) .addComponent(supplieruiButton) .addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED) .addComponent(purchaseuiButton) .addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.RELATED) .addComponent(productui) .addPreferredGap(javax.swing.LayoutStyle.ComponentPlacement.UNRELATED) .addComponent(systemExit1) .addContainerGap(20, Short.MAX_VALUE)) );

jPanel2.setBounds(10, 170, 120, 250); desktopPane.add(jPanel2, javax.swing.JLayeredPane.DEFAULT_LAYER);

fileMenu.setText("File");

openMenuItem.setText("Open"); fileMenu.add(openMenuItem);

saveMenuItem.setText("Save"); fileMenu.add(saveMenuItem);

saveAsMenuItem.setText("Save As ..."); fileMenu.add(saveAsMenuItem);

exitMenuItem.setText("Exit"); exitMenuItem.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { exitMenuItemActionPerformed(evt); } }); fileMenu.add(exitMenuItem);

menuBar.add(fileMenu);

helpMenu.setMnemonic('h'); helpMenu.setText("Help");

jMenuItem1.setAccelerator(javax.swing.KeyStroke.getKeyStroke(java.awt.event.KeyEvent.VK_F1, 0)); jMenuItem1.setMnemonic('a'); jMenuItem1.setText("About"); jMenuItem1.addActionListener(new java.awt.event.ActionListener() { public void actionPerformed(java.awt.event.ActionEvent evt) { jMenuItem1ActionPerformed(evt); } }); helpMenu.add(jMenuItem1);

menuBar.add(helpMenu);

setJMenuBar(menuBar);

javax.swing.GroupLayout layout = new javax.swing.GroupLayout(getContentPane()); getContentPane().setLayout(layout); layout.setHorizontalGroup( layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING)

.addComponent(desktopPane, javax.swing.GroupLayout.DEFAULT_SIZE, 804, Short.MAX_VALUE) ); layout.setVerticalGroup( layout.createParallelGroup(javax.swing.GroupLayout.Alignment.LEADING) .addComponent(desktopPane, javax.swing.GroupLayout.DEFAULT_SIZE, 432, Short.MAX_VALUE) );

pack(); }// </editor-fold>

private void exitMenuItemActionPerformed(java.awt.event.ActionEvent evt) { System.exit(0); } private void jMenuItem1ActionPerformed(java.awt.event.ActionEvent evt) { About about =new About(); about.setVisible(true);}

private void saleReportiButtonActionPerformed(java.awt.event.ActionEvent evt) { long salesId = Long.parseLong(JOptionPane.showInputDialog("Enter Sales ID")); HashMap hashMap = new HashMap(); hashMap.put("salesid",salesId); MyiReportViewer myReportViewer = new MyiReportViewer("reports/sales.jasper", hashMap);

myReportViewer.setSize(desktopPane.getWidth(),desktopPane.getHeight()); desktopPane.add(myReportViewer); myReportViewer.setVisible(true); }

private void stockReportButtonActionPerformed(java.awt.event.ActionEvent evt) { MyiReportViewer myReportViewer = new MyiReportViewer("reports/stock.jasper");

myReportViewer.setSize(desktopPane.getWidth(),desktopPane.getHeight()); desktopPane.add(myReportViewer); myReportViewer.setVisible(true);

}

private void dailyReportButtonActionPerformed(java.awt.event.ActionEvent evt) { MyiReportViewer myReportViewer = new MyiReportViewer("reports/dailyIncome.jasper");


private void weeklyReportButtonActionPerformed(java.awt.event.ActionEvent evt) { MyiReportViewer myReportViewer = new MyiReportViewer("reports/weeklyReport.jasper");


private void yearlyReportButtonActionPerformed(java.awt.event.ActionEvent evt) { MyiReportViewer myReportViewer = new MyiReportViewer("reports/yearlyReport.jasper");


private void saleuiButtonActionPerformed(java.awt.event.ActionEvent evt) { SalesUI salesUI = new SalesUI(); salesUI.setBounds(300, 100,600,470); desktopPane.add(salesUI); salesUI.setVisible(true); }

private void customeruiButtonActionPerformed(java.awt.event.ActionEvent evt) { CustomerUI customerUI = new CustomerUI(); customerUI.setBounds(300, 150,447,305);

desktopPane.add(customerUI); customerUI.setVisible(true); }

private void systemExit1ActionPerformed(java.awt.event.ActionEvent evt) { System.exit(0); }

private void categoryuiButtonActionPerformed(java.awt.event.ActionEvent evt) { CategoryUI categoryUI = new CategoryUI(); categoryUI.setBounds(300, 200,452,200); desktopPane.add(categoryUI); categoryUI.setVisible(true); }

private void supplieruiButtonActionPerformed(java.awt.event.ActionEvent evt) { SupplierUI supplierUI = new SupplierUI(); supplierUI.setBounds(300, 150,430,320); desktopPane.add(supplierUI); supplierUI.setVisible(true); }

private void purchaseuiButtonActionPerformed(java.awt.event.ActionEvent evt) { PurchaseUI purchaseUI = new PurchaseUI(); purchaseUI.setBounds(300, 100,615,470); desktopPane.add(purchaseUI); purchaseUI.setVisible(true); }

private void productuiActionPerformed(java.awt.event.ActionEvent evt) { ProductUI productUI = new ProductUI(); productUI.setBounds(300, 150,470,250); desktopPane.add(productUI); productUI.setVisible(true); }

public static void main(String args[]) { new SplashScreen(5000); java.awt.EventQueue.invokeLater(new Runnable() { public void run() { new MainUI().setVisible(true); } }); }

// Variables declaration - do not modify private javax.swing.JButton categoryuiButton; private javax.swing.JButton customeruiButton; private javax.swing.JButton dailyReportButton; private javax.swing.JDesktopPane desktopPane; private javax.swing.JMenuItem exitMenuItem; private javax.swing.JMenu fileMenu; private javax.swing.JMenu helpMenu; private javax.swing.JMenuItem jMenuItem1; private javax.swing.JPanel jPanel1; private javax.swing.JPanel jPanel2; private javax.swing.JMenuBar menuBar; private javax.swing.JMenuItem openMenuItem; private javax.swing.JButton productui; private javax.swing.JButton purchaseuiButton; private javax.swing.JButton saleReportiButton; private javax.swing.JButton saleuiButton; private javax.swing.JMenuItem saveAsMenuItem; private javax.swing.JMenuItem saveMenuItem; private javax.swing.JButton stockReportButton; private javax.swing.JButton supplieruiButton; private javax.swing.JButton systemExit1; private javax.swing.JButton weeklyReportButton; private javax.swing.JButton yearlyReportButton; // End of variables declaration }

Program Specification:

Manager or salesman operates this system. Purchased products are saving to the database

and if any product are sold salesman are make a sales report using this software and as a

result database is update automatically.

Flowchart:

PROCESS

TERMINAL

DECISION

CONNECTOR

THE FLOW OF PROCESSING

Start

Customers Wanted to buy product

Input Product Information

Product Information is Correct

Save Information and Product Sold Information

in Sales File

Update Master Sales File

End

No

Yes

Conclusion:

In this project we have developed Mobile accessories shop management Software, which

will convert the manual system into the automated system. For this we have to look back to the

existing system and had to take different actions to run the automated program to its preferred

functions. The measure includes finding out the scope of the problem, study of current or

existing system, analyzing the system, designing the proposed system etc. This project mainly

aims to provide better customer service, save cost & save the time, easy to maintain production

management system and also provide very informative daily, weekly, yearly. We’ve developed

technologically thus making it suitable to stand beside their technical environment. By

implementing the proposed Mobile accessories shop management system. I hope it will be

easier for manage the system keep the records up to date that will enable Mobile accessories

shop management system to know the current shop condition.

Testing

Introduction:

On completion of each module the programmers go through extensive testing with factitious

data. Any Activity that checks by means of actual execution whether a system or component

behaves in the desired manner is called testing.

Testing Strategy:

The programmer can go through the program with his colleague explaining how it works. The

mere task of explaining the program in detail may cover the error or the colleague may spot the

error. We can insert lines of code, which simply print out the values of variables after various

sections of code have been executed. Comparison of the values with those that were expected

may identify where errors are occurring. Debugging utilities allowing the programmer to step

through each line of the program and dump out the values associated with variables at any

point for comparison with expectation.

System tested at each of the following levels

Unit Testing

System Testing

Installation Testing

Acceptance Testing

Integration Testing

Unit Testing:

Each program is tested and corrected until the test result is satisfactory. Unit which are

independent of one to another to locate errors. Program testing starts with the unit testing, the

smallest testable units are class that contains attributes and operations. This will enable to

detect errors in earlier.

System Testing:

Here the website will be tested as a whole to validate. Website testing are carried out within the

system.

Contrived System Test: This type of testing contains deliberate faults and errors aimed

at testing the validation and control procedures.

Real System Test: After contrived test, errors were detected and corrected. The real

test is then run the complete system. This comprises a test using a representation of

real data for which accrual results are available on the old system. The real test did not

show any additional problems. The full system testing is a form of training for all

concerned. The satisfactory completion of testing is a vital requirement before system is

implemented.

Installation Testing:

The new system will be installed and implemented in the user site in this stage. Here the main

objective is not the test data and result, our objective is to see that whether the system suits the

new environment or not i.e. new hardware.

Acceptance Test:

The user will carry out this entire testing, and will enter all real life data and check manually

there correctness. Several programs working together to form a run and this is tested.

Individual module tested separately. It is important to check the use of computer agree with the

planned requirement. For example, the personal information switches board itself is a program

consisting of a collection of some sub programs. This sub program has functions for entering,

editing, displaying, and printing of different reports.

Integration Testing:

Integration testing has to be introduced early for object oriented system because objects

seldom stand alone. To validated integration testing make sure that all employee information

comes from personnel module and any module can share project data.

Conclusion:

This stage tests most of the functions of the proposed system by the valid and invalid input of

data all the tested function is primarily working correctly. So we can come to the decision that

the system is now ready for live implementation. The further testing process will be carried out

at the user’s environment

System Implementation

Introduction:

The implementation of a new system will involve changing from a manual system to a

computerized system where both data and procedures will require to be changed. At this stage,

the developed system will go live that is at the process level. Implementation assembles

hardware and application together to see that they are compatible and are working properly in

the live environment.

Implementation Plan:

Before cut over the new system, many tasks need to be accomplished for example the required

master data must be assembled from the existing clerical files. The following steps will be

undertaken to complete the implementation plan successfully:

Hardware Setup:

The minimum hardware requirements for both the server PC and client PCs are as follows:

Server computer Pentium® Core i7

Client computers Pentium® Core i5 or Pentium® Core i3 of quantity three

Application components that need to be set up to the server are:

Database component (My SQL 5.0 server)

Network Setup:

Third party will involve setup the network between server pc and client PCs that need to run the

Mobile Accessories management System.

User Training:

The users of the new system can be trained by many methods as follows:

Manual user guide Visual style presentation A third party expertise in training users

Conclusion:

Implementation procedure describes details about how the new system will go live followed by

a set of steps that include data conversion, infrastructure setup, integration testing, procedure

conversion etc. At the end of this stage, if any proposed system follows this kind of procedures

for development of an application then that will be good and reliable application to use.

Reference:

Name of Book

1. Business System Analysis Published by NCC Education Ltd.

2. Business System Design Published by NCC Education Ltd.

3. Database System Published by NCC Education Ltd.

4. Java Cryptography Jonathan B. Knudsen, ISBN: 1-56592-402-9

5. Java Certified Programmer for Java 6 (SCJP) Study Guide By McGraw Hill “Kathy Sierra Bert Bates”

6. Java how to program By Deitel Deitel

Web Address

7. www.deitel.com 8. www.sun.com 9. forum.java.sun.com10. java.sun.com11. www.javalobby.com 12. www.programmersheaven.com 13. www.codeproject.com

http://www.programmersheaven.com/

http://www.javalobby.com/

http://www.sun.com/

http://www.deitel.com/