Software Requirements Specification

For

Book-shop automation System
Prepared by Bidipta Samadder Banalata sen Akash kegirwal Ankit Gadia Calcutta Institute Of Technology, uluberia.

Date 07-05-10

Table of Contents
Table of Contents............................................................................................................... 1 1. 1.1 Purpose................................................................................................................................. Introduction..................................................................................................................2 1

1.2 Document Conventions........................................................................................................ 1 1.3 Intended Audience and Reading Suggestions...................................................................... 1 1.4 Project Scope....................................................................................................................... 1 1.5 References............................................................................................................................ 1

2. Overall Description......................................................................................................2

2.1 Product Perspective.............................................................................................................. 2 2.2 Product Features................................................................................................................... 2 2.3 User Classes and Characteristics......................................................................................... 2 2.4 Operating Environment........................................................................................................ 2 2.5 Design and Implementation Constraints.............................................................................. 2 2.6 User Documentation............................................................................................................ 2 2.7 Assumptions and Dependencies.......................................................................................... 3

3. System 3.1 System Feature 1.................................................................................................................. 3 Features........................................................................................................... 3 4. External Interface Requirements............................................................................... 4 4.1 User Interfaces..................................................................................................................... 4

3.2 System Feature 2 (and so on)............................................................................................... 4 4.2 Hardware Interfaces............................................................................................................. 4 4.3 Software Interfaces.............................................................................................................. 4 4.4 Communications Interfaces................................................................................................. 4 5.2 Safety Requirements............................................................................................................ 5 5.3 Security Requirements......................................................................................................... 5 5.4 Software Quality Attributes................................................................................................. 5

5. Other Nonfunctional 5.1 Performance Requirements.................................................................................................. 5 Requirements...........................................................................5

6. Other Requirements.................................................................................................... 5 Appendix A: Analysis Models

1. Introduction
1.1 Purpose
It is the project name Book-shop automation System. It automates the book records, their Selling and Maintenance, Balance evaluation, due to calculation other functions. In other words you can say it a complete book-shop automation System. In this project we can easily maintain book sales details. It gives information’s of Annual Transaction of books, its services, daily sales, daily Receipt & Balance. We can see the books details before selling the particular it book & view for our requirementsatisfying item detail. The book shop automation system provides ability to search any book records available in the shop. It maintains all the records of selling of books and its availability and information of all types of user.

1.2 Document Conventions
The SRS is a lower level of detailed document for the Book-shop automation System from the developers / Project Managers point of view; it has no further system or subsystem explained elsewhere. In the writing of this SRS, times new roman fonts and size 12 is used. For heading font is Times and its size is 18.

1.3 Intended Audience and Reading Suggestions
This SRS is basically intended for the project managers and developers, team member who want to get the overview of the projects & its scope and the higher details of the various modules in the system. Any person who want make next version of this system can prefer this SRS. This SRS document includes the over all design description. The reader should read thoroughly from first page to last page. In includes the data structure of system and hardware & software requirement for this software. It also includes the objective, purpose, scope, product feature and references.

1.4 Project Scope
The scope of project Book-shop automation System is to Develop Visual Basic dot net based software to support for daily sale, receipt & Balance of products and maintain the all information of books related items. This software will be very useful for the Big book-Shop as well as the customer. It will perform as the required task of Automation of product by itself in a systematic way. It will also save lots of time, as system will perform all tasks in quick time profiting customer and shop owner as well, so it will prove very economical in every respect.

The scope of project ‘Book-shop automation system’ is to Developed VB .Net based software to support for book-shop so that all information can gather and upload the information through this book-shop automation system and maintain the all information.

1.5 References
This web application has been prepared on the basis of discussion with members, faculty members and also taken information from following books & Team website

1.5.1 Websites:

1) www.google.com 2) www.wikipedia.org 3) www.yahoo.com

1.5.2 Books:
1) Fundamental of Software Engineering By Rajiv Mall 2) Software Engineering : A practitioner’s approach Ed. By Pressman, Roger 3) Software Engineering Seventh Edition Ian Sommerville 4) Software Engineering Ed.2 by Jalota & Pankaj. 5) Schaum’s Series, “Software Engineering”

2. Overall Description
2.1 Product Perspective
The Book-shop automation System is the new, self-contained product. The ‘Book-shop automation System is using vb.net. All components follow Model-View-Controller pattern. The user can retrieve information of their shop progress. All pages of the system are following a consistent theme and clear structure.

The occurrence of errors should be minimized through the use of checkboxes and scroll down in order to reduce the amount of text input from 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. Each level of user will have its own interface and privilege to mange and modify the project information. User interface elements are easy to understand. Part of user interface is wellorganized on screen and the parts are concatenated right. When users look at the interface, they understand which pane is used for which purpose. Each task of an interface is specified clearly and users use them correctly. For example, when users press to any button on interface, they can know which operations are done by pressing this button. The user interface is easy to learn. When users use the user interface, they can know which element is used to which operations. The interface actions and elements is consistent. When users press any button, required actions is done by the system. The screen layout and color of the user interface is appealing. When users look at the screen, it will have a nice vision. Colors will be selected clearly, thus eyes of users won’t be tired. Since the application must run on the PC, all the hardware shall require to connect the PC will be hardware interface for the system.The main interface would be the monitor, Keyboard and mouse. Book-shop Automation Systems is a technology that automat the book-shop. This technology includes more advantages over manual work. Here this system manage the all records of transaction or selling record in a day or month and can measure the profit of a day, month or yearly. The book-shop automation system provide following facilities and services. 12) Monitoring all records 13) Searching of books by name, publishers or by price 14) Updating records 15) Records of all transaction 16) Customer records 17) User records 18) Selling records
19) Saving records the

2.2 Product Features
• NETWORK SUPPORT. You can use more than one computer to work with Book-shop automation System • Support for VAT tax system. Also you can • Quickly create database backup! • Enter and print (optionally) component serial numbers when you selling systems! • Customize bills that you print! • Create estimates and latter convert it into bills! • Reports to make comparisons between months!

• User can see profit of a sold books during bill creating! • Print bills with currency sign. • See number of available books (for selected books in group) when you selling books! • Different kind of reports. • Check out earnings and get information about charged items! • Each sold book is registered in database with date of sale and notification if customer has paid! • Book-shop automation System software provides full billing and income control and Supports different password protected employee accounts! • Server database is protected from unauthorized modifications! • Process payments quickly and efficiently! • Unique design with very functional user interface! • Improve your store business with various reports and statistics! And many more...

2.3 User Classes and Characteristics
<Identify the various user classes that you anticipate will use this product. User may be classes differentiated based on frequency of use, subset of product functions technical expertise, security or privilege levels, educational level, or used, Describe the pertinent characteristics of each user class. Certain requirements experience. pertain only to certain user classes. Distinguish the favored user classes from those may are less important to who satisfy.>

2.4 Operating Environment
The proposed software is intended to run on client/server model network. A client/server can deliver the better performance than the file server system because a client application and database server work together to split processing load of applications (thus the term distributed processing). The server manages the database among the number of clients, while the client send, request, and analyze the data entry form with small specific data set, such as rows in a table not file as in the file server system. 1) Hardware Requirement
1) 20 GB HDD Free Space MB RAM 2) 128 3) P IV or above 4) Monitor Processor

5) Keyboard: Standard Optional 6) Mouse: 2) Requirement Software

1) MS-office-2003/2007 2) MS Visual Basic6.0

3) Front End Tool: MS Visual Basic6.0

4) Back End Tool: SQL server 5) PLATFORM USED : Windows XP, Windows 2000.

2.5 Design and Implementation Constraints
<Describe any items or issues that will limit the options available to the These might include: corporate or regulatory policies; hardware limitations developers. requirements, memory requirements); interfaces to other applications; (timing technologies, tools, and databases to be used; parallel operations; specific requirements; communications protocols; security considerations; design conventions language programming standards (for example, if the customer’s organization will be or for maintaining the delivered responsible software).>

2.6 User Documentation
<List the user documentation components (such as user manuals, on-line help, tutorials) that will be delivered along with the software. Identify any known and documentation delivery formats or user standards.>

2.7 Assumptions and Dependencies
While cost estimation of the proposed system it has been assumed that the cost hardware and for license of Operating System and back end will be met by client (the organization). Hence only the cost incurred for the proposed software is included therein. The followings are identified as some of the potential risk factors or dependencies: (1) Non-availability of required resources. (2) Power cuts. (3) Slippage of schedule due to unpredictable holidays, etc. Life Cycle Model - I am using SDLC model that begin at system level and progresses through analysis, design, coding, testing, implementation and maintenance.

3. System Features
1. the following features were required by the client: 1) The system should be secured enough to rely upon. 2) Users should not be allowed to delete/modify patient records. 3) Every patient medical report should keep the tracks of user inputting the record. 4) System should provide facility of exporting its data in text format. 5) System should provide facility of uploading the information.

3.1 System Feature 1
<Don’t really say “System Feature 1.” State the feature name in just a few words.> 3.1.1 Description and Priority <Provide a short description of the feature and indicate whether it is of High, Medium, or Low priority. You could also include specific component ratings, such as benefit, penalty, cost, and risk (each rated priority a relative scale from a low of 1 to a high of on 9).> 3.1.2 Stimulus/Response Sequences <List the sequences of user actions and system responses that stimulate behavior defined for this feature. These will correspond to the the elements associated with use dialog cases.> 3.1.3 Functional Requirements <Itemize the detailed functional requirements associated with this feature. These are the software capabilities that must be present in order for the user carry out the services provided by the feature, or to execute the use to Include how the product should respond to anticipated error conditions case. invalid inputs. Requirements should be concise, complete, or verifiable, and necessary. Use “TBD” as a placeholder to indicate unambiguous, necessary information is not yet when available.> <Each requirement should be uniquely identified with a sequence number or meaningful tag of some a kind.>

REQ-1: REQ-2:

3.2 System Feature 2 (and so on)

4. External Interface Requirements
4.1 User Interfaces
User interface is used to provide communication between users and system. Our product should have communication between them. Because, Airline Ticket System is a webbased system and it should get input from users for processing. Firstly the system should ask to its users about where they will go, when they will go, which option they will use (least money or least time).Users will enter their desired place, date period and they will select an option (least time or least money) for finding the optimized path. The system gets these inputs by using user interface. Then, the system will study to find an optimized path for users according to least money or least time constraint which is selected by users. After that, the system will give appropriate output for users via user interface. Finally users will see the optimized path at their screen according to their selected option. User interface elements should be easy to understand. Part of user interface should be well-organized on screen and the parts should be concatenated right. When users look at the interface, they understand which pane is used for which purpose. Each task of an interface should be specified clearly and users should use them correctly. For example, when users press to any button on interface, they should know which operations are done by pressing this button. The user interface should be easy to learn. When users use the user interface, they should know which element is used to which operations. We should teach using of the user

interface to users simply. If it is hard to learn, then teaching will take long time and there will be an extra cost for teaching of product. The interface actions and elements should be consistent. When users press any button, required actions should be done by the system. The screen layout and color of the user interface should be appealing. When users look at the screen, it will have a nice vision. Colors will be selected clearly, thus eyes of users won’t be tired.

It has been required that every form’s interface should be user friendly and simple to use.

4.2 Hardware Interfaces
The hardware interface for the user would be any PC having a configuration of P -I and above GB HDD for loading any OS for operating the browser shall be able to interact with the system without any problem The main interface would 1.2 . be the monitor Keyboard and mouse The bar code scanner is required for , scanning the assets during the yearly verification of the assets The requirements . . can be summarised as below :

SYSTEM REQUIREMENTS 28) System Requirements :
• WEB ( ) Recommended SERVER

o Hardware o Operating System o Windows NT Server with Option Pack 4.0 o .Pentium IV GHZ o Operating System o Windows Server with Option Pack 4.0

WORKSTATION ( o Hardware Recommended

4.3 Software Interfaces
In Airline Ticket System, users will use application program via the user interface program. When database management system access is required, the system establishes a connection to the database management system, once the connection is created; the client program can communicate with the database management system. A standard called Open Database Connectivity (ODBC) provides an application programming interface (API), which allows client-side programs to call database management system, as long as PC has the necessary software installed. Most database management system vendors provide ODBC drivers for their systems. A user can actually connect to several database management system and send query and transaction requests using the Open Database Connectivity (ODBC) API, which are then processed at the server site. Any query results are sent back to user, which can process or display the result as needed. The ODBC specification offers a procedural API for using SQL queries to access data. An implementation of ODBC will contain one or more applications, a core ODBC library, and one or more database drivers. The core library, independent of the applications and DBMS, acts as an interpreter between the applications and the database drivers, whereas the database drivers contain the DBMS specific details. Thus a programmer can write applications that use standard types and features without concern for the specifics of each DBMS that the applications may encounter. Likewise, database driver implementers need only know how to attach to the core library. This makes ODBC modular. It has been required that there could be a necessity of using the stored data for some kind of report that is not supported by proposed system at present

4.4 Communications Interfaces
Hypertext Transfer Protocol (HTTP) shall be used to provide a communication between system and users. Because, Airline Ticket System is a web-based system which should be reached on World Wide Web by users. Hypertext Transfer Protocol (HTTP) is a communications protocol which is used to transfer or convey information on intranets and the World Wide Web. Its original purpose was to provide a way to publish and retrieve hypertext pages. Development of HTTP was coordinated by the W3C (World Wide Web Consortium) and the IETF (Internet Engineering Task Force), culminating in the publication of a series of RFCs, most notably RFC 2616 (June 1999), which defines HTTP/1.1, the version of HTTP in common use. HTTP is a request/response protocol between a client and a server. The client making an HTTP request, such as a web browser, is referred to as the user agent. The responding server, which stores or creates resources such as HTML files and images, is called the origin server. In between the user agent and origin server may be several intermediaries, such as proxies, gateways, and tunnels. HTTP is not constrained to using TCP/IP and its supporting layers, although this is its most popular application on the Internet. Indeed HTTP can be implemented on top of any other protocol on the Internet, or on other networks. HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used. Typically, an HTTP client initiates a request by establishing a Transmission Control Protocol (TCP) connection to a particular port on a host (port 80 by default; see List of TCP and UDP port numbers). An HTTP server listening on that port waits for the client to send a request message.

It has been required its associated with the communications functions required by this product, including e-mail, web browser, network server communications protocols, electronic forms, and so on.if the application is used in web enviournment then using the HTTP,FTP

5. Other Requirements
5.1 Performance Requirements

Nonfunctional

As it is going to be used by all the concerned employees within the organization, the system should have a good performance in terms of speed and accuracy. The proposed system should be accurate and fast enough to handle huge data. It should provide fast communication between server and clients

5.2 Safety Requirements
As the system is going to handle parts records for a long run eliminating the manual system, it is supposed to ensure the retaining of data avoiding or eliminating any probable cause for data loss.

5.3 Security Requirements
The software should not allow unauthorized access to any module of the system. Besides, it should maintain the privileges granted to users at various user levels.

The prioritization of the software quality attributes are assumed as under: 1) Accurate and hence reliable. 2) Secured. 3) Fast speed.
& Portability 4) Compatibility.

5.4 Software Quality Attributes
The prioritization of the software quality attributes are assumed as under: 1) Accurate and hence reliable. 2) Secured. 3) Fast speed. 4) Compatibility.

6. Portability Other Requirements
There are a number of functionalities being provided in System which includesFunctions: It is clear that the two main or primary functions of bank’s are: 1) To collect and deposit money from those who have surplus money. 2) To invest funds of lands money to those who can fruitfully utilities it. 3) The third type of functions whose main objectives is to secure deposit indirectly and to provide certain facilities to customer to encourage them to deal with the bank.

Appendix A:

Project phases and Implementation

During planning of the project I have taken the following steps: A. First of all I identified the activities and tasks in the project. In my project I have select the following activities and tasks. Analysis, designing, coding, testing, implementation. proposed

ACTIVITYTASK

- Analysis activity has the following tasks:
Preliminary investigation Need identification Feasibility study

Design activity has the following tasks:

Form design Database design

B. C.

Determine the total estimation time for each activity . Plot activity on Gantt chart.

Appendix B: Role Of Team member and activity chart , Modules.
BidiptaRole Of Team member :Samadder Banalata sen

:- Analysis,Design,Coding,Testing,Documentation
Bidipta Samadder,Akash kegirwal Ankit Gadia

:- Design(form & database),Coding.

Activity chart :ACTIVITY CODE 1. 2. 3. 4. 5. NAME OF ACTIVITY ANALYSIS DESIGNING CODING TESTING IMPLEMENTATION TOTAL DURATION OF THE ACTIVITY 40 DAYS 18 DAYS 30 DAYS 7 DAYS 3 DAYS 98 DAYS

Modules : A) User login module :
In this face, existing user gives the user-name and password and can access the other details and if he is current user then first he would have to register himself by option Registration module.

B) Database module

:

This module gives a complete information about the existing & new database.

c) About us :
This module covers the information of the website owner and the purpose of the creation of the website.

Sign up to vote on this title
UsefulNot useful