Table of Contents
1. Introduction 3 1.1 Purpose 3 1.2 Scope 3 1.3 Overview 32. The Overall Description 4
2.1 Product Perspective 4 2.1.1 Interfaces 4 2.1.2 Hardware Interfaces 4 2.1.3 Software Interfaces 4 2.1.4 Communications Interfaces 4 2.1.5 Memory Constraints 4 2.2 Product Functions 4 2.3 User Characteristics 4 3. Specific Requirements 5
3.1 External Actor Description 5
3.1.1 Human Actor 5
3.1.2 Hardware Actor 5
3.1.3 Software Actor 5
3.2 Use Case Description 5
3.2.1 Use Case 1 5 3.2.2 Use Case 2 6 3.2.3 Use Case 3 6 3.2.4 Use Case 4 6 3.2.5 Use Case 5 6 3.2.6 Use Case 6 6 3.3 Performance Requirements 7
3.4 Logical Database Requirements 7
3.5 Design Constraints 7
3.6 Software System Attributes 7
3.6.1 Reliability 7
3.6.2 Availability 7
3.6.3 Security 7
3.6.4 Maintainability 8
1. Introduction
This SRS contains all the specifications required to make a Enquiry Management System. This Enquiry Management System should maintain the complete database of Customers, Enquiries, Products and Employee as well as Follow Up of an Enquiry. In this application Log-in process is needed to accessing the features, to log-in ; user must register himself, when he registers he will be able to log-in. After log-in user should be able to fill up the customer details, enquiry details, product and follow up details. Customer details contain all the information about the customer where enquiry detail contain the information about the enquiry made by customer as well as product detail also feed up in this section. Follow up detail contains the future reminders for the employee to the customer; if an enquiry not completed yet.
1.1 Purpose
This SRS is documented for breaking the application into smaller components that helps to organize all the information which helps to developer to understand the
functionality and boundries of the application. This will also helps to developer to understand the order of developing project.
1.2 Scope
(1) Scope of this project is to make a web application for an organization to maintain the information of Enquiry and releted components.
(2) This Enquiry Management System should maintain the complete database of Customers, Enquiries, Products and Employee as well as Follow Up of an Enquiry. This software can not be locally accessed by anyone.
(3) Many times in the organization the enquiry registration and follow up process get missed due to lack of good Enquiry Management System. This software works as a lead management system to maintain all the information.
1.3 Overview
(1) This SRS contains the overall description with Hardware interface and Software interface Performance Requirements, Design Constraints and Software system attributes.
(2) This SRS is organized by Use Case which contains External Actor Descriptions and Use Case Descriptions.
2. The Overall Description
2.1 Product Perspective
This product is independent and totally self-contained. As the compition is increasing in today’s environment organization has to work hard to attain the maximum profit. Due to lack of technology in an organization reflects in a low profit or certain losses like improper communications, no consumer satisfactions. This application helps to organize the complete database.
2.1.1 Interfaces
The interface between the software product and its users is GUI(Graphical User Interface) based.
2.1.2 Hardware Interfaces
“This system has no hardware interface requirements”
2.1.3 Software Interfaces
“This system has no software interface requirements”
2.1.4 Communications Interfaces
“This system has no communication interface requirements”
2.1.5 Memory Constraints
“This system has no memory constraints”
2.2 Product Functions
(1) This product provide facility of Registration. (2) User have to login to access the application. (3) Add new Customer entry.
(4) Add new Enquiry detail with respected Product. (5) Add Follow up with the Enquiry.
(6) Add new Products in the application. (7) Add new Employee in the application.
2.3 User Characteristics
The intended users of this product must have the prior knowledge of Internet accessing.
3. Specific Requirements
3.1 External Actor Description
3.1.1 Human Actors
User (Administrator or Employee) select the query they want to process from a
given list of queries.
3.1.2 Hardware Actors
Server : Pentium 4 or higher speed processors (versions) with a minimum of 512MB RAM and Hard Disk of 60 GB or more.
Client : Minimum of Pentium 4 processor with 256 MB RAM recommended 512 MB RAM for faster performance with a Hard Disk of 4.3GB or more.
Input Device: It is used to enter data and instructions in the computer. a ) It serves as an interface between user and computer.
b ) It converts data and instructions in machine language. c ) It accepts data and instructions from outside world.
Output Unit: It provides the information and result of computation to the outside world. Generally Monitor is used as output device.
a) It accepts the results produced by computer.
b) It converts the machine language into human readable form. c) It supplies converted result to the outside world.
3.1.3 Software System Actors
Operating System : Windows XP or higher. Database : SQL Server 2005.
Development Tool : Microsoft .Net 4
3.2 Use Case Descriptions
3.2.2 Use Case 2- Use case for adding new customer into the Database.
3.2.3 Use Case 3- Use case for adding Enquiry into the Database.
3.2.4 Use Case 4- Use case for adding Follow up into the Database.
3.2.5 Use Case 5- Use case for adding Product into the Database.
3.3 Performance Requirements
Consistency of data and non-redundancy are the major requirements. Any kind of inconsistency can lead to serious effects in the process. Thus, proper and immediate updationand entry of records to the server is the main aim.
3.4 Logical Database Requirements
Large amount of memory is needed for the storage and warehousing of data in the database. So choose appropriate data types for fields; to save space in the database and improve join operations.
3.5 Design Constraints
Every application or software consist of many sub-parts. So categorization and record keeping of each in necessary. The software needs to be completely error-free. For the implementation .NET framework will have to be installed on the system.
3.6 Software System Attributes
3.6.1 Reliability
Reliability are those in which the software must meet in order to perform a specific function under certain stated conditions, for a given period of time. The level of reliability can be dependant on the type of system.
3.6.2 Availability
EMS is a web application which have to run 24/7 or according to organization timings. In case of software failure it must be available for reuse after restarting the application. The system shall allow user to restart the application after failure.
3.6.3 Security
The system contains sensitive information about the administrator’s account status. So this information is given to the particular administrator who is eligible and authorized to view or change his/her personal information, and also make changes in the database. For this, the utility like username and password is provided for securing the sensitive information
3.6.4 Maintainability
Testing tools need to be applied for the verification of the software. The validation of the software also needs to be performed.
The software needs to be thoroughly tested on lines of consistency and integrity of data.
It needs to be ensured that the connection between the client side and the server are working properly.
The deployment of the software over the LAN needs to be handled very carefully.
3.6.5 Portability
Portability of a software system is the usability of same software in different environments. The abstraction between the application logic and system interface is required that helps to software to perform same functionality for several computing plateforms. Portability will have to be key issue for development cost reduction.
