Review techniques in software engineering
The book makes a distinction between error — a problem found before being released to the end user and defect or fault. However, in the real world, this distinction is not always made. Problems that are passed through can hide other bugs, or cause non-issues to appear to be an issue. Technical reviews are one of many actions that are required as part of good software engineering practice.
However, since there are only so many hours, you need to know what types of reviews are going to provide the best results. Reviews can fall under the informal, or casual, to a more formal and rigorous methodology. The more serious the situation and responsibility of the software, the more rigorous and detailed a review needs to be.
Consider a simple mobile game, like one of the millions where pop a collection of balloons to get a score. Little mistakes can have costly repercussions, so you need to test and verify every little step. Like Article.
Last Updated : 10 Jan, Recommended Articles. Article Contributed By :. Easy Normal Medium Hard Expert. Writing code in comment? Please use ide. Load Comments. What's New. Most popular in Software Engineering. More related articles in Software Engineering. We use cookies to ensure you have the best browsing experience on our website.
Start Your Coding Journey Now! Login Register.
0コメント