The correlation between project size and project failure is well known in the software industry. Despite this well documented danger, companies continue to sponsor huge projects. It's unlikely we will talk executives out of their dreams of huge projects, but we can talk with them about ways to manage the inherent risks. Often a short story is worth a thousand words. The "Hudson's Bay Start" is one of these stories and a great risk reduction technique.
An important component of any security system, its multi-layered access and encryption permissions provides a powerful combination, when configured properly. However, time and time again I find myself in front of a Windows 2000 Server, where a failed permissions configuration succeeded in creating a tangled mesh, denying access to everyone. At this point, without a documented roadmap, it becomes difficult to unravel the conflicts, but I hope to shed some light on what to do and avoid form personal experience.
Errors in requirements specifications translate into poor designs, code that does the wrong thing, and unhappy customers. Requirements documentation should be inspected early and often. Anything you can do to prevent requirements errors from propagating downstream will save you time and money. Karl Wiegers shows you how.
This article aims at establishing a test strategy because the development of a test strategy is a means of communication with the customer on the organization of testing. Moreover this article talks about why we need a test strategy and what happens if there are no test strategies. Finally, a test strategy will keep the customers aware of the extent to which the testing would be done thereby avoiding risks later.
Imagine a tool that generates functional and usage tests from UML-based models. What are the features of an "ideal" tool with this capability? This paper characterizes the components of such a tool. It describes the requirements notation and specifier module, the model checker, the automatic test designer, and the automatic scripter. It also provides practical references for each of these components. The paper's objective is to catalyze reflection, debate, and development of such tools.
Exploratory tests, unlike scripted tests, are not defined in advance or carried out precisely according to a plan. So where and how do they fit with the other tasks testers must perform? James Bach, a chief proponent of exploratory testing, provides some insight on how best to exercise exploration in your testing effort.
Risk-based testing is reviewed and presented as a case study using it on a system test for a retail banking application with complex test requirements. Test documentation produced prior to test execution was kept to a minimum with responsibility passed to the individual tester. To support this approach, progress tracking metrics were used to track actual progress made and to calculate the resources required to complete the test activities.
This article gives an overview of testing teams, including the common issues they encounter. It also discusses changes that can be implemented to have an effective and efficient testing team.
When it comes to measurement, the IT industry acts strangely. Even when it recognizes the merits of software measurement, the expectations for it are often unrealistic. Software practitioners want a silver-bullet metric that can answer any development question and do it to several-decimal-point accuracy. This article addresses the mistaken notion of measurement or a particular metric being a silver bullet - a notion that left untapped can impede your organization from ever getting started with measurement.
This article is aimed at providing team-based development for a small organization. It provides a solution to effectively utilize the resources present in small organizations and suggestions to overcome the shortcomings in terms of sophistication of tools and processes. It explains how small organizations can come up with a better and more efficient configuration management system by taking advantage of the current situations and resources. This article also explains how by effective communication and simple process definitions and implementations the magic term 'managed and controlled' can be achieved. This is a more simplistic approach towards Software Configuration Management.