【正文】 Approa ch Group sessi on Group sessi on Goal Pr oduct qua li t y Qu ick d elivery of produc t Ti me Not critica l Cri tica l Nov 23, 2020 SENG 613 QFD 72 SQFD ? QFD for software ? Software Engineering is requirements driven ? Addresses quality issues in software development ? Usually use QFD phase 1 ? Focuses on requirements ? “Hows” vs. functional or nonfunctional requirements ? “How much?s” vs. Testing Nov 23, 2020 SENG 613 QFD 73 How to Apply QFD to SE ? Use for new or upgrade type of projects ? Requirements refinements ? Customer has ideal, developer has solution ? Ideal to know application domain knowledge ? Software for internal use ? Software for general use such as OS, word processor etc. Nov 23, 2020 SENG 613 QFD 74 Presentation Summary ? Disadvantages of SQFD ? Advantages of SQFD ? How to Make SQFD work Nov 23, 2020 SENG 613 QFD 75 Disadvantage of SQFD What Makes QFD Unsuitable for SE ? Time and resources consuming ? Process limitation in iteration support ? Does not support mon language between users and developers ? Documentation requirements ? Focus on quality other than functionality Nov 23, 2020 SENG 613 QFD 76 Benefits of SQFD ? Communications among groups ? Decision justification ? Metrics ? Crosschecking ? Avoid loss of information ? Shortens the SDLC Source: Nov 23, 2020 SENG 613 QFD 77 Advantages of SQFD ? Customer / User involvement ? Focus on customer needs ? Team builder ? Improve product or service quality ? Shorter development cycles ? Lower costs and greater productivity Nov 23, 2020 SENG 613 QFD 78 Advantages of SQFD (2) ? Reduces design changes ? Good for munication, decision making and planning ? Allows for a lot of information in a small space Nov 23, 2020 SENG 613 QFD 79 How to Make SQFD Work ? Obtain management mitment ? Establish clear, upfront objectives ? Strong technical knowhow ? Establish multifunctional team. ? Designate a facilitator ? QFD training Nov 23, 2020 SENG 613 QFD 80 How to Make SQFD Work (2) ? Get an adequate time mitment from team members ? Schedule regular meetings ? Avoid first using QFD on a large, plex project ? Avoid gathering perfect data ? Avoid technical arrogance ? Focus on the important items Nov 23, 2020 SENG 613 QFD 81 Conclusion ? QFD originated in the Manufacturing industry and has been applied to software engineering ? QFD addresses the quality of the product ? SQFD is QFD for software ? QFD, JAD, SSM, PD, RAD and OO all have their merits and faults ? The use of the technique depends on the project Nov 23, 2020 SENG 613 QFD 82 Discussion Nov 23, 2020 SENG 613 QFD 83 Case Study ? We will now look at a case study of a DEC Software Process, DEC TP WORKcenter (Guerrieri and Taylor, 1997). ? We could also cite many automobile case studies which have more depth, but a software example, we felt, was more relevant. Nov 23, 2020 SENG 613 QFD 84 The ACMS TP Project ? DEC TP WORKcenter is Digital?s object based development environment for Application Control and Management System (ACMS) Transaction Processing (TP) applications ? The project team was very experienced and was made up of a team leader, 6 software engineers, a quality engineer, 2 test engineers, and 2 document writers. Nov 23, 2020 SENG 613 QFD 85 Software Engineering at DEC ? The theme for the project was ?use the process, but don?t let the process use you?. ? They evaluated each Software Engineering technique utilized, in a simple yet realistic manner and adjusted each to suit their needs. ? The casestudy contains a list of pros and cons of each technique used during the stages of the software life cycle. Nov 23, 2020 SENG 613 QFD 86 QFD at DEC ? QFD and Contextual Inquiry were used to gather the requirements. ? Past QFD project results were used, where similar functionality was sought, and were found to rapidly advance the requirements stage of the project. ? They did note that the QFD process was viewed as expensive but well worth it for what was returned. Nov 23, 2020 SENG 613 QFD 87 DEC QFD Results ? The QFD technique yielded prioritized lists which were ranked for importance, cost, and benefit. ? They used these lists, along with project market dates, to determine the functions to include. ? The milestones established early on, via QFD, kept them on track during all four phases. Nov 23, 2020 SENG 613 QFD 88 DEC?s Thorns ? Although they used QFD and generated a substantial requirements document (40 pages), they still had a major defect repair list to address before the product was released. ? Part of the issue was the 24 months the project took to plete. Nov 23, 2020 SENG 613 QFD 89 DEC?s Conclusions ? Software development processes should be as simple as possible. ? The team should formally adapt each process to its own needs. ? The team should understand the consequences of modifying each process. ? Keep the requirements specification as short as possible, concise, and only as descriptive