Skip to main content

David Gelperin

Profile picture for user ClearSpecs

Member for

8 years

David Gelperin is chief technology officer of ClearSpecs Enterprises. He has more than forty years of experience in software engineering with an emphasis on requirements risk management as well as software quality, verification, and test. David cofounded Software Quality Engineering. More information is available at www.clearspecs.com.

Company
ClearSpecs Enterprises
Job Function
Consulting
Job Title
CTO
Industry
Many
Interests
Agile
Business Analysis
Development Lifecycles
Process Improvement
Project Management
Quality Assurance
Requirements
Testing
Country
United States

David Gelperin is chief technology officer of ClearSpecs Enterprises. He has more than forty years of experience in software engineering with an emphasis on requirements risk management as well as software quality, verification, and test. David cofounded Software Quality Engineering. More information is available at www.clearspecs.com.

All Articles by David Gelperin


All Stories by David Gelperin

Improve Requirements Understanding by Playing Cooperative Games

Serious games are games whose primary purpose is not entertainment. Cooperative games structure communication (e.g. contract bridge) and cooperation (e.g. soccer) between players in the same group. Using serious, cooperative games improves Requirements Understanding (RU).  This paper defines six RU games, maps them into ‘initial understanding space’, and shows how to use a special Ouija board to choose the games to play on your project.  An example of RU game selection is included.

Developing a Requirements TeamForming, Storming, Norming, and Performing. No, they are not a law firm, but the stages of team development proposed by Bruce Tuckman in 1965. I wish I had known about this model much earlier in my career. If you haven't encountered it before and want to help your requirements team, read on.
Testing Complex Logic

Choosing effective tests for complex logical expressions can be difficult. This paper describes a black box strategy for choosing such tests. The strategy is shown to be a natural generalization of current methods for choosing tests for simpler expressions. The strategy chooses combinations that are not only effective at revealing implementation defects but, perhaps more important, are effective at helping detect defects in the requirements themselves.

In addition, if there are dependencies between variables in the required logic, a variant of the strategy excludes those truth-value combinations that are "impossible" because of the dependencies. It extends the required expression to include dependency information and then derives tests from this extension. This strategy is the only test selection method that smoothly incorporates dependency information. It also permits the dependency information itself to be partially validated through analysis of the "impossible" cases deve

An Ideal Architecture for Model-based Verification & Test Systems

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.