srs - test project
TRANSCRIPT
SOFTWARE REQUIREMENTS SPECIFICATION
for
TEST PROJECT
Version 1.0
Prepared by:
Nirmal Kollara
+91-9819404483
Date: 09-04-2012
Best viewed in Adobe Reader with page fit to window width or 140% zoom
SRS FOR TEST PROJECT Version : 1.0
Page | 2
Table of Contents Revisions ........................................................................................................................................... 3
1. Introduction .............................................................................................................................. 4
1.1. Document Purpose ............................................................................................................ 4
1.2. Project Scope .................................................................................................................... 4
1.3. Document Overview .......................................................................................................... 4
1.4. Definition And Abbreviations Used .................................................................................... 4
1.5. References ......................................................................................................................... 4
2. AS-IS Process ............................................................................................................................ 5
3. Overall Description .................................................................................................................... 6
3.1. Product Functions .............................................................................................................. 6
3.2. User Characteristics ........................................................................................................... 6
3.3. Operating Environment ..................................................................................................... 6
3.4. Assumptions ...................................................................................................................... 6
4. Functional Requirements .......................................................................................................... 7
4.1. User requirements ............................................................................................................. 7
4.1. Diagrams ........................................................................................................................... 8
5. Non-functional requirements .................................................................................................. 12
6. Data dictionary ......................................................................................................................... 13
8. Appendix – A ........................................................................................................................... 14
SRS FOR TEST PROJECT Version : 1.0
Page | 3
Revisions
Version Primary Author(s) Description of Version Date
1.0 Nirmal Kollara Initial version built from “Project Requirement”
document
09-04-2012
SRS FOR TEST PROJECT Version : 1.0
Page | 4
1. Introduction
1.1. Document Purpose Present to the reader the users’ requirements and expectations from the software that is going to be designed during the course of the project. Also included are the observations of the initial analysis. Various features of the system that are going to be implemented are in-cluded in this document. Other factors like constraints and non-functional requirements are also listed.
1.2. Project Scope
Currently the project aims to automate the sales and marketing business process
through a web based application which will be used by the end users at the client’s lo-
cation. A market research module is also part of the solution.
The sales and marketing module would help the company manage and engage its cus-
tomers better by managing information and making it readily available to its execu-
tives.
The market research module would be of strategic importance since it encompasses
competitor database along with the company’s very own product and customer data-
base and provides various actionable reports.
Only the activities mentioned in the parent document (i.e. the initial analysis) are to
be incorporated in the system. Activities like accounts receivable and payable , inven-
tory etc are out of the present scope
1.3. Document Overview This SRS documents the current manual process of the sales and marketing activities as understood and the expectations from the market research module as spelled out by the users
1.4. Definition And Abbreviations Used DB – Database DFD – Data Flow Diagram MIS – Management Information System OS – Operating System SRS – System Requirements Specification
1.5. References http://standards.ieee.org - for SRS template
SRS FOR TEST PROJECT Version : 1.0
Page | 5
2. AS-IS Process Sales and marketing business process
START
Execution
Quotation
Negotiation and Finalization
After sales service
END
Enquiry
Receive enquire via
email, phone or mail
Note enquiry
Review enquiry for
technical req.
Clarifications needed?
Contact customer
YES
Create samples, pilot
runNO
Prepare and send quotation
Send order confirmation
Record order amendments
in the log
Manual Log
Update log
Update log
Update log
Update log
Send drawing to customer
and construct on approval
Finalize dispatch,
erection, and commissioning
details
Update log
Customer complains via
e/mail or phone
Update log
Dispatch spares to customer
Send service engineer
onsite
Prepare service engg.
report
Update log
Update log
Calls & meeting to
discuss tech. & comm. terms
Record minutes
in log
Figure 1 : AS-IS Process
Subprocess
Process Decision
External Data
Figure 2 : Legend
SRS FOR TEST PROJECT Version : 1.0
Page | 6
3. Overall Description
3.1. Product Functions
Enquiry – ability to feed the incoming enquiry into the system
Quotation – generate and send the quotation to customer through the system
Negotiation – log the negotiation process in the system, log order confirmation, ac-
cept advance
Execution – track order amendments, log inspection activities and dispatch, erection,
& commissioning details
After sales – log incoming complaints, schedule engineer visit, spares requisition
Market research module – to capture its own product and customer information along
with competitor database which includes products, prices, market share and miscella-
neous information for strategic purposes
3.2. User Characteristics
Sales executives – Enter enquiry and prepare quotation in the system
Design engineers – Retrieve the requirement from the system and design prototype or
pilot run
Service engineers – attend to issue and log service report in the system
Production in-charge – retrieve new/pending orders and execute them
Stores in-charge – receive requisition for spares through the system and indicate
availability of spares
Managers – view reports, status of orders and complaints etc
3.3. Operating Environment
The solution should be a web application
The client has been using and is comfortable with the Microsoft Windows environ-
ment and hence the solution will be developed using suitable versions of Microsoft
.NET and SQL Server
User nodes would be running MS Windows OS and Google Chrome browser
3.4. Assumptions
Sales executive (sales rep) is the single point of contact for the customers’ enquiry and
complaints.
Sales executive on receipt of a new order initiates production and the production de-
partment executes the order and dispatches it on completion.
Service engineers are notified and directed by sales executives about customer issues
appropriately; service engineers log their report into the system after each visit.
Similarly stores in-charge is notified by the sales executive and arranges for dispatch of
necessary spares to the client location.
Inventory, procurement, cccounts receivable and payable is handled externally
Customer and product database is shared by both modules.
SRS FOR TEST PROJECT Version : 1.0
Page | 7
4. Functional Requirements
4.1. User requirements
Customer master to store information of existing and prospective clients
Product master to store information of products offered by the company
Competitor master to store information about the company’s competitors, their products, prices, market shares, customer feedback etc. This information would be used to make strategic decisions
The product should also be capable of storing various other information like taxation details, environmental regulations etc.
The four above mentioned requirements are elaborated in the “Project Requirements” document attached as Appendix – A
User must be able to enter and store enquiries received from customer
User must be able to prepare and store quotations
User must be able to enter and store orders received from customer
User must be able to record receipt of payment advance from customer
User must be able to record details of order confirmations sent to the customer
User must be able to enter and store customer negotiation history in the form of min-utes of meeting or phone call or any other form
User must be able to record complaints received from customer
User must be able to request for spare to be sent to customer
User must be able to place a service call for an engineer to be sent to customer site
User must be able to create and store service report
The system should be capable of aggregating the data records present in the database and deliver actionable reports to enable the higher management to make sound deci-sions
SRS FOR TEST PROJECT Version : 1.0
Page | 8
4.1. Diagrams
After sales serviceSales and Order Processing
prepare quotation
log and send quotation
Process enquiry
record amendments
Customer enquiry
Add new customer into DB
Log enquiry
Execute order and update status
log complaint
no
yes
New customer
Raise call to service engineer
Requisition spares
Log service report
yes
no
Spares needed
Figure 3 : Activity Diagram - Sales and after sales
SRS FOR TEST PROJECT Version : 1.0
Page | 9
SALES SYSTEM
SALES EXECUTIVE
MANAGER
LOGS ENQUIRY
PREPARE QUOTATION
LOG / UPDATE ORDER
VIEW ORDER
PRODUCTION
UPDATE ORDER STATUS
SERVICE ENGINEERUPDATE SERVICE
REQUESTS
LOG SERVICE REQUEST
REQUEST SPARES
DISPATCH SPARES &CLOSE REQ.
STORE IN-CHARGE
VIEW SERVICE
REQUESTS
S
UPDATE CUSTOMER
MASTER
Figure 4 : USE CASE Diagram - Sales and after sales system
SRS FOR TEST PROJECT Version : 1.0
Page | 10
ENQUIRY
ENQUIRIES
LOG ENQUIRY IN TO THEY SYSTEM
UPDATE DB
PREPARE QUOTATION
QUOTATIONS
UPDATE DB
ORDER CONFIRMATION
ORDERS
UPDATE DB
NEGOTIATION
IF NEEDED
UP
DA
TE D
B
EXECUTION
UPDATE DB
DISPATCH
SAMPLING
IF NEEDED
UP
DA
TE D
B
UPDATE CUSTOMER
MASTER
IF NEEDED
CUSTOMER DB
LINKED BY CUSTOMER ID
LINKED BY CUSTOMER ID
LINKED BY CUSTOMER ID
NEW CUSTOMER
Figure 5 : Basic Sales Flow
COMPLAINT
COMPLAINTS
LOG COMPLAINT IN TO THEY SYSTEM
UPDATE DB
REQUISITION SPARES
REQUISITIONS
UPDATE DB
DISPATCH SPARES
SERVICE REPORTS
DISPATCH SERVICE ENGINEER
UPDATE DB
RESOLVE
CUSTOMER DB
LINKED BY CUSTOMER IDLINKED BY CUSTOMER ID
LINKED BY CUSTOMER ID
Figure 6 : Basic after sales flow
Figure 7 : Context level DFD - Sales and After Sales system
SRS FOR TEST PROJECT Version : 1.0
Page | 11
Figure 8 : Gane-Sarson DFD - Market research module
SRS FOR TEST PROJECT Version : 1.0
Page | 12
5. Non-functional requirements The system should be able to support a minimum of 100 concurrent users
Any activity of the system (e.g. Login, retrieval etc) should complete within 5 seconds
Windows Active Directory authentication support required
SRS FOR TEST PROJECT Version : 1.0
Page | 13
6. Data dictionary
<<Intentionally left out of the scope of this document>>
Proprietary and Confidential
TEST PROJECT
Sales & Marketing Business Processes
No Activity
Enquiry
1.1 Enquiry is received via mail, telephone, or email.
1.2 Enquiry is recorded in a manual log
Quotation
2.1 Review of the enquiry for technical requirements
2.2 The customer is contacted if clarification/sample is required
2.3 Any pilot runs or sample tests are conducted in-house
2.4 Quotation is prepared and sent to the customer
2.5 Quotation is recorded in a manual log
Negotiation and Finalization
3.1 Telephone calls, or meetings are arranged to discuss technical queries, financial
terms, and delivery details.
3.2 Minutes of phone call or meetings are recorded in a manual log
3.3 Order Confirmation is sent to the customer and advance collected
3.4 Order Confirmation is recorded in a manual log
Execution
4.1 Order amendments are recorded in a manual log
4.2 Layout drawings are sent to customer.
4.3 Final inspection is conducted by customer.
4.4 Dispatch, erection, and commissioning details are finalized with customer.
After Sales Service
5.1 Complaints are received via mail, telephone, or email.
5.2 Complaint is logged in a manual log
5.3 Required parts are sent to customer
5.4 Service engineer is sent to customer
5.5 Service engineer report is logged in a manual log
8. Appendix – A
Page | 14
Proprietary and Confidential
Business Application System Requirements
The company desires a business application system that would meet the Sales &
Marketing process requirements as detailed above.
A Market Research Module is also desired to enable the company to capture customer
information and make better use of it for strategy and action reports. The module would
include…
• Customer Database
o Company Information, Purchase History, Product Usage, Expansion
Plans, Visit Logs, etc.
• Product Database
o Technical Specifications, Applications, Associated Consumables (Mediaand Chemicals) etc.
• Competition Database
o Products, Sales History, Market Share, Market Prices, Customer
Feedback, etc.
• Other Information
o Finance Schemes, Environmental Regulations, Taxation Details, etc.