Proceedings of the 21st International Requirements Engineering Conference
BibSLEIGH corpus
BibSLEIGH tags
BibSLEIGH bundles
BibSLEIGH people
EDIT!
CC-BY
Open Knowledge
XHTML 1.0 W3C Rec
CSS 2.1 W3C CanRec
email twitter


Proceedings of the 21st International Requirements Engineering Conference
RE, 2013.

REQ
DBLP
Scholar
CSDL
Full names Links ISxN
@proceedings{RE-2013,
	address       = "Rio de Janeiro-RJ, Brazil",
	ee            = "http://www.computer.org/csdl/proceedings/re/2013/9999/00/index.html",
	isbn          = "978-1-4673-5765-4",
	publisher     = "{IEEE Computer Society}",
	title         = "{Proceedings of the 21st International Requirements Engineering Conference}",
	year          = 2013,
}

Contents (62 items)

RE-2013-Maiden #idea #information management #requirements
Requirements engineering as information search and idea discovery (NAMM), p. 1.
RE-2013-Cousins #architecture #challenge #industrial #requirements
Starchitects and Jack-Hammers: Requirements engineering challenges and practices in the construction industry (FC), p. 2.
RE-2013-MasseyEAS #analysis #automation #documentation #mining #policy #requirements
Automated text mining for requirements analysis of policy documents (AKM, JE, AIA, PPS), pp. 4–13.
RE-2013-BreauxR #analysis #formal method #multi #privacy #requirements #specification
Formal analysis of privacy requirements specifications for multi-tier applications (TDB, AR), pp. 14–20.
RE-2013-MaxwellAE #empirical
An empirical investigation of software engineers’ ability to classify legal cross-references (JCM, AIA, JBE), pp. 24–31.
RE-2013-MahmoudN #refactoring #requirements #traceability
Supporting requirements traceability through refactoring (AM, NN), pp. 32–41.
RE-2013-0004CB #traceability
Foundations for an expert system in domain-specific traceability (JG, JCH, BB), pp. 42–51.
RE-2013-SultanovH #learning #requirements
Application of reinforcement learning to requirements engineering: requirements tracing (HS, JHH), pp. 52–61.
RE-2013-GhezziMSS #on the #requirements #verification
On requirements verification for model refinements (CG, CM, AMS, PS), pp. 62–71.
RE-2013-KrkaM #behaviour
Distributing refinements of a system-level partial behavior model (IK, NM), pp. 72–81.
RE-2013-DietrichA #interface #requirements
A mode-based pattern for feature requirements, and a generic feature interface (DD, JMA), pp. 82–91.
RE-2013-SutcliffeS #elicitation #requirements #towards
Requirements elicitation: Towards the unknown unknowns (AS, PS), pp. 92–104.
RE-2013-TodoranSG #case study #elicitation #how #requirements
How cloud providers elicit consumer requirements: An exploratory study of nineteen companies (IT, NS, MG), pp. 105–114.
RE-2013-CaireGHM #design #requirements #towards #visual notation
Visual notation design 2.0: Towards user comprehensible requirements engineering notations (PC, NG, PH, DLM), pp. 115–124.
RE-2013-PaganoM #empirical #feedback
User feedback in the appstore: An empirical study (DP, WM), pp. 125–134.
RE-2013-ShiWL #evolution #learning #predict
Learning from evolution history to predict future requirement changes (LS, QW, ML), pp. 135–144.
RE-2013-GordonB #modelling #requirements
Assessing regulatory change through legal requirements coverage modeling (DGG, TDB), pp. 145–154.
RE-2013-NakagawaOH #evolution
A goal model elaboration for localizing changes in software evolution (HN, AO, SH), pp. 155–164.
RE-2013-AlspaughS #development #requirements
Ongoing software development without classical requirements (TAA, WS), pp. 165–174.
RE-2013-ZarghamiVESW #identification #risk management
Assumption-based risk identification method (ARM) in dynamic service provisioning (AZ, EV, MZE, MvS, RW), pp. 175–184.
RE-2013-WangLWYZL #debugging #dependence #integration #network #question #requirements
Can requirements dependency network be used as early indicator of software integration bugs? (JW, JL, QW, DY, HZ, ML), pp. 185–194.
RE-2013-RempelMK #empirical #traceability
An empirical study on project-specific traceability strategies (PR, PM, TK), pp. 195–204.
RE-2013-NiuRC #requirements #visual notation
Keeping requirements on track via visual analytics (NN, SR, ZC), pp. 205–214.
RE-2013-Mead #requirements
A history of the international requirements engineering conference (RE)RE@21 (NRM), pp. 215–221.
RE-2013-NairVS #overview #requirements #research #traceability
A review of traceability research at the requirements engineering conferencere@21 (SN, JLdlV, SS), pp. 222–229.
RE-2013-Morris #modelling
Models in the RE seriesre@21 (SJM), pp. 230–237.
RE-2013-MussbacherK #requirements
A vision for generic concern-oriented requirements reusere@21 (GM, JK), pp. 238–249.
RE-2013-Salger #challenge #open science #requirements #research
Requirements reviews revisited: Residual challenges and open research questions (FS), pp. 250–255.
RE-2013-SavolainenHM #challenge #embedded #specification
Challenges in balancing the amount of solution information in requirement specifications for embedded products (JS, DH, MM), pp. 256–260.
RE-2013-HesariBY #challenge #framework #generative #industrial #testing #towards
Towards a systematic requirement-based test generation framework: Industrial challenges and needs (SH, RB, TY), pp. 261–266.
RE-2013-VogelsanagF #challenge #dependence #empirical #requirements #why
Why feature dependencies challenge the requirements engineering of automotive systems: An empirical study (AV, SF), pp. 267–272.
RE-2013-LarburuWBHN #collaboration #elicitation #requirements
Early phase telemedicine requirements elicitation in collaboration with medical practitioners (NL, IW, RGAB, HJH, CN), pp. 273–278.
RE-2013-NiknafsB #case study #effectiveness #elicitation #generative #idea #industrial #requirements
An industrial case study of the impact of domain ignorance on the effectiveness of requirements idea generation during requirements elicitation (AN, DMB), pp. 279–283.
RE-2013-Terzakis #quality #requirements
The impact of requirements on software quality across three product generations (JT), pp. 284–289.
RE-2013-SaitoTHKA #quality #requirements #specification
Requirements clinic: Third party inspection methodology and practice for improving the quality of software requirements specifications (SS, MT, MH, TK, MA), pp. 290–295.
RE-2013-FeldererB #fault #industrial #requirements #taxonomy #using #validation
Using defect taxonomies for requirements validation in industrial projects (MF, AB), pp. 296–301.
RE-2013-MuyanjaMNTKN #requirements
Requirements engineering for the uganda police force crime records management system (AM, PIM, CN, SSTT, EKK, AN), pp. 302–307.
RE-2013-GolnamRWK #case study #integration #scalability
The integration of an RE method and AHP: A pilot study in a large Swiss bank (AG, GR, AW, SK), pp. 308–313.
RE-2013-DwarakanathRS #automation #natural language #requirements #taxonomy
Automatic extraction of glossary terms from natural language requirements (AD, RRR, SS), pp. 314–319.
RE-2013-NistalaK #analysis #approach #consistency #requirements #validation
An approach to carry out consistency analysis on requirements: Validating and tracking requirements through a configuration structure (PN, PK), pp. 320–325.
RE-2013-RenzelBKJ #requirements #social
Requirements Bazaar: Social requirements engineering for community-driven innovation (DR, MB, RK, MJ), pp. 326–327.
RE-2013-GuillermDS #safety
A safety requirement engineering method and tool (RG, HD, NS), pp. 328–329.
RE-2013-TeuflMR #empirical #modelling #named #requirements
MIRA: A tooling-framework to experiment with model-based requirements engineering (ST, DM, DR), pp. 330–331.
RE-2013-PalomaresQF #elicitation #named #requirements
PABRE-Proj: Applying patterns in requirements elicitation (CP, CQ, XF), pp. 332–333.
RE-2013-SchneiderBB #architecture #enterprise #implementation #modelling #requirements
A tool implementation of the unified requirements modeling language as enterprise architect add-in (FS, BB, BB), pp. 334–335.
RE-2013-BaresiRP #named #platform #requirements
IRET: Requirements for service platforms (LB, GR, LP), pp. 336–337.
RE-2013-Cleland-HuangCH #design #empirical #requirements #using
Using tracelab to design, execute, and baseline empirical requirements engineering experiments (JCH, AC, JHH), pp. 338–339.
RE-2013-PasqualeYSCTN #adaptation #forensics
Requirements-driven adaptive digital forensics (LP, YY, MS, LC, TTT, BN), pp. 340–341.
RE-2013-NcubeLD #challenge #identification #requirements #research
Identifying top challenges for international research on requirements engineering for systems of systems engineering (CN, SLL, HD), pp. 342–344.
RE-2013-Cleland-HuangG #named #requirements
Ready-Set-Transfer: Technology transfer in the requirements engineering domain (JCH, SG), pp. 345–346.
RE-2013-WieringaEM #industrial #question #requirements
Requirements engineering conferences: Wither industry tracks? (RW, PvE, JM), pp. 349–352.
RE-2013-MahauxM #paradigm #requirements #research
A new paradigm for applied requirements engineering research (MM, AM), pp. 353–356.
RE-2013-Gorschek #requirements
A little rebellion now and then is a good thing: Views on the requirements engineering conference (TG), pp. 357–360.
RE-2013-Beatty #requirements
Winning the hidden battle: Requirements tool selection and adoption (JB), pp. 364–365.
RE-2013-YuAMFC #industrial #state of the art
Practical applications of i∗ in industry: The state of the art (ESKY, DA, GM, XF, JC), pp. 366–367.
RE-2013-GlinzW #requirements
RE@21 spotlight: Most influential papers from the requirements engineering conference (MG, RW), pp. 368–370.
RE-2013-MahauxC #interactive
Creative collisions: Meet and create: And other “RE interactive” suggestions (MM, DC), pp. 371–372.
RE-2013-PenzenstadlerFRCW #requirements
The requirements engineering body of knowledge (REBoK) (BP, DMF, DR, DC, KW), pp. 377–379.
RE-2013-Gordon #requirements
The regulatory world and the machine: Harmonizing legal requirements and the systems they affect (DGG), pp. 381–384.
RE-2013-Nair #assurance #certification #safety
Evidence management for evolutionary safety assurance and certification (SN), pp. 385–388.
RE-2013-Reddivari #requirements #visual notation
Visual analytics for software requirements engineering (SR), pp. 389–392.
RE-2013-Valenca #approach #ecosystem #evolution #requirements #social
Requirements negotiation model: A social oriented approach for software ecosystems evolution (GV), pp. 393–396.

Bibliography of Software Language Engineering in Generated Hypertext (BibSLEIGH) is created and maintained by Dr. Vadim Zaytsev.
Hosted as a part of SLEBOK on GitHub.