Chapter 1 Introduction 1.1 Purpose Purpose of online jewellery shop is customer can get any information about jewellery in less time and also can buy the jewelry in reasonable price. It is also convenient for customer to shop online. In view of the vast quantity of data the system deals with, detailed attention had to be paid to effiency, reliability and the technical challenges imposed by it. Online shopping jewellery web application is intended to provide complete solution for vendors as well customer through a single gate way using the internet as the sole medium it enables vendors to setup online shops, customer to brows through the shop and purchase them online without having to visit the shop physically. The administration module will enable a system administrator to approve and reject the request for new shop and maintain various list of shop category 1.2 Scope In view of the vast quantity of data the system deals with, detailed attention had to be paid to effiency, reliability and the technical challenges imposed by it.
Transcript
Chapter 1
Introduction
1.1 Purpose
Purpose of online jewellery shop is customer can get any information about jewellery
in less time and also can buy the jewelry in reasonable price. It is also convenient for
customer to shop online.
In view of the vast quantity of data the system deals with, detailed attention had to be
paid to effiency, reliability and the technical challenges imposed by it.
Online shopping jewellery web application is intended to provide complete solution
for vendors as well customer through a single gate way using the internet as the sole medium
it enables vendors to setup online shops, customer to brows through the shop and purchase
them online without having to visit the shop physically.
The administration module will enable a system administrator to approve and reject
the request for new shop and maintain various list of shop category
1.2 Scope
In view of the vast quantity of data the system deals with, detailed attention had to be
paid to effiency, reliability and the technical challenges imposed by it.
In this application one can search for any type of jewellery of gold, silver, diamond,
platinum and of any type of stones and can buy it too. One can also find for specific jewellery
like for ring, necklace etc.
Secure registration and profile management facility for customer
Customer can see the all jewellery design from website
Creating shopping cart so that customer can shop n numbers of items and checkout
finally with the entire shopping cart.
Regular update to registered customers of the osj about new arrivals
Uploading most purchased item in a each category of product in the shop like gold,
platinum and silver etc.
Strategic data and graphs for administrator and shop owners about the items that are
popular in each category and age group
Maintaining database of regular customer of different need
Shop employees are responsible for internal affairs like processing order ,assure home
delivery, getting a customer delivery-time feed back,updating orders status and answering
clients query online
Feedback mechanism,so that customer can give feed back for the product or service
which they have purchased also facility rating of individual product by relevant customer.
Also feedback can be given on the performance of the particular vendors and the
entire system as well
Adequate payment mechanism and gateway for all popular credit card,cheques and
other relevant payment option as available from time to time
1.3 Definations, acronyms and abbreviations
HTTP:Hyper text transfer protocol is a transaction oriented client/server
protocol between a web browser & a web server.
HTTPS:Secure hyper text transfer protocol is a http over ssl
TCP/Ip:Transmission control protocol/Internet protocol,the suite of
communication protocol use to connect host on the internet.TCP/IP uses several
protocols, the two main ones being TCP/IP.
EJB: Enterprise Java Beans
SLA:Serviece level agreement or SLA is a formal written agreement made
between two parties,the service provider and the service recipient.
It defines the term of engagement-the fundamental rules that will govern the
relationship
SQL: structured query language.
DFD: data flow diagram.
CFD: context flow diagram.
ER: entity relationship.
SRS: software requirement specification.
1.4Reference
IEEE SRS formate
1.5 OVERVIEW
The implementation of online jewelry system start with information about various
jewelry and design and selling of jewelry and user information.
Section 1 gives an overall description of system.
Section 2 gives general description product perspective, product functions, user
characteristics, general constrains and assumption and dependencies.
Section 3 gives overall description of software, it gives what level of proficiency is
expected of the user,some general constrain while making the software and some assumption
and dependencies that are assume.
It also gives specific requirements which the software is expected to deleiver.Function
requirements are given by various use cases.Some performance requirement and design
constrains are also given
Section 4 represent overall system process in diagram like sequence,data flow and
state transition diagram
CHAPTER 2
GENERAL DESCRIPTION
2.1 PRODUCT PERSPECTIVE
The proposed online jewelry system will take care of current jewelry detail at any
point of time. Our system can collect information about sold jewelry,payment of jewelry and
will update jewelry, So that user will get the update current jewelry detais.
2.2 PRODUCT FUNCTION
The main purpose of this project is to reduce manual work.
This software is capable of managing information about different types of jewelry,selling of
jewelry and calculating/managing finance. generating various reports for record kepping
according to end user requirements.
2.3 USER CHARACTERISTICS
User module
In this module user will check availability of jewelry and payment of jewelry.
Payment module
This module will register the information of user.and entry jewelry details and
selling jewelry.
2.4 GENERAL CONSTRAINTS
Any update regarding the jewelry design is to recorded to have update and correct price.
In this application user can not create or update the users database.
Users once buy jewellery then it can not change it.
2.5 ASSUMPTION AND DEPENDENCIES
The details related to the product, customer, payment and service transaction provided manually.
Administrator is created in the system already.
Roles and tasks are predefined
This system is depended on the user’s valid inputted password. If user passes wrong
password then he/she cannot logs in to the system.
Chapter 3
SPECIFIC REQUIREMENTS
1.correct
The srs must be correct that means all the requirements must be
correctly mentioned or the requirement must be realistic by nature
For instance, while developing software if there is a requirement of
cart and if cart can not work that means requirement is incorrect
2.complete
To make the srs complete it should be specified what a software
designer want to creat a software
The srs is said to be complete only in following situation
1.when srs consist of all the requirements related to
functionality,performance,attribute,design constrain or external
interface
2.when lables and corresponding references are mention for all
feagures,diagrams and tables in srs
3.when expected response to the input data is mention by
validity and invalidity of input
3.Unambiguous:
When requirements are understood correctly then only
unambiguous srs can be written.
Unambiguous specification means only one interpretation can
be made from specified requirement.
In other word there should be an unique interpretation of each
statement in srs
If for a particular term there are multiple meaning then those terms
should be mention in glossary with proper meaning
The requirement should not be mentioned in same manner
After preaparing srs it should be reviewed by third party
Normally srs is written in a some natural language like srs
4.consistant:
If there are not conflicts in the specified requirements then srs is said
to be consistant.three types of conflict may occur in srs
1.logical/temporal conflict: when one requirement specifies that event
x should occur before event y and if another requirement specify that
event y should occur before event x.
2.cfharacteristic conflicts of real world object:
If one requirements suggest to make use of radio button and other
specifies check box button then it represents conflicting
characteristics.
3.two different descriptions about the same real world object:
If one requirement specifying “enter” and other specify “submit” then
it describe one and the same action.
5.stability:
In srs it is not possible to specify all requirements.
The srs must contain all the essential requirements.
Each requirements must be explicit.
6 verifiable:
Srs should be written in such mnner tht the requirements that are
specified within it miswt be satisfied by the software.
7.traceable:
If origin of requirement is oroperly given or reference of requirements
are correctly mentioned then such requirements is called as traceable
requirements.
Various types it:
1)forward traceability:
each requirement is refferd in the srs document by it’s unique name or
reference no.
2)backward traceability:
If the reference to the requirement is mentioned in earlier document
then it is backward traceability.
3.1 EXTERNAL INTERFACE REQUIREMENTS
3.1.1 User Interface
The software provides good graphical interface for the user any administrator can
operate on the system, performing the required task such as create, update, viewing the
details of the jwellery.
● Allows user to view quick reports like show jwellery design and purchase
it etc in between particular time.
● Stock verification and search facility based on different criteria.
● The occurances of error should be minimize through the use of
checkbox,radio button,and scroll down in order to reduce the amount of
text input from the user
● Javascript implementation in html in order to provide a data check before a
submission
● Html tables to display information to give a clear structure that easy to
understand by user.
● Error message should be located beside the error input which clearly
highlight and tell user how to solve it.
● If system error it should provide the contact methods.
● The page should display the project process in different color to clearly
reflect the various states that customer done.
● Each level of user will have its own interface and privilege to manage and
modify the project information such as supervisor able to manage his
progress and make comment on it.
3.1.2 Hardware requirements
The Following are the Minimum Hardware & Software Requirements
256 MB Random Access Memory.
Min 40 MB Free space in Hard Disk.
1.server side:
The web application will be hosted on one of the department’s linux servers and
connecting to one of the database server.
The web server is listening on the web standard port,port 80.
2.client side:
The system is a web based application;clients are requiring using a modem web
browser such as mozila firefox 1.5,internet explorer 6 and enable cookies.
The computer must have an internet connection in order to able to access the system.
3.1.3 Software requirements
Operating system: Windows 7
Java language
Net beans IDE 7.0.1
MS SQL server 2005
1.server side
An Apache Web server will accept all requests from the client and forward SUMS specific requests to Tomcat 5.5 Servlet Container with J2EE 5.0 and Strut 1.2.8 hosting SUMS. A development database will be hosted locally (using MySQL); the production database is hosted centrally (using Oracle).
2.Client Side
An OS is capable of running a modern web browser which supports HTML version 3.2 or higher.
3.1.4 Communications interfacesThe HTTP protocol will be used to facilitate communications between the client and server.
Window.
3.2 FUNCTIONAL REQUIREMENTS:
3.2.1.1 Introduction
In this section we describe the basic function of our jwellery system.
this system is only for the customer.
In which so many jwellery designs are available.
and user or customer are login for purchasing and select jwellery and also select the
payment process. And system update the jwellery design.
And system keep the record and details of customer.
3.2.1.2 Input
In this the customer give his/her user-id for the login process.
And system authenticate the user.and keep the detail of user or customer.
3.2.1.3 Processing
This is the first activity of our project.
First of all the customer visit the system or website.
And system displays all the jwellery design. and customer show the design of
jwellery. And select the some design and put in cart.
And customers enter the user id and system authenticate user and keep the detail of
customer.
Customers check the cart. And choose the payment system. system prepare bill and
give the customer. and logout the customer. after that system update the jwellery
design.
3.2.1.3 Output
Customer gets a receipt for purchasing and they can get hand to hand
delivery of jewellery
3.2.1.4 Error handling
If someone choose some design that may be currently not available in this
situation system will display related available designs which can satisfy the
customer want.
In some situations if credit card is not accepted by the system in such a
case cash payment must be done.
3.3 use cases.
Use case diagram represents the overall scenario of the system.
A scenario is nothing but a sequence of step describing an interaction between a user and
system.
For example, in our system customer searches for different designs, purchase it and pay for it.
all these activities constitute a scenario.
Thus use case is set of scenario tied together by some goal.
Actor:
An actor is an entity which interact with the system.actor carry out use case.
In our system actors are user and system.
A single actor may perform many use case.
Use case may have several actors.it is not necessary that user should be an actor.
The external system that get some value or produces some value can be an actor.
Actor is nothing but a role play by a person,system,or a device or even an enterprise that has
a stake in the successful operation of the system.
Use cases:Use cases represents the behavior of the system.
Typically various functions are represent as a use case
For example in our system,use case like create an account,view item,add item etc are use
cases.
user
3.4Class diagram
Create account
Modify/delete account
View item for sale
Add item to cart
Remove item from cart
Log in
Choose payment method
Send order to system
View customer detail
View item in cart
Receive order
Verify payment
Log out
Update status
Class diagram is collection of classes.
Class:
Each class is a collection of data and the function that manipulate the data.
The data component of the class are called data member and function
component of class are called member function or method.
For example, in our system various classes are web user, customer, payment,
account, order, shopping cart, line item, product and order status.
Object:
Object is an instance of class.
Object represents real world entity.
For example, in our system various objects are web user, customer, payment,
account, order, shopping cart, line item, product and order status.
Attributes:
The data member and function members are called attribute of class.
For example in our system,
1.attribute of customer is a id,address.phone no,name,email etc.
2.attribute of order is number,order, total, status, ship_to, shipped
3.5 NON FUNCTIONAL REQUIREMENTS
3.5.1 Performance
o The performance defines the response time for system functionality.
o The load time for GUI should not be more than four second.
o The login must be verified within 7 second.
o The jwellery aviability query should be processed with in 3 second and
response must be given.
3.5.2 Reliability
o The application should be highly reliable and it should generate all the updated
information for jwellery in correct order.
o The system must be reliable to prevent any unauthorized access.
3.5.3 Availability
o Any information about the jwellery should be quickly available from any
computer to the authorized user.
o The previously visited user data must be maintained and should be made
available to the administrator by simply entering his registration-id.
3.5.4 Security
o The application will be password protected.
o The user has to enter correct user name and password.
o The password can be change by the system administrator.
o User is not allowed to modify the database.
o The system needs to log client’s information of registration such as IP address and time for security purpose.
o Password should encrypted and store in the database.
3.5.5 Maintainability
o There should be the facility to add/modify information about the types and
design of jwellery.
3.5.6 Portability
This application should be portable on any window based system.
The web application is coding in javascript and html and therefore, it should be transferable between different OS and Java container.
3.6 inverse requirements:
When customer specify that something must not be done it is called inverse
requirements.
It can be functional or non functional.
In our system it is not require login process to only show the all jwellery design.
3.7 Design constrain
o The system must be completed within four month.
o The system must be designed as a standalone system and must be run on
window based system.the system can be developed in visual basic.
o The database can be implemented in oracle or MYSQL.
o Every customer must be required user-id for purchasing jwellery.
3.8 logical database requirements:
All the user profile and information should be insert in the database.
