Patton P., Jayaswal B. — Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software
Обсудите книгу на
Нашли опечатку? Выделите ее мышкой и нажмите Ctrl+Enter
Название: Design for Trustworthy Software: Tools, Techniques, and Methodology of Developing Robust Software
Авторы: Patton P., Jayaswal B.
Аннотация:
This book presents an integrated technology, Design for Trustworthy Software (DFTS), to address software quality issues upstream such that the goal of software quality becomes that of preventing bugs in implementation rather than finding and eliminating them during and after implementation. The thrust of the technology is that major quality deployments take place before a single line of code is written!
This customer-oriented integrated technology can help deliver breakthrough results in cost, quality, and delivery schedule thus meeting and exceeding customer expectations. The authors describe the principles behind the technology as well as their applications to actual software design problems. They present illustrative case studies covering various aspects of DFTS technology including CoSQ, AHP, TRIZ, FMEA, QFD, and Taguchi Methods and provide ample questions and exercises to test the readers understanding of the material in addition to detailed examples of the applications of the technology.
The book can be used to impart organization-wide learning including training for DFTS Black Belts and Master Black Belts. It helps you gain rapid mastery, so you can deploy DFTS Technology quickly and successfully.
Learn how to
• Plan, build,maintain, and improve your trustworthy software development system
• Adapt best practices of quality, leadership, learning, and management for the unique software development milieu
• Listen to the customer’s voice, then guide user expectations to realizable, reliable software products
• Refocus on customer-centered issues such as reliability, dependability, availability, and upgradeability
• Encourage greater design creativity and innovation
• Validate, verify, test, evaluate, integrate, and maintain software for trustworthiness
• Analyze the financial impact of software quality
• Prepare your leadership and infrastructure for DFTS
Design for Trustworthy Software will help you improve quality whether you develop in-house, outsource, consult, or provide support. It offers breakthrough solutions for the entire spectrum of software and quality professionals—from developers to project leaders, chief software architects to customers.
case studies, QFD for new product development, quality tools case studies, QFD for new product development, self-evaluation of NPD efforts case studies, QFD for unprecedented software case studies, railroad MIS functional specification case studies, Ramsay County, Minnesota justice system case studies, RES (Raytheon Electronic Systems)2nd case studies, RES, CoSQ costs and benefits case studies, RES, CoSQ data gathering case studies, RES, CoSQ institutionalization case studies, RES, CoSQ model case studies, RES, CoSQ tracking case studies, RES, difficulties encountered case studies, RES, implications of case studies, RES, lessons learned case studies, RES, predictability case studies, RES, productivity case studies, RES, rework cost savings case studies, RES, ROI results case studies, RES, software improvement initiative case studies, RES, software quality case studies, software field maintenance case studies, Submarine Spitfire case studies, Taguchi Methods for RTOS design verification case studies, Tata Consultancy Services (TCS) case studies, Toyota Production System (TPS) case studies, Toyota Production System (TPS), people case studies, Toyota Production System (TPS), philosophy case studies, Toyota Production System (TPS), planning case studies, Toyota Production System (TPS), production Catastrophic failure cause-and-effect diagrams cause-and-effect diagrams, classifying processes with cause-and-effect diagrams, definition of cause-and-effect diagrams, elements of cause-and-effect diagrams, identifying causes with cause-and-effect diagrams, purpose of cause-and-effect diagrams, recommended applications CBO (Common Business Objects) layer CCM (CORBA Component Model) CEOs CEOs, General Electric (GE) Six Sigma initiative CEOs, role in DFTS implementation Change Change Acceleration Program (CAP) change, Change Acceleration Program (CAP) change, layers of resistance to changing requirements Charts[See also diagrams.] charts, bar charts charts, check sheets charts, check sheets, definition of charts, check sheets, example of charts, Chief Quality Officer (CQO) charts, chunks charts, CIDM (Customer Integrated Decision Making)2nd charts, clarity2nd charts, classes charts, classification of CoSQ (cost of software quality) charts, classification of CoSQ (cost of software quality), appraisal costs charts, classification of CoSQ (cost of software quality), downstream internal failure costs charts, classification of CoSQ (cost of software quality), external failure costs charts, classification of CoSQ (cost of software quality), prevention costs charts, classification of CoSQ (cost of software quality), upstream internal failure costs charts, cleaning up charts, cleanliness charts, CMM (Capability Maturity Model)2nd 3rd 4th charts, CMMI (Capability Maturity Model Integration)2nd 3rd charts, coherent development2nd charts, coherent development, best efforts charts, coherent development, Essential Path Method (EPM) charts, cohesiveness of teams charts, COM+ charts, Combination I.D./Matrix Method (prioritization matrices) charts, Common Business Objects (CBO) layer charts, Common Object Request Broker Architecture (CORBA) charts, communication charts, communication, effective communication charts, communication, failure of charts, communication, management's consensus and commitment, communicating charts, communication, organization-wide consultation and communication charts, control charts charts, control charts, control limits charts, control charts, definition of charts, control charts, R charts charts, control charts, recommended applications charts, control charts, X-Barcharts charts, control charts, XmR charts charts, flowcharts charts, flowcharts, creating charts, flowcharts, definition of charts, flowcharts, detailed flowcharts charts, flowcharts, high-level flowcharts charts, flowcharts, purpose of charts, flowcharts, recommended applications charts, flowcharts, swim lane flowcharts charts, flowcharts, symbols charts, Pareto charts charts, Pareto charts, example of charts, Pareto charts, recommended applications charts, pie charts charts, run charts Compilers complexity complexity, abstract complexity analysis complexity, Analytic Hierarchy Process (AHP) complexity, controlling complexity, IT portfolio alignment complexity, managing in high-tech start-up enterprises complexity, managing in patient record systems complexity, managing in system conversion complexity, of computers complexity, of software2nd complexity, sensitivity to complexity complexity, structuring component-based software development technology Comprehensive QFD computer complexity computer programming automation concept selection concept/architectural FMEA (Failure Modes and Effects Analysis) concurrent implementation Conjoint Analysis Consensus Criteria Method consistency ratios consistent comparison problem consistent performance, achieving with Taguchi Methods Constraints, Theory of (TOC) Constraints, Theory of (TOC), complexity Constraints, Theory of (TOC), layers of resistance to change Constraints, Theory of (TOC), problems Constraints, Theory of (TOC), Thinking Processes Consumer Encounters consumerism content analysis content validity continuous improvement (kaizen) control charts control charts, control limits control charts, definition of control charts, R charts control charts, recommended applications control charts, X-Barcharts control charts, XmR charts control factors control limits control systems control systems, belief systems control systems, boundary systems control systems, diagnostic control systems control systems, feedback control systems
|
|
О проекте