One of the most common misconceptions about software testing is that, once a program or software system has gone through testing, it is free of bugs. If you accept this assumption, it logically follows that, if any bugs are found by the end user, the software was not properly tested. Both of these statements are [...]
In the field of software engineering, you are never done learning. That should probably be one of the first ten rules of the profession. Software engineering is still a young discipline. We can contrast it with something like bridge building, for example. Humans have been building bridges for thousands of years, and they pretty much [...]
The biggest strength that traditional requirements gathering techniques have is their structure. When using these methods, the Requirements Engineer (RE) is applying a formula, pure and simple. There are outlines to follow and forms to fill out, which makes the job of RE more accessible to a larger group of people. Agile requirements gathering techniques [...]
On May 12, 2010, Valve made its Steam platform available on the Mac. There are a few key points of the way Valve chose to do this that show design decisions which support the needs and desires of the customer base. All too often, software companies do things the way that is easiest for them, [...]
A software system's "tested" status is an interesting thing. Sometimes, in a schedule crunch, the decision makers may decide to cut back on testing, hitting only the most commonly used portions of the system. Almost inevitably, when this is done, a bug in one of the less commonly used parts of the system gets out. [...]
