An Empirical Study on Decision making for Quality Requirements

[Context] Quality requirements are important for product success yet often handled poorly. The problems with scope decision lead to delayed handling and an unbalanced scope. [Objective] This study characterizes the scope decision process to understand influencing factors and properties affecting the scope decision of quality requirements. [Method] We studied one company's scope decision process over a period of five years. We analyzed the decisions artifacts and interviewed experienced engineers involved in the scope decision process. [Results] Features addressing quality aspects explicitly are a minor part (4.41%) of all features handled. The phase of the product line seems to influence the prevalence and acceptance rate of quality features. Lastly, relying on external stakeholders and upfront analysis seems to lead to long lead-times and an insufficient quality requirements scope. [Conclusions] There is a need to make quality mode explicit in the scope decision process. We propose a scope decision process at a strategic level and a tactical level. The former to address long-term planning and the latter to cater for a speedy process. Furthermore, we believe it is key to balance the stakeholder input with feedback from usage and market in a more direct way than through a long plan-driven process

Evaluation of e-learning web sites using fuzzy axiomatic design based approach

High quality web site has been generally recognized as a critical enabler to conduct online business. Numerous studies exist in the literature to measure the business performance in relation to web site quality. In this paper, an axiomatic design based approach for fuzzy group decision making is adopted to evaluate the quality of e-learning web sites. Another multi-criteria decision making technique, namely fuzzy TOPSIS, is applied in order to validate the outcome. The methodology proposed in this paper has the advantage of incorporating requirements and enabling reductions in the problem size, as compared to fuzzy TOPSIS. A case study focusing on Turkish e-learning websites is presented, and based on the empirical findings, managerial implications and recommendations for future research are offered

Analysis of design for environment requirements for future consumer electronics

Abstract. The scope of the study was to outline the critical areas of ‘Environment’ as a key stakeholder of product development. The aim of the research was three-folded. First, in the literature part, the aim was to understand design for environment (DFE) and capability creation concepts and resolve how to combine them into a concept. Second, in the empirical analysis part, the aim was to find the generic design for environment stakeholders and requirements for product development in the electronics industry. Finally, in the further analysis and discussion part, the methods and concepts to combine stakeholders and requirements for design for environment were generated at a generic level. A literature study was utilised to understand the topic, where general ideas and aspects around design for environment and capability creation were collected. An empirical survey was then conducted by interviewing experts and managers at three electronics and high technology companies in Finland. The survey was conducted via an online Teams meeting guided by a questionnaire related to design for environment and its related aspects. Finally, the analysis of the answers was performed using common knowledge and understanding. DFE is a product development approach that seeks to enhance a product’s environmental attributes throughout its lifecycle. The ultimate objective is to meet sustainability goals, and the early involvement of design for the environment facilitates product development in creating sustainability capabilities. Design for environment and sustainability capability creation are counterpart activities that support each other in a cycle loop. They both require and utilize identifying and assessing critical environmental stakeholders during the product development process for long-term sustainability. The empirical study indicates that there are two types of environmental stakeholders. They are internal stakeholders and external stakeholders. Business groups, design teams, quality teams, and experts are the internal stakeholders within the organization that participate actively in the product design and development process and have power in the decision-making process. Customers, suppliers, investors, and peers are the external stakeholders who strongly influence the product development process but do not have decision-making power. The key environmental stakeholders present essential environmental requirements that should be considered in making distinct changes and improvements in the new product development process. The central design for environment requirements are legal requirements, customer requirements, materials and energy requirements, and voluntary requirements. In conclusion, it can be stated that design for environment is a lifecycle thinking approach to product development that supports continuous improvement and development of sustainable products. Therefore, it is critical to identify and prioritise the key environmental stakeholders and their environmental requirements for better decision-making and focusing on fulfilling the sustainability targets. This study highlights the key areas of the environment where companies, especially the electronics industry, have to rethink the design for environment activities and recognise the concept to develop in an effective and organised way

Guide for Automation of Low Volume Production

There is a remaining need from both academia and practitioners, to gain further knowledge about the decision making process for automation of low volume production. This paper includes insights of drivers for automation, the development of a guide for low volume production and the outcome of using the guide. The research in this study is based on both empirical data and theoretical considerations. The empirical data was collected in five case studies and a questionnaire. This paper is part of a research project with the main objective to develop knowledge about how flexible automation may contribute to improvements in efficiency, ergonomics, quality and production economics in different industries with low volume production. One of the results in the project was a comprehensive guide, developed, refined and improved in an iterative collaborative process, where tools and parts ofthe guide were tested and verified by five manufacturing case companies. The paper describes briefly the development process of the guide and content. The requirements of the guide derived from literature, case companies, questionnaire as well as industrial experts. The resulting guide can be used in several ways, depending on the requirements of the application. The guide includes guiding principles, a decision model for the analysis of the company, choice of automation and facts about automation. In the end of the project, four companies had invested or decided to invest in different types of automation

A survey on quality attributes in servicebased systems

Service-based systems have become popular in the software industry. In software engineering, it is widely acknowledged that requirements on quality attributes (e.g., performance, security, reliability) significantly impact the design of software systems. This study explores the role of quality attributes during the design of service-based systems. We investigate the significance of quality attributes when designing service-based systems and how quality attributes are addressed through design decisions, across application domains, and related to other aspects of software development, e.g., architecture documentation. We conducted a descriptive survey. The survey was done as an online questionnaire targeting practitioners. Furthermore, we included researchers with practical design experience. We obtained 56 valid responses. Most survey participants consider quality attributes and functionality as equally important and treat quality attributes explicitly rather than implicitly. Furthermore, dependability is the most relevant quality attribute in service-based systems; we do not find quality attributes that are particularly important in specific application domains. Most quality attributes are addressed by ad hoc decisions, rather than established architecture or design patterns or technologies. Only few decision alternatives are considered when making architectural decisions to address quality attributes. Our results partially confirm anecdotal evidence from current literature, but also strengthen previous claims by providing empirical evidence. Our results point to future research directions (e.g., exploring the impact of decision types on how well quality attributes can be achieved) and implications for practitioners (e.g., training makes a difference to how quality attributes are treated).Peer ReviewedPostprint (author’s final draft

An investigation of informed consent in clinical practice in South Africa

This study was designed to evaluate the quality of informed consent practiced by healthcare professionals in South Africa using an empirical quantitative methodology combined with medicolegal analysis to produce an interdisciplinary thesis on bioethics and medical law. Informed consent is an ethical and legal doctrine derived from the principle of respect for autonomy, whereas the rights to bodily integrity, privacy and human dignity are constitutionally protected in South Africa. The National Health Act 61 of 2003 codified requirements for informed consent by stipulating that healthcare providers must inform healthcare users about diagnosis, risks, benefits, treatment options, and the right of refusal, while taking into consideration users language and literacy levels. However, African communities are inherently challenged by problems of poverty, poor education, power asymmetry, and unfamiliarity with libertarian rights-based autonomy, which could affect informed consent practice. An empirical study was conducted at randomly selected public hospitals in EThekwini metropolitan municipality involving 927 participants; comprising 168 medical doctors, 355 professional nurses, and 404 patients. The study showed that healthcare professionals had limited knowledge regarding ethical and legal requirements for informed consent, and were partially compliant with current informed consent regulations. Barriers to informed consent identified were language, poor education, workload, and lack of interpreters. Most patients attending public hospitals were indigent, but preferred full information disclosure, and a shift from informed to shared-healthcare decision-making. The study recommends that a corps of trained interpreters should be introduced at public hospitals. This will improve providerpatient communications and minimize workloads, increase job satisfaction, and the overall quality of healthcare service delivery. Analysis of recent South African case law on informed consent revealed vacillations between the “reasonable doctor” and “prudent patient” standards of information disclosure which are inconsistent with the jurisprudence from comparative foreign common law jurisdictions. Therefore, South African court judgments on informed consent ought to be re-evaluated to establish a uniform standard of information disclosure consistent with international jurisprudence, current legislation, and constitutional protections relating to human dignity and security of the person.JurisprudenceLL. D

The Unfulfilled Potential of Data-Driven Decision Making in Agile Software Development

With the general trend towards data-driven decision making (DDDM), organizations are looking for ways to use DDDM to improve their decisions. However, few studies have looked into the practitioners view of DDDM, in particular for agile organizations. In this paper we investigated the experiences of using DDDM, and how data can improve decision making. An emailed questionnaire was sent out to 124 industry practitioners in agile software developing companies, of which 84 answered. The results show that few practitioners indicated a widespread use of DDDM in their current decision making practices. The practitioners were more positive to its future use for higher-level and more general decision making, fairly positive to its use for requirements elicitation and prioritization decisions, while being less positive to its future use at the team level. The practitioners do see a lot of potential for DDDM in an agile context; however, currently unfulfilled

How do software architects consider non-functional requirements: an exploratory study

© 2012 IEEE. Personal use of this material is permitted. Permission from IEEE must be obtained for all other uses, in any current or future media, including reprinting/republishing this material for advertising or promotional purposes,creating new collective works, for resale or redistribution to servers or lists, or reuse of any copyrighted component of this work in other works.Dealing with non-functional requirements (NFRs) has posed a challenge onto software engineers for many years. Over the years, many methods and techniques have been proposed to improve their elicitation, documentation, and validation. Knowing more about the state of the practice on these topics may benefit both practitioners' and researchers' daily work. A few empirical studies have been conducted in the past, but none under the perspective of software architects, in spite of the great influence that NFRs have on daily architects' practices. This paper presents some of the findings of an empirical study based on 13 interviews with software architects. It addresses questions such as: who decides the NFRs, what types of NFRs matter to architects, how are NFRs documented, and how are NFRs validated. The results are contextualized with existing previous work.Peer ReviewedPostprint (author’s final draft

Extending IT infrastructures in the service sector organisations through enterprise resource planning – a telecom case study

Copyright @ 2012 ISEing.Service Sector Organisations (SSOs) have significantly focused on adopting and implementing Enterprise Resource Planning (ERP) systems to automate their prime business processes, enhance organisational productivity with lower costs and prompt service delivery to fulfil consumer demands. Thus, ERP systems are considered as a principal source to provide imperative information vital for strategic decision making process. On the contrary, ERP systems adoption and implementation is also highly considered as a challenging and expensive process that not only requires rigorous efforts but also demands to have an exhaustive investigation of influential factors that are critical to the adoption and implementation of ERP systems. As a result, the authors exhibit that it is of great significance to investigate this area within SSOs. In so doing, this paper thus focuses on the ERP critical success factors from five different categories such as: stakeholders; process; technology; organisation; and project based on the literature analysis. These perspectives comprise of 24 factors that are imperative for a successful ERP adoption and implementation. These factors are validated through an in-depth qualitative single case study based research. The findings from the literature and empirical demonstrate that most of the factors influencing the decision making process for ERP adoption and implementation are highly significant with exception to few that have either low or medium importance

Towards strategic-decision quality in Flemish municipalities: the importance of strategic planning and stakeholder participation

Legislation put forth by the Flemish government mandated Flemish municipalities to adopt strategic planning for their 2014-2019 policy cycle. The government’s assumption is that strategic planning’s approach to decision-making results in strategic-decision quality. Despite this assumption, it remains unclear whether and how strategic planning actually contributes to municipal decision-making. This study elucidates this issue. Drawing on survey data from 271 informants within 89 Flemish municipalities, we find that the systematic dimension of formal strategic planning and the participation of both core and peripheral stakeholders contribute to strategic-decision quality. However, the analytic dimension of formal strategic planning offers no significant contribution