![](bg8.png)
for systematic reviews. BMC medical informatics and
decision making, 13(1):7.
Gray, J. E., Hamilton, M. C., Hauser, A., Janz, M. M., Pe-
ters, J. P., and Taggart, F. (2012). Scholarish: Google
scholar and its value to the sciences. Issues in Science
and Technology Librarianship, 70(Summer).
Greer, D. and Ruhe, G. (2004). Software release planning:
an evolutionary and iterative approach. Information
and Software Technology, 46(4):243–253.
Halpin, T. (1998). Object-role modeling (orm/niam). In
Handbook on architectures of information systems,
pages 81–103. Springer.
Kabbedijk, J., Wnuk, K., Regnell, B., Brinkkemper, S.,
et al. (2010). What decision characteristics influence
decision making in market-driven large-scale software
product line development? Hildesheimer Informatik-
Berichte, 2010:42–53.
Kahneman, D. and Tversky, A. (1979). Prospect theory: An
analysis of decision under risk. Econometrica: Jour-
nal of the Econometric Society, pages 263–291.
Khurum, M., Uppalapati, N., and Veeramachaneni, R. C.
(2012). Software requirements triage and selection:
state-of-the-art and state-of-practice. In Software
Engineering Conference (APSEC), 2012 19th Asia-
Pacific, volume 1, pages 416–421. IEEE.
Kitchenham, B. and Charters, S. (2007). Guidelines for per-
forming systematic literature reviews in software en-
gineering. Engineering, 2(EBSE 2007-001). EBSE
2007-001.
Levy, Y. and Ellis, T. J. (2006). Towards a framework of
literature review process in support of information sy-
stems research. In Proceedings of the 2006 Infor-
ming Science and IT Education Joint Conference, vo-
lume 26.
Li, C., Van Den Akker, J., Brinkkemper, S., and Diepen, G.
(2007). Integrated requirement selection and schedu-
ling for the release planning of a software product. In
Requirements Engineering: Foundation for Software
Quality, chapter Requirements Engineering: Founda-
tion for Software Quality, pages 93–108. Springer.
Li, L., Harman, M., Wu, F., and Zhang, Y. (2017). The va-
lue of exact analysis in requirements selection. IEEE
Transactions on Software Engineering, 43(6):580–
596.
Mitchell, R. K., Agle, B. R., and Wood, D. J. (1997). To-
ward a theory of stakeholder identification and sa-
lience: Defining the principle of who and what really
counts. Academy of management review, 22(4):853–
886.
Mongin, P. (1997). Expected utility theory. Handbook of
economic methodology, 342350.
Neuhaus, C., Neuhaus, E., Asher, A., and Wrede, C. (2006).
The depth and breadth of google scholar: An em-
pirical study. portal: Libraries and the Academy,
6(2):127–141.
Noruzi, A. (2005). Google scholar: The new generation of
citation indexes. Libri, 55(4):170–180.
Okoli, C. and Schabram, K. (2010). A guide to conducting
a systematic literature review of information systems
research. Available at SSRN 1954824.
Racheva, Z., Daneva, M., Sikkel, K., Herrmann, A., and
Wieringa, R. (2010). Do we know enough about requi-
rements prioritization in agile projects: insights from a
case study. In Requirements Engineering Conference
(RE), 2010 18th IEEE International, pages 147–156.
IEEE.
Regnell, B., Beremark, P., and Eklundh, O. (1998). A
market-driven requirements engineering process: re-
sults from an industrial process improvement pro-
gramme. Requirements engineering, 3(2):121–129.
Regnell, B. and Brinkkemper, S. (2005). Market-driven re-
quirements engineering for software products. In En-
gineering and managing software requirements, chap-
ter Engineering and managing software requirements,
pages 287–308. Springer.
Rittel, H. W. and Webber, M. M. (1973). Dilemmas in a
general theory of planning. Policy sciences, 4(2):155–
169.
Royce, W. W. (1970). Managing the development of large
software systems. In proceedings of IEEE WESCON,
volume 26, pages 328–388. Los Angeles.
Ruhe, G. (2005). Software release planning. Handbook
of software engineering and knowledge engineering,
3:365–394.
Ruhe, G., Eberlein, A., and Pfahl, D. (2002). Quantitative
winwin: a new method for decision support in requi-
rements negotiation. In Proceedings of the 14th in-
ternational conference on Software engineering and
knowledge engineering, pages 159–166. ACM.
Shariff, S. Z., Bejaimal, S. A., Sontrop, J. M., Iansavichus,
A. V., Haynes, R. B., Weir, M. A., and Garg, A. X.
(2013). Retrieving clinical evidence: a comparison
of pubmed and google scholar for quick clinical sear-
ches. Journal of medical Internet research, 15(8).
Sivzattian, S. and Nuseibeh, B. (2001). Linking the se-
lection of requirements to market value: A portfolio-
based approach. In 7th International Workshop on
Requirements Engineering: Foundation for Software
Quality. Interlaken, Switzerland. Citeseer.
Turk, D., France, R., and Rumpe, B. (2014). Assumpti-
ons underlying agile software development processes.
arXiv preprint arXiv:1409.6610.
van de Weerd, I., Brinkkemper, S., Nieuwenhuis, R., Ver-
sendaal, J., and Bijlsma, L. (2006). On the creation
of a reference framework for software product ma-
nagement: Validation and tool support. In Software
Product Management, 2006. IWSPM’06. Internatio-
nal Workshop on, pages 3–12. IEEE.
Wnuk, K., Kabbedijk, J., Brinkkemper, S., Regnell, B., and
Callele, D. (2015). Exploring factors affecting de-
cision outcome and lead time in large-scale require-
ments engineering. Journal of Software: Evolution
and Process, 27(9):647–673.
Wohlin, C. and Aurum, A. (2005). What is important when
deciding to include a software requirement into a pro-
ject or release. In International Symposium on Empi-
ricial Software Engineering, volume 186. IEEE.
ICSOFT 2018 - 13th International Conference on Software Technologies
220