Srs document software testing

System: Clears the entered data. Guest User: Selects create account option Business Rules: Customer has to select minimum one product as well as quantity. There is no limitation for selecting maximum products and quantity w. System: Receives the vote and provides up-to-date poll results. System: Rejects the vote and provides message. Admin User: enters parent, Category Name, sort order, attaching logo by browsing. System: saves the details into the database Alternative Flows: 1.

Admin User: cancels the form without entering any data, after entering some data and entering full data. Deletes the category deleting Alternative Flows: Business Rules: Admin user can select one category at a time.

Admin User: selects parent, enters product name and product code, selects tax class, enters sort order, price number only , list price, In stock, shipping freight, weight, minimum order quantity and description HTML and saves.

System: Saves the details into the database and provides ACK. Alternative Flows: 1. System: Displays the All Products page. Admin User: selects parent, enters product name and product code, selects tax class, enters sort order, price number only , list price, In stock, shipping freight, weight, minimum order quantity. Selecting Import Excel option In the Catalog menu.

Selecting export Excel option In the Catalog menu. System: Saves the details into database Alternative Flows: 1. System: Displays the Special offers page. Admin User: Selects product, enters product price ,discount, selects Buy one get one free and saves.

Admin User: cancels the form without filling any data, after filling some data and after filling full data. System: Closes the page. Gives Ack. Business Rules: Admin User has to type one Question and 3 answer options each in separate line. Admin user can reset the data at any movement before saving the data. System: accepts the details and sends for intended Process.

Admin User: views the Report and Close. It should include all the functional and non-functional requirements, the correct numbering of the pages, any diagrams if required. Unambiguous — All the requirements should have the same interpretation.

Verifiable — SRS is said to be verifiable if and only if each requirement is verifiable; there must be a way to determine whether every requirement is met in the final product. Ranking for importance and stability — Each requirement should be ranked for its importance or stability. Modifiability — An SRS is said to have modifiability quality if it is capable of adapting changes in the future as much as possible.

Traceability — Tracing of requirements to a design document, particular source code module or test cases should be possible. Design Independence — SRS should include options of design alternatives for the final system; it should not have any implementation details. Testability — An SRS is said to be testable if it is easier for the testing team to design test plans, test scenarios, and test cases using an SRS.

Understandable by the customer — An SRS should be written with easy and clear language so that the customer can understand the document. The development team will use an SRS as a base for coding.

The testing team uses SRS to create a test plan , test scenarios , and test cases. So, the development and testing team should have a detailed knowledge of each section of an SRS. Their understanding of the requirements should be clear so that any discrepancies in the source code and further testing documents can be avoided. Ideally, a Business Analyst should schedule a review meeting with required parties.

Reviewers can be the client, developers, testers, project managers among others. Instead of giving the final document for review, a BA can arrange a periodic meeting with the reviewers whenever an incrementally updated version of the SRS is available.

It may include the use cases of how user is going to interact with software system. The software requirement specification document consistent of all necessary requirements required for project development. To develop the software system we should have clear understanding of Software system.

To achieve this we need to continuous communication with customers to gather all requirements. A good SRS defines the how Software System will interact with all internal modules, hardware, communication with other programs and human user interactions with wide range of real life scenarios.

It is very important that testers must be cleared with every detail specified in this document in order to avoid faults in test cases and its expected results.

It is highly recommended to review or test Software Requirement Specification documents before start writing test cases and making any plan for testing. Correctness of Software Requirement Specification should be checked. Since the whole testing phase is dependent on SRS, it is very important to check its correctness.

There are some standards with which we can compare and verify. Ambiguity should be avoided. Sometimes in SRS, some words have more than one meaning and this might confused testers making it difficult to get the exact reference. It is advisable to check for such ambiguous words and make the meaning clear for better understanding. Requirements should be complete. When tester writes test cases, what exactly is required from the application, is the first thing which needs to be clear.

For e. Consistent requirements. The SRS should be consistent within itself and consistent to its reference documents. This sets the standard and should be followed throughout the testing phase. Testing environment: some applications need specific conditions to test and also a particular environment for accurate result.

SRS should have clear documentation on what type of environment is needed to set up. Pre-conditions defined clearly: one of the most important part of test cases is pre-conditions.

If they are not met properly then actual result will always be different expected result. Verify that in SRS, all the pre-conditions are mentioned clearly. Requirements ID: these are the base of test case template.