Software Requirement Specification

SOFTWARE REQUIREMENT SPECIFICATION

DEVELOPERS RESPONSIBILITIES OVERVIEW:

The developer is responsible for:

Developing the system, which meets the SRS and solving all the requirements of the system?

·         Demonstrating the system and installing the system at client's location after the acceptance testing is successful.

·         Submitting the required user manual describing the system interfaces to work on it and also the documents of the system.

·         Conducting any user training that might be needed for using the system.

·         Maintaining the system for a period of one year after installation. 

 FUNCTIONAL REQUIREMENTS:

Following is a list of functionalities of the system.

This is made possible by prompting each user to enter his user-id and password before he can send or view his mails. This project has Inbox, compose and outbox.

This system should provide the administrator with the convenience such as adding a new agent, view and manage the information about the agents, view the following reports by day-wise, weekly, or monthly:

·         Employees view the mail and he composes or sends he mail to others.

·         It has Inbox, Outbox and Compose mail.

This system should help the users by providing the details online and provides a facility to search the employee records based on various options like based on the type of users, location of the employee. It should allow the users to set alert messages to the employees for the changes in the following rules etc. The users should be able to send messages through mails. The users should be able to generate the following reports:

·         Number of users processed in specified interval of time.

·         The storage of data becomes less  and the daily wise reports for amount and customer details

This system should include support for the users to view their details, view the information catalog and search facility for all available users.

     Non-Functional Requirements:

The system should be web-based system. Each user should have a user account. The system should ask the username and password to users. It doesn’t permit to unregistered user to access for Integrated Claim Settlement Services. The system should have Role based System functions access. Approval Process has to be defined. The system should have Modular customization components so that they can be reused across the implementation

These are the mainly following:

• Secure access of confidential data (user’s details). SSL (Secure Sockets Layer) can be used.
• 24 X 7 availability
• Better component design to get better performance at peak time
• Flexible service based architecture will be highly desirable for future extension

1. Performance

They understand the importance of timing, of getting there before the competition.  A rich portfolio of reusable, modular frameworks helps jump-start projects.  Tried and tested methodology ensures that we follow a predictable, low - risk path to achieve results.  Our track record is testimony to complex projects delivered within and evens before schedule.

  2. Security

Its  provides more security by setting username and password.

  3. Safety

This application provides more safety to the users for accessing the databases and for performing the operations on the databases.

   4. Interfaces

It provides the interface for accessing the database and also allows the user to do the manipulations on the databases.

  5. Reliability

This entire project is depends on the SQL Server.

6. Accuracy

Since the same table is created at different users account, the

Possibility of retrieving data wrongly increases. Also if the data is more,

Validations become difficult. This may result in loss of accuracy of data.

  7. Ease of Use

Ever user should be comfortable of working with computer and internet browsing. He must have basic knowledge of English.

8. Interoperability

This provides the import and export facilities for sending one database to another database.

9. Maintainability

The key to reducing need for maintenance, while working, if possible to do essential tasks.

1.   More accurately defining user requirement during system development.

2.   Assembling better systems documentation.

3.   Using more effective methods for designing, processing, login and communicating information with project team members.

4.   Making better use of existing tools and techniques.

5.   Managing system engineering process effectively.

10. Testability

   Testing is done in various ways such as testing the algorithm, programming code; sample data debugging is also one of following the above testing.

   11. Design Constraints

During system testing the system is used experimentally used to ensure that the software does not fail, i.e., it will run according to its specification and in the way the users expect.  Special test data are input for processing and the results examined.  A limited number of users may be allowed to use the system to see whether they try to use it in unforeseen ways.  It is preferable to discover any surprises before the organization implements the system.

 12. Cost Estimates

13. Preliminary Estimates.

  The project is decomposed into major structural     systems   or production equipment items, e.g. the entire floor of a building or a cooling system for a processing plant.

  14. Detailed Estimates.

 The project is decomposed into components of various major systems, i.e., a single floor panel for a building or a heat exchanger for a cooling system.

 15. Engineer's Estimates.

 The project is decomposed into detailed items of various components as warranted by the available cost data. Examples of detailed items are slabs and beams in a floor panel, or the piping and connections for a heat exchanger.

16. Development Platform

   The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. The .NET Framework is designed to fulfill the following objectives:

• To provide a consistent object-oriented programming environment whether object code is stored and executed locally, executed locally but Internet-distributed, or executed remotely.
• To provide a code-execution environment that minimizes software deployment and versioning conflicts.
• To provide a code-execution environment that guarantees safe execution of code, including code created by an unknown or semi-trusted third party.
• To provide a code-execution environment that eliminates the performance problems of scripted or interpreted environments.
• To make the developer experience consistent across widely varying types of applications, such as Windows-based applications and Web-based applications.

To build all communication on industry standards to ensure that code based on the .NET Framework can integrate with any other code.

17. Acceptance Criteria Procedures

         

       The “SQL Client” has been successfully completed. The goal of the system is achieved and problems are solved.

• The project has been appreciated by all the users in the organization.

• It is easy to use, since it uses the GUI provided in the user dialog.

• User friendly screens are provided.

• The usage of software increases the efficiency, decreases the effort.

• It has been efficiently employed as a Remote Database Access Tool.

• Administrator.
• It has been thoroughly tested and implemented.