Professional Documents
Culture Documents
Table of Contents
1. Introduction................................................................................................................................1
1.1 Purpose ............................................................................................................................................... 1
1.2 Objective of BAS................................................................................................................................ 1
2. Document Conventions..............................................................................................................1
2.1 Project Scope....................................................................................................................................... 2
2.2 Overview............................................................................................................................................. 2
3. Overall Description....................................................................................................................2
3.1 Product Perspective............................................................................................................................. 2
3.2 Product Features.................................................................................................................................. 3
3.3 User Classes and Characteristics........................................................................................................ 3
3.4 Operating Environment....................................................................................................................... 4
3.5 Design and Implementation Constraints............................................................................................. 4
3.6 User Documentation........................................................................................................................... 4
3.7 Assumptions and Dependencies......................................................................................................... 4
4. Requirements..............................................................................................................................4
4.1 System Features.................................................................................................................................. 5
3.1.2 Functional Requirements............................................................................................................. 5
4.2 External Interface Requirements......................................................................................................... 6
4.2.1 User Interfaces.............................................................................................................................. 6
4.2.2 Hardware Interfaces..................................................................................................................... 6
4.2.3 Software Interfaces....................................................................................................................... 6
4.3 Other Nonfunctional Requirements.................................................................................................... 6
4.3.1 Performance Requirements.......................................................................................................... 6
4.3.2 Safety Requirements.................................................................................................................... 6
4.3.3 Security Requirements................................................................................................................. 7
4.3.4 Software Quality Attributes......................................................................................................... 7
4.4 Other Requirements............................................................................................................................ 7
Revision History
Name Date Reason For Changes Version
Software Requirements Specification for Book Authoring System Page 1
1. Introduction
1.1 Purpose
Book Authoring System (BAS) is intended to help the user generate a printable copy of his/her e-copy of
their document. BAS will convert their simple text into a formatted publishable version.
This document is meant to delineate the features of BAS, so as to serve as a guide to the developers on
one hand and a software validation document for the prospective client on the other.
The basic aim is to target the budding authors, who do not have much man power at their disposal. A lot
of time is consumed in formatting and editing their blueprint to convert it into a printable format. The
user would be asked to select a template (the view in which he/she wants his/her book to be printed and
then start typing and submit their document. The output will be the formatted blueprint, ready for
publication.
Another advantage of BAS is that the user will not have to carry his/her data around. The database of our
application will store it, and all that is needed would be an internet connection, and the user would be
able to edit their data in any remote corner of the world.
This is the basic version of the software in which we are targeting on the authors. We plan to launch an
updated version soon which will turn out to be a boon for the research scholars as it would also contain
the feature of Research Paper authoring like the Book Authoring System.
2. Document Conventions
Acronyms and Abbreviations:
e) User authentication.
2.2 Overview
The rest of this SRS is organized as follows: Section 2 gives an overall description of the software. It
gives what level of proficiency is expected of the user, some general constraints while making the
software and some assumptions and dependencies that are assumed. Section 3 gives Requirements which
the software is expected to deliver which comprise of System Features, External Interface Requirements,
Non-Functional Requirements and Other Requirements. Section 4 gives some possible future extensions
of the system.
3. Overall Description
Cases related to system authorization User Type Different privileges for users
Creating a book in publishable format Sole Authority The owner of the s/w
2. They should have the basic idea of working with text editors.
Software Requirements Specification for Book Authoring System Page 4
But it can be used on the local area network easily .In terms of security it is at higher risk. In this
lieu of this we are trying to provide the best security to our customers.
4. Requirements
• Software requirements are documentation that completely describes the behavior that is
required of the software-before the software is designed, built and tested.
Sign-up
Login
Editor
The customer can interface to our software with the help of any browser. He\she can use our
services anywhere in the world with the help of internet.
SPEED 1.5GHz
RAM 256 MB
HARD DISK 40 GB
Visual Studio
MS Accesss
This software should be user specific and should cater the needs of all the individual users. For
the customer the main concern is to make the order of his\her choice and it should as simple as
Cake-walk.
This product is safe to be used on any level with a bit of modification at the highest level of
safety. It is very safe to be used and does not concern any damage to other available options.
Security should be the main concern of this system because the orders of the customers should
not mix up with each other, so that every customer can get his\her order without any mistake.
This software is for sorts of users and all sorts of machines. In a nutshell, it is adaptable to any
environment. It has all the features of
Availability
Correctness,
Robustness,
Testability
Usability
Appendix A: Glossary
a) BAS: Book Authoring System.
Start
Input data
in login
NO
Correct?
Yes
Create new/edit existing
Flow Chart : Create/Edit a new/existing
document
Submit
Exit
Save
Create new/Edit existing
Software Requirements Specification for Book Authoring System Page 10