Learn and understand What software requirements specifications are, their importance, and How to Write a Software Requirements Specification (SRS) Doc:
Software development teams are often enamored by the technical implementation details and managers by process implementation/maturity. Unless the team pays particular attention to understanding what we are building, who it is for, in what steps to achieve a certain goal, etc.
Before we start building the software, the sophisticated technology and/or process cannot rescue the software from its inadequacies.
Table of Contents:
- Software Requirements Specification (SRS) Doc
- What is a Software Requirement
- Types of Software Requirements
- What is a Software Requirement Specification Document
- Who Writes Software Requirements Specifications Documents
- 5 Characteristics of Good Software Requirements Specifications
- How to Write a Software Requirements Specification Document
- Software Requirement Specification Examples
- Software Requirement Specifications Template
- Tips for an Effective Software Requirements Specification Document
- Software Requirements Specification/Management Tools
- Risks of Incomplete, Undefined, and Undocumented Requirements
- How to Measure Functional SRS Documents
- Conclusion
Software Requirements Specification (SRS) Doc
Example situation: One evening an employee of a company calls asking why her insurance policy could not include her adopted son.
After several emails and frenzied phone calls, the realization hit that when the requirement was created the only life changes that caused adding or removing family members to the employee’s insurance policy were marriage, birth, death, employment/unemployment, and minor dependents becoming majors.
Adoption as a life event causing insurance changes was overlooked as a requirement and, hence was not a feature of the insurance software. It’s not hard to imagine the employee’s reaction and the company’s frustration and feeling of inadequacy that followed.
If only, Software Requirement Specifications included this scenario, the fiasco could have been completely avoided.
What is a Software Requirement
A software requirement is a description of software behavior from a user’s perspective. It should be noted that the user may not always be the customer. Although most requirements are from a user’s point of view. Some are technical while others could be compliance-oriented (for banking and other government systems.)
Formally, Software Requirements are defined as follows by Ian Sommerville and Pete Sawyer in their book Requirements Engineering: A Good Practice Guide, “Requirements are a specification of what should be implemented.
They are descriptions of how the system should behave, or of a system property or attribute. They may be a constraint on the development process of the system.
Types of Software Requirements
There are 4 main types of software requirements:
- Functional
- Business
- User
- Non-Functional
The book “Software Requirements” by Karl Wieger defines these requirements and their relationships(image) as follows:
- Functional Requirement: A description of behavior that a system will exhibit under specific conditions.
- Business Requirement: A high-level business objective of the organization that builds a product or of a customer who procures it.
- User Requirement: A goal or task that specific classes of users must be able to perform with a system, or a desired product attribute.
- Non-Functional Requirement: A description of a property or characteristic that a system must exhibit or a constraint that it must respect.
What is a Software Requirement Specification Document
A Software Requirement Specifications(SRS) document is an important project artifact that describes all the requirements (Functional, business, user, and nonfunctional) in detail so that they are clearly defined for further development, review, acceptance, and revision(if need be) by all the stakeholders of the software project.
Most waterfall projects have a dedicated phase during the software development life cycle to gather, analyze, prioritize, and finalize requirements. Agile projects too have a requirement-gathering phase; since the scope of each sprint is short, all the requirements to be implemented in a sprint are gathered and analyzed during the planning phase.
=> Click here to see how requirement gathering is carried out in SDLC.
Who Writes Software Requirements Specifications Documents
Business Analysts document software requirements after they gather the system inputs from all the stakeholders involved including the customers/users. They are usually proficient with how to write requirements for the software.
The SRS document is an important input for software development, technical architecture design, Software testing, project management, training, user manual writing, etc.
For a quick glance at how the QA utilizes SRS to devise test cases, check these articles:
The level of detail depends on the:
- The complexity of the system
- Available time and resources
- Involvement of stakeholders
If need be, there can be several different types of requirement documents created.
=> Click here to see a comprehensive list.
5 Characteristics of Good Software Requirements Specifications
Many aspects go into good system requirements specifications documents. Some of them are:
#1) Requirements have to be correct: It goes without saying that if we do not have correct requirements, we are going to build an incorrect product.
#2) Requirements have to be complete: Incomplete requirements waste time, create functionality gaps, and cause grave customer dissatisfaction.
#3) Requirements have to be feasible: We cannot expect a car to fly(as of 2023) so a requirement has to be assessed for feasibility irrespective of its originating source.
#4) Requirements have to be unambiguous: Clearer requirements mean clean objectives and a smooth sail when it comes to further development and design steps. Avoid and/or such as: enable search by name and/or DOB.
#5) Requirements have to be necessary: We can be ambitious but the software has to do things that are absolutely essential for the user and the business.
How to Write a Software Requirements Specification Document
When writing software requirements specifications a keen focus on business, end users, and the technical implementation has to be kept in mind. Firstly, a series of interviews and Q&A sessions are held with all the stakeholders involved to understand the current state of the business and the expectations from the final software product.
Based on the outcome of this step, the requirements undergo further analysis. Secondly, the requirements are assessed to understand accuracy, feasibility, and priority among other things. Finally, the requirements undergo a review process with the stakeholders to ensure that all the stakeholders are on the same page.
The review can be a casual walkthrough or a more formal step-by-step evaluation. The outcome of this review can be that some requirements might be:
- Ranked so that the team can decide what areas to focus the team’s energies on
- Eliminated because they are not accepted as necessary, collectively
- “How-to” steps for different features might need to be changed and finalized
- Finalized requirements are approved for further stages
- For tougher requirements, a minimal POC might be decided to be carried out and validated
Most projects and teams may not go to this level of detail but all of the teams undergo this process in some capacity.
Their lifecycle might look something like this:
[image source]
A generic template for a requirement written from the system’s perspective is (Mavin et al. 2009):
[optional user] [optional precondition] [optional trigger event] the system shall [expected system response].
Software Requirement Specification Examples
The following are some samples of software requirement specifications. These are examples of what goes into section 3.X of the template provided in the next section:
- The system must permit search by a Purchase order number, bill number, and customer order number.
- If the Buyer’s payment card on file has expired, the system shall allow the customer to either update the current credit card information or enter a new credit card for payment.
- When a manager logs into the leave approval system, they shall see the leave requests submitted by their reporters on the home page dashboard.
Software Requirement Specifications Template
A comprehensive SRS document contains the following sections. Depending on the context, sections could be added or removed but generally speaking, this is the outline followed by most software teams.
#1) Introduction
1.1 Purpose
1.2 Document conventions
1.3 Project scope – short description of the software being specified and its purpose.
1.4 References
Introduction section usually sets the context for the software project and/or the SRS document. The purpose of the document, the level of detail, the short forms and abbreviations that are going to be used, the outline, etc. are defined.
The project scope outlines what the project is about, who is going to use it, what problem it is going to solve, what is not in scope, the risks involved, etc.
#2) Overall description- a high-level overview of the product
2.1 Product Description and Goals
2.2 User Classes and Characteristics
2.3 Operating Environment: Describe the environment in which the system will operate
2.4 Design and Implementation Constraints: Programming language, cloud architecture to be used, etc.
2.5 Assumptions and Dependencies
This section goes into greater detail about the project features and its goals. At this stage, detailed goals are formulated. At this point, the requirements are from a business perspective. For example, it can list a requirement/goal as “the system shall provide controlled and secure access to all its users.” It does not go into system-level details.
For example, it does not talk about whether the secure access is going to be implemented using a simple login or multi-factor authentication or in some other way.
Also, the user level and the user-facing functionality and its elaboration using use cases are carried out in this step. For a quick look at what a use case might look like.
Please note this image is a screen capture from the very well-written SRS example document.
Some of the design and implementation details are also documented in this stage. Also important is to list out the assumptions and constraints so there is no ambiguity.
#3) System Features
3.x System feature X Name of the feature
3.x.1 Description
3.x.2 Functional requirements
We have already seen examples of how system features are documented in the section: Software Requirement Specification Examples:
#4) Data Requirements
4.1 Logical data model
4.2 Data dictionary
4.3 Reports
4.4 Data Acquisition, Integrity, Retention, and Disposal
The most important outcome of this step is designing the data. Consider an example feature, ‘The system shall provide a registration option for new users.’ This step will decide what data should be used using registration.
| Data Field | Data Type | Mandatory/Optional |
|---|---|---|
| First Name | String | Mandatory |
| Last Name | String | Mandatory |
| DOB | Date | Mandatory |
| Interests | Free text | Optional |
| Sign up for updates | Checkbox | Yes/No- Yes by default |
This is a super small scale and only gives you an idea, but this step takes considerable thought and effort.
#5) External Interface Requirements
5.1 User interfaces
5.2 Software interfaces
5.3 Hardware interfaces :
5.4 Communications interfaces
Look and feel, fonts to use, language, etc. are outlined in this section. Wireframes can be used to mock future pages. Sometimes a separate document outlining the colors, themes, and formats to be used is maintained depending on the need.
Other features such as interactions with other software systems, software components, tools, operations systems, etc. Interaction with hardware devices such as POS systems, barcode scanners, etc., and communication functions the product will use, including email, web browser, network protocols, and electronic forms are all listed and explained in this section.
#6) Quality Attributes: Record Nonfunctional Requirements
6.1 Usability Requirements
6.2 Performance Requirements
6.3 Security Requirements
6.4 Safety Requirements
6.5 Internationalisation and localization requirements
6.x [Others]
While there is no standard format or template for non-functional requirements, they can either be expressed as use cases in section 2 or system requirements listed in section 3.
- Performance requirements can look like this, “The system shall support up to 500 internal users at a given time while maintaining a 10-second response time to retrieve an artefact.”
- For example Usability requirements, the website will be both mobile and desktop compatible.
- Security requirements might look like this, “The system shall restrict registration with phone numbers without the United States country code.”
#7) [Other requirements]: Other requirements that are not covered elsewhere in the SRS. Examples are legal, regulatory, or financial compliance and standards requirements; etc.
To reiterate, a very well-written SRS example is here: https://www.cse.msu.edu/~cse435/Handouts/SRSExample-webapp.doc
Now that we know what software requirements are, how they are collected, the requirements lifecycle, and how to write a software requirements specification document, let’s look at some tips that can make your SRS document stand out.
Tips for an Effective Software Requirements Specification Document
- Don’t duplicate information.
- Use images when outlining complex business/user cases- flowcharts, use cases, context diagrams, mind maps, etc.
- Provide secure access to the document- read-only access vs. edit access.
- Use proper version control to track review and change history.
- Provide a glossary for abbreviations and other technical terminology used.
- For Agile projects or if you also use a requirement management tool such as JIRA, Micro Focus ALM, etc. provide hyperlinks to work items created.
Software Requirements Specification/Management Tools
Smaller scale teams might use MS Excel sheets, Google Sheets, or SmartSheet applications. However, with larger projects/teams they may need dedicated requirements management software. A simple spreadsheet used for requirements management can look like this:
Here are the three requirement management tools:
#1) Micro Focus ALM: One of the most prominent of the licensed enterprise requirements and test management tools out there. It has several important features like requirement definition, assignment, status tracking, and traceability features.
#2) JIRA: Atlassian JIRA is almost always part of most Agile teams and plays an important role in keeping all requirements/stories in a centralized place. Scrum/Kanban boards show an accurate status depiction, whereas integration with GitHub and Bitbucket lets you see the ensuing code changes/commits that originated from the requirement.
#3) Jama Software: Rated as the top ALM tool in 2019, Jama is a notable name in the world of requirements management. Support for requirement traceability with tests and risks is Jama’s key strength and is highly valued by many businesses and teams.
Other popular tools are:
- Visure
- SpiraTeam by Inflectra
- ReqSuite® RM
- Xebrio
- Process Street
- Visual Trace Spec
- IBM Rational DOORS
- Accompa
- Case Complete
- Katalon TestOps
=> Click here for more information on the most commonly used requirement management tools, their key features, and quick comparison.
Risks of Incomplete, Undefined, and Undocumented Requirements
The example in the introduction is just a needle in a haystack. Not taking time to properly gather, clearly define and document requirements is a recipe for disaster.
Cutting corners during the requirements gathering phase might seem like you are saving time and avoiding deeper effort, but the risks can be:
- Bugs later in the development process.
- All implementations are open for interpretation- developers will build the system based on their understanding, testers will create test cases based on their deciphering, etc.
- If working with implementation partners the agreement on terms of delivery and acceptance criteria becomes ambiguous.
- Schedule risks are huge too because UAT/Acceptance validation might fail due to the final product not behaving as expected.
- Team morale and working towards a common goal is jeopardized because each team in the SDLC has a different idea about what the ultimate goal is.
How to Measure Functional 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. The 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 the stakeholders: How much response time is ok for you? If they say that they 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 the next requirement too.
We just learned how to measure the requirements and freeze those in the Design, Implementation, and Testing phases.
Now let’s take another example: I was working on a Web-Based project. The client (stakeholders) specified the project requirements during the initial phase of the project development. My manager circulated all the requirements to the team for review. When we started the discussion on these requirements, we were just shocked!
Everyone had his or her own conception of the requirements. We found a lot of ambiguities in the “terms” specified in the requirement documents, which later on were sent to the client for review/clarification.
The client used many ambiguous terms, which had many different meanings, thereby making it difficult for us to analyze the exact meaning. The next version of the requirement doc from the client was clear enough to freeze for the design phase.
From this example, we learned that the “Requirements should be clear and consistent”
The next criterion for testing the requirements specification is to “Discover missing requirements”, let’s take a look at it.
Discover Missing Requirements
Many times the project designers don’t get a clear idea about each specific module and they simply assume some requirements in the design phase. None of the requirements should be based on assumptions. Requirements should be complete, covering each and every aspect of the system under development.
Specifications should state both the types of requirements i.e., what the system should do and what it should not.
Generally, I use my own method to uncover 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 that the SRS document is supposed to cover.
This will help ask questions about the unspecified requirements thereby making it clearer.
To check the completeness of the requirements, divide the requirements into three sections: ‘Must implement’ requirements, requirements that are not specified but are ‘assumed’ and the third type is ‘imagination’ type of requirements. Check if all types of requirements are addressed before the software design phase.
Check if the Requirements are related to the Project goal
Sometimes stakeholders have their own expertise, which they expect to come into the system under development. They don’t even think about whether that requirement would be relevant to the project at hand. Make sure to identify such requirements.
Try avoiding all irrelevant requirements during the first phase of the project development cycle.
If not possible, then ask questions to stakeholders like why do you want to implement this specific requirement? This will describe that particular requirement in detail, thereby making it easier to design the system considering the future scope.
But how to decide whether the requirements are relevant or not?
The answer is simple. Set the project goal and ask this question: If not implementing this requirement will cause any problems in achieving our specified goal? If not, then this is an irrelevant requirement. Ask the stakeholders if they really want to implement these types of requirements.
In short, the Requirements Specification (SRS) doc should address the following:
- Project functionality (what should be done and what should not be done).
- Software & Hardware interfaces and the user interface.
- System Correctness, Security, and performance criteria.
- Implementation issues (risks) if any.
Conclusion
We hope this article provides you with an overall overview of what software requirements specifications are, their importance, and how to write good software requirements specifications documents.
“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 during the requirement phase to avoid further requirement-related bugs. Communicate more and more with your stakeholders to clarify all the requirements before starting the project design and implementation.
This article borrows a lot of its ideas and concepts from these two books. Please read them if you would like to deepen your knowledge.
- “Software Requirements” by Karl Wieger
- “Requirements Engineering: A Good Practice Guide” by Ian Sommerville and Pete Sawyer
Finally, if you have any questions, feedback, and comments, please share them below with us.
Hi Guys
I am sushil chauhan and i am pursuing BCA(final year). Please give me good advice for finding a Job.
It is a nice write-up. SRS and other specifications like Functional specification and Program specification are necessary for testers.
bahu saras che………..
Thanks mate! This article is really useful and has been very informative… Keep up the good work!
This site is very helpfull. I want test plans on various sceanarios on excel sheet. Plz send this.
Hi all,
what are the phases to identify any SRS? how to analyze any SRS in an efficient method?
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
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
if explain with examples is good for learners
hi
please explain me what is BRS and SRS and diff btween tem
Amit, please specify your requirement clearly so i can help you as much as possible
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………………
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 ??
Hi Guys i Here By enclose My Personal Number – 9030258656 just get in touch and lets create a whatsapp group and explore more.
this information very useful.thankyou somuch to share with us.
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.
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.
@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..
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.
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.
what is use case testing? & hoe to test?
a good article .nice to understand and a clear view of how to test the software requirements.
0
wire frame document also consider as a Requirement document???
please update the latest contents…..
What a good article is this.Really good
This seems like a good blog for the 90ties, but I hope that fast iterative development cycles have beat the crap out of this traditional Waterfall requirements design staging that you describe.
Do you have proof for this “Most bugs” claim? Also the costs of fixing defects has become very low due to high automated test coverage. Really not sure in what age you are living 😉
I wrote a full response here: https://sqa.stackexchange.com/a/31127/3201
chutiya sale bevkuf banata hai
very nice & easy to understand article
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
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?
@ Sundar Sharma Machiraju
What do you say about Usability testing?
There are many, share your thoughts…
Regards,
Suhas M.
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
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.
What is the yellow box testing & the gray box testing in the Software Testing. And what is the defference between them.
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
please send me of srs for project tailoring ( this is my project defination)general developing are incuding.
bye.
hi
please explain me what is BRS and SRS
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.
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.
I REQUIRED SRS FOR DEFECT TRACKING SYSTEM IN DETAILS FORMAT
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
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.
I required SRS FOR bug tracking in database
Excellent Article………
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?
we’ll get the requirement document. As a QA team we’ll review and asks for clarifications and doubts if we have to our stakeholders.
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.
this s my id ramyamelody19@gmail.com
i have software tasting course because i am great
programer .
How to start with QTP automation testing for the websites application
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
How many test cases we can write in a day in a company.
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
ya a very good article. i got cleared abt software testing
I need the flow of testing from functional to acceptance testing.
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
Hello,
Your tutorials are very good.
Your tutorials covers all software testing aspects.
Harshal Ghisad
please send me the processes and templates for testing
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.
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
test message
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.
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.
d
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
i want to learn about
how to go about the software testing ?
what is mean by freeze
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
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
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
SRS for defect tracking??? wt this mean.
u asking the document related to Defect tracking??
Hey i m the student of software testing. so i want some more &more knowledge of this filed . so please sending me this
Goog article! Thanks for sharing.
thankie for not so bad article
.
NO NEED OF SRS IF U ARE GENIUS
@ 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.
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 ….
Hi,I also want to know about the design of Test Matrix
Vry Nice Article
Hi…..
i also have same question which posted by shantanu. we just study the module and start testing manually.
is this a bad practice?
Very much helpful article.
Hi Vijay
Can you please define good requirement & bad requirement?
test test test
Please do not define bottom-up and top down approach
I need template.
Hi all,
what are the phases to identify all the requirements of any SRS
Briefly describe the SRS…… I wanna know more about the SRS…….
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.
This is very good Article ,
Very informative article
Hi,
Its very usefullll….. I need the flow of testing from unit to acceptance…
Can anybody tell any software for requirements testing.
easy to understand article. help a lot. thank you
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
very interesting, but i wish the Admin would have their blogs proof read by somebody who’s first language was English. i keep getting caught up reading due to missing “a” or “the” that should be placed in a lot of sentences,…don’t get me wrong, its 98% perfect, but it does catch me and slow my reading down when i spot these simple mistakes.
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
What is the Big Bang Model in the Software Testing. Plz me the all concepts of this model of SDLC.
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
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.
o
Hi suresh,
Do you have any idea about certification in testing. i have read about international certification in software testing.
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?
Hi,
Its very usefullll….. I need the flow of testing from unit to acceptance testing…
Can some send me few sample test cases
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,
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….
@swetha
pls explain ur question very clearly ..i will hepl u,,
Thanx a lot vijay……
Hi ,
I need winrunner free Trial version ,can any one tell me the link to get the trial version.Its very urgent please reply.
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.
Hello members
Kindly send template for Integration Test case
kishoresharma1@gmail.com
we simply quote unit test caseid or something more
Please specify
Thanks
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?
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
How to create the good test scenario as per SRS in testing?
@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
Hi
I wanted to know do we perform functionality, integration,and system testing all in a same release or in 3 different releases… How much it may usually take to perform each kind of testing.
hi….
This sight is really good , I requested you that please send me the bug report in excel sheet format.
Hello guys,
I need some help. I am working on cross project bug prediction. So I want to know what are the elements which I can compare in two projects which are from different domains. Which elements create defects in systems, which elements do I have to use to create model?
Thanks in Advance
g
ya excellant…….. i want srs document for exam registration form pls send my id.
@Vishal
here u go..
ISTQB add ons ur resume and boost u..secret of ur energy towards testing..gud lck..
@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.
great article………
What is wrong with some people in here, my word. Excellent article, very informative. Thanks
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…
Hey,
The article is good but I would like to know more about Testing in SRS so Can you please share this type of article with a deep explanation…
Thanks in advance
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?
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
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.
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…
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……..
wanna know the flow of software testing process in a corporate….?
hi Vijay ;
would you tell us more example in Testing in SRS ?
thanks
Hi all,
what are the phases to identify all the requirements of any SRS? How to analyze all phases without any ambiguity.
help me in writing a srs document for exam registration
srs review helpful to find bug in early as poosible
by ks thangavel
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
yes,i do want to know the testing process.. please provide me the details
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
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
hi this is dinesh
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.
In our company they provide us SRS but we didn’t write any test cases for site. Our TL is told to us work without test caes..
Is it bad impact ?
or should i start the write the test caes for project.
but even we haven’t enough time for testing.
what should i do ?
I have no idea of software testing I’m trying to enter the QA teams because I found no value with BPO’s being an engineer. So I wish I could take the necessary steps to become a software engineer and I found manual testing would be the right choice. Let me know the needful, thank you.
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.
Hi
I have been working as a template(ms word) tester in a publishing comapny . can i move to software company with this experience