EngiGuide

Software Requirements Specification For
E-TENDERING


Prepared By,
Dhaval Modi
6^th IT
GEC Modasa
Table of Contents
Table of Contents

1. Introduction

1.1 Purpose

1.2 Scope

1.3 Definitions

1.4 References

2. Overall Description

2.1 Product Perspective

2.2.1 System Interfaces

2.2.2 User Interfaces

2.2.3 Hardware Interfaces

2.2.4 Communication Interfaces

2.2 Product Function

3. The Use Case definitions

4. Assumption and dependencies

5. Specific Requirements

5.1 External Interface

5.2 Function

5.3 Performance Requirements

5.4 Logic Database Requirements

5.5 Design Constraints

5.6 Software System Attributes

5.7 Organization Specific Requirements

5.8 Functional Hierarchy

1. Introduction

1.1 Purpose

Software Requirement Specification (SRS) is the starting point of the software developing activity. As system grew more complex it became evident that the goal of the entire system cannot be easily comprehended.  Hence the need for the requirement phase arose.  The software project is initiated by the client needs.

The SRS is the means of translating the ideas of the minds of clients (the input) into a formal document (the output of the requirement phase.)

The SRS phase consists of two basic activities:

1) Problem/Requirement Analysis: The process is order and more nebulous of the two, deals with understand the problem, the goal and constraints.

2) Requirement Specification: Here the focus is on specifying what has been found giving analysis such as representation, specification languages and tools, and checking the specifications are addressed during this activity.

1.2 Project Scope and Product Features

ROLE OF SRS:

The purpose of the Software Requirement Specification is to reduce the communication gap between the clients and the developers.  Software Requirement Specification is the medium though which the client and user needs are accurately specified.  It forms the basis of software development.  A good SRS should satisfy all the parties involved in the system.

SCOPE:

This software is used for tender management and posted tenders can be viewed anywhere and anytime. Suppliers can ask queries immediately. Bidding online saves a lot of time and buyers can answer queries posted by suppliers immediately.

1.3 Definitions, Acronyms and Abbreviation Term Definition

Buyer	The person who issues tender
Supplier,Bidder	The person who submit the quotations
Quotation	Responding to tender
IEEE	Institute   of   electrical   and   electronic  engineers
SRS	Software requirement specification

1.4 References

The  format  of  this   document  is  taken  from the

“IEEE standards collection – 2009 edition”.

The other document referred are

“SRS sample – IEEE standards” and “SRS template”.

The book referred is “System Analysis and Design- Awadh”.

2. System Overview

The   following   subsections   provide   the   complete   overview   of   the   software specifications   requirements   documentation   for   the   e-Tendering. The   entire   srs   is documented in view of both suppliers and the buyers and the following sub sections are arranged  to give a complete outlook of   the   software,   its perspective,   features, system requirements and users know how.

2.1 Product Perspective

This  website  may   be   a   standalone  website   if   is   used   only   up   to   submission   of quotations phase.  But  ifthe  later phases are also to be  incorporated  then  it  must be integrated with other websites for example for credit card details it must contact credit card handling website (credit cards are used as a means of e-payement

Thus the two perspectives may be as follows.

1) Independent

2) Integrated

Importance of product

The traditional  approach to tendering is often characterized as time consuming and expensive.

This is because:

•  Advertisements   for   the  required goods or  services are placed  in newspapers and

journals, incurring publication costs,

• Tender documents are issued in hard copy format, incurring printing, copying and

postag costs,

• Tender responses are returned in hard copy, so that bidders incur printing, copying

and postage costs etc.

e-tendering   can   deliver   savings   and   benefits   to   an   organization   by   enhancing efficiency and control in the process of purchases of goods or services. Savings and benefits can be categorized into cashable and non-cashable.

Cashable benefits

Cashable   benefits   result   in   a   reduction   in   expenditure.   In   terms   of   e-tendering, cashable benefits are largely process efficiencies (time saved that results in headcount saving sand hence  reduced expenditure)  and  reductions  in overhead costs  incurred during   the   tendering  process   as   stated   above. These   savings   are   achieved   through automation of   the  tender  process The main elements  of  overhead cost   savings  are printing, copying, paper, postage and stationery, which will mostly be avoided because tender  documents and tender  responses will  be issued/received electronically.This is also environmentally friendly since it reduces the use of paper. e-Tendering can also release additional  office space as contract  documentation (required  to be kept  for at least the length of the contract period) can be stored online.

Non-cashable benefits

This website will provide a range of non-cashable benefits:

• it will lead to better management and/or co-ordination of the tender process.

• it will enable a consistent tender process. Having one  system  shared across  the organizations ensures that anyone involved in the tender process will work within a consistent and unambiguous framework.

• The time spent analyzing numerical information (such as costs) is reduced. It will also   have   functionality   that   can   immediately   send   out   an   email   notification   to suppliers who fail to provide all expected information.

• This site will have the ability to create an evaluation report on each tender, including an outline of the methodology used in evaluating the tenders etc

• It is important for the tendering process in the public sector to be fair and for that fairness to be documented. This site will provide a secure history from advertising the tender to awarding a contract  This history encourages openness and integrity in all contractual decisions.With a traditional  tendering process, responses arriving late due to courier delay or Incorrect  addressing would have been disqualified from the tendering process. This website  will   ensure   this   does   not   occur   because   suppliers   receive   an   immediate confirmation by email that their tender has been received, thereby avoiding potential disputes and ill feeling.

• less time taken to process responses for evaluation; means that less person time spent administering but also responses can be evaluated faster, so end-to-end tendering time is reduced.

2.1.1. User Interfaces

There will be three types of actors of this site

(a)Buyers: the persons who are responsible for issuance of tenders

(b)Suppliers: the persons who will submit their response for tender

(c)Other users (unregistered): other people who only want to see the tenders but do not

want to respond.

A help document will be provide to the user. In case if he gets stuck up at something, he can invoke the help.

The characteristics are as follows:

• No pre knowledge of  database management
• Should know English
• Should be able to use and do according to the graphical user interface

2.1.2. Hardware Interfaces

The hardware requirements of the system are-

• Processor – Pentium 3 or above
• Hard disk – Atleast 8 GB
• Monitor – Any CRT or TFT
• Memory – Atleast 128 MB

2.1.3. Software Interfaces

• Operating System – Windows 98 or above
• Front end – Ecllipse
• Backend  Access 07

2.1.4. Communication Interfaces

LAN card.

2.2 Product Functions

This website will  give potential  suppliers 24 hour  a day access  to view all   tender opportunities including contract renewal dates, tender deadlines, status of tenders etc. Suppliers will be able to submit tender documents electronically on this site, thereby using the time that would have otherwise have had to be allowed for postal delivery to complete the response. As this is Internet based solution, suppliers will be able to easily view and engage in tendering opportunities without being constrained by location .this  website  will  maintain   an   approved   list   of   suppliers   that   have   responded   to previous tenders   and categorizes them by set criteria, such as location and goods or services offered.

This website will  offer  organizations  to submit   tenders online  in electronic  format thus saving their time of post delivery. the evaluation of responses to the tender will also be done on this site. Finally award of tender will be given to the selected party.

3. The Use case Definitions.

Figure 1 – E-Tendering Use-Case Diagram

Actors:

1. Buyers.
2. Suppliers
3. Other Users

Related Functions/Use case:

1. Login
2. Publish tender
3. Update tender
4. Answer queries
5. View bids
6. View open tender
7. View close tender
8. As queries
9. Bids

10.  View answer

(a)Buyers: the persons who are responsible for issuance of tenders

(b)Suppliers: the persons who will submit their response for tender

(c)Other users (unregistered): other people who only want to see the tenders but do not want to respond.

4.  Assumptions and Dependencies

It is being assumed that-

The user at least has a basic knowledge of the system.

The organization  for  which  the  software  is designed has a machine on which  the

software can run.

The dependencies associated with the system are-

The user must have a Microsoft office installed on its system.

It must have any browser to run the web site as well.

5.Specific Requirements

5.1 External Interfaces

5.1.1 User Interfaces –

5.1.2 Hardware Interfaces –

The hardware requirements of the system can be summed up as-

1.Processor-Pentium2 or above.

2.Hard Disk-At least 512MB

3.Monitor-any CRT OR TFT.

4.Memory-At least 64MB.

5.1.3 Software Interfaces –

1.Operating Systems can be any version of Windows 98 or above.

2. Front end- Java,JSP.

3.Back end-Mysql 5.0.

5.1.4 Communication Interfaces

None

5.2 Functions

The function performed by this software are divided into 4 major parts:-

5.3 Performance Requirements –

The graphical user interface of the software should serve as a application software.The user can open the software like any other software, i.e, by clicking on the icon of the software.

5.4 Logical database Requirements –

The software is designed to run with very common hardware configuration.The database being used is access 2007 which is quite quick and will very well suit the database.It also requires less memory.

5.5 Design constraints-

The   software   is   designed   by   keeping   in   view  that   the   user   is   a   naive   user   and therefore,  such precautions  are  taken so  that  no damage  is caused  to  the software keeping in view as safety measure.

Standard   Compliance-The   software  will   open   only   by   a   login   name   and password, thus avoiding the risk of unauthorized access.

5.6 Software system attributes

The user   interface provide within  the  software will  certainly help  the user   to get familiar with the system in a short periods of time .Almost every task is associated with a key , so the work of manual entry is minimized to a great extent.

5.6.1 Reliability

• The software is reliable for user to use it.
• All the login information stored in data base properly.
• Supplier easygoing check the buyers and buyer can get the all information properly.

5.6.2 Availability

• The software is available for use only and no modifications access is granted to user.
• Also software available whenever he want to see beads with mannerly.
• All bids are noted by software rightly.

5.6.3 Security

• The software will open only by a login name and password, thus avoiding the risk of unauthorized access.
• Authorized people can see the  bids.
• Also authorized people make assess in data base and make modification

5.6.4 Maintainability

• There is no such maintenance cost .user can use it easily.

5.6.5 Portability

• The software operates not only on Windows but portable to any platform available on the remote side.

5.7 Organizing the specific requirements-

• The system features mentioned earlier are discussed in this section.

5.7.1 System mode`1-

MOBILE STORE MANAGEMENT SYSTEM:OPENING PAGE

5.7.2 Feature-

This page opens up as soon as the software is initiated. it has got a high priority.

5.7.3 Stimulus-

The name of the software will  be displayed at the top and a progress bar will start loading.

5.7.4 Response-

The name of the software will  be displayed at the top and a progress bar will start loading.

5.8 Functional Hierarchy-

1. The software must be properly installed.

2. All the interfaces necessary for its working are installed.

5.8.1 System mode`2-

MANAGEMENT SYSTEM:LOGIN FORM

5.8.2 Feature-

This page opens up as soon as the progress bar is loaded. it has got a high priority.

5.8.3 Stimulus-

It ask the user to enter the login name and password.Failing which the software fails to open up and give a ,message of wrong password.

5.8.4 Response-

It ask the user to enter the login name and password.Failing which the software fails to open up and give a ,message of wrong password.

5.9 Functional Hierarchy-

1. The progress bar must be loaded.

5.9.1 System mode 3-

MANAGEMENT SYSTEM:FUNNCTIONAL PAGE

5.9.2 Feature-

This page opens up as soon as the user enter the name and password. It has got a high priority.

5.9.3 Stimulus-/5.9.4 Response-

The   page   consist   of   various   buttons/keys,   each   having   a   specific   functionality associated with it.

The keys are-

1.RECHARGE-This key opens up the page which show various frames each showing the various details of various recharges.

2.ACTIVATIONS-This   key   opens   up   the   page   which   show   details   of   various activations.

3.SALES -This key opens up the page which shows two frame-one showing sales.

4.TRASCATION DETAILS-.  This   key   opens   up   the   page  which   shows   variousrecords and generates reports on the basis of information stored in the data base

5.BILL DETAILS- Switching on this key show the customer bill.

6. PASSWORD CHANGE- Switching on this key change the software password

5.10 Functional Hierarchy-

1.The login name and password should be correct.

5.10.1 System mode 4-

MANAGEMENT SYSTEM:BILL PAGE

5.10.2 Feature-

This page opens up as soon as the user click on the bill details icon.

5.10.3 Stimulus-/5.10.4 Response-

The   page   consist   of   various   buttons/keys,   each   having   a   specific   functionality associated with it.

The Keys are:-

1.GET SERIAL NUMBER-the appropriate customer serial id is obtained.

2.ENTER-the quantity or item no should be enter properly.

3.ADD-this calculate total amount of the customer

4.BACK TO MAIN MENU-shooting this key goes back to menu form.

5.EXIT-exit from the software

5.11 Functional Hierarchy-

1.The bill no should be correct so that it can print the customer details properly.

5.11.1 System mode 5-

MANAGEMENT SYSTEM:PASSWORD CHANGE

5.11.2 Feature-

This page opens up as soon as the user click on the password change icon.An additional feature of the software to provide user with changing password as per requirement.

5.11.3 Stimulus-/5.11.4 Response-

The page consist  of 3 buttons/keys,  each having a specific functionality associated with. The Keys are:-

1.CHANGE-the appropriate password changes made.

2.RESET-everything is reset to null values.

3.BACK TO MAIN MENU-shooting this key goes back to menu form.