Jörg Dörr, Andreas L. Opdahl
Proceedings of the 19th International Working Conference on Requirements Engineering: Foundation for Software Quality
REFSQ, 2013.

@proceedings{REFSQ-2013,
	address       = "Essen, Germany",
	doi           = "10.1007/978-3-642-37422-7",
	editor        = "Jörg Dörr and Andreas L. Opdahl",
	isbn          = "978-3-642-37421-0",
	publisher     = "{Springer International Publishing}",
	series        = "{Lecture Notes in Computer Science}",
	title         = "{Proceedings of the 19th International Working Conference on Requirements Engineering: Foundation for Software Quality}",
	volume        = 7830,
	year          = 2013,
}

Contents (28 items)

19 ×#requirements
4 ×#development
4 ×#process
3 ×#bibliography
3 ×#case study
3 ×#modelling
3 ×#specification
3 ×#traceability
2 ×#ambiguity
2 ×#analysis

REFSQ-2013-DanevaBH #architecture #case study #experience #quality #question #requirements #what

Software Architects’ Experiences of Quality Requirements: What We Know and What We Do Not Know? (MD, LB, AH), pp. 1–17.

REFSQ-2013-Cleland-HuangCK #agile #approach #architecture #requirements

A Persona-Based Approach for Exploring Architecturally Significant Requirements in Agile Projects (JCH, AC, EK), pp. 18–33.

REFSQ-2013-FerrariGT #clustering #documentation #natural language #requirements #using

Using Clustering to Improve the Structure of Natural Language Requirements Documents (AF, SG, GT), pp. 34–49.

REFSQ-2013-Ott #automation #categorisation #natural language #overview #scalability #specification

Automatic Requirement Categorization of Large Natural Language Specifications at Mercedes-Benz for Review Improvements (DO), pp. 50–64.

REFSQ-2013-PhilippoHKCB #ambiguity #empirical #evaluation

Requirement Ambiguity Not as Important as Expected — Results of an Empirical Evaluation (EJP, WH, BK, MRVC, DMB), pp. 65–79.

REFSQ-2013-TjongB #ambiguity #design #lessons learnt #prototype #requirements #specification

The Design of SREE — A Prototype Potential Ambiguity Finder for Requirements Specifications and Lessons Learned (SFT, DMB), pp. 80–95.

REFSQ-2013-ProynovaP #feedback #predict

Factors Influencing User Feedback on Predicted Satisfaction with Software Systems (RP, BP), pp. 96–111.

REFSQ-2013-Regnell #modelling #requirements #scalability #towards

reqT.org — Towards a Semi-Formal, Open and Scalable Requirements Modeling Tool (BR), pp. 112–118.

REFSQ-2013-NoorwaliM #lessons learnt #perspective #requirements #research

Maps of Lessons Learnt in Requirements Engineering: A Research Preview (IN, NHM), pp. 119–124.

REFSQ-2013-RempelMKP #bound #overview #requirements #taxonomy #traceability

Requirements Traceability across Organizational Boundaries — A Survey and Taxonomy (PR, PM, TK, IP), pp. 125–140.

REFSQ-2013-BreauxG #analysis #requirements #specification #traceability #using

Regulatory Requirements Traceability and Analysis Using Semi-formal Specifications (TDB, DGG), pp. 141–157.

REFSQ-2013-BouillonMP #overview #requirements #traceability

A Survey on Usage Scenarios for Requirements Traceability in Practice (EB, PM, IP), pp. 158–173.

REFSQ-2013-HoffmannBL #comprehension #development #process

The Emergence of Mutual and Shared Understanding in the System Development Process (AH, EACB, JML), pp. 174–189.

REFSQ-2013-AzmehMC #community #requirements

Highlighting Stakeholder Communities to Support Requirements Decision-Making (ZA, IM, PC), pp. 190–205.

REFSQ-2013-IngolfoSJSPM

Choosing Compliance Solutions through Stakeholder Preferences (SI, AS, IJ, AS, AP, JM), pp. 206–220.

REFSQ-2013-BencomoB #adaptation #modelling #network #self

Supporting Decision-Making for Self-Adaptive Systems: From Goal Models to Dynamic Decision Networks (NB, AB), pp. 221–236.

REFSQ-2013-WauteletK #modelling #uml

Mapping i* within UML for Business Modeling (YW, MK), pp. 237–252.

REFSQ-2013-CallelePW #identification #interface #requirements #risk management

Risk Identification at the Interface between Business Case and Requirements (DC, BP, KW), pp. 253–268.

REFSQ-2013-Zorn-PauliPBKR #case study #industrial #process #release planning

Analyzing an Industrial Strategic Release Planning Process — A Case Study at Roche Diagnostics (GZP, BP, TB, HK, GR), pp. 269–284.

REFSQ-2013-Bennett-TherkildsenJNR #development #process #requirements

Redefinition of the Requirements Engineer Role in Mjølner’s Software Development Process (ABT, JBJ, KN, NMR), pp. 285–291.

REFSQ-2013-Bjarnason #development #process #requirements

Distances between Requirements Engineering and Later Software Development Activities: A Systematic Map (EB), pp. 292–307.

REFSQ-2013-DelaterP #development #perspective #requirements #research #source code

Analyzing the Tracing of Requirements and Source Code during Software Development — A Research Preview (AD, BP), pp. 308–314.

REFSQ-2013-PasqualeSPBR #experience #game studies #requirements

Requirements Engineering Meets Physiotherapy: An Experience with Motion-Based Games (LP, PS, DP, FB, TR), pp. 315–330.

REFSQ-2013-BonBGALTBFGATA #analysis #case study #requirements

Use Case and Requirements Analysis in a Remote Rural Context in Mali (AB, VdB, NBG, CvA, PDL, WT, SB, MF, AG, MA, AT, HA), pp. 331–346.

REFSQ-2013-Herrmann #requirements

Requirements Engineering in Practice: There Is No Requirements Engineer Position (AH), pp. 347–361.

REFSQ-2013-AdamS #effectiveness #elicitation #empirical #product line #requirements

Effective Requirements Elicitation in Product Line Application Engineering — An Experiment (SA, KS), pp. 362–378.

REFSQ-2013-KlambauerHG #monitoring #multi #product line #requirements

Monitoring System-of-Systems Requirements in Multi Product Lines (TK, GH, PG), pp. 379–385.

REFSQ-2013-JantunenHG #challenge #problem

Adjusting to Increasing Product Management Problems: Challenges and Improvement Proposals in One Software Company (SJ, KH, DCG), pp. 386–400.