Strider E Gas Sewa

Software Requirements Specification

Version<1.0>

KALINGA INSTITUTE OF INDUSTRIAL TECHNOLOGY BHUBANESWAR

TeamGuide

Kumar Devadutta
(Asst. Professor)

Dept. of Computer Science & Engineering Members Swapnit Das Swati Sonali Sahu

Strider/KIIT

Page1

E Gas Sewa Software Requirements Specification Strider

Version 1.0 14-12-2011

Table of Contents

Description
1.0 Introduction 1.1 1.2

Page no.

Purpose... 4 Scope 4

1.3 1.4 1.5 1.6

Definition, Acronyms, and Abbreviations. 5 References.. 6 Technologies to be used...6 Overview.... 6

2.0 Overall Description

2.1 2.2 2.3 2.4

Strider/KIIT

Product Perspective... 7 Software Interface... 8 Hardware Interface..... 8 Product Function.... 9

Page2

2.5 User Characteristics.... 9 2.6 Constraints. 10 2.7 Architecture Design... 10 2.8 2.9 Use Case Model Description.. 12 Class Diagram ... 13

2.10 Sequence Diagrams.......15 2.11 Database Design 2.11.1 ER Diagram........ 2.11.2 Schema....... 26 27

2.12 Assumptions and Dependencies...... 28 3.0 Specific Requirements 3.1 3.2 Use Case Reports..... Activity Diagrams... 29 33

4.0 Supporting Information 4.1 Index 46

Strider/KIIT

Page3

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 Page4

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 Java 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 service. 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

Page5

 HTTP (Hyper Text Transfer Protocol): It is a transaction oriented client/ server protocol between a web browser and a web server. ADMIN : Administrator. He has the complete control over the system and the authority 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 Practitioners 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

Page6

 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 Page7

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

Page8

2.2

Software Interface:
Web browser (Firefox, Opera, Chrome, Internet Explorer) Operating System (Windows, Linux)

Front End Client:

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:

Browser

Processor

Ram

Disk Space 100 MB

Firefox / Chrome / Intel Pentium or 256 MB Internet Explorer AMD 1 GHz Server Side:
Software DB2 RAD Processor Intel Pentium 4 or AMD Athlon or Higher Ram 1.5 GB 1 GB

Disk Space 4.8 GB 1.4 GB + Database Space Page9

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 complaint for unsatisfactory service, participate in discussion forum. They can also update 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 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 discussion forum. He can generate reports about all transactions.

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 Page10

2.7 Architecture Design:

Fig 2: Architecture Design Strider/KIIT Page11

2.8 Use Case Model Description :

<<uses>> Search for Customer / Distributor Audit Database View Customer / Distributor

Authenticate Registration

Take Backup

Admin

View Logs

Generate Reports Address Complaints View Complaints Login Logout View Profile Participate in Discussion forum Search Dealers

Apply for connection <<extend>>

Update Profile Lodge Complaint Distributor View Orders Register Customer

Orders

Cancel Order Place Order

View Status

Fig 3: Use Case Model

Strider/KIIT

Page12

Customer: Unregistered customers can register themselves. Registered customers can place order by booking gas or by cancelling an ordered gas. They can lodge complaint against distributor for unsatisfactory service. Customers can update their profile information as needed. They can also participate 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 discussion forum. He can generate reports about all transactions.

2.9 Class Diagram:

Strider/KIIT

Page13

Person Name : String Address : String DOB : Date e-mail : String Phone : String Password : String

DiscussionForum TopicID : String CreatorID : Integer Details : String +canParticipate ShowRecent() SelectTopic() ShowDetails() RequestSearch() EnterSearchDetails() RequestTopicDetails() GenerateTopicID() PostSuccessful() +canParticipate

Customer CID : String EnterDetails() VerifyDetails() SetDetails() CustomerRegistration() CustomerUpdate() RegistrationSuccessful() UpdateSuccessful() DisplayCustomerPage() DisplayErrorPage() EnterComplaintDetails()

Distributor DID : String +canParticipate EnterDetails() VerifyDetails() SetDetails() DistributorRegistration() DistributorUpdate() RegistrationSuccessful() UpdateSuccessful() DisplayDistributorPage() DisplayErrorPage() ViewPaymentStatus() ConfirmDelivery() AddressComplaint()

Admin AID : String EnterUsernamePassword() VerifyDetails() DisplayErrorPage() DisplayAdminPage() AddressComplaint() ForwardToDistributor()

+canPlace 1..* Order OrderID : String BookingData : Date DeliveryData : Date +canDeliver EnterBookingDetails() EnterPaymentDetails() TransactionSuccess() TransactionFailed() OrderSuccessful() AddOrder() 1..* Cancel CancelID : String CancelDate : Date SelectOrder() Delivered() NotDelivered() CannotCancel() RequestConfirmation() SendConfirmation() MoveToCancel() CancelDone() CancelSuccessful()

+canAddress 1..* +canAddress 1..* Complaints ComplaintID : String Details : String +canLodge 0..* RequestComlaintDetails() GenerateID() ForwardToAdmin()

Fig 4: Class Diagram Strider/KIIT Page14

2.10 Sequence Diagrams:

2.10.1 Customer Login Sequence Diagram

Customer 1 : LoginPrompt()

Interface

Database

2 : EnterUsernamePassword() 3 : SendData() 4 : ValidateData()

alt [Success] 6 : DisplayCustomerPage() [Failure] 8 : DisplayErrorPage()

5 : ValidationSuccess()

7 : ValidationFail()

Fig 5: Sequence Diagram Representing Customer Login

Strider/KIIT

Page15

2.10.2 Distributor Login Sequence Diagram

Distributor

Interface

Database

1 : LoginPrompt() 2 : EnterUsernamePassword() 3 : SendData() 4 : ValidateData()

alt [Success] 6 : DisplayAdminPage() [Failure] 7 : ValidationFail() 8 : DisplayErrorPage() 5 : ValidationSuccess()

Fig 6: Sequence Diagram Representing Distributor Login

Strider/KIIT

Page16

2.10.3 Admin Login Sequence Diagram

Administrator 1 : LoginPrompt()

Interface

Database

2 : EnterUsernamePassword()

3 : SendData() 4 : ValidateData()

alt [Success] 5 : ValidationSuccess() 6 : DisplayAdminPage()

[Failure] 8 : DisplayErrorPage()

7 : ValidationFail()

Fig 7:Sequence Diagram Representing Admin Login

Strider/KIIT

Page17

2.10.4 Customer Registration Sequence Diagram

Customer

Interface

Database

1 : PromptEnterDetails() 2 : EnterDetails() 3 : SendData() 4 : ValidateUsername()

alt

[Failure] 6 : EnterDetails()

5 : UserExists()

[Success]

7 : ValidationSuccess() 8 : ValidatePassword() 9 : InvalidPassword() 10 : ValidateMandatory() 11 : EnterDetails() 13 : RegistrationSuccessful() 14 : DisplayCustomerPage() 12 : SetDetails()

Fig 8: Sequence Diagram Representing Customer Registration

Strider/KIIT

Page18

2.10.5 Distributor Registration Sequence Diagram

Distributor

Interface

Distributor

Admin

1 : PromptEnterDetails() 2 : EnterDetails() 3 : SendData() 4 : ValidateUsername()

alt [Failure] 6 : EnterDetails() 5 : UserExists()

[Success]

7 : ValidationSuccess() 8 : ValidatePassword() 9 : InvalidPassword() 11 : EnterDetails() 13 : VerifyDetails() 14 : RegistrationApproved() 10 : ValidateMandatory() 12 : ForwardToAdmin()

Fig 9: Sequence Diagram Representing Distributor Registration

Strider/KIIT

Page19

2.10.6 Customer Profile Update Sequence Diagram

Customer 1 : PromptEnterDetails() 2 : EnterDetails()

Interface

3 : VerifyPassword()

alt

[Failure] 4 : InvalidPassword()

[Success]

5 : ValidateMandatory()

alt

[Failure] 6 : EnterDetails() [Success] 7 : UpdateSuccessful()

8 : DisplayCustomerPage()

Fig 10: Sequence Diagram Representing Customer Profile Update

Strider/KIIT

Page20

2.10.7 Book Gas Sequence Diagram

Customer

Interface

Payment Gateway

Database

1 : RequestBookingDetails() 2 : EnterBookingDetails()

3 : RequestPaymentDetails() 4 : EnterPaymentDetails()

alt [Failure] 6 : RequestPaymentDetails() 5 : TransactionFailed()

[Success] 7 : TransactionSuccess() 8 : OrderSuccessful() 9 : AddOrder()

Fig 11: Sequence Diagram for Booking Gas

Strider/KIIT

Page21

2.10.8 Confirm Delivery Sequence Diagram

Distributor

Interface

Database

1 : ListOrders() 2 : SelectOrder() 3 : SendData()

4 : SendDetails() 5 : DisplayPaymentStatus() 6 : ConfirmDelivery() 7 : SendData()

Fig 12: Sequence Diagram Representing Confirm Delivery

Strider/KIIT

Page22

2.10.9 Cancel Gas Sequence Diagram

Customer

Interface

Database

1 : ListOrders() 2 : SelectOrder()

3 : SendData() 4 : IfDelivered()

alt [Failure] 6 : CannotCanel() [Success] 8 : RequestConfirmation() 9 : SendConfirmation() 7 : NotDelivered() 5 : Delivered()

10 : MoveToCancel()

11 : CancelDone() 12 : CancelSuccessful()

Fig 13: Sequence Diagram forCancelling Gas

Strider/KIIT

Page23

2.10.10 Lodge Complaint Sequence Diagram

Customer

Interface

Distributor

Admin

Database

1 : RequestComplaintDetails() 2 : EnterComplaintDetails() 3 : SendData() 4 : GenerateID()

6 : AddressCompaint() 7 : ShowReply() 8 : ForwardtoDistributor() 9 : SendData()

5 : SendToAdmin()

10 : AddressComplaint() 11 : ShowReply()

Fig 14: Sequence Diagram forLodging Complaint

Strider/KIIT

Page24

2.10.11

Discussion Forum Sequence Diagram

Customer

Interface

Database

1 : ShowRecent() opt [Select]

2 : SelectTopic()

3 : SendData()

5 : ShowDetails() [Search] 6 : RequestSearch() 7 : EnterSearchDetails()

4 : RetriveData()

8 : SendData() 9 : SearchTopic() 10 : TopicsFound()

11 : ShowTopics()

[Create] 12 : RequestTopicDetails() 13 : EnterDetails() 14 : SendData() 15 : GenerateTopicID()

16 : PostSuccessful() 17 : ShowDetails()

Fig 15: Sequence Diagram Representing Discussion Forum

Strider/KIIT

Page25

2.1 Data 11 abase Design:

2.11 ER Di 1.1 iagram

Fig 16: Entity Relationship Diagram g i Strid der/KIIT Page26 6

2.11.2 Schem 2 ma

Fig 17: Schema a

Strid der/KIIT

Page27 7

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

Page28

3. Specific Requirements
3.1
3.1.1

Use Case Reports:

Customer Use Case Report

Find dealer Update Profile <<extend>>

<<extend>> Register Change area n dealer <<extend>> View Profile <<extend>> Place Order

Cancel Order Order <<extend>>

Customer

Login View Status Participate in discussion forum Search accessories

Lodge Complaint

Fig 18: Customer Use Case Diagram

Strider/KIIT

Page29

Use Case Register Login View Profile

Description Every customer has to register in order to use the features Customers have to log in to use the system Every registered customer has a profile which contains his personal information

Update Profile The customers can update their profile information as required Change area The customers can change their area and respective and dealer dealer if they change their residence Place Order Cancel Order View Status Lodge plaint The customers can place their order, i.e. book a gas The customers can cancel their order, i.e. cancel a booked gas The customers can view the status of their booking

Com- The customers can lodge complaints for unsatisfactory service

Participate in The customers can participate actively in the discussion discussion fo- forum rum Search Acces- The customers can search for accessories required sories

Strider/KIIT

Page30

3.1.2

Distributor Use Case Report

<<extend>> Register View Profile

Update Profile Deliver <<extend>>

<<extend>>

View Paymemnt Status

Distributor

Login

View Orders

View Reports View Complaints <<extend>> Participate in Discussion forum

Address Complaints

Fig 19: Distributor Use Case Diagram

Strider/KIIT

Page31

Use Case Register

Description Every distributor has to register in order to use the features

Login View Profile

Distributors have to log in to use the system Every registered distributor has a profile which contains his personal information

Update Profile

The distributors can update their profile information as required

View Orders View Payment Status Deliver

The distributors can view the orders placed The distributors can view whether the payments for the orders are successfully transferred or not The distributors can confirm the delivery after they verify the payment status

View Reports Participate in discussion forum View Complaints Address Complaints

The distributor can view reports on their transactions The distributors can participate actively in the discussion forum

The distributors can view complaints forwarded to them by the admin The distributors can address the complaints after viewing

Strider/KIIT

Page32

3.1.3 3

Admin Use Case Report R

ig in Fi 20: Admi Use Case Diagram

Use Case Log gin Acc Regist cept trations

Strid der/KIIT

Descrip ption The Admin ha to log in to use the system as The Admin ac ccepts the r registration of the distributors after verins ficat tion
Page33 3

Search er/Distributor

Custom- The Admin can search for customers and distributors The Admin can view the profile details of any customer or distributor

View Customer/Distributor

View and Address Com- The Admin can view complaints and address them or forward plaints them to the distributors Audit Database Participate Forum Take Backup in The Admin can audit the system database to make modifications Discussion The Admin can participate actively in the discussion forum The Admin can take backup of the system on timely basis

3.2 Activity Diagrams

3.2.1 Customer Login Activity

Enter username and password

Verify username and password

Invalid Valid Login Successful

Customer home page

Fig 21: Activity Diagram for Customer Login Strider/KIIT Page34

The customer has to enter his/her user name and password, which is then verified after the customer 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 distributor 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.

Enter username and password

Verify username and password

Invalid Valid Login Successful

Distributor home page

Fig 22: Activity Diagram for Distributor Login

Strider/KIIT

Page35

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.

Enter username and password

Verify username and password

Invalid Valid Login Successful

Administrator home page

Fig 23: Activity Diagram for Admin Login

Strider/KIIT

Page36

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 registration is completed successfully and the customer is taken to the profile page.

Enter details

If user name exists Invalid

Validation of user name Password not matching Valid Validation of password Invalid Valid Validation of mandatory fields Fill mandatory details

Invalid

Valid Registration successful

Go to customer profile page

Fig 24: Activity Diagram for Customer Registration Strider/KIIT Page37

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 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 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.

Enter details

If user name exists Invalid

Validation of user name Password not matching Valid Validation of password Invalid Valid Validation of mandatory fields Fill mandatory details

Invalid

Valid Forward to admin for verification Invalid Info

Valid Registration approved Send confirmation to registrant Registration denied

Fig 25: Activity Diagram for Distributor Registration Strider/KIIT Page38

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 verification of all details the update is successful and the user to taken to the profile page.

User login

Update Profile

Enter details

Validation of password Invalid

Password not matching Fill mandatory details

Valid Validation of mandatory fields

Valid Update Successful

Go to customer profile page

Fig 26: Activity Diagram for Profile Update Strider/KIIT Page39

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 details 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 Transaction failed Success Add order for processing

Order Successful

Strider/KIIT

Page40

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 presented 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.

Customer Login

Booking page

Booked history

Select order to cancel

Check if delivered Delivered Not delivered Cancel confirmation No Yes Cancel successful Cannot cancel delivered order

Fig 28: Activity Diagram for Cancelling Order Strider/KIIT Page41

3.2.9 Confirm Delivery Activity

The distributor first logs in to his account and views the pending orders page. Then he/she selects 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.

Distributor login Orders page

View pending orders Select order

View payment status Payment not done Payment done Confirm delivery

Fig 29: Activity Diagram for Confirm Delivery

Strider/KIIT

Page42

3.2.10 Lodge Complaint Activity

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

Customer login

Complaints page

Enter complaint details

Send to admin

Fig 30: Activity Diagram for Lodging Complaint

Strider/KIIT

Page43

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.

Admin login

Complaints

View pending complaints

Reply to customer

Forward to distributor

Fig 31: Activity Diagram for Addressing Complaint by Admin

Strider/KIIT

Page44

3.2.12 Addressing Complaint by Distributor Activity

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

Distributor login Complaints

View pending complaints

Reply to customer

Fig 32: Activity Diagram for Addressing Complaint by Distributor

Strider/KIIT

Page45

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.

View recent posts and topics

Search topic

Select topic

Create a new topic

Reply to post

Enter details

Show results

Submit

Fig 33: Activity Diagram for Participating in Discussion Forum Strider/KIIT Page46

4.0 Supporting Information

4.1
A Admin 4, 5, 9, 13 Administrator 4, 5, 13 Acronyms 5 Abbreviations 5 Architecture 10 Activity Diagram 33 B Book 4, 9, 21, 30 C Customer 4, 9, 13 Cancel 4, 9, 23, 30 Complaints 7 Constraints 10 Class Diagram 13 D Distributor 4, 9, 13 Dealers 4, 5 Definitions 5 DB2 5, 6, 8 Delivery 7, 9, 22 Drawbacks 7 E ER Diagram 26 F Forum 4, 5, 7 Strider/KIIT Page47 RAD 6, 8 Registration 4, 6, 7 References 6

Index:
H Hardware 9, 18 HTML 5, 8 HTTP 5 I Introduction 4 Interface 8, 9 J J2EE 5, 6 JSP 5, 6, 8 O Overview 6 Overall 4, 7 Operating System 8 Order 4, 9, 29 P Purpose 4 Perspective 7 Product 7, 8, 9 R T Technologies 6 Transaction 4, 9, 13 U Use case 12, 29 User 4, 6, 7, 28 W WASCE 5, 6, 8 S Scope 4 Sequence Diagram 15 Server 6, 8, 9 Service 5, 9, 13