Vous êtes sur la page 1sur 52

AUTO ANCILLARIES LIMITED

A project report submitted to


Mahatma Gandhi University
Meghalaya
In Partial Fulfillment of the requirement for the award of the
degree
Bachelor Of computer Application
(Information Technology)
2013-2016

Submitted By
Name of the student: ABDALLA ALI
MGU/132/RNS/280172/008
Under the Guidance of
Lecturer: Partha Bora, (MCA)
Aptech Computer Education
Castle Street, Bangalore

Table of contents

Table of contents.....................................................................................................................3
Definition of the problem........................................................................................................4
Customer Requirement Specification......................................................................................5
Project plan..............................................................................................................................6
Requirement Analysis.............................................................................................................8
ER/Class Diagram...................................................................................................................9
Table design...........................................................................................................................10
Relationship Diagram............................................................................................................11
Program Design.....................................................................................................................12
GUI Design...........................................................................................................................13
Task sheet..............................................................................................................................14
Unit Testing Checklist...........................................................................................................15
Final checklist.......................................................................................................................16
APPENDIX A Source Code...............................................................................................17
APPENDIX A User guide..................................................................................................18
APPENDIX B Install guide................................................................................................19
COMMENTS OF FACULTY...............................................................................................20

Mahatma Gandhi University


Bachelor Of computer Application
(Information Technology)

CERTIFICATE

This is to certify that Abdalla Ali a Student Of BCA 6th Semester 3rd year
Has Successfully Completed AUTO ANCILLARIES LIMITED Project
Under the Guidance Of Mr. Partha Bora (Lecturer). During the year 20132016 in partial fulfillment of BCA(Information Technology) Examination
Conducted By Mahatma Gandhi University, Meghalaya.

Signature of External Examiner


Lecturer

Signature of

Definition of the problem

After discovering the AAL Company situation recently, we realize your Invoicing &
Finished goods handling is too complex and heavy because every companys departments as
well as customers focus into this system. Hence there are problems.

There is no automation involved to speed up the distribution process or any other


business process.

Credibility with customers seems to be declining recently due to slip-ups on


customer order processing and dispatches.

Finished goods stock is not being managed properly and holding costs are high.

Difficulties in communication and updating data due to distributed set up.

Maintaining stocks at ware houses

Preparing Invoices as well as dispatching the related documents and routing them
to relevant departments or locations.

Calculating discounts and other taxes and levies

Delivering material in time

Categorizing items as Fast or Slow moving while controlling inventory

Prioritizing orders based on customer requirement and distance

Increasing material rejection from customers

Discrepancy between ordered and invoiced quantities due to either partial


availability of stocks or due to clerical oversights.

Insufficient checks in the current system for ensuring customer credit limits are not
exceeded.

Analyzing sales data to streamline production volumes.

Solution

According to the problems above, we suggest a solution building a website which can make
them become more easier to handle, it is the main bridge from company to the customer and
company itself. Website provide can handle all companys information, product information,
product management, payment, dispatch, summarize sales
There are functions in details:

Registration of Member (Customer) to the Site

Creation, Maintenance and Updating of Database, which will contain

Information regarding all transactions made

Details of Customers

Details of the Warehouses

Details of items and stocks

Details of the purchase orders

Details of invoices

Details of Material rejections

Login and verification

Entering query parameters by the user (Inventory status of company, rating of the
customer, outstanding with the companies etc)

The company databases should maintain the following

Details of customers

Other information like inventory, order status etc. that it wants to forward to the
service

Transmitting the queries to the servers of each Company.

Each server has to perform the search as per the query parameters.

The server has to transfer the data to the Web Site.

Presenting the result to the user in a consolidated format.

Accepting order booking from user.

Forwarding booking request to the particular Company server.

The order should be booked, server database updated in terms of availability.

The billing for the order is to be calculated taking into account the customer
entitlements in terms of discount and credit period.

The member account should be updated in terms of finances and transactions.

Customer Requirement Specification

Client: Mahatma Gandhi University


Business / Project Objective: Abdalla ali
Customer: Auto Ancillaries Limited
Project Target : Have an overview of college activities.
Customers Input Request:
-

System Input: Information about Customers, the Orders, and all about the
Producer: activities, capital, products
System output: The information is processed and display to the user, companys
sales, best-selling products. The user can access to view the information and direct
purchase online.
Process involved in system: The Company provides selling mechanism, products
price, past activities, warranty policy, the discount...
Delivery date: 24/06/2016

Hardware Requirements:
-

Processor intel core i3, i5, i7 2310m


Recommended: 2.10Ghz
RAM :8 GB
Available Hard Disk Space :4Gb and more
Video :1080 pix HD

Software Requirement:
-

Operate System Software:


A computer with Windows 7 windows 8,8.1,10
Internet Information Service 8 and more
Browser IE6 or opera and more
Net framework 2.0, 3.3.5
Sql server 2008
Development System Software:
Visual Studio 2005
SQL Server 2005
Adobe Dreamweaver CS3
Adobe Photoshop CS3
Adobe Flash CS3
Adobe Firework CS3

ASP.NET 2.0 AJAX Extensions

Ranger of Work :
Base on the common consent about the website management of the customer,
following is the basic requirements that website need to perform :
-

Verify and authorize administrator, user.


Create menu with catalogue and information of Companys products.
Customers can download companys quotation
Customers can purchase directly on the website

Project plan
Project details

Name of the Client: Auto Ancillaries Limit

Date of Project Plan: 17-JUNE-2016 to 24-JUNE-2016

Project Vision/ Objectives:


(Define the project vision/objective as stated by the client)

Scope:
(Mention the scope of the project giving the locations that will be covered, process,
range of services, etc.)

Our understanding of the client organization:


(Give the range of services, functions, overviews of the processes, etc.)

Project Organization with Responsibilities and Authorities:


Project : ABDALLA

ABDALLA ALI

Project initiation/Requirement documents


(Information required from the Client as inputs regarding his system, could be the information
about his services, process)

Deliverables
(The documents to be handed over to the client like CRS, Design Document, Installation
Manual, User Manual, Maintain Manual, Code documents)

Project Dependencies
(Any event or task outside the scope of the project, which will effect the success of the
project)

Quality plan

Review activities (review meeting participants, frequency)

Testing activities

Backup and recovery strategies

Requirement Analysis
1. Architecture & Design of Project

ASPX Page
Tier 1
Presentation Tier

Tier 2

Bussiness Logic-Class
and

Middle Tier

Components

Tier 3
Database Tier

Database SQL server

2.Usecase Model:
2.1 Actors:
- Admin
- Manager
- Customer
2.2 Use case Diagram:

2.3 Use case Description:


2.3.1 Use Case for Sale System
1.Use case for Customer View Catalog

Use case

Customer view catalog

Description

Customer visit website and view product catalog

Actor

Customer

Pathway

Primary

Steps

1. Click products navigation button


2.Display catalog

Variations

None

Non - Functional

None

Issues

None

2. Use Case for Customer View Product


Use case

Customer view product

Description

Customer visit website and view product

Actor

Customer

Pathway

Primary

Steps

1. Click on catalog
2.Display correlative a list of products

Variations

None

Non - Functional

None

Issues

None

3. Use Case for Customer adds item

Use case

Customer adds item

Description

Customer select an item and adds it to the current cart

Actor

Customer

Pathway

Primary

Steps

1. Customer adds item form list products


2. Item is added to cart
3. Updated cart is displayed

Variations

None

Non - Functional

None

Issues

None

4. Use Case for Customer removes item

Use case

Customer removes item

Description

Customer view cart and remove item from cart

Actor

Customer

Pathway

Primary

Steps

1. Customer removes item from current cart


2. Item is removed from cart
3. Updated cart is displayed

Variations

None

Non - Functional

None

Issues

What if customer remove all item in cart?

5. Use Case for Customer update cart

Use case

Customer update cart

Description

Customer view cart and update item in current cart

Actor

Customer

Pathway

Primary

Steps

1. Customer change the item amount in current cart


2. Item amount is changed
3. Updated cart is displayed

Variations

None

Non - Functional

None

Issues

What if item amount equal zero ?

6.UseCase for Customer check out

Use case

Customer check out

Description

Customer logs in, enter shipping and payment details and complete order

Actor

Customer

Pathway

Primary, Exception

Steps

1. Customer enter username and password


2. Username and password are checked
3. Current cart is displayed
4. Customer enter shipping details
5. Customer enter payment details
6. Customer completes order
7. Order is created
8. Customer receives receipt
9. An email contain order details will be sent

variations

Exemption Invalid customer


#3. Customer informed that username/password invalid

Non - Functional

None

Issues

How does customer register?


How does customer abandon order before completing?

7.Use Case for Customer searches

Use case

Customer searches product

Description

Customer visits website and searches product

Actor

Customer

Pathway

Primary, Exception

Steps

1. Customer enter keyword to search


2. Search result is displayed

Variations

Exception invalid keyword


#2. Display warning that user enter valid keyword for searching

Non - Functional

None

Issues

Can customer search by category, by price, by hot products ?

2.3.2 Use Case for Ware House System


1a. Use Case for Manager adds category

Use case

Manager adds category

Description

Manager gets in Ware House management page and adds category

Actor

Manager

Pathway

Primary

Steps

1. Add new category


2. Updated categories are displayed

variations

None

Non - Functional

None

Issues

None

2a. Use Case for Manager edits category

Use case

Manager edits category

Description

Manager gets in Ware House management page and edits category

Actor

Manager

Pathway

Primary

Steps

1. Change/Delete category
2. Updated categories are displayed

variations

None

Non - Functional

None

Issues

None

3a. Use Case for Manager adds product

Use case

Manager adds product

Description

Manager gets in Ware House management page and adds product

Actor

Manager

Pathway

Primary

Steps

1. Choose category for adding product


2. Add new product
3. Updated list of products are displayed

variations

None

Non - Functional

None

Issues

None

4a. Use Case for Manager edits product

Use case

Manager edits product

Description

Manager gets in Ware House management page and edits product

Actor

Manager

Pathway

Primary

Steps

1. Change/Delete product
2. Updated list of products are displayed

Variations

None

Non - Functional

None

Issues

What if Manager remove all product which belong to a category

5a. Use Case for Manager views rejection product report

Use case

Manager views rejection product report

Description

Manager gets in Ware House management page and views rejection product
report

Actor

Manager

Pathway

Primary

Steps

1. Reads rejection product report


2. Make report about bad sell product

Variations

None

Non - Functional

None

Issues

None

6a. Use Case for Manager calculates income


Use case

Manager calculates income

Description

Manager gets in Ware House management page and calculates income

Actor

Manager

Pathway

Primary

Steps

1. Query finished orders by day/month/year


2. Calculate the overturn

Variations

None

Non - Functional

None

Issues

None

7a. Use Case for Manager process order


Use case

Manager process order

Description

Manager gets in Ware House management page and process order

Actor

Manager

Pathway

Primary, Exception

Steps

1. View order status


2. Check payment
3. Send items

variations

Exception payment does not complete


#3. Send email inform customer about required date for payment

Non - Functional

None

Issues

What if required day for payment expired?

1b. Use Case for Admin checks income

Use case

Admin checks income

Description

Admin gets in Ware House management page and checks income

Actor

Admin

Pathway

Primary

Steps

1. Query income
2. Display income after and before tax

variations

None

Non - Functional

None

Issues

None

2b. Use Case for Admin checks good/bad sell product

Use case

Admin checks good/bad sell product

Description

Admin gets in Ware House management page and checks good/bad sell
product

Actor

Admin

Pathway

Primary

Steps

1.Display good and bad sell product

variations

None

Non - Functional

None

Issues

None

3b. Use Case for Admin adds Ware House

Use case

Admin adds Ware House

Description

Admin get in Ware House management page and adds new War House

Actor

Admin

Pathway

Primary

Steps

1. Add new Ware House


2. Updated list of Ware Houses are displayed

variations

None

Non - Functional

None

Issues

None

4b. Use Case for Admin Changes Ware House information


Use case

Admin changes Ware House information

Description

Admin get in Ware House management page and changes War House
information

Actor

Admin

Pathway

Primary

Steps

1. Display each Ware House information


2. Change Ware House information
3. Updated list of Warehouses are displayed

variations

None

Non - Functional

None

Issues

None

2.3.3. Use Case for Account System


1a. Use Case for Admin adds Manager

Use case

Admin adds Manager

Description

Admin get in Account management page and adds new Manager

Actor

Admin

Pathway

Primary

Steps

1. Add new Manager


2. Updated list of Manager are displayed

variations

None

Non - Functional

None

Issues

None

2a. Use Case for Admin edits Manager

Use case

Admin edits Manager

Description

Admin get in Account management page and edit Manager

Actor

Admin

Pathway

Primary

Steps

1. Change/Delete Manager
2. Updated list of Manager are displayed

variations

None

Non - Functional

None

Issues

None

1a. Use Case for Manager delete Customer

Use case

Manager delete Customer

Description

Manager get in Account management page and delete Manager

Actor

Admin

Pathway

Primary

Steps

1. Delete Customer
2. Updated list of Customer are displayed

variations

None

Non - Functional

None

Issues

None

1b. Use Case for Manager sets discount rating

Use case Manager sets discount rating


Description

Manager get in Account management page and discount rating

Actor

Manager

Pathway

Primary

Steps

1. View Customers orders history


2. Set discount rating

variations

None

Non - Functional

None

Issues

None

1c. Use Case for Customer register account

Use case

Customer register account

Description

Customer register an account

Actor

Customer

Pathway

Primary, Exception

Steps

1. Ask user name and password


2. Check existence username
3. Confirm password
4. Ask personal information
5. Ask secret question
6. Ask credit card/bank account number
7. Register complete
8. New Customer account is created
9. Send mail contain username and password

variations

Exception username exist


3# Inform customer change another username
Exception confirm password fail
4# Inform customer retype password correctly
Exception invalid input
7# Inform customer enter valid value

Non - Functional

None

Issues

None

2c. Use Case Customer update account info


Use case

Customer update account information

Description

Customers manage their account

Actor

Customer

Pathway

Primary

Steps

1. Customer logs in
2. Customer changes account informations
3. Update account info

variations

None

Non - Functional

None

Issues

None

3c. Use Case for Customer tracks order history


Use case

Customer tracks order history

Description

Customer tracks their order history

Actor

Customer

Pathway

Primary

Steps

1. Customer login
2. Display customers order history

variations

None

Non - Functional

None

Issues

None

3.Activity Diagram :
Sale System Activity Diagram

Account System Activity Diagram

Ware House System Activity Diagram

III . Design
1.Table Design
Table: Categories

Field

Data type

Null

Key

References
Tables

Description

Category ID

Int

No

PK

Uniquely
identifies
each
Category

Ware House
ID

Int

No

FK

Category
Name

varchar(30)

No

Stores the
name of
Category

Description

text

Yes

Stores the
content of
Users
Desription

Ware House

Uniquely
identifies
each Ware
House

Table: WareHouse

Field

Data type

Null

Key

WareHouseID

int

No

PK

FactoryID

int

No

FK

References
Tables

Description
Uniquely
identifies
each
WareHouse

Factory

Uniquely

identifies
each Factory
WareHouseName nvarchar(30)

Location

No

Stores the
name of
WareHouse

nvarchar(100) No

Stores the
location of
the Ware
House

Table: Factory

Field

Data type

Null

Key

FactoryID

Int

No

PK

CompanyID

Int

No

FK

References
Tables

Description
Uniquely
identifies
each Factory

Company

Uniquely
identifies
each

FactoryName nvarchar(50)

No

Stores the
Name of the
Factory

Description

No

Stores the
Description
of the Factory

ntext

Table: Company

Field
CompanyID

Data type
int

Null
No

Key

References
Tables

PK

Description
Uniquely
identifies the
Company

CompanyName varchar(50)

No

Stores the
name of our
Company

Description

varchar(500)

No

Stores the
Description
of the
Company

Address

varchar(50)

No

Stores the
Address of
the Company

Phone

bigint(50)

No

Stores the
Phone
number of the
Company

Logo

image

No

Stores the
Images of the
Company

Table: Products

Field

Data type

Null

Key

Product ID

Int

No

PK

Category ID

Int

No

FK

References
Tables

Description
Uniquely
identifies the
Product

Categories

Uniquely
identifies the

Category
Review ID

Int

No

FK

Review

Uniquely
identifies the
Review

ProductName nvarchar(70)

No

Stores the
Name of the
Product

Unit Price

money

No

Stores the Price


of the Product

Units In
Stock

stalling

No

Stores the
available
number of the
Product

Units On
Order

stalling

Yes

Stores the
number of the
Product that on
Order

Features

ntext

No

Stores the
Feature of the
Product

Description
Brief

ntext

Yes

Stores the
Description
Brief of the
Product

Description

ntext

Yes

Stores the
Description of
the Product

Picture

varchar(MAX) No

Stores the
Picture of the
Product

Rating

float

Stores the
Rating that user
voted for a
Product

Yes

Table: Orders

Field

Data type

Null

Key

References
Tables

Description

Order ID

Int

No

PK

Uniquely
identifies the
Order

User Name

varchar(50)

No

FK

Account

Stores the
Name of User

Ship ID

Int

No

FK

Ship

Uniquely
identifies the
Ship method

Order Date

Date time

No

Stores the
Date of the
Order

Require
Date

Date time

No

Stores the
Date of the
Limited Days
for Payment

Shipped
Date

Date time

Yes

Stores the
Date of
Shipping that
completed

Ship Name

Varchar
(MAX)

No

Stores the
Customers
Name that
Item will be
delivered

Ship
Address

Varchar
(MAX)

No

Stores the
Address that
Item will be
delivered

Ship City

varchar(MAX) No

Stores the
City that Item
will be
delivered

SubTotal

decimal(18, 0)

Yes

Stores Sub
Total of the
Order

Table: Orders Details

Field

Data type

Null

Key

References
Tables

Description

Order ID

int

No

PK,FK

Orders

Uniquely
identifies the
Order

Product ID

Int

No

PK.FK

Products

Uniquely
identifies the
Product

Unit Price

money

No

Stores the
Price of
Product

Quantity

Small int

No

Stores the
Quantity of
Product

Total

Decimal(18,0) No

Table: Account
Field

Data type

Null

User Name

varchar(50)

No

Password

varchar(30)

No

Secret
Question

varchar(MAX) No

Key
PK

References
Tables

Description
Uniquely
identifies the
User Name
Stores the
Password of
User
Stores the
Secret

Question of
User
Secret
Answer

varchar(MAX) No

Stores the
Secret
Answer of
User

Role

char(10)

No

Stores the
Role of User

Discount

float

Yes

Table: Customers

Field

Data type

Null

Key

References
Tables

Description

Customer ID

int

No

PK

Uniquely
identifies the
Customer

User Name

varchar(50)

No

FK

First Name

varchar(50)

No

Stores the First


Name of the
Customer

Last Name

varchar(50)

No

Store the Last


Name of the
Customer

Date Of Birth Date time

No

Stores the
Birthday of the
Customer

Email

varchar(100)

No

Stores the
Email of the
Customer

Address

varchar(MAX) No

Account

Uniquely
identifies the
User Name of
the Customer

Stores the

Address of the
Customer
City

varchar(30)

No

Stores the City


of the
Customer

Phone

varchar(20)

No

Stores the
Phone number
of the
Customer

Bank Name

varchar(100)

No

Stores the
Name of the
Bank that
Customer had

Account
Number

varchar(30)

No

Stores the
Bank Account
Number of the
Customer

Tax code

char(10)

Yes

Table: Ship

Field

Data type

Null

Key
PK

References
Tables

Description

Ship ID

Int

No

Uniquely
identifies the
Shipping
Method

Ship Via

varchar(50)

No

Stores the
Shipping
method

Price

decimal(18, 0)

No

Stores the
Price of the

Shipping

Table: Review

Field

Data type

Null

Key

References
Tables

Description

ReviewID

Int

No

PK

Uniquely
identifies the
Users
Review

Product ID

Int

No

FK

Products

Uniquely
identifies the
Product

Review Title

varchar(MAX)

Yes

User Name

Varchar (50)

No

FK

Account

Uniquely
identifies the
User Name

Contents

ntext

No

Stores the
content of the
Review

Review Rating

Int

Yes

Stores the
Rating of the
Product

Review Date

Date time

No

Stores the
Date Review

Relationship Diagram

Program Design
Presentation Tier: UI
Form/Dialog/Report Name
EditCategory.aspx

Type
Webpage

EditProduct.aspx

Webpage

EditWareHouse.aspx

Webpage

aboutus.aspx
billing.aspx
ChangePassword.aspx
checkoutcomplete.aspx
checkouterror.aspx
EditPersonalInformation.aspx
ForgotPassword.aspx
home.aspx
product.aspx
productdetail.aspx
searchresult.aspx
shoppingcart.aspx
signup.aspx

Webpage
Webpage
Webpage
Webpage
Webpage
Webpage
Webpage
Webpage
Webpage
Webpage
Webpage
Webpage
Webpage

GUI Design

Description
For admin
Use to manage Category: update or
delete a Category
For Admin
Use to manage Products: insert update
or delete a Product
For Admin
Use to manage Warehouse

Home Page

Products Page

III . Design43

Products Details Page

III . Design44

Shopping Cart Page

III . Design45

Biiling Information Page

III . Design46

Recipt Page

III . Design47

My Account Page

III . Design48

Unit Testing Checklist


Testing Parameter

Result (yes/no)

Fields in forms should be not null

Yes

Check date input in form Table booking is valid

Yes

Check time input in form Table booking is valid

Yes

All restaurant in Table booking is loaded to drop down list

Yes

All type of food is loaded to drop down list

Yes

Account number is required all form

Yes

Email is valid

Yes

Final checklist
Aspect tested

Result (yes/no)

Is the problem define correctly deduced from the project abstract

Yes

All relevant documents have been done

Yes

Are all program codes working?

Yes

Are the codes working as per specifications?

Yes

Are all webpages working?

Yes

Is the GUI design consistent all over?

Yes

Does the GUI development tally with design

Yes

APPENDIX A Source Code

APPENDIX A User guide

COMMENTS OF FACULTY

Vous aimerez peut-être aussi