The Latest
|
The Common Sense Approach to Gathering Requirements[article] The rapid development of applications nowadays does not always leave a project time to perform lengthy assessment of requirements and time to test; as in most cases, time is of the essence. Identifying a simple process for gathering and assessing Requirements makes the testing of applications easier and lessens the risk of delivering inadequately tested software. This paper provides the steps necessary to implement the process. |
||
|
Using "Backfiring" to Accurately Size Software[article] To make the transition between souce lines of code (SLOC) and function points (FP) easier, a method called "Backfiring" was developed to calculate function points by taking the SLOC count and multiplying it by a static factor based on the dominant software programming language. This article presents the basis for the two measures: Function Points and source lines of code, highlighting their differences and distinct advantages. |
Carol Dekkers
July 9, 2001 |
|
|
The Secrets of Highly Successful Measurement Programs[article] Can measurement be the system development savior of the 21st century, or is it a passing fad? The truth lies somewhere in between. The secrets of highly successful measurement programs extend well beyond the technical correctness of the chosen metrics and collecting of data. This article explores these secrets and identifies characteristics critical to measurement program success. The secrets of highly successful measurement programs extend well beyond the technical correctness of the chosen metrics and collecting of data. This article explores these secrets and identifies characteristics critical to measurement program success. |
||
|
Why Not Exploratory Testing?[article] Most of the Test Managers say, "Testing without test plans is a crime." The testers should know what is being built and should analyze the way to proceed. He/she will have to prepare the test plans based upon that to proceed with testing the application. Good knowledge of Exploratory Testing is necessary for reading this article. For those who don't have much idea about Exploratory Testing, a small intro is given here. |
||
|
Targeted Software Fault Insertion[article] This paper presents data on the effectiveness of software fault insertion, discusses the advantages and risks of fault insertion, provides tips on gaining cultural acceptance for fault insertion and suggests high payback areas for fault insertion which have proven themselves over multiple products. In a typical software development cycle, defect detection starts to trail off once the mainline code stabilizes. With software fault insertion, it was found that the defect detection rate does not level off and the hardest task becomes not one of finding defects but one of prioritizing the stream of defects. |
||
|
Standards for Test Automation[article] The Mocrosoft Windows team has transitioned from having no standards to having a strict set of guidelines to follow when writing new automated tests.
|
||
|
An Installation Saga[article] Have you ever run an installation program that wreaked more havoc than the installed application was worth? We often talk about user headaches from faulty software, but sometimes the pain begins with the installation process itself. Just for fun, here's a humorist's fictional account of a nightmare installation he (barely) endured. |
||
|
What You Don't Know May Help You[article] Some testers take it upon themselves to learn as much as possible about the inner workings of the system under test. This type of "gray box" testing is valuable, and most testers have the technical wherewithal to grasp much of what's going on behind the scenes. But it's important to recognize that sometimes "ignorance is strength" when it comes to finding problems that users will encounter. |
||
|
Software Metrics: Successes, Failures, and New Directions[article] The history of software metrics is almost as old as the history of software engineering. Yet, the extensive research and literature on the subject has had little impact on industrial practice. This is worrying given that the major rationale for using metrics is to improve the software engineering decision making process from a managerial and technical perspective. |
Norman Fenton
June 26, 2001 |
|
|
UML Extension for Business Modeling[article] This document defines the UML's extension mechanisms, namely Stereotypes, Tagged Values, and Constraints. |
||
 |
Agile Development[magazine] Technical Editor Brian Marick explains the values behind the Manifesto for Agile Software Development. Above all, Agile practitioners value: individuals and interactions; working software; customer collaboration; and responding to change. |
Brian Marick
June 26, 2001 |
|
The Butterfly Model for Test Development[article] There is a dichotomy between the development and testing of software, signified by the abundance of software development models and the dearth of test development models. Software testing's ephemeral nature aggravates the issue, as does the software developer's view of testing - represented only by a deadline, not a process. This paper presents a new model for software test development. The butterfly model is then correlated with the ubiquitous V development model to establish context. |
Steve Morton
June 21, 2001 |
|
|
Why Is Software Measurement Hard?[article] The presentation will explore and illustrate: the evidence of a problem establishing software measurement programs; the history of measurement, including the emergence and description of the Pantometric paradigm; the importance of different modeling Software Engineering Dynamics--systemic, empirical & metaphorical. Some techniques for modeling Software Engineering Dynamics. A new focus for software measurement. |
||
|
Earning Function Points in Software Projects[article] Measuring the progress of a software project requires a metric of the value the project creates. Progress implies a plan against which to measure. The concept of earned value provides a clear metric of project progress relative to a plan. For this purpose, the usual cost metrics for earned value are less interesting in a software project than other measures of value. In particular, function points provide a measure of value that earned value metrics can easily use to compare what you've created to what you plan to create. |
||
|
Across the Great Divide[article] Many bemoan the strained relationship between testers and developers. But while we can't force testers and developers to see eye to eye on everything, we can reduce some of the tension by making simple changes in the way we communicate. Learn some great tips and tricks in this article. |
Susan Joslyn
June 18, 2001 |
Pages
StickyMinds is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.