How to test software requirements specification (SRS)?

Do you know “Most of the bugs in software are due to incomplete or inaccurate functional requirements?”  The software code, doesn’t matter how well it’s written, can’t do anything if there are ambiguities in requirements.

It’s better to catch the requirement ambiguities and fix them in early development life cycle. Cost of fixing the bug after completion of development or product release is too high.  So it’s important to have requirement analysis and catch these incorrect requirements before design specifications and project implementation phases of SDLC.

How to measure functional software requirement specification (SRS) documents?
Well, we need to define some standard tests to measure the requirements. Once each requirement is passed through these tests you can evaluate and freeze the functional requirements.

Let’s take an example. You are working on a web based application. Requirement is as follows:
“Web application should be able to serve the user queries as early as possible”

How will you freeze the requirement in this case?
What will be your requirement satisfaction criteria? To get the answer, ask this question to stakeholders: How much response time is ok for you?
If they say, we will accept the response if it’s within 2 seconds, then this is your requirement measure. Freeze this requirement and carry the same procedure for next requirement.

We just learned how to measure the requirements and freeze those in design, implementation and testing phases.

Now let’s take other example. I was working on a web based project. Client (stakeholders) specified the project requirements for initial phase of the project development. My manager circulated all the requirements in the team for review. When we started discussion on these requirements, we were just shocked! Everyone was having his or her own conception about the requirements. We found lot of ambiguities in the ‘terms’ specified in requirement documents, which later on sent to client for review/clarification.

Client used many ambiguous terms, which were having many different meanings, making it difficult to analyze the exact meaning. The next version of the requirement doc from client was clear enough to freeze for design phase.

From this example we learned “Requirements should be clear and consistent”

Next criteria for testing the requirements specification is “Discover missing requirements”

Many times project designers don’t get clear idea about specific modules and they simply assume some requirements while design phase. Any requirement should not be based on assumptions. Requirements should be complete, covering each and every aspect of the system under development.

------------

Specifications should state both type of requirements i.e. what system should do and what should not.

Generally I use my own method to uncover the unspecified requirements. When I read the software requirements specification document (SRS), I note down my own understanding of the requirements that are specified, plus other requirements SRS document should supposed to cover. This helps me to ask the questions about unspecified requirements making it clearer.

For checking the requirements completeness, divide requirements in three sections, ‘Must implement’ requirements, requirements those are not specified but are ‘assumed’ and third type is ‘imagination’ type of requirements. Check if all type of requirements are addressed before software design phase.

Check if the requirements are related to the project goal.
Some times stakeholders have their own expertise, which they expect to come in system under development. They don’t think if that requirement is relevant to project in hand. Make sure to identify such requirements. Try to avoid the irrelevant requirements in first phase of the project development cycle. If not possible ask the questions to stakeholders: why you want to implement this specific requirement? This will describe the particular requirement in detail making it easier for designing the system considering the future scope.

But how to decide the requirements are relevant or not?
Simple answer: Set the project goal and ask this question: If not implementing this requirement will cause any problem achieving our specified goal? If not, then this is irrelevant requirement. Ask the stakeholders if they really want to implement these types of requirements.

In short requirements specification (SRS) doc should address following:
Project functionality (What should be done and what should not)
Software, Hardware interfaces and user interface
System Correctness, Security and performance criteria
Implementation issues (risks) if any

Conclusion:
I have covered all aspects of requirement measurement. To be specific about requirements, I will summarize requirement testing in one sentence:
“Requirements should be clear and specific with no uncertainty, requirements should be measurable in terms of specific values, requirements should be testable having some evaluation criteria for each requirement, and requirements should be complete, without any contradictions”

Testing should start at requirement phase to avoid further requirement related bugs. Communicate more and more with your stakeholder to clarify all the requirements before starting project design and implementation.

Do you have any experience testing software requirements?  




135 comments ↓

#1 Shantanu

In my company we testers don’t get any specifications for review. We get directly the module to test.
When we get module we study the module requirement and then start on testing.
can u tell is this a bad practice?

#2 Beena

Hi…..

#3 shaila

i also have same question which posted by shantanu. we just study the module and start testing manually.
is this a bad practice?

#4 Sunil Yadav

In our company some time we get the SRS to read and start to test the application.
they are not giving enough time to review and give the feedback about the requirements.
We r getting the application for 1-2 days for testing after that got new application to test

such a bad practice……..

#5 KAT22

Very informative article

#6 raj

what do u mean by study the module:

do you get any release notes document for the module

or

do you have any write up which details about the functionality of the received module.

if no documents are given and just given a component for testing.

then
you are suppose to do some explority testing
if not

if you know the componet domain, you can have some idea about the given componet for testing

and do some adhoc , exploratory testing and write a document for what u understand
and send it to the client
what ever you find while tesing as an obseravation seeking him clarification whether that observation is correct or not with respect to the given component.

hope i have answered you

sweetraj80@yahoo.com

#7 Jens

Also in my company we testers are not involved at this early stage. And I must say, it’s a shame since it’s really like that: “Most of the bugs in software are due to incomplete or inaccurate functional requirements?”

However, which way the company chooses to develop their applications often depends on the complexity of the project and the people involved. Usually there’s a lack of money in smaller projects since no customer wants to pay people to review the specification when everything seems to be simple and clear.
Reviews belong to the static test and according to my experience, the static testing part is the most neglected part.

#8 Kavitha

Hi friends,
In our company, from the client information, we(includes testers and two developers) will prepare the SRS and give it to the stackholder. This is just to know whether we have observed the exact requirements and to know what are missed out. Then, based on the feed back we will proceed further(design, development, test cases etc…

Is there any other better way to do…

#9 Raju

In our company, our client just tell the requirements verbally to the development team then they will develop according to the requirements.

After the development developers will explain the changes in functionality then we will prepare test cases accrodingly and starts testing.

such a bad practice…

#10 Suhas

Hi Shantanu, Shaila,

Many companies follow the same procedure for testing, because there is time bounding and expenses calculation. Some of them even don’t write any SRS, they just get the clone or a Rough idea for the project.. This creates a bad impact on the quality process of Software development..Even in my company it happened the same way before one and half year but I personally started writing the SRS for myself.. Taking out time from browsing other websites… i managed to write SRS of most of the projects… this also helped me to generate more test cases and test the application with maximum number of scenario… I suggest all of the readers who have the same problem to write the SRS them self (or just a functional document)…This practice is very useful like:

1. Testing the application thoroughly.
2. Getting complete Project Knowledge
3. Getting Complete domain knowledge
4. You can also use these practice for Case Studies.

Case Studies are assets for your professional life.

#11 swati

very nice & easy to understand article

#12 Jai

Indeed a good article.
Can I have answer for my question.
1) what is the end result of SRS review? is there any defined format where we report.

Regards
JAi

#13 Karthick

Hey guys …What i feel is …..Its always better to get the requirement from ur TL or managers for the review purpose ….Its we …who should take the initiative ….We shouldnt be waiting for them to come to us ….And managers like people who take initiatives …..

Workin on a module without reading the script is like Acting in a movie without knowing the story ….Wat u say guys ….

#14 Vijay

@Shantanu, Shaila, sunil
Please ask your team leader or manager to provide the SRS document as early as possible to review to test team.
Review from development and testing team early before design phase can explore potential bugs that could cost lot in later stages to catch and fix.

@jens, Raju
You can discuss this issue with your company management if mangers or team leaders are not involving testers in early stages of software development. Make sure to explain the importance of early stage requirement review to your management.
You can take reference of this article.
Also don’t rely on verbal requirements. Have everything in written.Don’t keep any communication verbally even with your team members and developers.

@Jai
Yes SRS is having some templates. I will make this SRS template available for our readers. This SRS is usually provided by stakeholders. So you can review it and can make your comments inline with the same doc. and submit it to test lead or manager. Which is expected to be reviewed/discussed in team by test/project manger.

@ Karthick:
i like this statement “Working on a module without reading the script is like Acting in a movie without knowing the story” it’s a perfect example for SRS review importance.

#15 test

test test test

#16 Karthick

Thanx a lot vijay……

#17 pankaja

.

#18 pankaja

g

#19 pankaja

o

#20 pankaja

0

#21 pankaja

d

#22 Swati Deshpande

Hi,
Very nice artical. we are facing same problem in our company.Your artical is very helpful for this issue. Now I can show this to my senior.
I have query, how i analyse or study the requirements since every project is different than other? How I use my testing skills without using same testcases or how I improve my creativity?
Thank you,

#23 rickflu

hi !!!
your site is very good !
i want to know how can i put this code in my blog,
“continue reading”
Can you help me with it ?
I holp answer :)
hugs

#24 suresh

Hi,
I am working as a test lead in an MNC. The Porject is on web based application for testing.
Instead of appreciating everybody equally, PM take it on community wise.in ONE-ONE meeting one of my team member elevated this, from now onwards he was threating by PM. Now he started leaving the company.
could you please suggest me how to react in this situation, as a team lead.

#25 Inder P Singh

Hi

A couple of comments:
1) Requirement definition is an iterative process. Whenever there is any effort to refine/ disambiguate/ clarify/ complete the requirements that results in a modification to the requirements specification, the process of requirements testing/ review should be repeated.

2) The requirements should deal with the “what” aspect and not with the “how” aspect. It is possible that you come across a requirement specification that mentions the “how” part e.g. a particular design, the name of the tool to be used (without proper evaluation of the tool) etc. This should be avoided since it unnecessarily reduces the number and scope of design choices available to you.

3) It should be understood that sometimes there are statutory requirements that need to be implemented. If this does not happen, there can be unwarranted legal implications. You can take the example of an application that processes credit card information. Legally, such an application has to keep the credit card information secure at all times.

Regards,
Inder P Singh

#26 Ashwin P

It is very unlikely that testers will every get documneted requirements (and even if they do, it I bet cannot address more than a small percentage of test conditions, because of the implied reqs, incomplete reqs, related reqs, obscure reqs, obsolete reqs and so on). But hey if you do get one, one thing you could do is to search for ambiguous words in the text (like ‘etc’, ‘all cases’,’good looking’ etc).

Ashwin
http://www.testersdesk.com

#27 Abhishek Kumar

How many test cases we can write in a day in a company.

#28 Abhishek Kumar

What is the Big Bang Model in the Software Testing. Plz me the all concepts of this model of SDLC.

#29 Abhishek Kumar

What is the yellow box testing & the gray box testing in the Software Testing. And what is the defference between them.

#30 Tiger2K

Dear Abhishek,
Gray Box testing is a combination of white box and black box testing.
Yellow box testing for testing “Warning messages” that should appear as part of the application in software.

Regards,
Tiger2K

#31 dinesh

I need the flow of testing from functional to acceptance testing.

#32 Jai

Hello members
Kindly send template for Integration Test case
kishoresharma1@gmail.com
we simply quote unit test caseid or something more
Please specify

Thanks

#33 Jai

Please do not define bottom-up and top down approach
I need template.

#34 Namrata

Hi,
Its a very good and useful article , i appreciate your good work and time that you contribute towards scripting these articles.
Keep up the good work

Regards
Namrata

#35 Param

Vry Nice Article

#36 Venkat

Excellent Article………

#37 Sarika

Hi Vijay,

i found all info given by you is very helpful.
I have 3.5 yrs of experience in Software Testing and now I want to do testing certification or any kind of technical sertification. Should I give CSTE/ISTQB or any technical exams?

#38 Nagendra

Its true that most of the testers are not involved while freezing the requirements. This is good. belive it or not, this is the practicle way.

I am not oppossing to what was said earlied by all of you. I am trying to address the core problem, i.e. Incomplete Req, unclear req etc…

Validating or Testing a requirement document do need some business knowledge of the product and its domain. And the important is the Client.

In my view the end tester is not the right person to test the requirements. But it is the Business Analyst and the Management who should be the right people to test the requirements. If these people dont test the requirements and map them to the clients needs, you can’t have a quality product.

#39 ANKIT

great article………

#40 SUMIT

bahu saras che………..

#41 shalu

According to me the requirments sholuld be given by businees analyst so that it’ll be very correct.
Because the persons who sits in the coding part or in testing side have no deal with the client, so better requirments will be given only by the peolple who r really having analyitcal skill who sits especiallly for collecting requirment………………

#42 Nagendra

The phrase “really having analytical skill” is not the right term I guess. Probably you mean people with business knowledge and process.

Testers and Developers too have the required domain skills but not to the extent of the client or business analyst or SME.

#43 Vaneeta

I have 1.5 yrs of experience in Software Testing (Manual )and now I want to do testing certification or any kind of technical certification. Should I give CSTE/ISTQB/IIST or any technical exams?

#44 SHYAM

Hi friends, i am only tester in my org.. my team lead(developer) will prepare only the basic req doc. which is not cleare, we don’t have any other docs like SRS, i am feeling very diff.. to test the application. can any one suggest what should i do

#45 Qastation

Hi
If requirements is established as the identified baseline configuration Item and would been signed off from the client then most of the projects not been resulted as failure.

I personally feel mostly small and medium sized projects they prepare SRS at the time of delivery and that too prepared by developers, so they prepare it as user manual rather than SRS.

#46 vaneeta

Hi suresh,

Do you have any idea about certification in testing. i have read about international certification in software testing.

#47 Manikandan

Finding the holes in the requirement before starting the development is good. generally maual testing will give only 60-70% coverage. but i am using the concept what the article is explained. it gives 100% coverage. so, i request testers to take a small requirement by your own and analyze the holes in the requirement (ambiguious statement). Once you got resolution from the client and you feel the requirement is Unambiguious prepare a test scripts against requirement. once the Development team finish the product. Execute the test script with the product. if the product pass in all test scripts. the Developed software is a Bug free software.

#48 vijai

wanna know the flow of software testing process in a corporate….?

#49 prasanna

yes,i do want to know the testing process.. please provide me the details

#50 Sundar Sharma Machiraju

Can I have the answer for my question?
Can anybody tell me one scenario in which we can test the application manually and we can’t do the automation testing.

#51 Nagendra

Hey guys, Plz keep this article and discussions to the main topic Testing Requirement Specifications…ask your other questions in relative blogs…..dont mind otherwise

#52 vinoth

Hi ,

I need winrunner free Trial version ,can any one tell me the link to get the trial version.Its very urgent please reply.

#53 Suhas

Hi Vinoth,

you may use utorrent component this may give you winnrunner with crack latest avail is 9.2 winrunner use
http://www.torrentz.com to search torrent and utorrent.exe to download

regards,
Suhas.
http://www.adccindia.com

#54 Kishore

Hi Vijay
Can you please define good requirement & bad requirement?

#55 Tarun

i want to learn about
how to go about the software testing ?

#56 sasidhar

if explain with examples is good for learners

#57 chanchal

Hi guys !

I am in bangalore searching for jobs in software testing field .my qualification is 10+2+3yrs(Dip in IT). can any one help me to get a job in this field .I am the freshers i have knowledge of both manual as well as automated pl help me .

Advance Thanks.

#58 Suhas M

@ Sundar Sharma Machiraju

What do you say about Usability testing?
There are many, share your thoughts…

Regards,
Suhas M.

#59 Suhas M

@ Manikandan,

Bug Free Software ???
Nothing like that exixts, if you know – please tell me know, i would love to look at it.

Regards, Suhas M.

#60 Babe

Hi all,
In the first time i come this page, I like it very much, thanks all.
My company is out sourcing company, some time, us project has to create SRS document to know more requirement from customer.
SRS is reviewed by QA group or experts, after modified it is approved by manager and announce for all project member (Tester is one member in this group).
I agree with Vijay, SRS is importance so all project team have to read before create test plan, test case (to tester) or design (desginer) or coding (dev).
Finally i want to share my opinion that: SRS is reviewed by experts before used.

#61 shahnaz

NO NEED OF SRS IF U ARE GENIUS

#62 samvida

It is a nice write-up. SRS and other specifications like Functional specification and Program specification are necessary for testers.

#63 Raman

Thanks mate! This article is really useful and has been very informative… Keep up the good work!

#64 Arun Vijayaraghavan

Well, SRS review is very much necessery. SRS followed by FS review would be carried out by the technical experts along with the BA. There is always very little involvement from the testers side.

Best practice would be to involve test management in this phase we can stream-line testing along with development.

Regards,
Arun
http://www.focustesting.com

#65 sree

hi
please explain me what is BRS and SRS and diff btween tem

#66 sreesree

hi
please explain me what is BRS and SRS

#67 sushil kumar

Hi Guys
I am sushil chauhan and i am pursuing BCA(final year). Please give me good advice for finding a Job.

#68 Vishal

Hi Vijay,

I am Vishal, curently working as QA in a small company at Kolkata. I have done Bsc and currently persuing Msc IT from Sikkim Manipal. Pls advice me which certification should I go for to boost my carrer.

Regards

#69 thangavel ks

srs review helpful to find bug in early as poosible
by ks thangavel

#70 sobha

please send me the processes and templates for testing

#71 Amit Vegad

please send me of srs for project tailoring ( this is my project defination)general developing are incuding.

bye.

#72 samvida

Amit, please specify your requirement clearly so i can help you as much as possible

#73 swetha

For checking the requirements completeness, divide requirements in three sections, ‘Must implement’ requirements, requirements those are not specified but are ‘assumed’ and third type is ‘imagination’ type of requirements. Check if all type of requirements are addressed before software design phase.

Here what is the difference between “Requirements those are not specified but are assumed” and “Imagination type of requirements”. Can you explain with an example.

#74 Vikas Kumar

How to start with QTP automation testing for the websites application

#75 Rahul

@Vikas Kumar
this is very basic question ..and i believe it wont be ant problems if u know QTP..
this is wt u learn very 1st in QTP dude,,
so get basic right and enjoy automation..

#76 Rahul

@swetha
pls explain ur question very clearly ..i will hepl u,,

#77 Rahul

@Vishal
here u go..
ISTQB add ons ur resume and boost u..secret of ur energy towards testing..gud lck..

#78 Ashish Verma

Hi,
I want to know about the ISTQB
The process of apply?How to register?the study Material?The palce of Test?Also the eligiblity criteria?
Plz inform me….

#79 Ashish Verma

Hi,I also want to know about the design of Test Matrix

#80 ch.girishchander raju

hi Ashish,

i got your mail because of time matters,i unable to give reply.

its better to call me directly,i will help you

my number:9391395989

ch.girish chander raju
Hyderabad.

#81 pengli

hai Vijay
I am fresher in software testing field. I have been learning “How to test software requirements specification?”,but i don’t have mature idea.how to use your method to application?

#82 johnson

How to create the good test scenario as per SRS in testing?

#83 Ansi

Hi all…
Yr since three months(My First three months of First job) i have been working on a product and Mgmt asked to to prepare srs on a module on which i haven’t worked on.. though i got KT but i think practicing physical would be more helpful. Can u people help me out in defining Scope of Project..
what pts shall i mention in it..
Plz help me out

#84 Sneha

hi….
This sight is really good , I requested you that please send me the bug report in excel sheet format.

#85 ruchi

Can some send me few sample test cases

#86 satyajeet

I required SRS FOR bug tracking in database

#87 BHAVIKA

I REQUIRED SRS FOR DEFECT TRACKING SYSTEM IN DETAILS FORMAT

#88 Prasad

SRS for defect tracking??? wt this mean.

u asking the document related to Defect tracking??

#89 sneha

ya a very good article. i got cleared abt software testing

#90 savitha

a good article .nice to understand and a clear view of how to test the software requirements.

#91 Bharat

What a good article is this.Really good

#92 Dinesh

hi this is dinesh

#93 Dinesh

Hi this is Dinesh i am working as Tech. Support Eng.in govt Organisation.i am ISTQB certifed but still i am wating for testing job.
what can i do.
( I want to change my profile)

Dinesh

#94 sanjay Dhankar

This site is very helpfull. I want test plans on various sceanarios on excel sheet. Plz send this.

#95 Reena

Hey i m the student of software testing. so i want some more &more knowledge of this filed . so please sending me this

#96 Darshan Patel

Briefly describe the SRS…… I wanna know more about the SRS…….

#97 Ramesh kudle

Vijay,

I am Ramesh, curently working as QA in a small company at Pune. I have done Bsc and currently persuing Msc IT from chavan institute. Pls advice me which certification should I go for to boost my carrer.
i am intrested in softwere testing
Regards

#98 Sajib

The article is good enogh for Testers. But I have a question- If there is no document (SRS, SDD, UI etc.) how to test that application?

#99 Mayasen

Hi Sajib, #98

It is too difficult to test the application without spec. It is just like a blind test. You can’t judge the user’s needs, thoughts and requirements.

Starting a project with spec is the best practice on working with.

In some cases, for micro level projects there are some chances to skip the spec. docs, on such cases try to document the discussions (MOM) from the initial phase, so that it will be much more helpful during the time of testing. From that you can derive the spec for your application for testing purpose.

#100 meena

Nice info, the site is very helpful for me.

I am about to appear for my istqb certification exam and I am very confused as how to derive testcases with some of the test techniques like statement, branch and condition coverages.

Can anyone please help me.
My email address is meena_ku@hotmail.com

Thanks
Meena.

#101 Fredric

Hi All,
I came with the same Question which was Shantanu, What i get answer from Vijay, but the thing is i approach management, i approach team lead, but nothing i get result instead bug exist, i am getting fired. what shall i do ??

#102 Bond

Hi,
Its very usefullll….. I need the flow of testing from unit to acceptance…

#103 Bond

Hi,
Its very usefullll….. I need the flow of testing from unit to acceptance testing…

#104 Tirumal

what is use case testing? & hoe to test?

#105 Ramya

ya excellant…….. i want srs document for exam registration form pls send my id.

#106 Ramya

this s my id ramyamelody19@gmail.com

#107 i need a srs document for exam registration

help me in writing a srs document for exam registration

#108 chinna

this is very helpful for all people… i need
in details of software requirement specifications and difference between the functional requirements and non functional requirements

#109 pankaj

i have software tasting course because i am great
programer .

#110 Rajesh

Hi

I have been working as a template(ms word) tester in a publishing comapny . can i move to software company with this experience

#111 venkatesh

what is mean by freeze

#112 sartaj

Can anybody tell any software for requirements testing.

#113 Mohammed

please update the latest contents…..

#114 test

test message

#115 kiran

According to me the requirments sholuld be given by businees analyst so that it’ll be very correct.
Because the persons who sits in the coding part or in testing side have no deal with the client, so better requirments will be given only by the peolple who r really having analyitcal skill who sits especiallly for collecting requirment

#116 sachin Policepatil

hi friends,
can anybody please clear my doubt?
well…,
what is main relation between the SRS,CRS,FRS,Which one is first?
and
please tell me how to get open software?
and
what is component test perspective?

as soon as possible please inform me friends,

thanQuu

#117 sachin Policepatil

i want to learn software testing….please give me small projects,
please….
please….
please….
my CV is noot good,so i have to learn any small projects,

thanQuu

#118 wuri

easy to understand article. help a lot. thank you

#119 Sagar Kumbhar

This is very good Article ,

#120 amit

wire frame document also consider as a Requirement document???

#121 rahul

chutiya sale bevkuf banata hai

#122 Amit Sharma

hi,

This is very helpful website to understand and clarify all concept of s/w testing. I realy learn lots of from here. so thank u so much to all.

Best Regard
Amit Sharma

#123 hp

Very much helpful article.

#124 Pearl Motsewapuo

you r of great help

can u help me here
suppose you ve been given logging in snippet code to collect and validate entered values, then connect to database, and you r 2 test dis. how many path are u going to have in CFG SNIPPET.

#125 manas dash

Hello guys
Actually i need a manual testing project for my reference if any one having a project please could you send me in my mail id “dashmanas254@gmail.com” thanks in advance

#126 Tina

Can someone help me how to get a software testing job? With over 10 years experience in manual testing but I can’t get a job and I don’t know which company is really hiring qa in Alpharetta, GA. Many thanks.

#127 neeraja

this information very useful.thankyou somuch to share with us.

#128 tanvi

hii i m taking a look on live project on orange hrm.but i didnt find srs document of it.can u please help me .
thanku

#129 pvss kamala ratnam

@sundar sharma
we can do testing according to the requirement specifications it is depends on the models like water fall model ,spiral model, V and V model ,agile model etc.. as a test engineers we all knows that agile model is very popular because its iterative and incremental model where the verification and validations will be very fast (developers,BA,costumer also will be part of in this model .. we can conduct daily stander meetings so work will will move very fast compare to other models ..

if we want to test the applications like web applications first we need to read the requirement ,understand requirement based on that we are going to test the product ..like functional ,integration ,system testing ……its depends on BA.

based on the requirement specification we should be able to test the application with create scenarios ..

thank u

#130 Lee

What is wrong with some people in here, my word. Excellent article, very informative. Thanks

#131 Chingu chop

thankie for not so bad article

#132 Hui Zhu

Goog article! Thanks for sharing.

#133 Ameer

hi Vijay ;
would you tell us more example in Testing in SRS ?
thanks

#134 Gaurav

Hi Sir,

In my company i am indulge in a project from scratch. I have SRS document, please let me know the process how to start to craete test scenario and test cases. It is product based company.

#135 tamara

Kindly quickly fetch and send me the template please.

REFERENCE FROM ABOVE:
Yes SRS is having some templates. I will make this SRS template available for our readers. This SRS is usually provided by stakeholders. So you can review it and can make your comments inline with the same doc. and submit it to test lead or manager. Which is expected to be reviewed/discussed in team by test/project manger.
dosan7@gmail.com

Thank you in spades, Sir.

Leave a Comment