Josekin VIVA Book

CHAPTER 1 - INTRODUCTION
1.4
Purpose
The main objective of SRS is to illustrate the requirements of the project

AUTOMATED DISTRIBUTOR MANAGEMENT SYSTEM The document is
intended for the definition of the requirements that are necessary for the development of
the software. This specification is the primary document, upon which all the subsequent
design, implementation, test/validation plan will be based upon.
2.4
Document Conventions
All main titles are written in bold. Unless otherwise noted, all requirements
specified here are of high priority and committed for release 1.0.
This document is written in the following style.
1.3
Font Style
- Bookman Old Style
Headings
- 14
Sub headings - 12
Data
- 12
Intended Audience and Reading Suggestions
Developers: The project developers use the SRS in order to be sure they are developing
the right project that fulfills requirements provided in this document.
Testers: The testers use the SRS in order to have and exact list of the features and
functions that have to respond according to requirements and provided diagrams.
Users: The user of the system uses the SRS in order to get familiar with the idea of the
project and suggest other features that would make it even more functional.
Documentation writers: SRS helps documentation writers know what features and in
what way that have to explain. What security technologies are required, how the system
will respond in each user actions etc.
Advanced end users, end users/desktop and system administrators: In order to know
exactly what they have to expect from the system, right inputs and outputs and response
in error situations
1.4
Project Scope
A manufacturing company doesnt sell their products directly. Using distributors

only they sell their goods and distribute it. So a company maintains the distributor
information, product information, stock availability. The registered distributor can view
their dealership, personal information, and product sales. According to this information
the performance about the distributors is analyzed and some discounts are given to the
distributor
CHAPTER 2 THE OVERALL DESCRIPTION

2.1 Product Perspective
2
The proposed system, automated distributor management system is used to

maintain the distributing process in manufacturing company. The distributor applies the
dealership that can be approved by the authorized person. The distributor pays the
advance payment to the company that is providing purchasing authority. The distributor
can also cancel the purchase if any damages occurs.
2.2 Product Features
The product has got a login page where administrator/distributor can login once
he has registered. Administrator gets into a page with higher privileges than the
distributors. New distributor can apply the distribution dealership that is approved by a
administrator. After the confirmation of the dealership distributor can register their
information.
The administrator handles the employee management, distributor performance
analysis and company turn over and can view all the reports generated. Authenticated
distributors can also view their dealership information, cancel their order.
2.3 User Classes and Characteristics
The two classes of users in this application are administrator and distributors.
Administrator will be provided with the highest level of access control whereas the
distributors will be granted authentication to resources based on their dealership.
2.4 Operating Environment
Hardware Specification
Processor
-Intel Pentium 3
Memory
-64 MB SDRAM
Hard disk
- 2.2 GB or above
Monitor
-14 inch VGA Monochrome
Keyboard
-101 keys
Pointing device
- Mouse
Software Specification
Programming Language ASP.NET
Operating System
-Windows NT, Windows 2000/XP.
Database Used
-SQL Server2000.
2.5 Design and Implementation Constraints
The product is developed using ASP.NET. The backend database used is SQL Server.
The product is accomplished with login facility so that specific function is available to
specific user.
2.6 User Documentation
The user documentation provides components such as
User manuals
On-line help
2.7 Assumptions and Dependencies

The product needs following third party product.
Microsoft SQL server to store the database.
ASP.NET using C# to develop the Product
The users have the basic knowledge of using a computer
and internet.
CHAPTER 3 SYSTEM FEATURES
This section describes in detail the various feature of this software. They
are listed below
3.1 Dealership Approval Module

3.1.1 Description and Priority
The distributor sends his information to the administrator. The administrator

verifying the information approves the dealership of the distributor.
3.1.2 Stimulus/Response Sequences
Stimulus:
Distributor enters his details.
Response:
Administrator approves the dealership.
2.1.3 Functional Requirements

Purpose:
dealership approval
Inputs:
Distributors information.
Processing:
Validating Distributors information.
Outputs:
Generates userif and password for the distributor
3.2 Login module

The project is accessed by the distributor and administrator by entering a valid
username and password. This phase has highest priority as it handles the authentication.
Stimulus:
User enters the valid user id and password.
Response:
User will be logged in successfully.
Purpose:
Login
Inputs:
User id and password.
Processing:
Validating the user id and password.
Outputs:
Successfully logged in.
3.3 Distributor module

The distributor can approve dealership, purchasing product from a company
and login to the distributor page. User is provided with these priorities.
Stimulus:
Enters the distributor information
Response:
Distribution registration is successful and can view reports.
The distributors can also purchasing goods.

Purpose:
Access the data
Inputs:
Enter distributor and purchasing details
Processing:
Authorizing the distributor
Outputs:
Distributor is registered, purchase details. The

report can be viewed.
3.4 Order Module

The distributor views for the available products. If the product is needed by the
distributor he orders the product form the company.
Stimulus:
Viewing and ordering.
Response:
Bill from the company for the purchased products.

Purpose:
Ordering the products
Inputs:
Selecting the needed products.
Processing:
Preparation of bill for the purchased products.
Outputs:
Bill is generated.
3.5 Payment Module

The Distributor verifies the ordered products. After the ordered products the payment is
calculated how much they are ordering.
Stimulus:
Distributor verifies the products.
Response:
Payment is calculated.
Purpose:
Verifying and returning the products.
Inputs:
Orders and Product information
Processing:
Calculating the payment
Outputs:
Payment is calculated automatically
CHAPTER 4 - SOFTWARE REQUIREMENT SPECIFICATION

4.1 External Interface Requirements
4.1.1 User Interfaces
The user interface will be a GUI. User friendly menus and screens will be
provided. The screens are designed using forms, buttons, labels and textboxes. Necessary
menu controls and other controls have been used to make the system more users friendly.
The users will access the screens according to their role after entering their id and
passwords.
4.1.2 Hardware Interfaces
Automated distributor management is a web-based project. So any personal
computer, which has an internet browser, is enough to use this system.
4.1.3 Software Interfaces
Database:
SQL Server;
Application:
ASP.NET with C#
Web Server :
IIS (Internet information services (IIS) is a powerful Web
server that provides a highly reliable, manageable, and scalable Web application
infrastructure)
4.1.4 Communications Interfaces
Web Server: The web server is used to store and run the application. Clients can access
the application from Web Server.
Web Browser: Any browser that supports HTML 4.0 has JavaScript enabled and
supports flash and cookies, e.g. IE or higher, Mozilla Firefox 2.0 or higher, Oprah,
Netscape Navigator.
Protocols:Communication protocol: HTTP

Mail Transfer Protocols and Formats: TBD
Security Protocols: TBD
The Communication Interface device can either be a Network Interface Card
(NIC).Modem or VSAT (Very Small Aperture Terminal).
4.2 Other Non Functional Requirements
4.2.1 Performance Requirements
Non blocking I/O
Cross browser compatibility.
Allows concurrent access to multiple users
4.2.2 Safety Requirements

Our product can not cause loss of user data. The data entered into the system
should be valid. In the event of a server hard disk problem, your details backed up on a
daily basis. So the data is safe.
4.2.3 Security Requirements
Access to your information through our internet application is determined by you
on a per web folder basis. Security checks are employed throughout our internet
application to ensure that only you and your explicitly invited users have access to your
secured documents. Only authenticates users are able to access the documents. Only
administrator is able to update the details.
10
4.2.4 Software Quality Attributes

The web site needs to be easily useable and flexible to work for the most amounts
of people to bring in the most amounts of people to bring in the most traffic.
11
CHAPTER 5 - SOFTWARE DESIGN SPECIFICATIONS
5.1 Architectural Design

5.1.1 Section Overview
The basic role of architectural design notations is to facilitate mapping of
functional and data specifications into individual modules. In addition to this, the flow
of data between modules, and the conditions of a given module are all represented in
the architectural design section.
In the general constraints section, the global constrains like hardware and
software constraints, performance and network constraints are presented. The database
design section deals about the database design such as the structure of the database,
and naming conventions and normalization.
In program structure, the architectural model chosen, its major
components are discussed.
5.1.2 General Constraints

The proposed application is working efficiently by meeting the constraints
such as hardware and software requirements which are listed below.
HARDWARE PROFILE
Processor
: Any 32-bit Processor
Speed
: 2.44GHZ
RAM
: 128MB
Hard disk
: 40GB
SOFTWARE PROFILE
Operating System
: Windows 2000 Professional
Front End
: ASP.NET with C#
Back End
: SQL SERVER 2005
12
Automated Distributor Management System is a web-based project. So

any personal computer, which has an internet browser, is enough to use this system.
Using three classes Response time, throughput and concurrency, the performance is
assessed. The network has been established by the full support of TCP/IP and HTTP
protocols.
5.1.3 Database Design
The database is implemented by using SQL Server. The following
is the database design of the application.
Normalized Tables
1. Table Name: distributor
Table description: Stores the distributor details to register.
Field Name
Dist_id
Data Type
Varchar
Size
8
Constraint
Primary key
Description
Id identifies the distributor table
Dist_name
Dob
Gender
Address
Date
Email
Phone
Dep_amount
Scheme_id
comp_id
Username
Password
Varchar
Datetime
Varchar
Varchar
Datetime
Varchar
Int
Varchar
Varchar
Varchar
Varchar
Varchar
25
10
6
25
10
25
14
9
8
8
15
15
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Not null
Foreign Key
Foreign Key
Not Null
Not Null
First name of the distributor

Date of birth of the distributor
Gender of the distributor
Address of the distributor
Date of registering
Email Id of the distributor
Phone number of the distributor
Deposit amount of registration
Id references the scheme table (sheme_id)
Id references the company table (comp_id)
Username of the distributor
Password of the distributor
2. Table Name: Schemes

Table description: Stores the Scheme details.
Field Name
Scheme_id
Data Type
Varchar
Size
8
Constraint
Primary key
Description
Id identifies the scheme table
Scheme_name
Sche_Ch_date
Varchar
Datetime
15
10
Not null
Not null
Scheme name
Scheme choosing date
13
Scheme_level
Duration
Scheme_amt
Varchar
Varchar
Varchar
15
6
15
Not null
Not null
Not null
Scheme level
Duration
Scheme amount
3. Table Name: Products

Table description: Stores the product details.
Field name
Data type
Size
Constraints
Description
pro_id
Pro_name
Manf_price
Retail_price
commission
Manf_date
Exp_date
Varchar
Varchar
Varchar
Varchar
Varchar
Datetime
Datetime
8
10
15
15
8
10
10
Primary Key
Not null
Not Null
Not Null
Not Null
Not Null
Not Null
Id identifies the product table

Product name
Manufacturing price
Retail price
Commission price
Manufacturing date
Expiry date
4. Table Name: DD
Table description: Stores the Demand Draft details.
Field name
Data type
Size
Constraint
Description
DD_no
DD_date
Bank name
Branch
Varchar
Varchar
Varchar
Varchar
8
10
15
15
Primary Key
Not null
Not null
Not null
Id identifies the DD table

DD date
Bank name
Branch name
5.
Table Name: Order

Table description: Stores the order details.
Field name
Data type
Size
Constraint
Description
Pro_id
Order_id
Order_Quan
Order_date
Total amount
Varchar
Varchar
Varchar
Datetime
Varchar
8
8
8
10
10
Foreign Key
Primary Key
Not null
Not null
Not null
Id references the product table(pro_id)

Id identifies the order table
Quantity of the order
Date of order
Total amount of the order
6. Table Name: Company

Table description: Stores the company details.
Field Name
Comp_id
Data Type
Varchar
Size
8
Constraint
Primary key
Description
Id identifies the company table
Description
Varchar
25
Not null
Description
14
Address
Phno
Email
City
Varchar
Int
Varchar
Varchar
20
14
15
15
Not null
Not null
Not null
Not null
Address
Phone number
Email Id
City name
7. Table Name: Payment
Table description: Stores the payment details.

Field name
Data type
Size
Constraint
Description
Bill_no
Varchar
Primary Key
Id identifies the payment table
Order_id
Varchar
Foreign Key
Id references the order table(order_id)
Pay_Date
Datetime
10
Not null
Payment date
DD_no
Varchar
12
Not null
DD Number
8. Table Name: Bill

Table description: Stores the bill details.
Field name
Data type
Size
Constraint
Description
Bill_no
Varchar
Primary Key
Id identifies the bill table
Dist_id
Varchar
Foreign Key
Id references the distributor table(dist_id)
Order_id
Varchar
Foreign Key
Bill_date
Datetime
10
Not null
Date of bill
9. Table Name: Sales

Table description: Stores the Sales details.
Field name
Data type
Size
Constraint
Description
Order_id
Varchar
Foreign Key
Comp_id
Varchar
10
Foreign Key
Id references the company table(comp_id)
Pro_id
Varchar
Foreign Key
15
Sold_p_val
Varchar
Not null
Sold product value
Ret_p_val
Varchar
30
Not null
Return product value
10. Table Name: Turnover

Table description: Stores the turnover details.
Field name
Data type
Size Constraint
Description
Comp_id
Comp_name
Turnover
Varchar
Varchar
Varchar
8
15
15
Id references the company table(comp_id)

Company name
Turnover
Foreign Key
Not null
Not null
11. Table Name: Stock
Table description: Stores the stock details.

Field name
Data type
Size Constraint
Description
pro_id
Stock_quan
Stock_amt
Varchar
Varchar
Varchar
8
15
15

Stock quantity
Stock amount
Foreign Key
Not null
Not null
5.1.4 Program Structure

The technology that is used for developing this application is ASP.Net
using C#. The application will follow three tier architecture.
16
Client/Presentation Tier
The top most level of the application is the user interface. The main
function of the interface is to translate tasks and result to something the user can
understand.
Logic /Business rules Tier
This layer co-ordinate the applications, processes commands makes
logical decisions and evaluations and performs calculations. It also moves and processes
data between the two surrounding layers.
Data Tier
Here information is stored and retrieved from the database or file system.
The information is then passed back to the logic tier for processing and then eventually
back to the user.
5.2 Detailed Designs
This section gives the clear idea about the different components that
comprises the system operations.
17
5.2.2 Component Detail

This section will give the details of all components of the system.
Component 1: Distributor mgmt
This component will give the details of the user and tasks performed by the user.
Methods:- login(), register(), apply(), dealership(),logout(),initial payment()
Component 2: Administrator
This component will give the details of the administrator and operations done by the
administrator.
Methods:-login(),advertise(),insert(),update(),delete(),canceldealership()
generatereport(), logout()
Component 3: Schemes
This component will give the details of the schemes created by the administrator.
Methods :- createschemes(), viewschemes(), updateschemes(), deleteschemes()
Component 4: Products
This component will give the details of the products created by the administrator.
Methods: - insertproduct(), viewproduct(), updateproduct(), deleteproduct()
Component 5: Order
This component will give the details of the order created by the distributors.
Methods: - createorder(), vieworder(), updateorder(), deleteorder(),
Component 6: Bill
This component will give the details of the bill created by the administrator and
produce a bill to the distributor.
Methods: - createbill(), viewbill()
Component 7: Payment
This component will give the details of the payment created by the distributor and
pay the amount to the company.
Methods: - paybill(), viewpaybill()
5.3 User Interface Design

18
A user interface is the physical means of communication between a person

and a software program or operating system. It can also be defined as the
components of a computer system that the operator uses to interact with the
computer the screen display, keyboard and mouse etc. This section of the
document provides the output design strategies used and gives the description of the
GUI components which is used by the system
5.3.2 Interface Design Rules
The following interface design guidelines has been followed:
The application displays only the information that is relevant to the current
context.
Producing meaningful warning message such as valid user or invalid user.
Maintaining consistency between information display and data input.
Deactivating commands that are inappropriate in the context of the current

actions.
Entries relevant to the particular task are visible.
Entries are on graphical interface, Includes text.
5.3.3 GUI Components

A well-designed Graphical User Interface (GUI), which is simple and easy to use, is
very essential to the success of any application.
GUI acts as the mode of
interaction between the user and the application and so, it is designed based on
principles and a development processes that center on users and their tasks. An
important principle of a good GUI design is that the user feels in control of the
software instead of the application controlling the user. In order to design a usercentered GUI that is easy and simple to use, certain rules and standards need to be
followed consistently in any application.
A GUI component is a graphical building block for developing an application.
The application of Automated Distributor management system has been designed
with wide range of various components, which are mentioned below.
19
Component
Description
Homepage
Homepage is accessible from any other page on the Web site.
Label
Label is helps to get better understanding about what that control

represents.
Textbox
Text box allows the user to type in a single line of text
Button
When clicked by a user, it performs some action
Checkbox
Check boxes are given to enable user to select multiple choice.
Radio button
Radio buttons is used to select single option
Scrollbar
Scrollbars is used to navigate to the top and bottom of a web

page.
List box
List boxes provide selectable items.
Combo box
A combo box is like a list box, and is set up in the same way. It
just takes up less space on your form by collapsing to a single line
when deselected, showing the chosen list item
Panel
While building a form, various components is grouped using the

panels
Menu
A menu provides a space-saving way to let the user choose one of

several options.
Tables/Grids
Tables and grids allow users to enter or view larger amounts of

information at a time.
Calendar
This control provides a calendar month display that enables the

user to select a date.
Image Button
Displays a click-able image
Required Field Validator
Specified field cannot be null.
Compare Validator
For comparing two fields.
RegularExpression Validator
Specific pattern of input.
Range Validator
For specifying the range for validation.
Drop Down List
To display a list of values.
20
CHAPTER 6 - VERIFICATION AND VALIDATION PLAN

6.1 Component Test Plans and Procedures
6.1.1 Login
Test
case
group Login
identification
Functions to be tested
Functions tested include:
User authentication.
Controls include :
Links available in login page.
Testing approach
Login.
Testing whether the user is authenticated user or not.
Pass/Fail criteria
Functional testing technique is used.

If the test is success then the user is directed to the
appropriate page, provided the status is approved else error
21
message is displayed. If the user clicks the link for new

registration, then the registration page is displayed, else
the test fails.
Individual test cases
Test case 1:
Test case identifier: Login.
Input: The user enters the username and password and

submits the form. The corresponding username and
password is checked with the login table.
Expected output: If username and password is valid,

the user is redirected to appropriate page.
Environment: Internet Explorer is required.
Special procedures: Validator controls are used.
Precedence and dependencies: Depends upon the

login table.
Test case 2:
Test case identifier: Links available.
Input: Mouse click on New Distributor?Register

here!.
Expected output: Registration page is displayed.
Environment: Internet Explorer is used.
6.1.2 Registration
Test case group identification
Registration
Functions tested include:
Register with the website
Validation of registration page
Controls include:
Textboxes available in the registration form.

22
Create account button in the registration page.
Testing approach
Testing the validation for the textboxes using data entered.
Pass/Fail criteria

If data entered is valid it is inserted into the database, else error
message is displayed. If the username entered is already exists
then error message is displayed.

Test case 1:
Test case identifier :Apply
Input: Mouse Click on Apply button
Expected output: If user has entered valid details, the user

is redirected to user type registration page and the details
are stored in the database.

Special procedures: Various validator controls are used.
Precedence and dependencies: Depends upon the

database.
Reference: Link from Home page.
6.1.3 Distributor Dealership

Distributor Availability.
Functions to be tested include:
Buttons to validate
View.
Cancel.
23
Testing approach
Test whether the data is retrieved and displayed in the grid

view. Functional testing technique is used.
Pass/Fail criteria
If the test is success data is retrieved in correct format else
error in retrieving.
Test Case:1
Test case identifier: View.
Input: Mouse click on View button.
Expected output: The distributor availability is

displayed.
Environment: Internet Explorer is used
Special procedures: Validator controls and grid view

are used.
References: Link from distributor registration page.
Test case 2:
Test case identifier: Cancel.
Input: Click on cancel button.
Expected output: Redirect to the Distributor home page
Special procedures: No special procedures are required.
Precedence and dependencies: This test case has no

dependencies.
References: Link from the Distributor home page.
6.1.4 Product Details

Product Details
Buttons to validate
Add
24
Cancel
Delete
Testing approach
Pass/Fail criteria
Upon clicking the button, appropriate event takes place, else test
fails.
Test Case:1
Test case identifier : Add button
Input: Mouse click on add button.

Expected output: The product is added into the
company product list.
Precedence and dependencies: No special dependencies.
References: Link from Distributor home page.
Test Case:2
Test case identifier : Cancel button

Input: Mouse click on Cancel button.
Expected output: The product is not added into the

product list.
Precedence and dependencies: No dependencies.
Test Case:3
Test case identifier : Delete button
Input: Mouse click on delete button
Expected output: The product is deleted from the product

list.
Precedence and dependencies: No special dependencies.

25
References: Link from home page.
6.1.5 Company profile.

Company profile.
Buttons to validate
Testing approach
Save
Cancel
Test the validation for the text boxes using data entered.
Pass/Fail criteria
If data entered is valid it is inserted into the database and

redirect to the distributor availability page, else error message
is displayed.
Test Case:1
Test case identifier : save button
Input:
Company name.
Description
Address
City
Country
State
Phone
Email
Expected output: Data is inserted into the database

and redirect to distributor availability page.

26
Precedence and dependencies: Depends upon the company

profile table.
References: Link from company home page
Test case 2:
Test case identifier : Cancel button
Input: Mouse click on cancel button.
Expected output: Redirect to the same page.
Special procedures: No special procedures are used.

dependencies.
References: Link from employer home Page.
6.1.6 Order Products

Order Products
Testing approach
Functions Tested Include:

Buttons to validate
Order
Cancel.
Testing the validation for the textboxes using the data entered.
Pass/Fail criteria

If data entered is valid it is inserted into the database and
redirected to the second part of registration page, else error
message is displayed.
Test case 1:
Test case identifier: Order.
Input:
Distributor Name
Company Name
27
Order Id
Choose Products
Expected output: If Distributor has entered valid details,

the Distributor is redirected to the Verify Products Page and
the details are stored in the database, else error message is
displayed and redirected to the same page.
Special procedures: Validator control is used.
Precedence and dependencies: Depends upon order table.
Test case 2:
Test case identifier: Cancel.
Input: Click on cancel button.
Expected output: Redirect to the Distributor home page
Special procedures: No special procedures are required.

dependencies.
References: Link from the Distributor home page.
6.1.7 Payment
Payment
Buttons to validate
Grid View
Payment
Cancel
28
Testing approach
Testing the program and check whether the ordered product details
are displayed in grid view and also check whether the details are
editable and pay the amount for the ordered product. Functional
testing technique is used.
Pass/Fail criteria
The Ordered Product is displayed in the grid view else
appropriate error message is displayed.

Test Case:1
Test case identifier : Grid view
Input: None
Expected output: The ordered product details are

displayed.
Precedence and dependencies: Depends on the

product table
References: Distributor home page
Test Case:2
Test case identifier : Payment
Input: Mouse click on Payment button.
Expected output: Pay the amount of r ordered product.
Precedence
and
dependencies:
Depends
Payment table
References: Distributor home page
6.1.8 Distributor Cancelation

Distributor Cancelation
Buttons to validate
Cancel dealership
29
on
Testing approach
No
Inspect the program and check whether it travels to the correct
page and execute functions properly. Functional testing
Pass/Fail criteria
technique is used.
Upon clicking the button, the appropriate records are canceled,
else test fails.

Test Case:1
Test case identifier : Cancel Dealership
Input: Mouse click on Cancel Dealership button.

Expected output: The distributor dealership is
canceled.
Precedence and dependencies: Depends upon the dist

profile table
References: Link from distributor home Page.
Test Case:2
Test case identifier : No
Input: Mouse click on No button.
Expected output: Redirect into the distributor page.
Precedence and dependencies: Depends on the dist

profile table.
References: Link from distributor home Page
6.2 System Test Plans and Procedures

6.2.1 System test strategy overview
30
The entire software product is tested to ensure that the interfaces among
the components are defined and functions properly, after each individual component
has already been tested. The integration tests ensure that the system components
work together as well as they works individually.
6.2.2 Linking Integration

Distributor Management System(The complete product)
Features tested
Links and buttons from the various web pages within the
system.
Testing approach
Top down approach
Pass/Fail criteria
All modules are functioning as tested individually in the

component verification. The complete application works
correctly and fulfills the requirements
6.2.3 Coherence and Accuracy of Information

Coherence and accuracy of Information
Information content of each page.
Testing approach
Inspection of the information its organization, accuracy,

and flow.
Pass/Fail criteria
The information is correct and accurate, yet simple

enough. The organization and flow is logical so that the
concept is able to understand easily.
3.3.1 Test case: Login
Input: Username, Password

Expected output: Access is given.
Environment: Internet Explorer.
Reference: Mouse click on Login button from home
page.
3.3.2 Test case: Register
Input: Personal details

Expected output: Request is sent to administrator.
Reference: Mouse click on Register button
31
3.3.3 Test case: Product Details.
Input: Product details.

Expected output: Product details are displayed.
Reference: Mouse click on Add button.
3.3.4 Test case: company profile.
Input: Company details.

Expected output: Company details are stored in the
database.
Reference: Link from the distributor page.
3.3.5 Test case: Order products
Input: Order products

Expected output: Ordered products details are stored in
the database.
Reference: Link from the distributor page.
3.3.6 Test case: Payment
Input: Mouse click on appropriate button.

Expected output: Pay the amount for ordered product
Reference: Link from the distributor page
6.3. Acceptance Test and Preparation for Delivery

Acceptance test enables the clients to determine if the system built meets
their needs and expectations. Acceptance testing uncovers more than requirement
discrepancies.
6.3.1 Procedure by which the software product will be acceptance tested
The component at the highest levels of the system is tested first. Each subcomponent is tested until the most detailed components at the lowest levels have all
been tested thereby correcting all the encountered errors. The product is evaluated
to ensure that it meets design specifications stated in the SRS and SDS.
32
6.3.2 Specific acceptance criteria

The client expects the following criteria:
The product runs from the internet, has an interactive graphical user
interface.
The product should contain all the information of Company and
Product
which is registered in this site.
The product should contain all the information of Distributor like Personal
Detail, Scheme Detail, and Ordered Product Detail etc.
The product should process and evaluate distributor registered by

companies.
The product should maintain proper financial records.
The product should have Administrator for scheduling administrative

work of site
The product displays all the information that user needs.
6.3.3 Scenario by which the software product will be installed

The product is accessed via the Internet website so no installation is
required. The communication between the users is established via Internet.
33
CHAPTER 7 - CONCLUSIONS AND FURTHER SCOPE
7.1 Broad Conclusions

Thus Automated Distributor Management System is a website which
allows the distributor to search the distributor availability and apply the dealership.
The administrator approves the dealership after the verification. Already registered
distributors entered the website and view the products. This site will be very useful
for distributors; they order the products though online. Distributor can view their
Scheme. Distributor pay the amount for ordered products.
7.2 Further Scope and Enhancements
The website is much flexible to include further enhancements. The
project can be enhanced in such a way that the distributor can give their details in
more secured manner by using encryption technique. Currently the payment details is
not saved in an encrypted format as future enhancement the payment details be
encrypted for more security. This application can be helpful for the distributors in
various organizations.
This application is developed using the current technologies so further
special techniques can be used.
34
APPENDIX A
Figure A.1 Level 0 DFD
Administrator/
Distributor
Request
Distributor
managemen
t system
Response
Employer/
jobseeker
35
Figure A.2 Level 1 DFD
Schemes
Dist/Schem
e availabilty
view
Company
Apply
Dealership
Distributor
Approval
Viewing
products
products
Login
Order the
products
Deliver
y
Paymen
t
Cancel
Dealership
payment
36
Figure A.3 Entity-Relationship Diagram

disti
d
proid
Scheme
id
compid
Retail
price
disti
d
Distnam
e
DISTRIBUTOR
PRODUCTS
vie
w
choos
e
app
ly
scheme
id
durat
ionn
Sch
amt
disti
d
Purch
ase
order
SCHEMES
retu
rn
add
Manf
price
compid
descript
ion
upda
te
COMPANY
orderid
proid
compna
me
compid
Orderdat
e
quantit
y
turnove
r
ORDER
TURNOVER
pay
s
giv
es
vie
w
giv
es
orderid
billno
compid
DDno
SALES
PAYMENT
billno
giv
es
distid
orderid
sen
ds
BILL
37
Figure A.4 Architectural Design Block Diagram
Update Status
Admin
Automated
Distributor
Management System
Fresh
Distribut
ors
Search
availability.
Order products
Distributor
s
payment
38
APPENDIX B
UML DIAGRAMS
Figure B.1
Class Diagram
1..*
product
pro_id
pro_name
manf_price
retail_price
manf_date
exp_date
view
N
Distributor
1..*
dist_id
dist_name
dob
address
phno
1..*
email
deposit amt
scheme id apply1..*
view
Schemes
dist_id'
schemeid
schemeoffer
duration
scheme level
company
payment
order_id
DD_no
DD_date
Bank name
order
compid
comp name
turnover
N
create order()
view order()
update order()
delete order()
turnover()
N
gives
advertise()
insert()
update()
delete()
view()
view
dist_id
order_id
order date
order_quan
total_amt
commision
turn over
dist_id
comp_id
N comp_name
address
phno
email
branch
N
order
1 update
insert product()
view product()
update product()
delete product()
createscheme()
view scheme()
updatescheme()
delete scheme()
update
N
apply()
register()
initial payment()
1
pays
store
sales
compid
proid
orderid
sold_p_value
ret_p_value
payment()
view()
bill
invoice_no
pro_id
dist_id
order_id
Date
amt_paid
Sold_p_value()
ret_p_value()
1
gives
create bill()
view bill()
39
Figure B.2 Sequence Diagram
Distributor
dist mgm t sys tem
Database
company
Advertise
store availabilty
View schem es and availabilty
check availabilty
res pons e
Apply Dealership
pay initial am ount

4. Verify delership
5.Stores dist details
Give unam e,pwd
login
View product
retrive product details
order the product
verify the product
confirm ation
paym ent
store paym ent details
produce a bill
delivery
turn over
update s chemes and products

apply cancel dealers hip
verification
cancelization
40
APPENDIX C
USER INTERFACE SCREEN SHOTS
Home page
41
Login
Registration
42
Company details
Product Details
43
Dealership Cancelation
Dealership Approval
44
Order products
Payment
45
46
BIBLIOGRAPHY
1. G Andrew Duthie, ASP.Net in a Nutshell, 2002, Second Edition.
2. Bryan Syverson, Murachs SQL for SQL Server, 2003, BPB Publication, First
Indian Edition.
3. Greg Mable, MS SQL Server 7 Unleashed, May 1999, First Edition.
4. Roger Pressman,Software Engineering, 2003, Tata McGraw Hill, 7th Edition.
5. Chris Hart, John Kauffman, David Sussaman, Chris Ullaman, Beginning
ASP.Net 2.0, 2004,Second Edition, Wrox.
Websites
http://www.scribd.com/doc/7201973/Job-Site-Documentation-32Ank
https://login.naukri.com/nLogin/Login.php?msg=0&URL=http
%3A%2F%2Fmy.naukri.com
http://hire.timesjobs.com/employer/onlineBuyJob.html
http://database.about.com/od/specificproducts/a/normalization.html
http://publib.boulder.ibm.com/infocenter/rtnlhelp/v6r0m0/index.jsp?
topic=/com.ibm.xtools.modeler.doc/topics/rreltyp.html
47

Josekin VIVA Book

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Josekin VIVA Book

Diunggah oleh

Hak Cipta:

Format Tersedia

CHAPTER 1 - INTRODUCTION

The main objective of SRS is to illustrate the requirements of the project

- Bookman Old Style

Intended Audience and Reading Suggestions

A manufacturing company doesnt sell their products directly. Using distributors

CHAPTER 2 THE OVERALL DESCRIPTION

The proposed system, automated distributor management system is used to

-14 inch VGA Monochrome

Programming Language ASP.NET

-Windows NT, Windows 2000/XP.

2.5 Design and Implementation Constraints

The user documentation provides components such as

2.7 Assumptions and Dependencies

CHAPTER 3 SYSTEM FEATURES

3.1 Dealership Approval Module

The distributor sends his information to the administrator. The administrator

Distributor enters his details.

Administrator approves the dealership.

2.1.3 Functional Requirements

Validating Distributors information.

Generates userif and password for the distributor

3.2 Login module

3.2.1 Description and Priority

3.2.2 Stimulus/Response Sequences

User enters the valid user id and password.

User will be logged in successfully.

3.2.3 Functional Requirements

User id and password.

Validating the user id and password.

Successfully logged in.

3.3 Distributor module

Enters the distributor information

Distribution registration is successful and can view reports.

The distributors can also purchasing goods.

Access the data

Enter distributor and purchasing details

Authorizing the distributor

Distributor is registered, purchase details. The

3.4 Order Module

Viewing and ordering.

Bill from the company for the purchased products.

3.4.3 Functional Requirements

Ordering the products

Selecting the needed products.

Preparation of bill for the purchased products.

3.5 Payment Module

Distributor verifies the products.

3.5.3 Functional Requirements

Verifying and returning the products.

Orders and Product information

Calculating the payment

Payment is calculated automatically

CHAPTER 4 - SOFTWARE REQUIREMENT SPECIFICATION

IIS (Internet information services (IIS) is a powerful Web

Protocols:Communication protocol: HTTP

Non blocking I/O

Cross browser compatibility.

Allows concurrent access to multiple users

4.2.2 Safety Requirements

4.2.4 Software Quality Attributes

CHAPTER 5 - SOFTWARE DESIGN SPECIFICATIONS

5.1 Architectural Design

5.1.2 General Constraints