SRSv-1

Strider/KIIT

Strider E – Gas Sewa

Software Requirements Specification Version<1.0>

KALINGA INSTITUTE OF INDUSTRIAL TECHNOLOGY

BHUBANESWAR

Team Guide Kumar Devadutta

(Asst. Professor) Dept. of Computer Science & Engineering

Members

Swapnit Das

Swati Sonali Sahu

Strider/KIIT

E – Gas Sewa Version 1.0 Software Requirements Specification 14-12-2011 Strider

Table of Contents

Description Page no.

1.0 Introduction

1.1 Purpose………………………………………………………... 4

1.2 Scope…………………………………………………………… 4

1.3 Definition, Acronyms, and Abbreviations……………………. 5

1.4 References……………………………………………….………. 6

1.5 Technologies to be used…….…………………………………..6

1.6 Overview……………………………………….………………... 6

2.0 Overall Description

2.1 Product Perspective….……………………………………….. 7

2.2 Software Interface…..…………………………………………. 8 2.3 Hardware Interface……..……………………………………... 8 2.4 Product Function………………..…………………….………. 9

Strider/KIIT

2.5 User Characteristics……………………………...….………… 9 2.6 Constraints……………………………………………………. 10

2.7 Architecture Design……………………………………………... 10

2.8 Use Case Model Description…….……………………………. 12

2.9 Class Diagram ………………….………………………….……. 13

2.10 Sequence Diagrams…………………...………………………....15 2.11 Database Design

2.11.1 ER Diagram…………….……………………...…....… 26

2.11.2 Schema…….……………………………………...…... 27

2.12 Assumptions and Dependencies…………...………….….….… 28

3.0 Specific Requirements

3.1 Use Case Reports….…….………………………………………... 29

3.2 Activity Diagrams….…………………………………………….. 33

4.0 Supporting Information

4.1 Index………………………………………………………… 46

Strider/KIIT

1.0 Introduction 1.1 Purpose:

E-Gas Sewa is an online web service for gas agency of Indian Company to make the availability and booking of LPG and other services a much more easier ,systematic and fast process than the old tedious manual method . It also aims in reducing paper work and securing transaction details more efficiently, benefiting customers and dealers in vast area of company services. The old process of gas booking through phone or by manually going to the dealer is replaced by this online service.

1.2 Scope:

There are 3 basic user- Customer , Admin, Distributor(Dealers). All users have their profiles in E-Gas Sewa which they can view and update at any point of time. Customer can-

• Create and update their account. • Book gas online. • Lodge complaints against a service. • Apply for transfer of LPG connection to another location. • Cancel an existing order of LPG • Search and request of LPG accessories. • Participate in discussion forum. • Search and change dealer.

Distributors are basically dealers and franchise owner who supply LPG gas to the customers.

They can- • Apply for dealership online or register as a dealer. • View orders and payment status of the orders. • View reports. • Participate in discussion forum. • View complaints.

Strider/KIIT

Admin administer the overall performance and working of this system. They can-

• Accept registrations for dealership. • Accept request for new LPG connection or transfer of connection of a customer. • Audit all data base. • View profiles of customers and distributors. • Generate and view reports. • Search for existing customer or distributor. • View and address complaints. • View logs. • Take backup of data. • Participate in discussion forum.

1.3 Definitions, Acronyms, and Abbreviations:

• HTML (Hyper Text Markup Language): It is used to create static web pages.

• JSP (Java Server Pages): It is used to create dynamic web content.

• J2EE (Java 2 Enterprise Edition): It is a programming platform, belonging to the Ja-

va platform, which is used for developing and running distributed java applications.

• WASCE (WebSphere Application Server Community Edition): It is an application

server that runs and supports the J2EE and the web service applications.

• WSAD (WebSphere Studio Application Developer ): It is a designer toolkit which is

designed to develop more complex projects by providing a complete dynamic web ser-

vice.

• DB2 (IBM Database 2): It is a database management system that provides a flexible

and efficient database platform to raise a strong "on demand" business applications.

Strider/KIIT

• HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server pro-

tocol between a web browser and a web server.

• ADMIN : Administrator. He has the complete control over the system and the author-

ity to approve or remove customers and distributors, view reports and audit database.

• XML (Extensible Markup Language): It is a markup language that was designed to

transport and store data.

• Ajax (Asynchronous Java Script and XML): It is a technique used in java script to

create dynamic web pages.

• Web 2.0: It is commonly associated with web applications which facilitate interactive

information sharing, interoperability, user-centered design and collaboration on the

World Wide Web.

1.4 References:

Software Engineering, A Practitioner’s Approach by Roger S Pressman

Database Systems Concepts by Korth

DB2 Certification materials

The Complete Reference J2EE by Keogh

IBM TGMC resources

IBM Redbooks

1.5 Technologies to be used:

• J2EE: (Servlet, JSP, JAXP, Java Beans) Application architecture.

Strider/KIIT

• JAVA: Application architecture.

• WASCE: (WebSphere Application Server Community Edition) Web Server

• DB2: IBM Database.

• Ajax: Asynchronous Java Script and XML.

• XML: Extension Markup Language. Web 2.0: RSS Feed 2.0.

• RAD 7.0: Development tool.

1.6 Overview:

Existing System: Registration for customers Booking and Cancellation of Gas Complaints

Drawbacks: No registration for dealers(distributors) No discussion forum No provision for ordering accessories No way of viewing delivery status No report system for Admin and Distributors No FAQ about the system Users cannot view the recent rates or security aspects of using LPG gas

Proposed System:

Registration for customers and dealers(distributors) Online booking and cancellation of gas Viewing the delivery status of booked gas Active discussion forum for customers, distributors and admin

Strider/KIIT

Comprehensive FAQ about the system Both users and guests can view the rates and security aspects A dedicated section of QA

Our Plan:

Registration for customers and dealers(distributors) Online booking and cancellation of gas Online ordering of accessories Active discussion forum A detailed reporting system for Admin and Distributor

2.0 Overall Description:

2.1 Product Perspective:

Fig 1: Product Perspective

Strider/KIIT

2.2 Software Interface: Front End Client:

Web browser (Firefox, Opera, Chrome, Internet Explorer)

Operating System (Windows, Linux)

Web Server:

WASCE

Operating System (Windows Server, Fedora, RedHat)

Database Server

DB2

Operating System (Windows Server, Fedora, RedHat)

Back End:

Rational Rose (Modeling),RAD (J2EE, Java Beans, JSP, HTML, XML, AJAX), DB2 (Database), Operating System (Windows, Fedora), Websphere (Webserver)

2.3 Hardware Interface:

Client Side:

Server Side:

Browser Processor Ram Disk Space Firefox / Chrome / Internet Explorer

Intel Pentium or AMD 1 GHz

256 MB 100 MB

Software Processor Ram Disk SpaceDB2 Intel Pentium 4 or

AMD Athlon or Higher

1.5 GB 4.8 GB

RAD 1 GB 1.4 GB + Data-base Space

Strider/KIIT

2.4 Product Functions:

Customers can book / cancel gas online Distributors can confirm delivery after receiving payment online Customers can lodge complaints for unsatisfactory service Customers, Distributors and Admin can take part in discussion forum Customers can order accessories online

2.5 User Characteristics:

Customer: Customers can book gas, cancel booked gas, request for accessories, lodge com-plaint for unsatisfactory service, participate in discussion forum. They can also up-date their profile when required

Distributor: Distributors can view orders and confirm their delivery. They can view complaints forwarded to them by the administrator and address them accordingly. They can up-date their profile information as needed. They participate in discussion forum. They can also generate reports about their daily or monthly transactions. Admin: The admin or administrator has complete control over the system. He authenticates distributor registration, add/ delete users as required. He can view complaints by the customers and address them or forward them to the respective distributor. The admin can also participate in the discussion forum. He can generate reports about all trans-actions.

2.6 Constraints:

The interface is only in English

Only registered users can use the system

Guests are limited to view the FAQ section only.

Strider/KIIT

2.7 Architecture Design:

Fig 2: Architecture Design

Strider/KIIT

2.8 Use Case Model Description :

Fig 3: Use Case Model

Search for Customer / Distributor

Place OrderCancel Order

View Orders

Distributor

View Complaints

View Logs

Generate Reports

Take Backup

Authenticate Registration

Audit Database View Customer / Distributor

<<uses>>

Address Complaints

Admin

Register

Login Logout View Profile Participate in Discussion forum

Apply for connection

Lodge Complaint

Search Dealers

Update Profile

<<extend>>

Orders

Customer

View Status

Strider/KIIT

Customer: Unregistered customers can register themselves. Registered customers can place order by book-ing gas or by cancelling an ordered gas. They can lodge complaint against distributor for unsa-tisfactory service. Customers can update their profile information as needed. They can also par-ticipate in the discussion forum. Distributor: Unregistered distributors can register themselves. Registered distributors can view orders and confirm their delivery. They can view complaints forwarded to them by the administrator and address them accordingly. They can update their profile information as needed. They participate in discussion forum. They can also generate reports about their daily or monthly transactions. Admin: The admin or administrator has complete control over the system. He authenticates distributor registration, add/ delete users as required. He can view complaints by the customers and address them or forward them to the respective distributor. The admin can also participate in the discus-sion forum. He can generate reports about all transactions.

2.9 Class Diagram:

Strider/KIIT

Fig 4: Class Diagram

PersonName : StringAddress : StringDOB : Datee-mail : StringPhone : StringPassword : String

ComplaintsComplaintID : StringDetails : String

RequestComlaintDetails()GenerateID()ForwardToAdmin()

AdminAID : String

EnterUsernamePassword()VerifyDetails()DisplayErrorPage()DisplayAdminPage()AddressComplaint()ForwardToDistributor()

1..*

DiscussionForumTopicID : StringCreatorID : IntegerDetails : String

ShowRecent()SelectTopic()ShowDetails()RequestSearch()EnterSearchDetails()RequestTopicDetails()GenerateTopicID()PostSuccessful()

CustomerCID : String

EnterDetails()VerifyDetails()SetDetails()CustomerRegistration()CustomerUpdate()RegistrationSuccessful()UpdateSuccessful()DisplayCustomerPage()DisplayErrorPage()EnterComplaintDetails()

0..*

CancelCancelID : StringCancelDate : Date

SelectOrder()Delivered()NotDelivered()CannotCancel()RequestConfirmation()SendConfirmation()MoveToCancel()CancelDone()CancelSuccessful()

DistributorDID : String

EnterDetails()VerifyDetails()SetDetails()DistributorRegistration()DistributorUpdate()RegistrationSuccessful()UpdateSuccessful()DisplayDistributorPage()DisplayErrorPage()ViewPaymentStatus()ConfirmDelivery()AddressComplaint()

1..*OrderOrderID : StringBookingData : DateDeliveryData : Date

EnterBookingDetails()EnterPaymentDetails()TransactionSuccess()TransactionFailed()OrderSuccessful()AddOrder()

1..*

1..*

1..*+canPlace

1..*

+canDeliver

0..*

+canLodge

1..*1..*

+canAddress+canAddress

+canParticipate

+canParticipate

+canParticipate

Strider/KIIT

2.10 Sequence Diagrams:

2.10.1 Customer Login Sequence Diagram

Fig 5: Sequence Diagram Representing Customer Login

alt

Customer Interface Database

1 : LoginPrompt()

2 : EnterUsernamePassword()

3 : SendData()

4 : ValidateData()

5 : ValidationSuccess()

6 : DisplayCustomerPage()

7 : ValidationFail()

8 : DisplayErrorPage()

[Success]

[Failure]

Strider/KIIT

2.10.2 Distributor Login Sequence Diagram

Fig 6: Sequence Diagram Representing Distributor Login

alt

Distributor DatabaseInterface

1 : LoginPrompt()

2 : EnterUsernamePassword()

3 : SendData()

4 : ValidateData()


6 : DisplayAdminPage()



[Success]

[Failure]

Strider/KIIT

2.10.3 Admin Login Sequence Diagram

Fig 7:Sequence Diagram Representing Admin Login

alt

InterfaceDatabaseAdministrator

1 : LoginPrompt()

2 : EnterUsernamePassword()3 : SendData()

4 : ValidateData()


6 : DisplayAdminPage()



[Success]

[Failure]

Strider/KIIT

2.10.4 Customer Registration Sequence Diagram

Fig 8: Sequence Diagram Representing Customer Registration

alt


1 : PromptEnterDetails()

2 : EnterDetails()3 : SendData()

4 : ValidateUsername()

5 : UserExists()

6 : EnterDetails()

7 : ValidationSuccess()8 : ValidatePassword()

9 : InvalidPassword()10 : ValidateMandatory()

11 : EnterDetails() 12 : SetDetails()

13 : RegistrationSuccessful()

[Failure]

[Success]


Strider/KIIT

2.10.5 Distributor Registration Sequence Diagram

Fig 9: Sequence Diagram Representing Distributor Registration

alt

Distributor Interface Distributor Admin



4 : ValidateUsername()

5 : UserExists()6 : EnterDetails()


8 : ValidatePassword()

9 : InvalidPassword()10 : ValidateMandatory()

11 : EnterDetails()

[Failure]

[Success]

12 : ForwardToAdmin()

13 : VerifyDetails()14 : RegistrationApproved()

Strider/KIIT

2.10.6 Customer Profile Update Sequence Diagram

Fig 10: Sequence Diagram Representing Customer Profile Update

alt

altaltalt

Customer Interface


2 : EnterDetails()

3 : VerifyPassword()

4 : InvalidPassword()

5 : ValidateMandatory()

6 : EnterDetails()

7 : UpdateSuccessful()


[Failure]

[Success]

[Failure]

[Success]

Strider/KIIT

2.10.7 Book Gas Sequence Diagram

Fig 11: Sequence Diagram for Booking Gas

alt

Customer Interface DatabasePayment Gateway

1 : RequestBookingDetails()

2 : EnterBookingDetails()

3 : RequestPaymentDetails()

4 : EnterPaymentDetails()

5 : TransactionFailed()

6 : RequestPaymentDetails()

7 : TransactionSuccess()

8 : OrderSuccessful()9 : AddOrder()

[Failure]

[Success]

Strider/KIIT

2.10.8 Confirm Delivery Sequence Diagram

Fig 12: Sequence Diagram Representing Confirm Delivery

Distributor Interface Database

1 : ListOrders()

2 : SelectOrder() 3 : SendData()

4 : SendDetails()

5 : DisplayPaymentStatus()

6 : ConfirmDelivery()7 : SendData()

Strider/KIIT

2.10.9 Cancel Gas Sequence Diagram

Fig 13: Sequence Diagram forCancelling Gas

alt


1 : ListOrders()2 : SelectOrder()

3 : SendData()

4 : IfDelivered()

5 : Delivered()

6 : CannotCanel()

7 : NotDelivered()8 : RequestConfirmation()

9 : SendConfirmation()10 : MoveToCancel()

11 : CancelDone()12 : CancelSuccessful()

[Failure]

[Success]

Strider/KIIT

2.10.10 Lodge Complaint Sequence Diagram

Fig 14: Sequence Diagram forLodging Complaint

Customer AdminInterface DatabaseDistributor

1 : RequestComplaintDetails()

2 : EnterComplaintDetails()3 : SendData()

4 : GenerateID()

5 : SendToAdmin()6 : AddressCompaint()

7 : ShowReply()8 : ForwardtoDistributor()

9 : SendData()

10 : AddressComplaint()

11 : ShowReply()

Strider/KIIT

2.10.11 Discussion Forum Sequence Diagram

Fig 15: Sequence Diagram Representing Discussion Forum

opt


1 : ShowRecent()

2 : SelectTopic()3 : SendData()

4 : RetriveData()5 : ShowDetails()

6 : RequestSearch()

7 : EnterSearchDetails()8 : SendData()

9 : SearchTopic()

10 : TopicsFound()

11 : ShowTopics()

12 : RequestTopicDetails()


15 : GenerateTopicID()

16 : PostSuccessful()17 : ShowDetails()

[Select]

[Search]

[Create]

Strid

2.1

2.11

der/KIIT

11 Data

1.1 ER Di

abase D

iagram

esign:

Figg 16: Entity

Relationshiip Diagram

6

Strid

der/KIIT

2.11.2

Fig

2 Schem

17: Schema

ma

a

7

Strider/KIIT

2.12 Assumptions and Dependencies: The assumptions made by the system are as follows:

All users have basic knowledge of computer and internet

The admin is already registered

The admin has complete knowledge of the software used and hardware requirements of the system

The dependencies of the system are as follows:

Services offered by the system and its users depend upon internet connection and the performance of the database.

The software requires both the DB2 and WASCE to function properly

Strider/KIIT

3. Specific Requirements

3.1 Use Case Reports: 3.1.1 Customer Use Case Report

Fig 18: Customer Use Case Diagram

Update Profile

Cancel Order

Place Order

View Status

Find dealer

Register

Customer

View Profile

<<extend>>

Order

<<extend>>

<<extend>>

<<extend>>

Change area n dealer

<<extend>>

Participate in discussion forum

Lodge Complaint

Search accessories

Login

Strider/KIIT

Use Case Description Register Every customer has to register in order to use the fea-

tures Login Customers have to log in to use the system View Profile Every registered customer has a profile which contains

his personal information Update Profile The customers can update their profile information as

required Change area and dealer

The customers can change their area and respective dealer if they change their residence

Place Order The customers can place their order, i.e. book a gas Cancel Order The customers can cancel their order, i.e. cancel a

booked gas View Status The customers can view the status of their booking Lodge Com-plaint

The customers can lodge complaints for unsatisfactory service

Participate in discussion fo-rum

The customers can participate actively in the discussion forum

Search Acces-sories

The customers can search for accessories required

Strider/KIIT

3.1.2 Distributor Use Case Report

Fig 19: Distributor Use Case Diagram

Update Profile

View Paymemnt Status

DeliverRegister

<<extend>>

Address Complaints

Distributor

View Profile

<<extend>>

View Orders

<<extend>>

View Reports

Participate in Discussion forumView Complaints

Login

<<extend>>

Strider/KIIT

Use Case Description

Register Every distributor has to register in order to use the

features

Login Distributors have to log in to use the system

View Profile Every registered distributor has a profile which con-

tains his personal information

Update Profile The distributors can update their profile information

as required

View Orders The distributors can view the orders placed

View Payment

Status

The distributors can view whether the payments for

the orders are successfully transferred or not

Deliver The distributors can confirm the delivery after they

verify the payment status

View Reports The distributor can view reports on their transactions

Participate in

discussion fo-

rum

The distributors can participate actively in the dis-

cussion forum

View Com-

plaints

The distributors can view complaints forwarded to

them by the admin

Address Com-

plaints

The distributors can address the complaints after

viewing

Strid

3.1.3

LogAcc

der/KIIT

3 Admin

Use gin cept Regist

Use Case R

Case

trations

Report

Fi

TheTheficat

ig 20: Admi

Admin ha Admin action

in Use Case

as to log in ccepts the r

Diagram

Descripto use the

registration

ption system

ns of the ddistributors

after veri-

3

-

Strider/KIIT

Search Custom-er/Distributor

The Admin can search for customers and distributors

View Customer/Distributor The Admin can view the profile details of any customer or dis-tributor

View and Address Com-plaints

The Admin can view complaints and address them or forward them to the distributors

Audit Database The Admin can audit the system database to make modifications Participate in Discussion Forum

The Admin can participate actively in the discussion forum

Take Backup The Admin can take backup of the system on timely basis

3.2 Activity Diagrams 3.2.1 Customer Login Activity

Fig 21: Activity Diagram for Customer Login

Enter username and password

Verify username and password

Invalid

Login Successful

Customer home page

Valid

Strider/KIIT

The customer has to enter his/her user name and password, which is then verified after the cus-tomer hits the login button. If the details are successfully verified then the customer is taken to the profile page else an error is displayed requesting the customer to enter the valid details.

3.2.2 Distributor Login Activity

The distributor has to enter his/her user name and password, which is then verified after the dis-tributor hits the login button. If the details are successfully verified then the distributor is taken to the profile page else an error is displayed requesting the distributor to enter the valid details.

Fig 22: Activity Diagram for Distributor Login



Invalid

Login Successful

Valid

Distributor home page

Strider/KIIT

3.2.3 Admin Login Activity

The admin has to enter his/her user name and password, which is then verified after the admin hits the login button. If the details are successfully verified then the admin is taken to the profile page else an error is displayed requesting the admin to enter the valid details.

Fig 23: Activity Diagram for Admin Login



Invalid

Login Successful

Valid

Administrator home page

Strider/KIIT

3.2.4 Customer Registration Activity

The customer is asked to fill in the details required. When the customer hits the register button, the username is verified. If the user name already exists or if its not properly entered then the user is asked to change the username. Once the username is successfully verified, its checks the password. If the password is not matching then it asks the customer to enter properly. Then the mandatory details are verified. If any mandatory details is left blank or filled incorrectly then customer is asked to fill the entries properly. After the verification of all details is done the reg-istration is completed successfully and the customer is taken to the profile page.

Fig 24: Activity Diagram for Customer Registration

Enter details

Validation of user name

If user name exists

Invalid

Validation of password

Password not matching

Invalid

Validation of mandatory fields

Fill mandatory details

Invalid

Valid

Valid

Registration successful

Go to customer profile page

Valid


InvalidValid

Valid


Strider/KIIT

3.2.5 Distributor Registration Activity The distributor is asked to fill in the details required. When the customer hits the register button, the username is verified. If the user name already exists or if its not properly entered then the user is asked to change the user-name. Once the username is successfully verified, its checks the password. If the password is not matching then it asks the customer to enter properly. Then the mandatory details are verified. If any mandatory details is left blank or filled incorrectly then distributor is asked to fill the entries properly. After the verification of all details is done the registration details are forwarded to the admin for verification. Once admin verifies the details the distributor account is created and if the admin denies the registration then the account is rejected.

Fig 25: Activity Diagram for Distributor Registration

Enter details

Validation of user name

If user name exists

Invalid

Validation of password

Password not matching

Invalid



Invalid

Valid

Valid

Forward to admin for verification

Registration approved

Send confirmation to registrant

Registration denied

Invalid Info

Valid

Valid

Strider/KIIT

3.2.6 Update Profile Activity Both customers and distributors can update their profile according to their need. The users are asked to enter the details. The password and mandatory details are verified as in the registration activity. After the successful veri-fication of all details the update is successful and the user to taken to the profile page.

Fig 26: Activity Diagram for Profile Update

User login

Update Profile

Enter details

Validation of password Password not

matching


Invalid

Valid

Valid


Update Successful

Go to customer profile page

Strider/KIIT

3.2.7 Booking Gas Activity

The customer first logs in to his account and go to the booking page. He/she then fill in the de-tails and proceeds for payment. The customer is then redirected to the payment gateway. If the transaction succeeds then the order is added for processing and if the transaction fails then the customer is again requested to go through the payment process.

Customer Login

Booking page

Book gas

Redirect to payment gateway

Payment successful

Add order for processing

Order Successful

Success

Transaction failed

Strider/KIIT

Fig 27: Activity Diagram for Booking Gas

3.2.8 Cancelling Order Activity

The customers goes to the booking page and selects cancel order. The customer is then pre-sented with a list of orders placed by him. He/she then selects the order to cancel. The selected order is then checked if it is already delivered or not. If the order is delivered then the user is redirected to the cannot cancel delivered order page. If the order is not already delivered then the customer is asked to confirm the cancellation of the order. If the customer selects yes then the order is added for cancellation.

Fig 28: Activity Diagram for Cancelling Order

Customer Login

Booking page

Booked history

Select order to cancel

Check if delivered

Cannot cancel delivered order

Cancel confirmation

Cancel successful

Delivered

Not delivered

Yes

No

Strider/KIIT

3.2.9 Confirm Delivery Activity

The distributor first logs in to his account and views the pending orders page. Then he/she se-lects an order and views its payment status. If the payment is successful then he confirms the delivery of the order else he goes back to select another order.

Fig 29: Activity Diagram for Confirm Delivery

Distributor login

Orders page

View pending orders

Select order

View payment status

Confirm delivery

Payment done

Payment not done

Strider/KIIT

3.2.10 Lodge Complaint Activity

The customer goes to the complaints page, enters the complaint details and sends it to admin

Fig 30: Activity Diagram for Lodging Complaint

Customer login

Complaints page

Enter complaint details

Send to admin

Strider/KIIT

3.2.11 Addressing Complaint by Admin Activity

The admin receives the complaints and views them. He/she then either replies to the customers or forwards it to the respective distributor.

Fig 31: Activity Diagram for Addressing Complaint by Admin

Admin login

Complaints

View pending complaints

Reply to customer

Forward to distributor

Strider/KIIT

3.2.12 Addressing Complaint by Distributor Activity

The distributor receives the complaints forwarded to them by the admin. He/she views the com-plaints and addresses them accordingly.

Fig 32: Activity Diagram for Addressing Complaint by Distributor

Distributor login

Complaints

View pending complaints

Reply to customer

Strider/KIIT

3.2.13 Participating in Discussion Forum Activity

All users can participate in the discussion forum. At first the recently posted topics are shown. The user can then either select a topic to view and post hi/her reply in that topic or can search for a particular topic and select the desired topic from the returned search list. The user can also create topic and post the details and submit it.

Fig 33: Activity Diagram for Participating in Discussion Forum

View recent posts and topics

Search topic Select topic Create a new topic

Show results

Reply to post Enter details

Submit

Strider/KIIT

4.0 Supporting Information

4.1 Index: A H S Admin 4, 5, 9, 13 Hardware 9, 18 Scope 4 Administrator 4, 5, 13 HTML 5, 8 Sequence Diagram 15 Acronyms 5 HTTP 5 Server 6, 8, 9 Abbreviations 5 Service 5, 9, 13 Architecture 10 I Activity Diagram 33 T Introduction 4 Technologies 6 B Interface 8, 9 Transaction 4, 9, 13 Book 4, 9, 21, 30 J U C J2EE 5, 6 Use case 12, 29 JSP 5, 6, 8 User 4, 6, 7, 28 Customer 4, 9, 13 Cancel 4, 9, 23, 30 O W Complaints 7 Constraints 10 Overview 6 WASCE 5, 6, 8 Class Diagram 13 Overall 4, 7 Operating System 8 D Order 4, 9, 29 Distributor 4, 9, 13 P Dealers 4, 5 Definitions 5 Purpose 4 DB2 5, 6, 8 Perspective 7 Delivery 7, 9, 22 Product 7, 8, 9 Drawbacks 7 R E

RAD 6, 8 ER Diagram 26 Registration 4, 6, 7 References 6 F Forum 4, 5, 7

SRSv-1

Documents

Transcript of SRSv-1