Evaluation of Non Functional Requirements in a Request for Proposal (RFP)
Keywords
contractsformal specification
organisational aspects
software architecture
software maintenance
software metrics
software quality
nonfunctional requirement evaluation
request-for-proposal
contracted-based software development project
software user company
system requirements specification
technical plans
RFP quality evaluationn
user requirements
system architecture
response time
security issues
user maintenance
operation issues
NFR categories
NFR metrics
description level grading
NFR weight
Measurement
Information systems
Companies
Software
Maintenance engineering
Guidelines
Educational institutions
RFP
requirements evaluation
Full record
Show full item recordAbstract
2012 Joint Conference of the 22nd International Workshop on Software Measurement and the 2012 Seventh International Conference on Software Process and Product Measurement, 17-19 Oct. 2012, Assisi, ItalyIn the beginning of a contracted based software development project, the RFP is provided by a software user company and used as an initial system requirements specification to ask software developer companies to propose their technical plans to fulfill the requirements. In this process, it is very important to evaluate the quality of the RFP to make sure that basic user requirements are written enough. Especially, non-functional requirements (NFRs) are important since the system architecture greatly depends on the NFRs such as response time and security issues. This paper proposes a simple evaluation model of NFRs included in the RFP, mainly focusing on the user maintenance and operation issues. This model consists of NFR categories, NFR metrics, description level grading and weight to each NFR. As a case study, RFPs of 29 projects were evaluated by the proposed model. As a result, we confirmed that the model could identify poorly-written NFR aspects in the RFP, which need refinement before asking the developer company for a proposal.
Date
2018-10-30Type
Conference PaperIdentifier
oai:library.naist.jp:10061/127489781467331272
http://hdl.handle.net/10061/12748
https://doi.org/10.1109/IWSM-MENSURA.2012.23
106
111
73292310
Copyright/License
c Copyright IEEE 2012Collections
Related items
Showing items related by title, author, creator and subject.
-
New Industries from New Places : The Emergence of the Software and Hardware Industries in China and IndiaGregory, Neil; Nollen, Stanley; Tenev, Stoyan (Washington, DC: World Bank and Stanford University Press, 2009)China and India have grown rapidly in importance in the global economy over the past two decades the same period in which hardware and software have become important tradable products in the global economy. China has reached global scale in the hardware industry but not in software; India has achieved the reverse. These recent developments offer new insights into the ways in which new industries can take root and flourish within the broader context of developing economies. This progress has attracted widespread comment, most of it anecdotal or based on partial explanations of industrial growth. This study seeks to provide a fuller explanation based on an empirical analysis of the macro and micro underpinnings of these contrasting growth stories. In doing so, the study sheds a broader light on the economic development paths that China and India have taken since 1990, and also on the process by which developing economies can enter and succeed in new markets.
-
Financial Management Information
 Systems : 25 Years of World Bank Experience on What Works
 and What Doesn'tDener, Cem; Dorotinsky, William Leslie; Watkins, Joanna Alexandra (World Bank, 2012-03-19)This paper was prepared by the public
 sector and governance group of the World Bank poverty
 reduction and economic management network. Since 1984, the
 World Bank has financed 87 Financial Management Information
 System (FMIS) projects in 51 countries, totaling over US
 $2.2 billion, of which US $938 million was for FMIS-related
 Information and Communication Technology (ICT) solutions.
 This study presents the World Bank's experience with
 these investment operations, including substantial ICT
 components, in order to share the achievements and
 challenges observed, and provide guidance for improving the
 performance of future projects. This study is dived into
 five chapters. The introduction covers the definitions used
 and methodology applied in reviewing projects. Chapter 2
 provides descriptive characteristics of the sample data
 drawn from Bank databases and describes general patterns in
 duration, regional distribution, costs, and ICT solutions
 implemented, among other aspects. Chapter 3 analyzes the
 performance of the projects, differentiating between ratings
 of the Implementation Completion Reports (ICRs) and the
 Independent Evaluation Group (IEG) reports, as well as the
 factors contributing to the success and failure of projects
 and individual components. A detailed analysis of country
 case studies from Mongolia, Turkey, Albania, Guatemala, and
 Pakistan are presented in chapter 4. In conclusion, chapter
 5 synthesizes the main lessons learned and prerequisites
 necessary for an effective FMIS project. The findings of
 this study are based on a comprehensive database of 55
 closed and 32 active Treasury and FMIS projects implemented
 between 1984 and 2010 (pipeline projects were also analyzed
 in some sections). The data presented here was gathered from
 individual project ICRs, Project Appraisal Documents (PADs),
 the IEG reports, and complemented with interviews with task
 team leaders and relevant public sector and informatics specialists.
-
Requirements Engineering for Digital Health.Fricker, Samuel A.; Thuemmler, Christoph.; Gavras, Anastasius.Healthcare and well-being have captured the attention of established software companies, start-ups, and investors. Software is starting to play a central role for addressing the problems of the aging society and the escalating cost of healthcare services. Enablers of such digital health are a growing number of sensors for sensing the human body and communication infrastructure for remote meetings, data sharing, and messaging. The challenge that lies in front of us is how to effectively make use of these capabilities, for example to empower patients and to free the scarce resources of medical personnel.Requirements engineering is the process by which the capabilities of a software product are aligned with stakeholder needs and a shared understanding between the stakeholders and development team established. This book provides guide for what to look for and do when inquiring and specifying software that targets healthcare and well-being, helping readers avoid the pitfalls of the highly regulated and sensible healthcare domain are and how they can be overcome.This book brings together the knowledge of 22 researchers, engineers, lawyers, and CEOs that have experience in the development of digital health solutions. It represents a unique line-up of best practices and recommendations of how to engineer requirements for digital health. In particular the book presents:· The area of digital health, e-health, and m-health· Best practice for requirements engineering based on evidence from a large number of projects· Practical step-by-step guidelines, examples, and lessons-learned for working with laws, regulations, ethical issues, interoperability, user experience, security, and privacy· How to put these many concerns together for engineering the requirements of a digital health solution and for scaling a digital health productFor anybody who intends to develop software for digital health, this book is an introduction and reference with a wealth of actionable insights. For students interested in understanding how to apply software to healthcare, the text introduces key topics and guides further studies with references to important literature.