Getting the balance right between functional and non-functional requirements: the case of requirement specification in IT procurement
(2013) In IJISPM - International Journal of Information Systems and Project Management 1(1). p.5-16- Abstract
- IT procurement represents a business process of high importance, including the ability to articulate requirements that
the procurement deals with. Furthermore, specifying requirements is of importance for both procurer and potential
supplier, as it functions as central contractual element between the two. The purpose of this article is two-fold: (i) to
show how established terminology for requirement specification is represented in current call for bids for the
procurement of IT; and (ii) to introduce an organizing framework that may assist procurers in actively addressing
functional requirements and business requirements. Ten “call for bids” were examined from a Swedish national
... (More) - IT procurement represents a business process of high importance, including the ability to articulate requirements that
the procurement deals with. Furthermore, specifying requirements is of importance for both procurer and potential
supplier, as it functions as central contractual element between the two. The purpose of this article is two-fold: (i) to
show how established terminology for requirement specification is represented in current call for bids for the
procurement of IT; and (ii) to introduce an organizing framework that may assist procurers in actively addressing
functional requirements and business requirements. Ten “call for bids” were examined from a Swedish national
procurement database. From the analysis of the bids, it can be concluded that: (i) the call for bids displays a high degree
of precision regarding hardware aspects, but less precision regarding software; (ii) supplier experience and competence
is stressed, but rarely elaborated on in detail; and (iii) call for bids vagueness may be used as a lock-in opportunity for
suppliers. From the discussion on this, a tentative procurement framework is suggested, aiming on increasing the logical
transparency for the procurement of IT. (Less)
Please use this url to cite or link to this publication:
https://lup.lub.lu.se/record/3731003
- author
- Johansson, Björn LU and Lahtinen, Markus LU
- organization
- publishing date
- 2013
- type
- Contribution to journal
- publication status
- published
- subject
- keywords
- procurement of IT, software specification, government procurement, software requirement, procurement checklist
- in
- IJISPM - International Journal of Information Systems and Project Management
- volume
- 1
- issue
- 1
- pages
- 5 - 16
- publisher
- SciKA
- external identifiers
-
- scopus:84897795806
- ISSN
- 2182-7796
- language
- English
- LU publication?
- yes
- id
- 0e3efb5f-6424-4003-920e-6edef6503bbe (old id 3731003)
- alternative location
- http://www.sciencesphere.org/ijispm/archive/ijispm-010101.pdf
- date added to LUP
- 2016-04-04 09:23:23
- date last changed
- 2022-02-21 00:32:06
@article{0e3efb5f-6424-4003-920e-6edef6503bbe,
abstract = {{IT procurement represents a business process of high importance, including the ability to articulate requirements that<br/><br>
the procurement deals with. Furthermore, specifying requirements is of importance for both procurer and potential<br/><br>
supplier, as it functions as central contractual element between the two. The purpose of this article is two-fold: (i) to<br/><br>
show how established terminology for requirement specification is represented in current call for bids for the<br/><br>
procurement of IT; and (ii) to introduce an organizing framework that may assist procurers in actively addressing<br/><br>
functional requirements and business requirements. Ten “call for bids” were examined from a Swedish national<br/><br>
procurement database. From the analysis of the bids, it can be concluded that: (i) the call for bids displays a high degree<br/><br>
of precision regarding hardware aspects, but less precision regarding software; (ii) supplier experience and competence<br/><br>
is stressed, but rarely elaborated on in detail; and (iii) call for bids vagueness may be used as a lock-in opportunity for<br/><br>
suppliers. From the discussion on this, a tentative procurement framework is suggested, aiming on increasing the logical<br/><br>
transparency for the procurement of IT.}},
author = {{Johansson, Björn and Lahtinen, Markus}},
issn = {{2182-7796}},
keywords = {{procurement of IT; software specification; government procurement; software requirement; procurement checklist}},
language = {{eng}},
number = {{1}},
pages = {{5--16}},
publisher = {{SciKA}},
series = {{IJISPM - International Journal of Information Systems and Project Management}},
title = {{Getting the balance right between functional and non-functional requirements: the case of requirement specification in IT procurement}},
url = {{http://www.sciencesphere.org/ijispm/archive/ijispm-010101.pdf}},
volume = {{1}},
year = {{2013}},
}