KMITMASTERS

Supply Chain Management

Software Requirements Specification

Team
KMITMasters

Team Members
P S Vishnu Vardhan
Vasireddi V L N Goutham

Project Guide
Syed Fasi Ahmed.
[Type text]

Table of Contents
1. Introduction 3
1.1 Purpose 3
1.2 Scope 3
1.3 Definitions, Acronyms and Abbreviations 3
1.4 References 4
1.5 Technologies to be used 4
1.6 Overview 4

2. Overall Description 5
2.1 Use-Case Model Survey 7
2.2 Architecture diagram & database design 9
2.3 Assumptions and Dependencies 13

3. Specific Requirements 13
3.1 Use-Case Reports 13
3.2 Supplementary Requirements 24

2
[Type text]

Software Requirements Specification

1. Introduction
1.1 Purpose
This project is aimed to develop an online system to provide the management of the flow of
materials, information, and funds across the entire objects of supply chain. It helps business
people in different sectors to introduce their products into market and to supply in their best
forms and getting best profits. Manufacturer, distributor and retailer can easily check there
products and change its details as per needs of market. They also have option to see their
transaction details and there profit details.
1.2 Scope

 Create different system users and assign different roles with related permissions.
 Manage all the account details such as user name, phone numbers, address, email
addresses of all the users from one central location.
 Track all the customers and their contact details.
 Maintain the services provided to the customer through Service Level Agreements.
 Give authority to sellers to provide offers on items which they sell.
 Seller will be able to give discount on large scale orders.
 Track all the payment details of the customer and their product ownership detail.
 Group the contacts together in a single account according to some criteria.
 Capture, View and edit all user transactions, including email, chats, and services calls
in a single system.
 Confirmation of end user identity and will verify which users are authorized to
receive support.
 Maintain history of each user and their related information about the product sale,
SLA & support related transactions.
 Anticipate the need and potential of sales opportunities.
 View all the details of all the interactions made with the customer.
 Activities like updating, creations done in the system by the system users will be
maintained in the form of logs for auditing and maintaining the integrity of the
system.
 Send SMS alerts for new products details by users.

1.3 Definitions, Acronyms and Abbreviations

 HTML: Hypertext Markup Language is a markup language used to design static

web pages.
 EJB: Enterprise Java Beans.
 J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java
Platform—for developing and running distributed multitier architecture Java
applications, based largely on modular software components running on an
application server.

3
[Type text]

 DB2: DB2 Database is the database management system that delivers a flexible
and cost effective database platform to build robust on demand business
applications.
 WAS: Web sphere application server is an application server that runs business
applications and supports the J2EE and web services standards.
 WSAD: Web sphere studio application developer is a toolkit which is designed
for the creation of more complex projects, providing fully dynamic web
application utilizing EJB’s. This consist of EJB tools , CMP ,data mapping tools
& a universal test client that is designed to aid testing of EJB’s.
 HTTP: Hypertext Transfer Protocol is a transaction oriented client/server
protocol between web browser & a Web Server.
 HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket
layer).
 TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of
communication protocols used to connect hosts on the Internet. TCP/IP uses
several protocols, the two main ones being TCP and IP.
1.4 References
 IEEE SRS Format
 Problem Definition (Provided by IBM)

1.5 Technologies to be used

 J2EE: Application Architecture
 DB2: Database
 WSAD: Development Tool
 WAS: Web Server
 Rational: Design Tool
 I-Reporter: File Creator
1.6 Overview: SRS will include two sections:
 Overall Description will describe major components of the system,
interconnection and external interfaces.
 Specific Requirements will describe the functions of actors, their role in the
system and constraints.

4
[Type text]

2. Overall Description
Describe the general factors that affect the product and its requirements.

2.01) Product Perspective:

 The web pages (XHTML/JSP) are present to provide the user interface on customer client
side. Communication between customer and server is provided through HTTP/HTTPS
protocols.
 The Client Software is to provide the user interface on system user client side and for this
TCP/IP protocols are used.
 On the server side web server is for EJB and database server is for storing the
information.
2.02) Software Interface:
 Client on Internet: Web Browser, Operating System (any)
 Client on Intranet: Client Software, Web Browser, Operating System (any)
 Web Server: WAS, Operating System (any)
 Data Base Server: DB2, Operating System (any)
 Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML),
DB2, OS (Linux), Web Server.

5
[Type text]

2.03) Hardware Interface:

Client Side
Processor RAM Disk Space
Internet Explorer Pentium II at 500
64 MB 1 GB
6.0 MHz
Server Side
Web sphere
Pentium III at 1
application server 512 MB 2 GB
GHz
V2.0
Pentium III at 1 1GB (Excluding
DB2 V9.1 512 MB
GHz data size)

2.04) Communication Interface:

 Client on Internet will be using HTTP/HTTPS protocol.
 Client on Intranet will be using TCP/IP protocol.
2.05) Product Function:
 Track Account Level Data: In this module , receivables from customer are
maintained.
 Service Level Agreements: It contains the agreements of providing the services
related to product and customer.
 User Contact Information: It maintains all the details (Personal, Official,
Contact, and Company) of the customer.
 Product Ownership Details: It maintains the information that does which
customer own which product.
 Track Support Transactions: Maintenance of transactions related to the services
provided to the customer in the form of support.
 Maintaining Logs: Activities of the System Users can be tracked through the
logs, which are maintained by the system.
2.06) User Characteristics:
Every user should be comfortable of working with computer and net browsing.
He must have basic knowledge of English too.
2.07) Constraints:
 GUI is only in English.
 Login and password is used for identification of customer and there is no facility
for guest.
 This system is working for single server.
 There is no maintainability of back up so availability will get affected.
 Limited to HTTP/HTTPS.

6
[Type text]

2.1 Use-Case Model Survey

Accept or Decline orders

Get Reports

Edit details of Items Distributor

Manufacturer on Chart

Forums, chats, polls Customise his Cancel Processing Add or Remove Give orders
own details Order Items on charts

Retailer

7
[Type text]

1. Manufacturer:

 Manage Items: He can add and change the product details into the
items chart.
 Add and remove products from sales chart: He can view and verify
the details of items in his sales chart.
 Accept/Decline orders: He can view the orders/bulk orders from
distributors, retailers and accept or decline them.
 Communicate: He can view the list of distributors and retailers and
know there comments on his service and products.

2. Distributor:

 Manage Items: He can add products to his item chart by purchasing

them from the manufacturer.
 Add and remove products from sales chart: He can view, verify and
change the details of items in his sales chart.
 Accept/Decline orders: He can view the orders from retailers and the
orders given to manufacturers and accept or decline them.
 Communicate: He can view the list of manufacturers and retailers and
know there comments on his service and products.

3. Retailer:
 Manage Items: He can add products to his item chart by purchasing
them in bulk from the manufacturer or from a distributor.
 Add and remove products from chart: He can view his items chart
and remove the items.
 Accept/Decline orders: He can view the bulk orders\orders given to
manufacturers and distributors and accept or decline them.
 Communicate: He can view the list of manufacturers, distributors and
communicate with them and let them know about there services and
products.
.

8
 [Type text]

2.2 Architecture diagram & database design

Application layer Business layer Data layer

Role_UI Role Role

Permission_UI Permission Permission

User_UI User User

Task_UI Task Task

Receivable_UI Receivable Receivable

User details_UI User details User details

Profile_UI Profile PROFILE

Items_UI Items
Items

Orders details_UI Orders details

Orders details

Forms, Mails polls, Forms, Mails Forms, Mails

chats_ UI polls, chat polls, chat

Reports_UI Reports Reports

SMS (J2ME)_UI
SMS (J2ME) LPS

User details_UI User details User details

9
[Type text]

Data base diagram

System_Role
ISA

Role_ID
Role_Name

Manufacturer Distributor Retailer

System_User

User_ID
Login_name
Password_value
First_Name
Last_Name
Mobile_Number
Email_ID

10
 [Type text]

Personal
Items
First _name Orders
Last _name Itm_code
Date_of_birth Item_name Ordered_date
Age Item price/unit Order_given_by
Sex Bulk order quantity Item_ordered
Address No.of available units Quantity
E_mail Category Delivery_date
Mobile_No Transport_type
City
State
Country
Zip _Code

User_Details

User name
Reports Password
Name of user
Item_name Date of birth
Item_code Age
Mfd.Price Sex
Selling_Price Phone No.
Profit Fax
Net_Profit E-mail
Address
City
State
Country
Zip-Code

11
[Type text]

MANUFACTURER DISTRIBUTOR

View/Edit Add/Remove View/Edit Add/Remove

Profile items Profile items

Accept/Decline Communicate Accept/Decline Communicate

Orders with retailers Orders with retailers and
and distributors manufacturer

RETAILER

View/Edit Add /remove

Profile items

Communicate with
Place bulk Manufacturer,
orders/orders to Distributors
Manufacturer/
Distributor

12
[Type text]

2.3 Assumptions and Dependencies

 Roles and tasks are predefined.
3. Specific Requirements
3.1 Use-Case Reports

1) Manufacturer: Manufacturer is the starting point in the market. He is the major

producer of products in the market. He produces more items for an existing
product under his manufacturing category and also can produce new items and
introduce them into the market.

 Manage Profile: He can view his personal, official details and update
them according to his progress in the market.
 Manage Items: He can manage the details of already present products
according to market rates.
 Add and remove products from sales chart: He can add a new
product to his already manufacturing products and remove any product
for which he stopped manufacturing.
 Accept/Decline orders: He can view the orders/bulk orders from
other members of chain such as Distributors, Retailers and accept or
decline them.
 Communicate: He can view the list of Distributors and Retailers and
know their opinions and get their comments on his service and
products.

2) Distributor: Distributor is the next level in this chain. Distributor can buy new
items and add quantity to existing items by giving order to the Manufacturer and
sell products to Retailer at a price present in the market.

 Manage Profile: He can view his personal and official details

according to present market requirements.
 Manage Items: He can manage the details of already present products
according to market rates.
 Add and remove products from sales chart: He can add new items
to his selling products and also can buy already present product from
Manufacturer.
 Accept/Decline orders: He can view the orders from retailers and
accept or decline them.
 Communicate: He can view the list of retailers and know there
comments on his service and products and give his opinions to the
Manufacturer about his products.

13
[Type text]

3) Retailer: Retailer can buy items by giving orders/bulk orders to

Distributor/Manufacturer and as time increase he can evolve into a wholesaler.

 Manage Profile: He can view and change his profile according to

present market requirements.
 Manage Items: He can add and change the products and their details
into the items chart.
 Add and remove products from sales chart: He can view and verify
the details of items in his sales chart.
 Accept/Decline orders: He can view the orders from retailers and
accept or decline them.
 Communicate: He can view the list of Manufacturers and Distributors
from whom he bought products and comment on their service and
products and give his opinions to the Manufacturer and Distributor
about their products.

Name of use case: Add/Remove items to chart

Description: To allow the users to add/remove items from there chart list.
Preconditions:
 User is already logged in.
 System users have already been created and assigned some roles, tasks.
Normal flow of events:
 A user for adding item should fill the details and the item will be seen in chart with
given price.
 A user for removing item should select the type name and code of item, and then the
specified item will removed from chart.
 An alert is made to the user that all the orders which are pending concerning the item
to be removed will be cancelled.
Alternate flow of events: None.
Post Condition: None.

14
[Type text]

Add or Remove items

Add Remove

product name, code, price/unit,type of product

Item type, code

NO

YES YES

Product Removed
Item added

Name of use case: Edit details of items on chart.

Description: To edit or change the details of items in chart.
Precondition: User is already logged in.
Normal flow of events:
 Enter the new details of the items.
 Save those details.
Alternate flow of events: None
Post condition: None.

15
[Type text]

Sel ect the product

Edi t the detai ls

Updated

Name of use case: Get reports.

Description: View the reports of users about their items and its sales.
Precondition:
 The user is already created
 User is already logged in.
Normal flow of events:
 Select the date or month.
 View the reports of the specified date or month.
Post condition: None.

16
[Type text]

Enter date and month

Reports displayed

Name of use case: Cancel processing order.

Description: A user can cancel the processing order between him and other accepted orders of
users.
Preconditions: User must be logged in.
Normal flow of events:
 Select the order.
 Confirm the cancel option.
Alternate flow of events:
 A message appears for the user whose order has been canceled.
Post condition: None

17
[Type text]

Select the processing order

Cancel

YES
NO

Order cancelled

Name of use case: Give orders.

Description: To allow
 Retailer to order either to a Distributor or to a Manufacturer and
 Distributor to order to a Manufacturer
Precondition:
 The user is already created.
 User (either a Retailer or Distributor) is already logged in.
Normal flow of events:
 Select the category, then item to be ordered.
 Select the Manufacturer if quantity to be ordered is more than the bulk order
quantity mentioned by the manufacturer else select a Distributor to order required
quantity of item.
 Give the three dates for the seller to choose any one as the final delivery date.
 Place an order.
Alternate flow of events: A message appears if the user does not exist.
Post condition: Order must be sent to another user after completing all the process.

18
[Type text]

USER

CHECK USER

Distributor Retailer

Details of product Bulk orders Simple orders

Orders passed to manufacture

Details of product Details of product

Orders passed to Manufacturer Order passed to Distributor

19
[Type text]

Name of use case: Customize his own details

Description: User can change his details and be up to date with the market.
Precondition:
 User must be registered to the site already.
 User must be logged in already.
Normal flow of events:
 User can change any of his profile components.
 Update his profile according to the market requirements.
Alternate flow of events: A message appears if the user does not exist.
Post condition: The changes must be saved.

LOG IN USER

NO

User already logged in

YES

Change his details

Update

20
[Type text]

Name of use case: Forum, chats, polls.

Description: Here,
 Seller can contact the buyer for feedback over the items produced or
distributed by them.
 Buyer can also come in direct contact with the producer or distributor for
giving his feedback over the products he bought either from the Distributor or
the Manufacturer.
Precondition:
 The user must be registered already to the site.
 The user must be logged in already.
 The seller can only ask comments on his products to only his customers i.e.,
persons who had bought items from him only can give feedback.
 The Buyer is also restricted to give feedback only to those people from whom he
bought the items.
Normal flow of events:
 Buyer can put a forum on the products he buys.
 Buyer can post a poll so that he understands the quality of product he's going to
buy.
 Any one of Seller and Buyer can initiate the chat between each other for
discussing about the products.
Alternate flow of events: A message must be displayed if the user does not exist.
Post condition: These messages can be saved for further future use.

21
[Type text]

User

Manufacturer

Distributor

Post for a unavailable product

Receive comments from Retailers

Give coomments for products of Manufacturer

Request for comments and opinions of his products Give Comments and opinions on products bought

22
[Type text]

Name of use case: Accept/Decline orders.

Description: To accept or decline orders given to a user by another user.
Precondition:
 User must be logged in already.
Normal flow of events:
 If User is retailer is then he can only place orders to Manufacturer and Distributor.
 If User is Distributor then he can,
a. Place orders to Manufacturer,
b. Accept or decline orders from Retailers
 If User is Manufacturer then he can accept or decline orders from both Distributor
and Retailer.
 Confirm the option
Alternate flow of events: A message is displayed if User does not exists.
Post condition: None.
.

USER

Retailer Manufacturer and Distributor

Manufacturer
Can only place orders
Distributor

Accept or decline orders from Retailer

Accept or decline orders from Retailer and Disributor

23
[Type text]

3.2. Supplementary Requirements

Have hours of operation that are 24 x 7 - Because system can be an automated process, so
it can stay open for 24 hours a day. If the base is now the entire world, staying open 24
hours a day becomes critical. System is required to be available 24X7 so UPS support
must be on server site for at least 8 hours in case of power failure. System will remain
inaccessible to users at 2:00 to 4:00 am for backup and maintenance purpose.

Make the existing Web site more dynamic in nature - Many early Web implementations
consisted of static HTML pages. This becomes very difficult to manage if the number of
pages gets too large. An effective system should be largely dynamic taking advantage of
technology that automates this process rather than relying on manual processes.
Application should serve dynamic user based customized web pages to its clients from
server.

Provide good performance and the ability to scale the server – The Web Application
Server should provide good performance and the ability to manage performance with
techniques, such as support for caching, clustering, and load balancing.

Providing session management capability - Web application developers should not spend
valuable time worrying about how to maintain sessions within the application. The Web
Application Server should provide these services.

Uninterrupted Mail and SMS service – The server provides uninterrupted service of Mail
and SMS for Online reporting system to be active throughout the day.

24