DOCSLIB.ORG

QFD in SOFTWARE ENGINEERING a Thesis Submitted to Kent State

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
QFD in SOFTWARE ENGINEERING a Thesis Submitted to Kent State QFD IN SOFTWARE ENGINEERING A thesis submitted to Kent State University in partial fulfillment of the requirements for the degree of Master of Science by Leenah O. Alrabghi December, 2013 Thesis written by Leenah O. Alrabghi B.S., King Abdulaziz University, 2006 M.S., Kent State University, 2013 Approved by Dr. Austin Melton Chair, Master Thesis Committee Dr. Arden Ruttan Members, Master Thesis Committee Dr. Paul Farrell Members, Master Thesis Committee Accepted by Dr. Javed Khan Chair, Department of Computer Science Dr. Raymond Craig Associate Dean, College of Arts and Sciences ii TABLE OF CONTENT LIST OF FIGURES ...................................................................................................... VII LIST OF TABLES .......................................................................................................... IX ACKNOWLEDGEMENTS ............................................................................................ X CHAPTER 1 INTRODUCTION ..................................................................................... 1 1.1 Background ............................................................................................................... 1 1.2 Objectives of the Study ............................................................................................. 2 1.3 Research Problem ...................................................................................................... 2 1.4 Scope of the Study ..................................................................................................... 2 1.5 Organization of Thesis .............................................................................................. 3 CHAPTER 2 QFD OVERVIEW ..................................................................................... 4 2.1 Definitions of QFD .................................................................................................... 4 2.2 Difference between QFD and Other Quality Methodologies .................................... 6 2.3 Brief History .............................................................................................................. 7 2.4 Benefits of QFD ........................................................................................................ 8 2.5 Objectives of QFD .................................................................................................. 11 2.6 Applications of QFD ............................................................................................... 12 2.7 Problems and Limitations of QFD .......................................................................... 14 2.8 Quantitative Approaches of QFD ............................................................................ 15 iii 2.8.1 AHP ............................................................................................................... 16 2.8.2 Fuzzy logic .................................................................................................... 16 2.8.3 ANN .............................................................................................................. 18 2.8.4 The Taguchi Method ..................................................................................... 18 2.8.5 Statistically Extended QFD ........................................................................... 20 2.8.6 Dynamic QFD ............................................................................................... 21 CHAPTER 3 THE QFD PROCESS .............................................................................. 22 3.1 Four-Phase Model ................................................................................................... 22 3.2 House of Quality (HOQ) ......................................................................................... 25 3.2.1 Part A. Customer Requirements (WHATs)................................................... 28 3.2.2 The Kano Model............................................................................................ 30 3.2.3 Part B. Planning Matrix (WHYs) .................................................................. 33 3.2.4 Part C. Technical Measures (HOWs) ............................................................ 36 3.2.5 Part D. Relationship Matrix between WHATs and HOWs ........................... 38 3.2.6 Part E. Technical Correlation Matrix ............................................................ 39 3.2.7 Part F. Technical Matrix................................................................................ 41 3.3 Numerical Example ................................................................................................. 44 3.3.1 The HOQ ....................................................................................................... 53 3.3.2 The Complete QFD ....................................................................................... 55 CHAPTER 4 ATTEMPTS TO USE QFD IN SOFTWARE DEVELOPMENT ...... 57 4.1 Zultner’s Software Quality Deployment (SQD) Approach ..................................... 57 iv 4.2 Blitz QFD ................................................................................................................ 62 4.3 Shindo’s Approach .................................................................................................. 65 4.4 Ohmori’s Model ...................................................................................................... 66 4.5 Herzwurm, Schockert, and Mellis PriFo Software QFD Model ............................. 68 4.6 Liu’s Software QFD ................................................................................................ 71 4.7 Experiences with Software QFD ............................................................................. 73 CHAPTER 5 IDENTIFY SOFTWARE ENGINEERING ACTIVITIES THAT ARE QFD STEPS AND FILLIING THE GAPS ....................................................... 79 5.1 Phase 1 ..................................................................................................................... 81 5.1.1 Product Planning in QFD .............................................................................. 81 5.1.2 Requirement Phase in Software Engineering ................................................ 82 5.1.3 How Can a Software Engineer Get Benefits from QFD? ............................. 85 5.1.4 What is QFD Missing? .................................................................................. 89 5.1.5 Suggestions to Improve QFD for Software Engineering .............................. 91 5.2 Phase 2 ..................................................................................................................... 97 5.2.1 Parts Deployment in QFD ............................................................................. 97 5.2.2 Design Phase in Software Engineering ......................................................... 97 5.2.3 How Can a Software Engineer Benefit from QFD? ...................................... 98 5.2.4 What is QFD Missing? .................................................................................. 98 5.2.5 Suggestions to Improve QFD for Software Engineering .............................. 99 v 5.3 Phase 3 ..................................................................................................................... 99 5.3.1 Process Design Phase in QFD ....................................................................... 99 5.3.2 Implementation Phase in Software Engineering ........................................... 99 5.3.3 How Can a Software Engineer Benefit from QFD? .................................... 100 5.3.4 What is QFD Missing? ................................................................................ 100 5.4 Phase 4 ................................................................................................................... 101 5.4.1 Process/Quality Control in QFD ................................................................. 101 5.4.2 Testing Phase in Software Engineering ...................................................... 101 5.5 Phase 5 ................................................................................................................... 102 5.5.1 Maintenance Phase in Software Engineering .............................................. 102 5.6 An Enhanced Software QFD ................................................................................. 103 5.7 A Numerical Example of HOQ ............................................................................. 110 CHAPTER 6 CONCLUSION AND FUTURE WORK ............................................. 114 REFERENCES .............................................................................................................. 118 vi LIST OF FIGURES Figure 2.1. Interpretation of Japanese characters for QFD. ................................................ 5 Figure 2.2. Japanese automakers with QFD made fewer changes than did U.S. companies without QFD. ............................................................................................................... 9 Figure 3.1. The four-phase model of QFD. ...................................................................... 23 Figure 3.2. Brief description of the HOQ. ........................................................................ 26 Figure 3.3. Detailed description of the HOQ. ................................................................... 27 Figure 3.4. The Kano model. ...........................................................................................
Load more

Recommended publications
  • Quality Management for IT Support Services - a Case Study of an IT Helpdesk Service
    Quality Management for IT Support Services - A case study of an IT helpdesk service Master of Science Thesis in the Master Degree Programme, Quality and Operations Management JOHANNA IVARSSON Department of Technology Management and Economics Division of Quality Sciences CHALMERS UNIVERSITY OF TECHNOLOGY Gothenburg, Sweden 2013 Report No. E2013:080 REPORT NO. E2013:080 QUALITY MANAGEMENT FOR IT SUPPORT SERVICES A CASE STUDY OF AN IT HELPDESK SERVICE JOHANNA IVARSSON Department of Technology Management and Economics Chalmers University of Technology Göteborg, Sweden QUALITY MANAGEMENT FOR IT SUPPORT SERVICES A CASE STUDY OF AN IT HELPDESK SERVICE JOHANNA IVARSSON © Ivarsson, J. 2013 Report no. E2013:080 Department of Technology Management and Economics Division of Quality Sciences Chalmers University of Technology SE-412 96 Göteborg Sweden Telephone: + 46 (0)31-772 1000 Printed by Chalmers Reproservice Göteborg, Sweden 2013 Abstract IT services are a necessary support for most business processes; therefore the quality of IT support services is a topic of high importance. The aim of this study was to analyse how an IT helpdesk service can be improved in order to align with the organisation’s expectations. The study was conducted as a case study of an IT helpdesk service during spring 2013. The data collection combined a quantitative analysis of event logs data for a two-year period, with a qualitative approach conducting observations and ten interviews. The result showed that the quality issues arose from two main areas; resolution time of requests and professionalism of IT staff. The quality issues are, according to both the quantitative and qualitative analysis, caused by high workload for one of the IT department’s teams and high expectations of the organisation.
    [Show full text]
  • Innovations in Natural Language Document Processing for Requirements Engineering
    Calhoun: The NPS Institutional Archive Faculty and Researcher Publications Faculty and Researcher Publications 2008 Innovations in Natural Language Document Processing for Requirements Engineering Berzins, Valdis þÿB. Paech and C. Martell (Eds.): Monterey Workshop 2007, LNCS 5320, pp. 125 146, 2008. http://hdl.handle.net/10945/46073 Innovations in Natural Language Document Processing for Requirements Engineering Valdis Berzins, Craig Martell, Luqi, and Paige Adams Naval Postgraduate School, 1411 Cunningham Road, Monterey, California 93943 {berzins,cmartell,luqi,phadams}@nps.edu Abstract. This paper evaluates the potential contributions of natural language processing to requirements engineering. We present a selective history of the relationship between requirements engineering (RE) and natural-language processing (NLP), and briefly summarize relevant re- cent trends in NLP. The paper outlines basic issues in RE and how they relate to interactions between a NLP front end and system-development processes. We suggest some improvements to NLP that may be possible in the context of RE and conclude with an assessment of what should be done to improve likelihood of practical impact in this direction. Keywords: Requirements, Natural Language, Ambiguity, Gaps, Domain- Specific Methods. 1 Introduction A major challenge in requirements engineering is dealing with changes, especially in the context of systems of systems with correspondingly complex stakeholder communities and critical systems with stringent dependability requirements. Documentation driven development (DDD) is a recently developed approach for addressing these issues that seeks to simultaneously improve agility and de- pendability via computer assistance centered on a variety of documents [1,2]. The approach is based on a new view of documents as computationally active knowledge bases that support computer aid for many software engineering tasks from requirements engineering to system evolution, which is quite different from the traditional view of documents as passive pieces of paper.
    [Show full text]
  • Managing Requirements Engineering Risks: an Analysis and Synthesis of the Literature
    Lars Mathiassen – Timo Saarinen – Tuure Tuunanen – Matti Rossi MANAGING REQUIREMENTS ENGINEERING RISKS: AN ANALYSIS AND SYNTHESIS OF THE LITERATURE W-379 HELSINKI SCHOOL OF ECONOMICS ISSN 1795-1828 WORKING PAPERS ISBN 951-791-895-X (Electronic working paper) W-379 2004 Lars Mathiassen* – Timo Saarinen** – Tuure Tuunanen** – Matti Rossi** MANAGING REQUIREMENTS ENGINEERING RISKS: AN ANALYSIS AND SYNTHESIS OF THE LITERATURE *Center for Process Innovation, Georgia State University **Helsinki School Economics, Department of Management, Information Systems Science November 2004 HELSINGIN KAUPPAKORKEAKOULU HELSINKI SCHOOL OF ECONOMICS WORKING PAPERS W-379 HELSINGIN KAUPPAKORKEAKOULU HELSINKI SCHOOL OF ECONOMICS PL 1210 FIN-00101 HELSINKI FINLAND © Lars Mathiassen, Timo Saarinen, Tuure Tuunanen, Matti Rossi and Helsinki School of Economics ISSN 1795-1828 ISBN 951-791-895-X (Electronic working paper) Helsinki School of Economics - HeSE print 2004 Managing Requirements Engineering Risks: An Analysis and Synthesis of the Literature Lars Mathiassen ([email protected]) Center for Process Innovation, Georgia State University P. O. Box 4015, Atlanta, GA 30303-4015, USA Phone: +1-404-651-0933, Fax: +1-404-463-9292 Timo Saarinen ([email protected]) Helsinki School Economics, Department of Management, Information Systems Science P. O. Box 1210, FIN-00101 Helsinki, Finland Phone: +358-9-431-38272, Fax: Fax: +358-9-431-38700 Tuure Tuunanen ([email protected]) Helsinki School Economics, Department of Management, Information Systems Science P. O. Box 1210, FIN-00101 Helsinki, Finland Phone: +358-40-544-5591, Fax: +358-9-431-38700 http://www.tuunanen.fi Matti Rossi ([email protected]) Helsinki School Economics, Department of Management, Information Systems Science P.
    [Show full text]
  • Requirements Management Applied in an Agile Project Management Environment
    Requirements Management applied in an agile Project Management environment Franco (Frank) Curtolo CEng, Principal Consultant, Program Planning Professionals Ltd, [email protected] Categorisation • Accessibility: PRACTITIONER • Application: GOOD PRACTICE • Topics: Agile Systems Engineering; Project Management Abstract This paper looks at how the Requirements Management process of Systems Engineering may benefit from some of the aspects derived from developing systems within an agile Project Management environment, using as example, the Scaled Agile Framework® of © Scaled Agile, Inc. The aim is to see if some of these agile techniques can enhance the Systems Engineering approach. Systems Engineering (SE) is well suited to develop large, complex products in a project environment where the requirements can be defined and fixed upfront. In fact, SE relies on an initial, well-defined End User’s need specified in for example, a User Requirements Specification (URS), to establish an initial requirements baseline which is used to drive the rest of the development process. However not all development projects happen that way. Sometimes the End User’s need is not clear, or cannot be well defined upfront, thus not allowing it to be captured in a fixed requirements baseline. Furthermore, the project environment may need to accommodate rapid change, both in the End Users’ need and in the technologies available to satisfy this need. In such a project environment, an agile development approach, as described in the Scaled Agile Framework® (SAFe®), may be more suitable since it allows for incremental delivery of the product and change to requirements. This can accommodate undefined End User needs, rapid change in requirements and allow for the introduction of innovation during the development and implementation stages.
    [Show full text]
  • Requirements Engineering Objectives
    Requirements Engineering Chapter 2 Requirements Engineering Processes Learning Objective ...to give a general introduction to the requirements engineering process. Different approaches to modeling requirements engineering processes are suggested and why human, social and organizational factors are important influences on those processes. Other concepts that are evaluated include process maturity, tools and process improvement. Frederick T Sheldon Assistant Professor of Computer Science University of Colorado at Colorado Springs CS 531 Software Requirements Analysis and Specification Chapter 2 From Requirements Engineering Processes and Techniques by G. Kotonya and I. Sommerville 1998 Slide 1 Objectives ⊗ To introduce the notion of processes and process models for requirements engineering ⊗ To explain the critical role of people in requirements engineering processes ⊗ To explain why process improvements is important and to suggest a process improvement model for requirements engineering CS 531 Software Requirements Analysis and Specification Chapter 2 From Requirements Engineering Processes and Techniques by G. Kotonya and I. Sommerville 1998 Slide 2 Processes ⊗ A process is an organized set of activities which transforms inputs to outputs ⊗ Process descriptions encapsulate knowledge and allow it to be reused ⊗ Examples of process descriptions • Instruction manual for a dishwasher • Cookery book • Procedures manual for a bank • Quality manual for software development CS 531 Software Requirements Analysis and Specification Chapter 2 From Requirements Engineering Processes and Techniques by G. Kotonya and I. Sommerville 1998 Slide 3 Design processes ⊗ Processes which involve creativity, interactions between a wide range of different people, engineering judgement and background knowledge and experience ⊗ Examples of design processes • Writing a book • Organizing a conference • Designing a processor chip • Requirements engineering CS 531 Software Requirements Analysis and Specification Chapter 2 From Requirements Engineering Processes and Techniques by G.
    [Show full text]
  • Elicitation of Quality Agile User Stories Using QFD
    Elicitation of Quality Agile User Stories Using QFD NDIA 20th Annual Systems Engineering Conference “Agile in Systems Engineering“ 10:15 – 10:40 AM October 25, 2017 Sabrina J. Ussery, Shahryar Sarkani, Thomas Holzer Dissertation Topic Department of Engineering Management and Systems Engineering School of Engineering and Applied Science The George Washington University 1176 G Street NW Washington, DC 20052 1 Agile Requirements Engineering (RE) The lack of standard Requirements Engineering (RE) practices in Agile negatively impacts system quality, contributing to 24% of the causes for challenged or failed projects. • The 2015 CHAOS Standish Group report indicates Agile projects are 3x more likely to succeed than Waterfall projects due to increased customer collaboration and customer satisfaction. [2] • The Agile community claims that they do not really tackle requirements in a structured way, which may bring problems to the software organization responsible for software built following an Agile method. [1] • Though more successful in some respects, the Image source: [2] lack of stand RE practices in Agile contributes to 24% of the reasons for challenged or failed projects due to poor requirements quality (i.e., unclear or volatile). [2] 2 What is Agile? 3 Agile RE: As Is Requirements Requirements engineering (RE) refers to the process of defining, documenting and maintainingEngineering requirements. [5] Requirements Requirements Development Management Elicitation Priorities Specification Traceability Analysis Specifications Validation Configuration
    [Show full text]
  • Integrated Requirements Engineering: a Tutorial
    focusrequirements engineering1 Integrated Requirements Engineering: A Tutorial Ian Sommerville, Lancaster University efore developing any system, you must understand what the sys- tem is supposed to do and how its use can support the goals of the individuals or business that will pay for that system. This in- B volves understanding the application domain (telecommunica- tions, railways, retail banking, games, and so on); the system’s operational constraints; the specific functionality required by the stakeholders (the peo- ple who directly or indirectly use the system or the information it provides); and essential system characteristics such as The fundamental process performance, security, and dependability. Re- The RE process varies immensely depend- quirements engineering is the name given to a ing on the type of application being devel- structured set of activities that help develop oped, the size and culture of the companies in- this understanding and that document the sys- volved, and the software acquisition processes tem specification for the stakeholders and en- used. For large military and aerospace sys- gineers involved in the system development. tems, there is normally a formal RE stage in This short tutorial introduces the funda- the systems engineering processes and an ex- mental activities of RE and discusses how it tensively documented set of system and soft- has evolved as part of the software engineering ware requirements. For small companies de- process. However, rather than focus on estab- veloping innovative software products, the RE lished RE techniques, I discuss how the chang- process might consist of brainstorming ses- ing nature of software engineering has led to sions, and the product “requirements” might new challenges for RE.
    [Show full text]
  • A Requirements Modeling Language for the Component Behavior of Cyber Physical Robotics Systems
    A Requirements Modeling Language for the Component Behavior of Cyber Physical Robotics Systems Jan Oliver Ringert, Bernhard Rumpe, and Andreas Wortmann RWTH Aachen University, Software Engineering, Aachen, Germany {ringert,rumpe,wortmann}@se-rwth.de Abstract. Software development for robotics applications is a sophisticated en- deavor as robots are inherently complex. Explicit modeling of the architecture and behavior of robotics application yields many advantages to cope with this complexity by identifying and separating logically and physically independent components and by hierarchically structuring the system under development. On top of component and connector models we propose modeling the requirements on the behavior of robotics software components using I/O! automata [29]. This approach facilitates early simulation of requirements model, allows to subject these to formal analysis and to generate the software from them. In this paper, we introduce an extension of the architecture description language MontiArc to model the requirements on components with I/O! automata, which are defined in the spirit of Martin Glinz’ Statecharts for requirements modeling [10]. We fur- thermore present a case study based on a robotics application generated for the Lego NXT robotic platform. “In der Robotik dachte man vor 30 Jahren, dass man heute alles perfekt beherrschen würde”, Martin Glinz [38] 1 Introduction Robotics is a field of Cyber-Physical Systems (CPS) which yields complex challenges due to the variety of robots, their forms of use and the overwhelming complexity of the possible environments they have to operate in. Software development for robotics ap- plications is still at least as complex as it was 30 years ago: even a simple robot requires the integration of multiple distributed software components.
    [Show full text]
  • Collecting and Analyzing Requirements Related Software Project Queries
    Collecting and Analyzing Requirements Related Software Project Queries Sugandha Malviya*, Jane Cleland-Huang**, and Alexander Rasin* *DePaul University, College of Computing and Digital Media, Chicago, IL **University of Notre Dame, South Bend, Indiana [email protected], [email protected], [email protected] Abstract Project data is often underutilized due to lack of accessibility and difficulties users have in constructing the non-trivial SQL queries that are often needed to support realistic Software Engineering questions. In our prior work we therefore presented TiQi – a natural language interface which allows users to issue trace queries in their own words. We initially collected sample queries from a limited number of industrial stakeholders, and utilized these to evaluate our proof of concept solution. As the work has matured, we have collected and analyzed a far more extensive set of trace queries from which we derive additional requirements for TiQi and construct a more challenging evaluation context. This paper not only describes the collected queries and their derived requirements, but discusses the need for iteratively building realistic benchmarks when engaging in research design projects. 1 TiQi: A Quick Overview All software and systems engineering projects accumulate large amounts of artifacts in the form of requirements, design artifacts, code, test cases, project scheduling, fault logs, and other such data. This collection of data represents a valuable resource for managing various aspects of a software project; however, in practice it is often underutilized primarily because of the difficulties in accessing and retrieving it from heterogeneous data stores and then using it to formulate useful queries. To alleviate this problem, we have developed a natural language query interface, named TiQi for use in Software Engineering projects [1, 2].
    [Show full text]
  • Tool Demo) Benoît Ries, Alfredo Capozucca and Nicolas Guelfi University of Luxembourg, Esch-Sur-Alzette, Luxembourg
    Messir: A Text-First DSL-Based Approach for UML Requirements Engineering (Tool Demo) Benoît Ries, Alfredo Capozucca and Nicolas Guelfi University of Luxembourg, Esch-sur-Alzette, Luxembourg Context 2. Messir Textual DSLs Students Feedback Our students surveys on the lectures using Due to the need for (and absence of) Messir/Excalibur resulted, out of 90+ answers, an integrated requirements engineering tool Messir Constraint Messir Validation Rules in a majority of students agreeing both on centered on a textual specification language, Language Documentation "recommending the lectures to others", and providing rich coverage of UML, report • A number of syntactical Language that "the learning resources met their needs". generation, and formal simulation to be used validation rules are generated • declarative specification of Positive comments were "the integrated hands-on by our students at University of Luxembourg, automatically by the XText operations • complementary textual approach" and "the report generation". Negative in our software engineering project-based framework based on the • syntax inspired from OCL language comments were mostly about "the actual presence lectures, we have started to develop the Messir DSL grammar. • semantics defined as a manual • natural language descriptions of bugs in the tool". Excalibur workbench and Messir DSLs. • We have implemented 50 translation to prolog used during report generation additional runtime validation • covered concepts include: • allow documenting Messir Conclusion rules used as educational
    [Show full text]
  • Quality Engineering in The
    QUALITY ENGINEERING IN THE NEW A vision and R&D update from Accenture Labs and Accenture Testing Services QUALITY ENGINEERING WITH BUSINESS PURPOSE In recent years, traditional approaches to application testing have been significantly disrupted with the advent of DevOps and intelligent automation, as well as proliferation of digital applications. As delivery timelines have shrunk from months to weeks and now days, testing has shifted both left and right in the software development lifecycle. DevOps and agile have merged development and testing into a single continuous activity. Testing has evolved to quality engineering that begins upfront as part of initial application planning and establishes a continuous feedback loop to anticipate and act on the unknown. But to truly understand the scale of evolution from testing to quality engineering, we need to recognize how data has changed software development itself. The power of data goes well beyond fueling automation use cases and AI learning datasets for repetitive development and testing tasks. The massive amounts of data users generate every day is now elevating quality engineers to predict risk, identify opportunities, increase speed and agility and minimize technical debt. With this vast influx of data, the quality engineer’s role has become far more exciting but also complex. It will further evolve as we move towards AI, edge computing and the massive IoT end datasets which require machine-to-machine (M2M) communications with complete autonomy and failsafe protection. Accenture has long been at the forefront of testing innovation, and now we are leading our clients into the world of quality engineering at scale.
    [Show full text]
  • An Empirical Study of Data Constraint Implementations in Java
    Preprint An empirical study of data constraint implementations in Java Juan Manuel Florez · Laura Moreno · Zenong Zhang · Shiyi Wei · Andrian Marcus Abstract Software systems are designed according to guidelines and con- straints defined by business rules. Some of these constraints define the allow- able or required values for data handled by the systems. These data constraints usually originate from the problem domain (e.g., regulations), and developers must write code that enforces them. Understanding how data constraints are implemented is essential for testing, debugging, and software change. Unfor- tunately, there are no widely-accepted guidelines or best practices on how to implement data constraints. This paper presents an empirical study that investigates how data con- straints are implemented in Java. We study the implementation of 187 data constraints extracted from the documentation of eight real-world Java software systems. First, we perform a qualitative analysis of the textual description of data constraints and identify four data constraint types. Second, we manually identify the implementations of these data constraints and reveal that they can be grouped into 30 implementation patterns. The analysis of these imple- mentation patterns indicates that developers prefer a handful of patterns when implementing data constraints and deviations from these patterns are associ- ated with unusual implementation decisions or code smells. Third, we develop a tool-assisted protocol that allows us to identify 256 additional trace links for the data constraints implemented using the 13 most common patterns. We find that almost half of these data constraints have multiple enforcing statements, which are code clones of different types.
    [Show full text]