Case study, interrupted: the paucity of subject systems that span the requirements-architecture gap

Authors:
Mamadou H. Diallo;Susan Elliott Sim;Thomas A. Alspaugh
Affiliations:
University of California, Irvine;University of California, Irvine;University of California, Irvine
Venue:
Proceedings of the 1st ACM international workshop on Empirical assessment of software engineering languages and technologies: held in conjunction with the 22nd IEEE/ACM International Conference on Automated Software Engineering (ASE) 2007
Year:
2007

Citing 10
Cited 1

Managing the development of large software systems: concepts and techniques

ICSE '87 Proceedings of the 9th international conference on Software Engineering
An integrated approach to software engineering

An integrated approach to software engineering
Software architecture: practice, potential, and pitfalls

ICSE '94 Proceedings of the 16th international conference on Software engineering
A Study of 12 Specifications of the Library Problem

IEEE Software
Scenario-Based Analysis of Software Architecture

IEEE Software
Architectural Design to Meet Stakeholder Requirements

WICSA1 Proceedings of the TC2 First Working IFIP Conference on Software Architecture (WICSA1)
A Structured Demonstration of Program Comprehension Tools

WCRE '00 Proceedings of the Seventh Working Conference on Reverse Engineering (WCRE'00)
Architecture-level modifiability analysis (ALMA)

Journal of Systems and Software
Comparison of Scenario-Based Software Architecture Evaluation Methods

APSEC '04 Proceedings of the 11th Asia-Pacific Software Engineering Conference
Introduction to Software Engineering Design: Processes, Principles and Patterns with UML2

Introduction to Software Engineering Design: Processes, Principles and Patterns with UML2

Toward Architecture Evaluation through Ontology-Based Requirements-Level Scenarios

Architecting Dependable Systems V

Quantified Score

Hi-index	0.00

Visualization

Abstract

A number of approaches for spanning the requirements-architecture gap have been published in recent years, and we sought to rigorously characterize the gap and to conduct a comparative evaluation of approaches to span the gap using a case study method on a realistic problem. However, our intentions were impeded by the problem of finding appropriate subject systems that included sufficient information in both requirements and architecture document. Most subject systems that we found contained either detailed requirements or detailed architecture description, but not both. In this paper, we report on our search and the seventeen most suitable subject systems with the hope of aiding others undertaking a similar study. We speculate on the reasons for the paucity of suitable subject systems and invite contributions and suggestions for our ongoing work.