Vous êtes sur la page 1sur 17

CONTENS

S1.no TOPIC
1. TITLE OF THE PROJECT
2. OBJECTIVE OF THE PROJECT
3. PROJECT CATEGORY
4. TOOLS/PLATEFORM,LANGNUAGE TO BE USED
4.1 APPLICATION ENVIRONMENT
5. A COMPLETE STRUCTURE OF THE PROGRAM
5.1 ANALYSIS (DFD AND ER-DIAGRAM)

5.2 NUMBER OF MODULES AND THEIR DESCRIPTION

5.3 DATA STRUCTURES (TABLE etc.) OF ALL MODULE

5.4 PROCESS LOGIC FOR EACH MODULE

5.5 TYPE OF REPORT GENERATION

6. SCOPE OF FUTURE APPLICATION

1.Title of the project:


Sales system for Zeeyan international,
Noida.

2.Objectives of the project:


The proposed system is to
computerize keeping in views the problems. This system will make all processes
efficient, cost -Effective and user-friendly. The Zeeyan international specializes
in the area of celerity items for hotels, garments. It is the largest exporter of
celerity items and garments in the worlds.

We are called to develop software that will be used for carrying out
all the Activities performed in sales department of Zeeyan International. The
following Objectives have been identified for the current project :

•To provide facility to add order acceptance details, packing details, new
customer, new size of product, new specification of product, new
transporter, new product head, new product, new transporter rate.
•To provide facility to make sales enquiry, sales quotation, sales challan,
sales invoice.
•To provide facility to forward an invoice to accounts department.
•To provide facility to update customer, size, specification, transporter,
Product head, product, transporter rate.
•The option to generate various reports.

The proposed system is aimed to automate


all these processes. If we do this job manually, there will be lot of complexities and
computations involved.

3.Project category:
Internet based project using RDBMS concepts :

•Web Application by .net technology in ASP.NET using C#.NET


•ADO.NET using SQL SERVER
•Operating system as windows NT Server/Windows XP

4.Tools/platform/language to be used:
The following are the
Tools/Platform/Language, which will be used to develop the proposed
system:
Platform: Windows XP
Web Technologies: ASP.NET USING C#.NET, HTML
Database: ADO.NET USING SQL Server
Application Server: IIS 4.0 (Internet Information Server)
Browsers :Internet Explorer 5.0, Netscape Communicator 4.0
4.1 APPLICATION ENVIRONMENT:
The below mention hardware and software specification talk about the
minimum Needed to run the software as well as to install and use the tools associated in
the process:
•Microsoft Windows xp
•Microsoft Visual Studio.Net 2003
•Microsoft SQL Server 7.0
•Celeron ® cpu 2.26GHz Processor
•VGA card
•256 MB RAM for Application (This will vary depending upon the specific type
of libraries or DDLs that will be included in the application)

5. A complete structure of the program:

5.1 Analysis:

Normal requirements:
1.Graphical Displays:
(a) Intuitive key assignments and user interactive screen
(b) User configurable
2. Backup and restore facilities.
3. Search facilities

Expected Requirements:
These requirements are implicit to the product or system and may be so
fundamental
That the customer doesn't state them.
The following are listed:
1. Indexing
2. Ease of human/machine interaction.
3. Reliability and operational correctness.
4. Ease of software installation.
5. Single point data storage for each data element.
6. Maintenance of integrity and inter-linkages of data.
7. Extensive query facility to provide immediate answers for management.
8. Matching of physical and logical movement of file.
9. Should be upgradeable to incorporate new features.
10. Should be expendable.
11. Should have fastest possible response while processing queries, reports
and updates.
Exciting Requirements:
1. Customize update facility for customer details.
2. Error control mechanism.
3. Graphical animations.
4. Other look and feel appeals.
5. Mandatory field are marked with *
6. Short cut key facility.

Functional Requirement:
The current project in hand should have the following functional
requirements:
•System should provide the facility to make a new Sales Enquiry.
•It should support the feature to add some item in a previous Sales Enquiry.
•System should provide the facility to update the value of any desired field of an
existing
Sales Enquiry.
•System should provide the facility to search an existing Sales Enquiry.
•System should provide the facility to delete an existing Sales Enquiry.
•System should provide the facility to update an existing Sales Enquiry
•System should provide the facility to make a new Sales Quotation.
•System should provide the facility to update an existing Sales Quotation.
•System should provide the facility to search an existing Sales Quotation.
•System should provide the facility to delete an existing Sales Quotation.
•System should provide the facility to print an existing Sales Quotation.
•System should provide the facility to update an existing Quotation Mail Id.
•System should support insertion of Sales Order Acceptance details through
either directly or quotation.
•System should provide the facility to update an existing Sales Order
Acceptance details.
•System should provide the facility to search an existing Sales Order
Acceptance details.

•System should provide the facility to delete an existing Sales Order Acceptance
details.
•System should provide the facility to print an existing Sales Order Acceptance
details.
•System should provide the facility to update the value of any desired field of an
existing
Sales Order Acceptance details.
•System should provide the facility to insert Packing Details through order or
without order.
•System should provide the facility to search an existing Packing Details.
•System should provide the facility to delete an existing Packing Details.
•System should provide the facility to update an existing Packing Details.
•System should provide the facility to print Packing Sheet.
•System should provide the facility to make Challan.
•System should provide the facility to search an existing Challan.
•System should provide the facility to delete an existing Challan.
•System should provide the facility to update an existing Challan.
•System should provide the facility to print an existing Challan.
•System should provide the facility to make invoice.
•System should provide the facility to search an existing invoice.

5.2Number of modules and their description: -


MODULE Name: -
1. Sales Enquiry
2. Sales Quotation
3. Sales Order Acceptance
4. Sales Packing Details
5. Sales Challan
6. Sales Invoice
7. Administer Sales Systems
8. Sales Reports

Description of Modules: -

1. Sales Enquiry: The sales system begins with sales enquiry. In this
Module user can.
1.1 Create a new Sales Enquiry or add another product in the same Enquiry.
1.2 Search/Update/Delete an existing Sales Enquiry.
1.3 Customize update of Sales Enquiry.

2. Sales Quotation: When a Sales Enquiry is being made then company


Have to prepare a sales quotation containing product specific details. These
All function will be done in this module. But for clarity, I want to Depict all
function,
Which user can perform? That is as follows: -
2.1 Insert Sales Quotation
2.2 Search/Update/Delete an existing Sales Quotation
2.3 Print Quotation
2.4 Update Quotation Mail Id
2.5 Pending Enquiry
3. Sales Order Acceptance: When a sales Quotation is prepared then it
will be sent to customer. In reply of quotation customer sends an order
acceptance letter. Order acceptance can also be informed without any quotation
or enquiry (in case of regular customer). So I have to consider both cases.
These order acceptance details must be stored for future reference and on the
basis of order acceptance letter production order must be prepared and
forwarded to production department. These all function will be done in this
module. But for clarity, I want to depict all function that can be performed by
user. That is as follows: -
3.1 Insert Sales Order Acceptance details through quotation.
3.2 Insert Sales Order Acceptance details directly.
3.3 Search/Update/Delete an existing Sales Order Acceptance details.
3.4 Print Sales Order Acceptance details.
3.5 Customize update of Sales Order Acceptance details.
3.6 Print Production order details.

4. Sales Packing Details: - When a production order is arrived to


production department. It starts production on the basis of received details. Now when
production is prepared than will be sent to packing department where packing sheet will
be attached to these finished products. So it is important to store the packing details
because a single order may be delivered into many slots. In this module user can
perform following functions:-
4.1 Insert packing details through order.
4.2 Insert packing details without order.
4.3 Search/Update/ Delete an existing Packing details.
4.4 Print packing sheet.

5. Sales Challan: - In this module user can perform following functions :-


5.1 Insert Sales Challan
5.2 Search/Update/Delete an existing Sales Challan
5.3 Print Sales Challan

6. Sales Invoice: - In this module you can perform following functions: -


6.1 Insert Sales Invoice
6.2 Search/Update/Delete an existing Sales Invoice
6.3 Print Sales invoice, Hindi, bank Document
6.4 Forward Invoice to Accounts Department

7. Administer Sales System: - In this module user can perform


following
Functions: -
7.1 Add/Update Customer, Size, Specification, Transporter, Product Head,
Product,
Transporter Rate and Update HCL Rate.
7.2 Delete Customer
7.3 Customize Update for Customer details

8. Sales Report: -
This module will generate a number of Sales Reports, which may be proved
beneficial
For the business. At the same time it will assist the management to take
right decision
At right time. In this module user can generate following reports: -
8.1 Order Acceptance Register within a period
8.2 Dispatch within a period report
8.3 Daily dispatch territory wise report
8.4 Daily Challan report
8.5 Insurance statement for a period
8.6 Sale against form within a period

5.3 Data structure (tables etc) of all modules: -


1. Table Name: Zeeyan international

Field name length Data type


Enquiryld 50 Varchar
Enquiryld date Date time
Enquiryld reg no 16 Varchar
Enquiryld reg date Date time
Customer id 16 Varchar
Customer name 200 Varchar
Customer address 500 Varchar
Product id 16 Varchar
Product name 200 Varchar

5.4 Process logic for each module: -


The process specifications were developed considering the following points:
• The Users and system analyst must express the process specification in a
form that can be verified.
• Process specifications must be expressed in a form that can be effectively
communicated to the various audiences involved.
•A good process specification should specify what the policy is, not how the
policy is carried.

Structured English:
Structured English is used to document the logic of process. This method
makes
Use of narrative statements which shrike reasonable balance between the
precisions
Of a programming language and the casual informality and readability of the
English
Language.

DFD Level 2: Details of Sales Enquiry module

Bubble 1: Identification of user requirement


Sequential Structure:
Action 1: Take User Requirement
Action 2: Exit the bubble
Bubble 2: New Sales enquiry insert
Sequential Structure:
Action 1: Get the valid data about sales enquiry
Action 2: Save data in database
Action 3: Exit the bubble.

Bubble 3: Sales enquiry Search/ Update/ Delete


Sequential Structure:
Action 1: Get valid data about sales enquiry as per user choice
Action 2: perform appropriate action as per user choice
Action 3: Exit the bubble.
Bubble 4: Sales Enquiry Customize Update
Sequential Structure:
Action 1: Get the valid data about sales enquiry as per user demand
Action 2: Save updated data into database
Action 3: Exit the bubble.

DFD Level 2: Details of Sales Quotation module

Bubble 1: Identification of user requirement


Sequential Structure:
Action 1: Take User Requirement
Action 2: Exit the bubble
Bubble 2: New Sales Quotation insert
Sequential Structure:
Action 1: Get the valid data about sales quotation
Action 2: Save data in database
Action 3: Exit the bubble.
Bubble 3: Sales Quotation Search/ Update/ Delete
Sequential Structure:
Action 1: Get valid data about sales enquiry as per user choice
Action 2: perform appropriate action as per user choice
Action 3: Exit the bubble.
Bubble 4: Update Quotation Mail Id
Sequential Structure:
Action 1: Get the valid data about sales quotation to update quotation mail id
Action 2: Save updated data into database
Action 3: Exit the bubble.
Bubble 5: Pending Enquiry Details
Sequential Structure:
Action 1: Get the valid data about pending Sales enquiry
Action 2: Extract data from database and display
Action 3: Exit the bubble.
Bubble 6: Print Sales Quotation
Sequential Structure:
Action 1: Get valid data about sales quotation to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.

DFD Level 2: Details of Sales Order Acceptance module

Bubble 1: Identification of user requirement


Sequential Structure:
Action 1: Take User Requirement
Action 2: Exit the bubble
Bubble 2: New Sales Order Acceptance insert
Sequential Structure:
Action 1: Get the valid data about sales Order Acceptance
Action 2: Save data in database
Action 3: Exit the bubble.

Bubble 3: Sales Order Acceptance Search/ Update/ Delete


Sequential Structure:
Action 1: Get valid data about sales Order Acceptance as per user choice
Action 2: perform appropriate action as per user choice
Action 3: Exit the bubble.
Bubble 4: Sales Order Acceptance Customized Update
Sequential Structure:
Action 1: Get the valid data about sales Order Acceptance to update on user
demand
Action 2: Save updated data into database
Action 3: Exit the bubble.

Bubble 5: Print Sales Order Acceptance Details


Sequential Structure:
Action 1: Get the valid data about Order Acceptance to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.
Bubble 6 : Print Production Order
Sequential Structure :
Action 1: Get valid data about sales Order Acceptance to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.

DFD Level 2: Details of Sales Packing Details module

Bubble 1: Identification of user requirement


Sequential Structure:
Action 1: Take User Requirement
Action 2: Exit the bubble
Bubble 2: New Sales Packing Details insert through order/ without order
Sequential Structure:
Action 1: Get the valid data about sales packing
Action 2: Save data in database
Action 3: Exit the bubble.
Bubble 3: Search/ Update/ Delete an existing Sales Packing Details
Sequential Structure:
Action 1: Get valid data about Sales Packing Details as per user choice
Action 2: perform appropriate action as per user choice
Action 3: Exit the bubble.
Bubble 4: Packing Sheet Print
Sequential Structure:
Action 1: Get the valid data about Sales Packing Details to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.

DFD Level 2: Details of Sales Challan module


Bubble 1: Identification of user requirement
Sequential Structure:
Action 1: Take User Requirement
Action 2: Exit the bubble

Bubble 2: New Challan details insert


Sequential Structure:
Action 1: Get the valid data about sales Challan
Action 2: Save data in database
Action 3: Exit the bubble.
Bubble 3: Search/ Update/ Delete an existing Challan details
Sequential Structure:
Action 1: Get valid data about sales enquiry as per user choice
Action 2: perform appropriate action as per user choice
Action 3: Exit the bubble.
Bubble 4: Print Challan
Sequential Structure:
Action 1: Get the valid data about sales Challan to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.

• DFD Level 2: Details of Sales Invoice module

Bubble 1: Identification of user requirement


Sequential Structure:
Action 1: Take User Requirement
Action 2: Exit the bubble
Bubble 2: New Sales invoice insert
Sequential Structure:
Action 1: Get the valid data about sales invoice
Action 2: Save data in database
Action 3: Exit the bubble.
Bubble 3: Search/ Update/ Delete an existing Sales invoice
Sequential Structure:
Action 1: Get valid data about sales enquiry as per user choice
Action 2: perform appropriate action as per user choice
Action 3: Exit the bubble.
Bubble 4: Print Sales invoice/ Hindi/ Bank Document
Sequential Structure:
Action 1: Get the valid data about Sales invoice/ Hindi/ Bank Document to be
printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.
Bubble 5: Forward Invoice to Account department
Sequential Structure:
Action 1: Save data in accounts database
Action 2: Exit the bubble.

• DFD Level 2: Details of Administer Sales System


module

Bubble 1: Identification of user requirement


Sequential Structure:
Action 1: Take User Requirement
Action 2: Exit the bubble
Bubble 2: Add
Sequential Structure:
Action 1: Get user choice
Action 2: perform appropriate action as per user choice
Action 3: Exit the bubble.
Bubble 3: Update
Sequential Structure:
Action 1: Get user choice
Action 2: perform appropriate action as per user choice
Action 3: Exit the bubble.
Bubble 4: Delete Customer
Sequential Structure:
Action 1: Get the valid data about Customer to be deleted
Action 2: delete data from database
Action 3: Exit the bubble.
Bubble 5: Customized update for Customer
Sequential Structure:
Action 1: Get the valid data about Customer to be updated on user demand
Action 2: Save updated data into database
Action 3: Exit the bubble.

DFD Level 2: Details of Sales Reports module

Bubble 1: Identification of user requirement


Sequential Structure:
Action 1: Take User Requirement
Action 2: Exit the bubble
Bubble 2: Order Acceptance Register Within A Period report
Sequential Structure:
Action 1: Get the valid data about Order Acceptance Register to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.
Bubble 3: Dispatch Within A Period report
Sequential Structure:
Action 1: Get valid data about Dispatch to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.

Bubble 4: Daily Dispatch Territory Wise Report


Sequential Structure:
Action 1: Get the valid data about Dispatch to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.
Bubble 5: Daily Challan report
Sequential Structure:
Action 1: Get the valid data about Challan to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.
Bubble 6: Insurance Statement For A Period Report
Sequential Structure :
Action 1: Get valid data about Insurance Statement to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble.
Bubble 7 : Sale Against Form within A Period Report
Sequential Structure:
Action 1: Get valid data about Sales to be printed
Action 2: Extract data from database and display
Action 3: Exit the bubble

5.5Types of report generation:


The following reports will be generated
• Order Acceptance Register within a period
• Dispatch within a period
• Daily dispatch territory wise
• Daily Challan (transport)
• Insurance Statement for a Period
• Sale against form within a period

6. Scope and future enhancement of the project : -


This system may have following future application :-
• This System with some modification can be used to develop Export system
of any Manufacturing Company.
Zeeyan
Zeeyan international
international sales
sales quotation
enquiry
Zeeyan international order acceptance
Zeeyan international packing details
Zeeyan international product head master
eeyan international chalan details
Zeeyan international product master
Zeeyan international invoice general

international LrRcompany master Zeeyan international transport rate master