"Filling Gaps in Requirements," Software Testing & Quality Engineering, November 2000
	With a brief introduction to requirement patterns to quality control analysts, the article explains to the reader how they can spot gaps in the requirement set early and throughout the development cycle.
"Requirement Patterns: Capturing All the Requirements," QSSNewsBytes, June 2000
A brief introduction to requirement patterns to requirement engineers to illustrate the different type of requirements that need to be captured. The requirement pattern can be implemented in the QSS product, DOORs.
"Requirement Allocation," ICRE-2000 Conference Proceedings, June 2000
Developing quality requirements requires the right individuals to provide the information as well as the right individuals to elicit, analyze, specify, validate and manage the requirements. This article discusses the "allocation" process that is followed to delegate the responsibility to the right individuals
"Facilitating Communication," IEEE Software, October 1998
	Software teams are dynamic. They attract a concentration of work styles that may or may not conflict with the user community. This article introduces the reader to the different work styles and how to resolve communication conflicts. The approach discussed is based upon the Myers-Briggs Type Indicator (MBTI™) to team building
"Reengineering With The Right Types," Software Development, July 1994
	This article provided an overview of the Myers-Briggs Type Indicator (MBTI™). The objective was to educate the reader on how the different work styles affect the success of the project team. The article describes how all types are needed and add value to the successful implementation of a software project.