Hot answers tagged

6

Requirement Traceability matrix maps the user requirements with the test cases. In simple words, the matrix helps in determining if all the requirements have been covered(i.e there are test cases which can be traced back to the requirements). There are 3 types of RTM: 1. Forward:Requirements->Test Cases 2. Backward: Test Cases->Requirements 3. ...


6

System requirements are the translations of user requirements in a much more technical language. They are basically the things that a software must perform. Not exactly. The system usually consists of hardware and software. In some situations, it could even include humans performing well defined processes (for instance, changing depleted batteries). The ...


4

In my opinion, there is incorrect use of terms: User's requirements in plain language should be called user's stories or etc. Requirements for the hardware are often called system requirements. Functional requirements cover what your Application need to do and in which way (i.e. its functions) P.S. Also, you can read about requirements from the wiki: ...


4

What you need is to improve your Requirements Engineering processes. There are commercial tools that help in this area (I have worked with Doors some years ago), but I don't know of any open-source alternative I could recommend. The problem is that these tools and processes are very "heavy weight", and in my opinion, achieving requirements traceability ...


3

Some points would include, Battery back time. Screen resolution. Its weight. Its dimensions. What accessories come along with it. ... And you can keep on going with your list of expectations.


2

"we keep forgetting to handle all the numerous features which were implemented in last few years" If things are being forgotten on a regular basis, this isn't a tool problem - it's a process problem. Your process seemingly doesn't require that these things are tracked in an accessible place, and that the feature list be kept up-to-date. We use ...


2

Welcome to SQA, Little. Without seeing the context, it is hard to know exactly what the document means by "System Environment". Generally, it means everything the system interacts with. For a program running on a single computer, the system environment might include any other programs running on the computer, the operating system, all the computer's ...


2

I think UX is often miss-interpreted as design. Design is often an acquainted taste and therefor it is pretty much untestable, but usability testing is something different. It is important that user can use the product with only minimal training, but more important it should feel logical and non repetitive within the users mental model. During evaluation ...


2

Bidirectional traceability is the ability to trace both forward and backward (i.e., from requirements to end products and from end product back to requirements). It means tracing the code from requirements and vice-versa throughout a Software Development Life Cycle (SDLC). When you are in the course of your project, your fundamental aim would be to ensure ...


1

To be precise and very specific there are no certain guidelines and benchmark defined for the web application related to their Performance. This is a thing which comes to mind of every QA, but unfortunately there are no worldwide or Organization wise accepted standards for the Response Time. It depends upon a number of factor including (but not limited to) ...


1

One way to help keep track of the commits attached to the JIRA is to include the Jira associated with the fix in the commit comment. By doing so, it will link the commit to the Jira and you will be able to see all of the code/tests that were committed to a given Jira.


1

For me, the baseline is always a comparison to some other system. The other system need not be software. It might be implemented by, say, people wielding pencils and paper forms. If that exists, you can measure its response time, availability, reliability, error rate, and so on. The other system need not exist. I can always posit an imaginary ...


1

There are plenty of ways to keep track of the requirements.The very important thing to be considered is to keep track of requirements and changes from the Inception of thoughts/Requirement analysis, without which it might become a costly affair. Requirement Analysis Aiding Tools- An Excel sheet could sometimes be the simplest way to keep track of ...


1

I approach that problem by maintaining written test cases in a wiki. Each test case is a declarative statement. (I have worked places where test cases were documented in step-by-step detail, but I found it was too hard to maintain the details when features changed, as they often did.) If you search SQA or Google, you will find other structures for written ...


1

The definition of ‘functional requirement’ is that it essentially specifies something the system should do. The definition for a non-functional requirement is that it essentially specifies how the system should behave and that it is a constraint upon the systems behaviour. One could also think of non-functional requirements as quality attributes for of a ...



Only top voted, non community-wiki answers of a minimum length are eligible