18-10-2012, 11:08 PM
Team Name
Online Book Sales with Mobile SMS
Software Requirement Specification
Version <1.0>
Team Guide: Mr. Deepak Moud
Members:
Student Name1 (Registration Id)
Student Name2 (Registration Id)
Student Name3 (Registration Id)
Student Name 4(Registration Id)
College Name: Poornima Institute of Engineering and Technology
Department: Computer Engineering
State: Rajasthan
(Academic Year 2012-13)
Revision History
Date Version Description Author
20-10-2012 <1.0> Software Requirement Specification Document Initial Release1.0
Team Name
Table of Contents
Description Page No.
1. Introduction
1.1. Purpose
1.2. Scope
1.3. Definition,Acronyms,andAbbreviations
1.4. Tool Used
1.5. References
1.6. Technologies to be Used
1.7. Overview
2. Overall Description – I
2.1. Product Perspective
2.2. Interfaces
2.2.1. User Interfaces
2.2.2. System Interfaces
2.2.3. Hardware Interface
2.2.4. Communication Interface
2.3. Product Function
2.4. User Characteristics
2.5. Constraints
2.6. Process Flow Diagram
2.7. Database Design
2.7.1. Schema
2.8. Assumptions and Dependencies 5
5
7
9
10
10
10
11
14
14
15
15
16
17
18
18
18
19
22
26
27
Chapter 1
INTRODUCTION
The proposed project is to implement a computer based Online Book Sales System with the help of Mobile SMS. This system will help the users to know automatically when certain book requested by them has arrived once they have registered with the website.
It will also help the users to know the latest books of their interests being introduced into the market like fiction, science, technology, romance etc. The database will be developed with open source software.
1.1 PURPOSE
The purpose of Software Requirements Specification (SRS) document is to describe the external behavior of Online Book Sales with Mobile SMS.
Requirements Specification defines and describes the operations, interfaces, performance, and quality assurance requirements of the project. The document also describes the non-functional requirements such as the user interfaces. It also describes the design constraints that are to be considered when the system is to be designed, and other factors necessary to provide a complete and comprehensive description of the requirements for the software. The Software Requirements Specification (SRS) captures the complete software requirements for the system, or a portion of the system.
1. Identification of purpose of Software Requirements Specification (SRS)
• SRS gives the complete description about the project.
• Describe the software requirements of the project.
• Describes the hardware requirements of the project.
• Describes about the functional and non-functional requirements of the project.
• Brief description about the technologies used.
• Tools description i.e. required for the project.
• In the pictorial view SRS gives the description of flow of data of whole project.
• It gives the idea about the interconnection and external interfaces for the project.
• SRS shows the relationship among entities i.e. used in the project.
• SRS gives the user characteristics.
2. Identification of intended audience
1. Library at schools and colleges as corporate users
2. Individual Customers as Retail Clients
3. Non-members that search for books
4. Administrator
3. Define and describe the operations, interfaces, functional, non- functional, optional requirements of the product
Online Book Sales with Mobile SMS is a web application which provides online book shop to everyone at their doorstep. The users living in metro or remote village can connect through internet to get its services. This web application is more effective, quick in providing all the required info about the book especially to people in villages where these books are not available. This saves a lot of time of all people.
SRS is a communication tool because it contains a repository of all the work done to date and makes it available to all persons working on related parts of a large project. As a management tool it gives access to the latest work tool to all project personnel and determines project status and progress.
Functional Requirement
• it focused on the acquisition, distribution and management of books.
• It mainly emphasized creation and implementation of a book sales management information system.
• It automated the system with the help of SMS that informs the user about the availability, price and method of purchasing the book.
• It will ease and speed up the planning decision making process, secure confidential and reliable reports
• It helps for addressing problems of security secrecy and confidentially of customer records. Used to check the delays errors inconsistencies in records and access to historical records.
• It has eased the control and distribution of books in various parts of the country basing on regional demands
Non- Functional Requirement
• Secure access of confidential data
• Better component design to get to better result at peak time.
• Equalities such as security which are observable at run time.
• Execution qualities like such as testability, maintainability and scalability which are embedded in the static of the software system.
Optional Feature
• It is very smart in choosing different books for customers based on the type of area that they like.
1.2 SCOPE
1. Scope of SRS
The Software Requirements Specification captures all the requirements in a single document. Online book sales with mobile sms to be developed will be developed keeping in mind the effectiveness of the project. It also provides many other facilities. The web portal is supposed to have the following features:-
• Create different system users and assign different roles with related permissions.
• There are four basic users-
o Library at schools and colleges as corporate users
o Individual Customers as Retail Clients
o Non-members that search for books
o Administrator
• Manage all the account details such as user name, password, contact details, phone numbers, address and other relevant information.
• The registered users are having their own profiles/accounts .They can edit their profile, update, and search and give feedback to the administrator.
• The system provides the members with the option to check their account and/or change their options like password of the account whenever and wherever they needed.
• Admin is the central head which monitors and controls from anything to everything. He can access all details of the users and also revoke their authentication depending upon the feedback received.
• All users have their own profiles on website.
• Patients can search for books and make online bookings. They also can view the overview of book, list of their favorite books.
• Admin has the authority to add/delete users. He also views the complaints of users and takes necessary action against it.
• The system allows the users to give their feedbacks and ask their queries.
• The system allows the users for searching relevant books on the site.
• The features that are described in this document are used in the future phases of the software development cycle. The features described here meet the needs of all the users. The success criteria for the system are based in the level up to which the features described in this document are implemented in the system.
2. Product Features.
a. Identify the software product to be produced by name
Online Book Sales with Mobile SMS
b. Explain what the software product(s) will, and if necessary, will not do
• Secure data transformation between buyer and seller.
• Member ID is provided by the mail at the time of registration of the user.
• System provides communication interface between buyer and seller.
c. Describe the application of the software being specified, including relevant benefits, objective, and goals
• Whole system managed by online so it is easy to manage data information of user.
3. The success criteria for the system are based in the level up to which the features described in this document are implemented in the system.
1.3 DEFINITIONS, ACRONYMS AND ABBREVIATIONS
• User–User is a person that accesses the database with the authorization of the Administration. A general user ID is provided to operator, Administrator and User.
• HTML–Hypertext Markup Language is to create static websites.
• J2EE–Java 2 Enterprise Edition is a programming platform and it is
the part of the java platform for developing and running distributed java applications.
• WAS–Web sphere application server community edition is an application server that runs and supports the J2EE and web service applications.
• DB2–Database 2 is the database management system that provides a flexible and efficient database platform to erect strong on demand business applications.
• XML-Extensive Markup Language used for data transfer and XML is stored naturally in DB2
• HTTP–Hypertext transfer protocol is a transaction oriented client/server protocol between web browser and a web server.
1.4 TOOLS USED
1. Eclipse/RAD/Lotus forms Designer/Port let Factory
2. DB2 Express Core DB2 UDB
3. Tivoli CDP /TSM/Tivoli Directory Server
4. Linux will be the preferred OS
1.5 REFERENCES
• Object Oriented Modeling and Design with UML-Michael Balham, James Ram Baugh.
• Software Engineering, Seventh Edition, Ian Somerville.
• IBM Red Books.
• IBM TGMC Sample Synopsis.
• IBM –
• Java -
• Database Management Systems - Nava the.
• Complete Reference - J2EE - Keogh.
1.6 TECHNOLOGIES TO BE USED
.NET:
The fundamental forces that necessitated the invention of .NET are portability and security; other factors also played an important role in molding the final form of the language. The key considerations were:
• Simple
• Secure
• Portable
• Object-oriented
• Robust
• Multithreaded
• Architecture-neutral
• Interpreted
• High performance
• Distributed
• Dynamic
The Internet helped catapult Java to the forefront of programming, in turn has had a profound effect on the Internet. The reason for this is quite simple: Java expands the universe of objects that can move about freely in cyberspace. In a network, two very broad categories of objects are transmitted between the server and your personal computer: passive information and dynamic, active programs
DB2:
DB2 is considered by many to have been the first database product to use SQL(also developed by IBM).
DB2can be administered from either the command-line or a GUI. The command-line interface requires more knowledge of the product but can be more easily scripted and automated. The GUI is a multi-platform Java client that contains a variety of wizards suitable for novice users.
DB2 supports both SQL and XQuery. DB2 has native implementation of XML data storage, where XML data is stored as XML (not as relational data or CLOB data) for faster access using XQuery.
IBM Web Sphere Application Server(WAS):
It is a software application server, is the flagship product within IBM's Web Sphere brand. WAS is built using open standards such as Java EE, XML, and Web Services. It is supported on the following platforms: Windows, AIX, Linux, Solaris, i/OS and z/OS. Beginning with Version 6.1 and now into Version 7, the open standard specifications are aligned and common across all the platforms. Platform exploitation, to the extent it takes place, is done below the open standard specification line.
1.7 OVERVIEW
Existing System:
• Registration for membership.
• Online order of books.
Drawbacks:
• No interaction with user.
• No SMS service.
• No track of user’s choice.
Proposed System:
• Registration for users.
• SMS service.
• Track of user’s favorite.
• Our Plan:
• Registration for users.
• Online maintenance of user data.
• Online review of book from experts.
• User reviews and ratings for books.
Chapter 2
OVERALL DESCRIPTION
The project will allow people to checkout favorite books online and new arrivals. Also the review and rating of each and every book will be available. The user can also book a forth coming book in advance and he/she will be informed on the arrival of book via SMS. The project also have the feature of keeping the track of user’s favorite books and hence provide suggestion of the books of same category.
• Simple user interface
• Secure communication
• Registration facility for Users.
• Reviews & Suggestions for user.
• All users have separate username and password.
• User ID is given to each and every user for ease of handle information of user.
• Information sharing among all system users.
2.1 PRODUCT PERSPECTIVE:
• To develop a book management system.
• To design a book management system.
• To design a costumer Mobile-Book sales management system interface this interacts with database system.
• To mobile client be optimized and also an interface for connecting through PC.
• It focused on the acquisition, distribution and management of books
• It mainly emphasized creation and implementation if a book sales management information system.
• It automated the system with the help of SMS that informs the user about the availability, price and method of purchasing of the book.
• It will ease and speed up the planning decision making process, secure confidential and reliable reports
• It helps for addressing problems of security secrecy and confidentially of customer records.
• Used to check the delays errors inconsistencies in records and access to historical records.
• It has eased the control and distribution of books in various parts of the country basing on regional demands
2.2 INTERFACES
2.2.1 USER INTERFACES
• The design or layout of every form will be very clear and very interactive to the user.
• When the user opens the web application, the Home page will appear.
• In the login window the user can easily enter the desired password and login name.
• Then it will give the successfully login message.
• From each and every web page, the user can easily go to any desired web page as there would be an absolute and relative linking.
• On every web page, there is help and support option present for the ease of user.
• There will be a proper collection of GUI interface, which will provide better look and feel.
• In the screen layout, the background color is very light and the graphics and font style will be in proper manner and well organized.
• If the user will print any error statement then it will give the proper error message display.
• On each and every web page, there will be save, cancel etc. message box before making permanent modifications to the user’s data and his/her profile.
• The user will be able to search any data from the record filling the necessary books required for generating the desired results.
• The website also fulfills the security measures as the account will be accessed only according to correct combination of the username and the password entered on logging in.
• User can easily save its data in to the database and keep track of the records of his/her
• This web application will be easily understandable and operable by the user.
2.2.2 SOFTWARE INTERFACE
Front End Client
• Client on Internet
Web Browser (any), Operating System (any)
• Client on Intranet
Web Browser (any), Operating System (any)
• Web Server
Web Sphere (Web Server), Operating System (any)
• Data Base Server
DB2, Operating System (any)
Development End
RAD (J2EE, Java, Java Bean, Servlet, Sessions, HTML, XML, AJAX), DB2, OS (Windows).
2.2.3 HARDWARE INTERFACE
MINIMUM REQUIREMENTS:
RECOMMENDED: REQUIREMENT:
2.2.4 COMMUNICATION INTERFACE
• Online book sales with mobile SMS will be connected to World Wide Web.
• Client (customer) on Internet will be using HTTP/HTTPS protocol.
• Client (system user) on Internet will be using HTTP/HTTPS protocol.
2.3 PRODUCT FUNCTION
• Simple user interface
• Secure communication
• Registration facility for Users.
• Reviews & Suggestions for user.
• All users have separate username and password.
• User ID is given to each and every user for ease of handle information of user.
• Information sharing among all system users.
• To mobile client be optimized and also an interface for connecting thru PC
• It focused on the acquisition, distribution and management of books.
• It mainly emphasized creation and implementation of a book sales management information system.
• It automated the system with the help of SMS that informs the user about the availability, price and method of purchasing the book.
• It will ease and speed up the planning decision making process
process, secure confidential and reliable reports.
2.4 USER CHARACTERISTICS
1. Library at schools and colleges as corporate users:
• Familiar with English language.
• Familiar with computers & Internet.
• Should be registered.
2. Individual Customers as Retail Clients
• Buy book in large quantity.
3. Non-members that search for books
• Can only see the books.
4. Administrator
• Higher authority of the system.
• Should be computer proficient.
• Expatiation in management.
2.5 CONSTRAINTS
• GUI is only in English.
• Login and password is used for the identification of users.
• Only registered users will be authorized to use the services.
• Limited to HTTP/HTTPS.
• This system is working for single server.
2.6 PROCESS FLOW DIAGRAM
1. Login
Fig 7: Login
2. Forgot Password
Fig 8: Forgot Password
3. User registration
Fig 9: User registration
2.7 SCHEMA
Author:
Field Name Data Type
Name Varchar
Address Varchar
URL Varchar
Book:
Field Name Data Type
Name Varchar
Price Double
Title Varchar
Year Integer
ISBN Integer
Publisher:
Field Name Data Type
Name Varchar
Address Varchar
URL Varchar
Phone Integer
Customer:
Field Name Data Type
Name Varchar
Password Varchar
Address Varchar
Phone_no. Big Int
Fav_id Integer
Email Varchar
2.8. ASSUMPTIONS AND DEPENDENCIES
• The users must have sufficient knowledge of computers.
• The users should know the English language, as the user interface will be provided in English.