|
 |
Home > Articles & Papers > Articles and Papers
 |
Viewing 1-10 of 2247 Collapse Descriptions
Sort by: Date Posted | Title
 Blue Diamond Delivery Model (BDDM)
Author(s): Manoj Kumar Varatharajan
Summary: Blue Diamond Delivery Model (BDDM) is an easier delivery-tracking model, which helps to track the delivery for every day and gives some valuable remarks over the certitude of the deliverables. The Diamond Model is fragmented into the number of workdays per month and the deliverables are eventually distributed across these workdays prior to the Project Plan. Everyday results should be tracked with respect to the time period by naming as Best Period, Grace Period, Warning Period & Failure Period and shade them as Blue, Green, Red and Black respectively (as per the delivery time). The Reasons behind the timely and untimely deliverables are noted and maintained in the history.
Date Posted: Jul 14, 2008 |
Real-World Math
Author(s): Danny R. Faught
Summary: Math is often not easy to learn, even for those of us who enjoy it. And if you don't use your mathematical knowledge, you just might forget how to use it. Danny Faught likes math and has found ways of using basic math like algebra, the modulo function, expected values, and logarithms in testing. It's kept his mind fresh on mathematical concepts and formulas, and he hopes it will do the same for you. In this week's column, he explains how to use math to improve testing.
Does Exploratory Testing Have A Place On Agile Teams?
Author(s): Johanna Rothman
Summary: Exploratory testing--questioning and learning about the product as you design and execute tests rather than slavishly following predefined scripts--makes sense for many projects. But does it make sense for agile projects? In this week's column, Johanna Rothman examines how exploratory testing might work on an agile project.
Data Object Pattern in Complex Business Objects Testing
Author(s): Dmitri Korolkov
Summary: In automated customer testing, scripts can operate with system under test (SUT) objects indirectly, via some interfaces: graphical user interface (GUI), application programming interface (API), command-line, etc. Business objects may contain a number of data fields. If many of these fields are supposed to be used in some data or behavior verification, the problem of business data storing can appear. This article describes general approach for complex business objects testing.
Date Posted: Jul 3, 2008 |
Write Now
Author(s): Naomi Karten
Summary: Software professionals excel at writing code, test plans, and other types of technically oriented documents. However, many of them struggle when it comes to writing of a non-technical nature. This is unfortunate because the ability to communicate fluently in writing helps to build a reputation as a valued contributor and an expert in your field. In this week’s column, Naomi Karten offers tips for strengthening your ability to write articulately and compellingly.
Programming with GUTs
Author(s): Kevlin Henney
Summary: Since tests are commonly viewed in terms of offering quantitative feedback on the presence or absence of defects in specific situations, Good Unit Tests need both to illustrate and define the behavioral contract of the unit in question. Do you have GUTs?
Date Posted: Jun 24, 2008 |
Two Cheers for Ambiguity
Author(s): Michael Bolton
Summary: Some people dismiss words such as skill, diversity, problems, and mission as being too ambiguous to be useful. But one tester's ambiguity is another tester's gauge for assessing consensus on a project and how to achieve that consensus.
Date Posted: Jun 24, 2008 |
Going on a Picnic with James Watt
Author(s): Clarke Ching
Summary: What if you had a picnic and no one brought potato salad? Find out what picnic planning and steam engines have to do with project success and not just satisfying your customers but delighting them.
Code Ownership Revisited
Author(s): Jurgen Appelo
Summary: Among well-known methodologies for software development one can recognize two philosophies regarding the assignment of responsibilities to team members for the code that they produce: collective code ownership and individual code ownership. In this article, Jurgen explains that there are not two but four ways of assigning responsibilities among team members. He also claim that the choice for either of these models should be made not by methodologies but by project managers, architects or team leaders. Jurgen also presents a number of criteria which might be helpful while selecting the best model.
Date Posted: Jun 20, 2008 |
May I Take Your Temperature?
Author(s): Linda Hayes
Summary: This week's column isn't for you; it's about you. Linda Hayes wants to find out what it takes to be successful in the testing profession these days--if such a thing is really possible. Too many good ideas, such as incentive and recognition plans, have backfired. Linda feels there are a few good practices out there, but she needs your help to find them.
|
|
|
|
 | Census: Web-based Bug Tracking and Defect Tracking
Track software bugs, defects, enhancements, support calls, and more. Issue tracking software that is scaleable, fully customizable and integrated with VSS. Includes e-mail notifications, role-based workflow, change history, and Crystal reporting.
| | New Webcast: How to Profit with Remote Support.
Discover how REMOTE SUPPORT can fuel your IT business in ways you've never thought of before.
| | The Very Best in Pairwise Test
Testcover.com - Compare our test case efficiency, response time, and ease of use. Simply the best!
| | Villanova University Six Sigma & IT Certificate Programs
100% Online programs in Six Sigma, IS Security, CISSP Prep, Business Analysis, Proj. Mgmt. and more!
| | Build IT Knowledge with Current & Trusted Content
Helps Employees Develop & Hone New Technical Programming Skills. Sign Up & Get Full Access.
|
| | Get your product or service listed here.
| |
|
|
|
|
|
