Write a srs for restaurant billing system?

Answer 1

Software

Requirements Specification for library management system Page 9

switching between interfaces with the minimum impact for theusers.

4.

Risks

To reduce the circumstances under which this requirement mightnot able to be satisfied, all the designers must have beendeveloped web sites previously and they must be aware of htmlrestriction and cross browsers implementations before starting thedesigning. In order to reduce the probability of this occurrence theentire design team will be trained in basic html development andmacromedia fireworks, this tool will be used instead of Photoshop.

5.

Dependencies with other requirements

All user interfaces should be able to interact with the usermanagement module and a part of the interface must bededicated to the login/logout module

4.Non Functional Requirements

4.1. User Interfaces

4.2

. Hardware Interfaces

Server Side:

Software

Requirements Specification for library management system Page 10



Operating System: Windows 9x/xp ,Windows ME



Processor: Pentium 3.0 GHz or higher



RAM: 256 Mb or more



Hard Drive: 10 GB or more

Client side:



Operating System: Windows 9x or above, MAC or UNIX.



Processor: Pentium III or 2.0 GHz or higher.



RAM: 256 Mb or more

4.3

. Software Interfaces



Database:

SQL Server.



Application:

ASP (Active Server Pages)



Web Server:

IIS (internet Information Services (IIS) is a powerfulWeb server that provides a highly reliable, manageable, and scalableWeb application infrastructure)

4.4. Communications Interfaces

The Customer must connect to the Internet to access the Website:



Dialup Modem of 52 kbps



Broadband Internet



Dialup or Broadband Connection with a Internet Provider.

5.Other Nonfunctional Requirements

Software

Requirements Specification for library management system Page 11

5.1

Performance Requirements

The proposed system that we are going to develop will be used as the Chief performance system within the different campuses of the university

whichinteract with the university staff and students. Therefore, it is expected thatthe database would perform functionally all the requirements that arespecified by the university.

5.2Safety Requirements

The database may get crashed at any certain time due to virus or operatingsystem failure. Therefore, it is required to take the database backup

5.3Security Requirements

We are going to develop a secured database for the university .There aredifferent categories of users namely teaching staff,administrator,library staff ,students etc.,Depending upon the category of user the access rights aredecided.It means if the user is an administrator then he can be able to modifythe data,delete,append etc.,All other users other than library staff only havethe rights to retrieve the information about database.

Software Quality Attributes

The Quality of the database is maintained in such a way so that it can be veryuser friendly to all the users of the database

5.4Hardware Constraints

The system requires a database in order to store persistent data. Thedatabase should have backup capabilities.

5.5 Software Constraints

The development of the system will be constrained by the availabilityof required software such as web servers, database and developmenttools. The availability of these tools will be governed bythe University of Ballarat. The most recent versions of software development tools may not beinstalled at the University of Ballarat.

Software

Requirements Specification for library management system Page 12

5.6Design Constraints

The system must be designed to allow web usability. That is, thesystem mustbe designed in such a way that will be easy to use and visible on mostof the browsers.