Program

Match 1: Methods for specification- do they meet the requirements?

Cass et al.
Describes the usage of a SE principle and notation (a process programming language) to support a typical UE problem (selective undo)

vs.

Brown et al.
An approach is presented that supports elicitation and specification of interactive systems. Elicitation is supported by a checklist derived from elements of the Activity Theory. Specification is supported by proposing a specification structure, reportedly to be derived from AT.

Match 2: Can pattern get rid of experts?

Schmettow
A method is presented, that enables a non-expert to correctly identify, evaluate and apply usability knowledge within a SE process. Method can be evaluative as well as constructive.

vs.

Vossen
Derived from systems theory, the influence from user/usage on the systems quality is discussed. Further the difference between functionally correct but still bad systems is discussed. It is mentioned that specific skills and knowledge is needed, to find mismatches and to understand that they are different from defects. Bridging the gap by integrating experts into an organization.

Match 3: What is most needed? Full-Automation or Developer-Assistance?

Forbrig et al.
Describe roughly two basic concepts. First a model-based development approach that claims to support transitions between models via patterns, second the application of these models in order to perform remote usability tests. Topics are models, notations, tools, methods and common artifacts.

vs.

Ye
The author discusses the need for information and knowledge, as well as communication and cooperation during software development. Two tools are presented that claim to support these needs more than traditional CASE tools.

Match 4: Principles; Requirements for tools and methods

Wassermann
A very good argumentation, that underlying principles from different disciplines have become a science. The reader is eager to get to know these principles, but is disappointed by the results: abstraction, modularity and architecture sure are basics of SE but far away from a joint set of principles for interactive systems. Principles are a good point though.

vs.

Schmidt et al.
The results of a survey are presented, in which typical SME's are described and the factors for acceptance, or non-acceptance of UE-methods are analyzed. The result is a requirement catalogue for UE-methods in order to be easily able to integrate into SE-processes of SME's.

Summary: How to Publish

electronic, special issue, or edited book?