ONLINE MARKET

Software Requirement Specification

CHANDIGARH GROUP OF COLLEGES LANDRAN, MOHALI

Team Members
Dheeraj Kumar Anish Sharma Harvir Kaur Shama Sharma 90172129973 90172129964 90172129977 90172130009

Project Guide
Mr. Sunil Batra Lecturer
Department Of Computer Application Chandigarh Engineering College Landran, Mohali

College Name: - Chandigarh Engineering College Punjab State: -

1. Introduction 1.1 Methodology 1.2 Purpose 1.3 Scope 1.4 Definitions, Acronyms and Abbreviations 1.5 Tools Used 1.6 References 1.7 Technologies to be used 1.8 Overview 2. Overall Description 2.1 Product Perspective 2.2 Software Interface 2.3 Hardware Interface 2.4 Communication Interface 2.5 Constraints 2.6 ER Diagram 2.7 Use-Case Model Survey 2.8 Architecture Design 2.9 Database Design 3. Specific Requirements 3.1 Use-Case Reports 3.2 Activity Diagrams 3.3 Sequence Diagrams 4. Supporting Information 4.1 Index 29 14 20 25 7 8 8 8 8 9 10 12 13 3 4 4 5 6 7 7 7

1. Introduction
1.1 Methodology
Rational Unified Process
The Rational Unified Process brings together elements from all of the generic process models, supports iteration and illustrates good practice in specification and design. The RUP is normally described from three perspectives: A dynamic perspective that shows the phases of the model over time. A static perspective that shows the process activities that are enacted. A practice perspective that suggests good practices to be used during the process.

Fig

1.1:Phases of RUP

The different phases in RUP are

Inception
The goal of the inception phase is to establish a business case for the system. Identifying all external entities that will interact with the system and defining these interaction. This information is used to assess the contribution of system to business.

Elaboration
The goals of the elaboration phase are to develop an understanding of the problem domain, establish an architectural framework, develop project plan and identify key project risks.

Construction
This phase is concerned with system design, programming and testing. Parts of the system are developed in parallel and integrated during this phase.

Transition
This is the final phase of RUP and is concerned with moving the system from the development community to the user community and making it work in real environment.

1.2 Purpose
Online Market is an E- Market where people can buy, sell or advertise products.The users living in metro or remote village can connect through internet to get these services. This web application is more effective, quick in providing Buying ,Selling and advertising products from home or remote locations.

1.2

Scope
There are four basic users Admin, Buyers/Sellers,Employees.

All users have their own profiles in Online Market.

Buyers can browse though the various categories and select the items to purchase and add them to the shopping cart. They can also view his/her order status.

Sellers can advertise their product for sale.

Admin has the authority to add/remove, update items and manage the database.

Employees are responsible to process orders, ensure home delivery and receive feedback from user and reports to admin

1.4 Definitions, Acronyms and Abbreviations

Admin
Administrator. He has the authority to add/delete items, and manage the employee and seller/buyer database..

WASCE
WebSphere Application Server Community Edition. It is an application server that runs and supports J2EE and web service applications.

DB2
Database_2.A database management system that provides a flexible and efficient database platform to maintain records of students, teachers, admin and dm.

JSP
Java Server Pages. It is used to create dynamic web content.

J2EE
Java 2 Enterprise Edition. A programming platform which is a part of java platform for developing and running distributed java.

UML
Unified Modeling Language is a standard language for writing software blueprints. The UML may be used to visualize, specify, construct and document

XML
Extensible Markup Language is a text based format that let developers describe, deliver and exchange structured data between a range of applications to client for display and manipulation.

HTTP
Hypertext Transfer Protocol. Its a service protocol.

Tools Used Application architecture JAVA, J2EE JAVA

Java is an object-oriented programming language developed by Sun Microsystems a company best known for its high end UNIX workstations. Java language was designed to be small, simple, and portable across platforms, operating systems, both at the source and at the binary level, which

means that Java programs (applet and application) can run on any machine that has the Java virtual machine (JVM) installed.

J2EE
Java Platform, Enterprise Edition or Java EE is a widely used Plateform for Server programming in the java programming language. The java platform (Enterprise Edition) differs from the java standard edition platform(Java SE) in that it adds libraries which provide functionality to deploy fault-tolerant, distributed,multi tier, Java software, based largely on modular component running on an application server.

Web server WASCE

WebSphere Application Server Community Edition (from now on WASCE) is a free, certified Java EE 5 server for building and managing Java applications. It is IBM's supported distribution of Apache Geronimo that uses Tomcatfor servlet container and Axis 2 for web services. Over 15 WASCE developers are committers in the Apache Geronimo project.

Development tool ECLIPSE

Eclipse is an open universal platform for tool integration - an open extensible Integrated Development Environment (IDE), and an open source community. Eclipse is a platform that has been designed from the ground up for

building integrated web and application development tooling. Eclipse provides a common user interface (UI) model for working with tools. It is designed to run on multiple operating systems while providing robust integration with each underlying OS. Plug-ins can program to the Eclipse portable APIs and run unchanged on any of the supported operating systems.

Database platform DB2

DB2 Database is the database management system that delivers a flexible and cost effective database platform to build robust on demand business applications and supports the J2EE and web services standards.

Design tool Rational Software Modeler

IBM Rational Software Modeler, (RSM) made by IBM's Rational Software division, is a Unified Modeling Language UML 2.0-based visual modeling and design tool. Rational Software Modeler is built on the Eclipse open-source software framework and includes capabilities focused on visual modeling and model-driven develop

1.6 References
Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh. Software Engineering, Seventh Edition, Ian Sommerville. IBM Red Books. IBM TGMC Sample Synopsis. IBM - www.ibm.in/developerworks

1.7 Overview
Our Plan:
Registration for users. Online Buying and Selling of items Online Advertising of products. Online payments.

2. Overall Description
2.1 Product Perspective

Fig 2.1: Product Perspective

2.2 Software Interface Client on Internet

Web Browser, Operating System (any)

Client on Intranet
Web Browser, Operating System (any)

Web Server
WASCE, Operating System (any)

Data Base Server

DB2, Operating System (any)

Development End Eclipse (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows),
WebSphere(Web Server)

2.3 Hardware Interface Minimum Requirements:

Recommended Requirements:

2.4 Communication Interface

Client (customer) on Internet will be using HTTP/HTTPS protocol. Client (system user) on Internet will be using HTTP/HTTPS protocol.

2.5 Constraints
GUI is only in English. People who dont hav the knowledge of internet cant use it. Limited to HTTP/HTTPS. This system is working for single server.

2.6 ER Diagram

2.7 Use Case Model Survey

Fig2.2: Use Case Model Survey

10

Buyers:
Buyers can visit the site, browse the catalog, purchase items, give feedback and register themselves.

Seller:
Seller can register in the site and advertise their product for sale. And can view the status of currently advertised products and add/remove items for sale.

Admin:
Admin manages the Buyer, seller, Employee databases, update the items and categories in the catalog and create/delete user accounts.

Employe:
Employee process orders and ensures home delivery. Employee also receive feedback from buyer/seller and reprts to admin.

11

2.8 Architecture Diagram

Fig2.3: Architecture Diagram

12

2.9 Database Design

Fig2.4:Database Design

13

3. Specific Requirements:
3.1.1 Buyer use-case report

33Requirements

Fig3.1: Use case diagram for Buyer

14

3.1.2 Seller use-case report

Fig3.2: Use case diagram for Seller

15

3.1.3 Employee use-case report

Fig3.3: Use case diagram for Employee

16

3.1.4 Admin use-case report

Fig3.4: Use case diagram for Employee

17

3.1.5 Visitor use-case report

Fig3.5: Use case diagram for Visitor

18

Use Case
Visit Browse the catalog Register

Description
Visitor can visit the sit visitor can browse the catalog. Visitor can register in the site if he want.

19

3.2 Activity Diagrams

3.2.1 User Registration Activity Initially user is made to fill all mandatory fields filled in registration form. Once the user clicks submit, the username is verified. If the username is already present, then the user is again taken back, so that he can change the username. If the username is not present then it checks for password and remaining mandatory fields. If any of the mandatory field is left empty or filled incorrect, then the user is informed to enter the correct values. Once all these verifications are succeeded, then the registration is done.

Fig 3.6: Activity Diagram Representing User Registration

20

3.2.2 User Login Activity

User is made to enter the username and password. If it is a valid username and password, then the user is logged in, or else they are asked to re enter the correct values.

Fig 3.6: Activity Diagram Representing User Log in

21

3.2.3 Item purchase Activity Buyer Log in and choose the item by browsing the catalog and if he is satisfied then he purchase the item else he will not. And finally log out.

Fig 3.7: Activity Diagram Representing Purchase of item

22

3.2.4 Item Advertisement Activity by seller.

Fig 3.8: Activity Diagram Representing Advertisement of item by seller

23

3.2.5 Privileged User Login Activity.

Privileged User such as Admin, Employee and buyer/seller is made to enter the username and password, entered values are verified. If it is a valid username and password, then the user is logged in and assigned the respective privileges, or else they are asked to retry by entering the correct values.

24

Fig 3.9: Activity Diagram Representing Privileged Log in Activity

3.3 Sequence Diagrams

3.3.1 Users Login Sequence Diagram

Fig 3.10: Sequence Diagram Representing Login Process

25

3.3.2 Authentication of Privileged Users Sequence Diagram

Fig 3.11: Sequence Diagram to Authenticate privileged users

26

3.3.3 Feedback Sequence Diagram

Fig 3.12: Sequence Diagram to Feedback

27

3.3.4 Purchase Item Sequence Diagram

Fig 3.13: Sequence Diagram to show Purchase of item

28

4. Supporting InformationSupporting

4.1 Index I A
Abbreviations 5 Acronyms 5 Administrator 11 Inception 3 Interface 8, 9 Introduction 4

S
Scope 4 Sequence 25

J C
Client on Internet 8 Client on Intranet 8 Communication 9 Construction 4 J2EE 5, Java 5 JSP 5

T
Transition 4 Technologies 5

U M
Methodology 4 Use-case 14 UML 5

D
Data Base 15 DB2 5, 6 Definitions 5 Development End 8

O
Our Plan 7 Overall Description 7 Overview 7

W
WASCE 5,6

E
Elaboration 4 ER Diagram 9

P
Product Perspective 7 Purpose 4

H
Hardware 8 HTTP 5

R
References 7 Rational Unified Process 3

29

Information

30