scispace - formally typeset
Journal ArticleDOI

Early Lifecycle Work: Influence of Individual Characteristics,Methodological Constraints, and Interface Constraints

TLDR
It is concluded that studies comparing extreme programming approaches with conventional CASE tool approaches are needed to help determine if the struggle to understand the constraint environment at a high level of abstraction is worthwhile or not, and that every subject-based experiment should consider and understand the performance of individuals.
Abstract
This paper reports the results of an experiment undertaken for the CADPRO (Constraints And the Decision PROject) project. Subjects with varied experience produced data flow diagrams (DFDs) using a DFD tool generated by CASEMaker, a meta-CASE tool. Half the subjects received routine notice of instances of internal (as opposed to hierarchical) methodological constraint violations via an unobtrusive window whilst the other half did not. The DFD tool automatically recorded subjects' delivery and constraint profiles. Video records, observer notes, and subject debriefings were also used to yield other performance data. While evidence was found in support of the research model underpinning the CADPRO project, the model needs to be revised to take into account the affects of human-computer interface constraints and the different speeds with which people work. We learnt an important lesson about subject randomisation, which is not to assume that all subjects can be treated alike if they share the minimum necessary experience thought required of the problem. We believe it is important for every subject-based experiment to consider and understand the performance of individuals. Because of the complexity of constraint environments in CASE tools we also conclude that studies comparing extreme programming approaches with conventional CASE tool approaches are needed to help determine if the struggle to understand the constraint environment at a high level of abstraction is worthwhile or not. Further experiments, possibly replication variants of this one, are needed to help validate our interpretations.

read more

Citations
More filters
Journal ArticleDOI

A Systematic Review of Theory Use in Software Engineering Experiments

TL;DR: It is found that theory use and awareness of theoretical issues are present, but that theory-driven research is, as yet, not a major issue in empirical software engineering.

Replication of Controlled Experiments in Empirical Software Engineering - A Survey

TL;DR: This thesis is to collect guidelines for the replication of software engineering experiments, and to refine and supplement these guidelines where needed to contribute to the establishment of an empirical framework for the software engineering discipline.

State-of-the-Art in Empirical Studies

TL;DR: This report gives an overview on the state of the art in empirical studies in software engineering by prescribing a high-level process for empirical studies, which is refined for the three most often used empirical strategies: Controlled experiments, case studies, and surveys.
Dissertation

Quality of Design, Analysis and Reporting of Software Engineering Experiments:A Systematic Review

TL;DR: The review revealed that software engineering experiments were generally designed with unacceptably low power and that inadequate attention was paid to issues of statistical power, and that insufficient quality was revealed in the reviewed experiments.
Journal ArticleDOI

Methodology Support in CASE Tools and Its Impact on Individual Acceptance and Use: A Controlled Experiment

TL;DR: Based on these findings, it is recommended that vendors should provide CASE tools with adaptable methodology support, which allow their users to fit automated consistency assurance to the task at hand.
References
More filters
Book

Modern structured analysis

TL;DR: From the Publisher: Yourdon provides a fresh perspective on structured systems analysis, integrating traditional methodologies with modern technology.
Journal ArticleDOI

Embracing change with extreme programming

Kent Beck
- 01 Oct 1999 - 
TL;DR: Rather than planning, analyzing, and designing for the far-flung future, XP exploits the reduction in the cost of changing software to do all of these activities a little at a time, throughout software development.
Journal ArticleDOI

Why are CASE tools not used

TL;DR: The author examines attitudes toward CASE usage in a wide variety of organizations and finds that one year after introduction, 70% of the respondents indicated good profitability of CASE investments while 31% assessed it as poor.
Journal ArticleDOI

User analysis in HCI—the historical lessons from individual differences research

TL;DR: It is concluded that HCI could gain significant predictive power if individual differences research was related to the analysis of users in contemporary systems design.
Journal ArticleDOI

The case for user-centered CASE tools

TL;DR: This article analyzes problems that impede wide adoption of CASE tools and proposes remedies to some of the problems and direct this article to managers involved in CASE tool adoption, CASE tool users, and CASE tool developers.