Classification of research efforts in requirements engineering
ACM Computing Surveys (CSUR)
Proceedings of the Conference on The Future of Software Engineering
22nd International Conference on Software Engineering
Toward Reference Models for Requirements Traceability
IEEE Transactions on Software Engineering
Requirements Engineering: A Good Practice Guide
Requirements Engineering: A Good Practice Guide
Empirical Software Engineering
Software Architecture in Practice
Software Architecture in Practice
Team-Based Fault Content Estimation in the Software Inspection Process
Proceedings of the 26th International Conference on Software Engineering
Using Students as Subjects in Requirements Prioritization
ISESE '04 Proceedings of the 2004 International Symposium on Empirical Software Engineering
Architecture-driven Problem Decomposition
RE '04 Proceedings of the Requirements Engineering Conference, 12th IEEE International
Testing to Improve Requirements - Mission Impossible?
RE '06 Proceedings of the 14th IEEE International Requirements Engineering Conference
The Impact of Requirements Knowledge and Experience on Software Architecting: An Empirical Study
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
The TAME project: towards improvement-oriented software environments
IEEE Transactions on Software Engineering
A Methodology for Collecting Valid Software Engineering Data
IEEE Transactions on Software Engineering
An exploratory study of architectural effects on requirements decisions
Journal of Systems and Software
Ontological analysis for generating baseline architectural descriptions
ECSA'10 Proceedings of the 4th European conference on Software architecture
Hi-index | 0.00 |
Requirements permeate many parts of the software development process outside the requirements engineering (RE) process. It is thus important to determine whether software developers in these other areas of software development face any requirements-oriented (RO) problems in carrying out their tasks. Feedback so obtained can be invaluable for improving both requirements and RE technologies. In this paper, we describe an exploratory case study of requirements-oriented problems experienced by 16 architecting teams designing the same banking application. The study found that there were several different types of RO problems, of varying severity, which the architects faced in using the given requirements; those architects with RE background also faced RO problems; and about a third of all problems were RO problems. There was much concurrence of our findings with software-expert opinion from a large insurance company. There were also areas where there were relatively few RO problems. The paper also describes some implications of the findings for the RE field, particularly in the areas of: expression of quality requirements for different stakeholders; empirical studies on quality scenarios; tighter integration of RE and software architecting processes; and requirements to architecture mapping. There are opportunities for further research based on two emergent hypotheses which are also described in this paper.