Tag Info

Hot answers tagged

4

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 consist of hardware and software. In some situations, it could even include humans performing well defined processes (for instance, changing deployed batteries). ...


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: ...


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.


3

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 ...


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 ...


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 ...



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