Product Development System
Design Review Business Process Guide
PDS 6.0
July 2005
Copyright ? 2005 Parametric Technology Corporation. All Rights Reserved.
User and training documentation from Parametric Technology Corporation (PTC) is subject to the copyright laws of the United States and other countries and is provided under a license agreement that restricts copying, disclosure, and use of such documentation. PTC hereby grants to the licensed user the right to make copies in printed form of this documentation if provided on software media, but only for
internal/personal use and in accordance with the license agreement under which the applicable software is licensed. Any copy made shall include the PTC copyright notice and any other proprietary notice provided by PTC. This documentation may not be disclosed, transferred, modified, or reduced to any form, including electronic media, or transmitted or made publicly available by any means without the prior written consent of PTC and no authorization is granted to make copies for such purposes.
Information described herein is furnished for general information only, is subject to change without notice, and should not be construed as a warranty or commitment by PTC. PTC assumes no responsibility or liability for any errors or inaccuracies that may appear in this document.
The software described in this document is provided under written license agreement, contains valuable trade secrets and proprietary information, and is protected by the copyright laws of the United States and other countries. It may not be copied or distributed in any form or medium, disclosed to third parties, or used in any manner not provided for in the software licenses agreement except with written prior approval from PTC. UNAUTHORIZED USE OF SOFTWARE OR ITS DOCUMENTATION CAN RESULT IN CIVIL DAMAGES AND CRIMINAL PROSECUTION.
Registered Trademarks of Parametric Technology Corporation or a Subsidiary
Advanced Surface Design, Behavioral Modeling, CADDS, Computervision, CounterPart,
Create Collaborate Control, EPD, EPD.Connect, Expert Machinist, Flexible Engineering, GRANITE, HARNESSDESIGN, Info*Engine, InPart, MECHANICA, Optegra, Parametric Technology,
Parametric Technology Corporation, PartSpeak, PHOTORENDER, Pro/DESKTOP, Pro/E, Pro/ENGINEER, Pro/HELP, Pro/INTRALINK, Pro/MECHANICA, Pro/TOOLKIT, Product First,
Product Development Means Business, Product Makes the Company, PTC, the PTC logo, PT/Products, Shaping Innovation, The Way to Product First, and Windchill.
Trademarks of Parametric Technology Corporation or a Subsidiary
3DPAINT, Associative Topology Bus, AutobuildZ, CDRS, CV, CVact, CVaec, CVdesign, CV-DORS, CVMAC, CVNC, CVToolmaker, EDAcompare, EDAconduit, DataDoctor, DesignSuite, DIMENSION III,
Distributed Services Manager, DIVISION, e/ENGINEER, eNC Explorer, Expert Framework,
Expert MoldBase, Expert Toolmaker, Harmony, InterComm, InterComm Expert, InterComm EDAcompare, InterComm EDAconduit, ISSM, KDiP, Knowledge Discipline in Practice, Knowledge System Driver, ModelCHECK, MoldShop, NC Builder, Pro/ANIMATE, Pro/ASSEMBLY, Pro/CABLING, Pro/CASTING, Pro/CDT, Pro/CMM, Pro/COLLABORATE, Pro/COMPOSITE, Pro/CONCEPT, Pro/CONVERT,
Pro/DATA for PDGS, Pro/DESIGNER, Pro/DETAIL, Pro/DIAGRAM, Pro/DIEFACE, Pro/DRAW, Pro/ECAD, Pro/ENGINE, Pro/FEATURE, Pro/FEM-POST, Pro/FICIENCY, Pro/FLY-THROUGH, Pro/HARNESS,
Pro/INTERFACE, Pro/LANGUAGE, Pro/LEGACY, Pro/LIBRARYACCESS, Pro/MESH, Pro/Model.View, Pro/MOLDESIGN, Pro/NC-ADVANCED, Pro/NC-CHECK, Pro/NC-MILL, Pro/NC-POST,
Pro/NC-SHEETMETAL, Pro/NC-TURN, Pro/NC-WEDM, Pro/NC-Wire EDM, Pro/NETWORK ANIMATOR, Pro/NOTEBOOK, Pro/PDM, Pro/PHOTORENDER, Pro/PIPING, Pro/PLASTIC ADVISOR, Pro/PLOT,
Pro/POWER DESIGN, Pro/PROCESS, Pro/REPORT, Pro/REVIEW, Pro/SCAN-TOOLS,
Pro/SHEETMETAL, Pro/SURFACE, Pro/VERIFY, Pro/Web.Link, Pro/Web.Publish, Pro/WELDING, ProductView, PTC Precision, Routed Systems Designer, Shrinkwrap, Simple Powerful Connected,
The Product Development Company, Wildfire, Windchill DynamicDesignLink, Windchill PartsLink, Windchill PDMLink, Windchill ProjectLink, and Windchill SupplyLink.
Patents of Parametric Technology Corporation or a Subsidiary
Registration numbers and issue dates follow. Additionally, equivalent patents may be issued or pending outside of the United States. Contact PTC for further information.
GB2363208 25-August-2004
GB2365567 10-March-2004
6,665,569 B1 16-December-2003 GB2353115 10-December-2003 6,625,607 B1 23-September-2003 6,580,428 B1 17-June-2003
GB2354684B 02-July-2003
GB2384125 15-October-2003 GB2354096 12-November-2003 GB2354924 24-September-2003 6,608,623 B1 19-August-2003 GB2353376 05-November-2003 GB2354686 15-October-20036,545,671 B1 08-April-2003
GB2354685B 18-June-2003
GB2354683B 04-June-2003
6,608,623 B1 19-August-2003
6,473,673 B1 29-October-2002
GB2354683B 04-June-2003
6,447,223 B1 10-Sept-2002
6,308,144 23-October-2001
5,680,523 21-October-1997
5,838,331 17-November-1998
4,956,771 11-September-1990
5,058,000 15-October-1991
5,140,321 18-August-1992
5,423,023 05-June-1990
4,310,615 21-December-1998
4,310,614 30-April-1996
4,310,614 22-April-1999
5,297,053 22-March-1994
5,513,316 30-April-1996
5,689,711 18-November-1997
5,506,950 09-April-1996
5,428,772 27-June-1995
5,850,535 15-December-1998
5,557,176 09-November-1996
5,561,747 01-October-1996
Third-Party Trademarks
Adobe, Acrobat, Distiller, and the Acrobat logo are trademarks of Adobe Systems Incorporated.
Advanced ClusterProven, ClusterProven, and the ClusterProven design are trademarks or registered trademarks of International Business Machines Corporation in the United States and other countries and are used under license. IBM Corporation does not warrant and is not responsible for the operation of this software product. AIX is a registered trademark of IBM Corporation. Allegro, Cadence, and Concept are registered trademarks of Cadence Design Systems, Inc. Apple, Mac, Mac OS, and Panther are trademarks or registered trademarks of Apple Computer, Inc. AutoCAD and Autodesk Inventor are registered trademarks of Autodesk, Inc. Baan is a registered trademark of Baan Company. CADAM and CATIA are registered trademarks of Dassault Systemes. COACH is a trademark of CADTRAIN, Inc. DOORS is a registered trademark of Telelogic AB. FLEXlm is a trademark of Macrovision Corporation. Geomagic is a registered trademark of Raindrop Geomagic, Inc. EVERSYNC, GROOVE, GROOVEFEST, https://www.doczj.com/doc/bc14740931.html,, GROOVE NETWORKS, iGROOVE, PEERWARE, and the interlocking circles logo are trademarks of Groove Networks, Inc. Helix is a trademark of Microcadam, Inc. HOOPS is a trademark of Tech Soft America, Inc. HP-UX is a registered trademark of Hewlett-Packard Company. I-DEAS, Metaphase, Parasolid, SHERPA, Solid Edge, and Unigraphics are trademarks or registered trademarks of UGS Corp. InstallShield is a registered trademark and service mark of InstallShield Software Corporation in the United States and/or other countries. Intel is a registered trademark of Intel Corporation. IRIX is a registered trademark of Silicon Graphics, Inc. LINUX is a registered trademark of Linus Torvalds. MainWin and Mainsoft are trademarks of Mainsoft Corporation. MatrixOne is a trademark of MatrixOne, Inc. Mentor Graphics and Board Station are registered trademarks and 3D Design, AMPLE, and Design Manager are trademarks of Mentor Graphics Corporation. MEDUSA and STHENO are trademarks of CAD Schroer GmbH. Microsoft, Microsoft Project, Windows, the Windows logo, Windows NT, Visual Basic, and the Visual Basic logo are registered trademarks of Microsoft Corporation in the United States and/or other countries. Netscape and the Netscape N and Ship's Wheel logos are registered trademarks of Netscape Communications Corporation in the U.S. and other countries. Oracle is a registered trademark of Oracle Corporation. OrbixWeb is a registered trademark of IONA Technologies PLC. PDGS is a registered trademark of Ford Motor Company. RAND is a trademark of RAND Worldwide. Rational Rose is a registered trademark of Rational Software Corporation. RetrievalWare is a registered trademark of Convera Corporation. RosettaNet is a trademark and Partner Interface Process and PIP are registered trademarks of RosettaNet, a nonprofit organization. SAP and R/3 are registered trademarks of
SAP AG Germany. SolidWorks is a registered trademark of SolidWorks Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and in other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. Sun, Sun Microsystems, the Sun logo, Solaris, UltraSPARC, Java and all Java based marks, and “The Network is the Computer” are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries. TIBCO, TIBCO Software, TIBCO ActiveEnterprise, TIBCO Designer, TIBCO Enterprise for JMS,
TIBCO Rendezvous, TIBCO TurboXML, TIBCO BusinessWorks are the trademarks or registered trademarks of TIBCO Software Inc. in the United States and other countries. WebEx is a trademark of WebEx Communications, Inc.
Third-Party Technology Information
Certain PTC software products contain licensed third-party technology: Rational Rose 2000E is copyrighted software of Rational Software Corporation. RetrievalWare is copyrighted software of Convera Corporation. VisTools library is copyrighted software of Visual Kinematics, Inc. (VKI) containing confidential trade secret information belonging to VKI. HOOPS graphics system is a proprietary software product of, and is copyrighted by, Tech Soft America, Inc. G-POST is copyrighted software and a registered trademark of Intercim. VERICUT is copyrighted software and a registered trademark of CGTech.
Pro/PLASTIC ADVISOR is powered by Moldflow technology. Moldflow is a registered trademark of Moldflow Corporation. MainWin Dedicated Libraries are copyrighted software of Mainsoft Corporation. The JPEG image output in the Pro/Web.Publish module is based in part on the work of the independent JPEG Group. DFORMD.DLL is copyrighted software from Compaq Computer Corporation and may not be distributed. METIS, developed by George Karypis and Vipin Kumar at the University of Minnesota, can be researched at https://www.doczj.com/doc/bc14740931.html,/~karypis/metis. METIS is ? 1997 Regents of the University of Minnesota. LightWork Libraries are copyrighted by LightWork Design 1990–2001.
Visual Basic for Applications and Internet Explorer is copyrighted software of Microsoft Corporation. Parasolid ? UGS Corp. Windchill Info*Engine Server contains IBM XML Parser for Java Edition and the IBM Lotus XSL Edition. Pop-up calendar components Copyright ? 1998 Netscape Communications Corporation. All Rights Reserved. TECHNOMATIX is copyrighted software and contains proprietary information of Technomatix Technologies Ltd. TIBCO ActiveEnterprise, TIBCO Designer,
TIBCO Enterprise for JMS, TIBCO Rendezvous, TIBCO TurboXML, TIBCO BusinessWorks are provided by TIBCO Software Inc. Technology "Powered by Groove" is provided by Groove Networks, Inc. Technology "Powered by WebEx" is provided by WebEx Communications, Inc. Oracle 8i run-time and Oracle 9i run-time, Copyright ? 2002–2003 Oracle Corporation. Oracle programs provided herein are subject to a
restricted use license and can only be used in conjunction with the PTC software they are provided with. Apache Server, Tomcat, Xalan, Xerces, and Jakarta are technologies developed by, and are copyrighted software of, the Apache Software Foundation (https://www.doczj.com/doc/bc14740931.html,) – their use is subject to the terms and limitations at: https://www.doczj.com/doc/bc14740931.html,. Adobe Acrobat Reader and Adobe Distiller are copyrighted software of Adobe Systems Inc. and are subject to the Adobe End-User License Agreement as provided by Adobe with those products. UnZip (? 1990-2001 Info-ZIP, All Rights Reserved) is provided “AS IS” and WITHOUT WARRANTY OF ANY KIND. For the complete Info-ZIP license see
ftp://https://www.doczj.com/doc/bc14740931.html,/pub/infozip/license.html. The Java? Telnet Applet (StatusPeer.java, TelnetIO.java, TelnetWrapper.java, TimedOutException.java), Copyright ? 1996, 97 Mattias L. Jugel, Marcus Mei?ner, is redistributed under the GNU General Public License. This license is from the original copyright holder and the Applet is provided WITHOUT WARRANTY OF ANY KIND. You may obtain a copy of the source code for the Applet at http://www.mud.de/se/jta (for a charge of no more than the cost of physically performing the source distribution), by sending e-mail to leo@mud.de or marcus@mud.de—you are allowed to choose either distribution method. The source code is likewise provided under the GNU General Public License. GTK+ - The GIMP Toolkit is licensed under the GNU Library General Public License (LGPL). You may obtain a copy of the source code at https://www.doczj.com/doc/bc14740931.html,, which is likewise provided under the GNU LGPL. zlib software Copyright ? 1995-2002 Jean-loup Gailly and Mark Adler. OmniORB is distributed under the terms and conditions of the GNU General Public License and GNU Library General Public License. The Java Getopt.jar file, copyright 1987-1997 Free Software Foundation, Inc.; Java Port copyright 1998 by Aaron M. Renn (arenn@https://www.doczj.com/doc/bc14740931.html,), is redistributed under the GNU LGPL. You may obtain a copy of the source code at https://www.doczj.com/doc/bc14740931.html,/arenn/hacking/download.html. The source code is likewise provided under the GNU LGPL. This product may include software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (https://www.doczj.com/doc/bc14740931.html,): Copyright ? 1998-2003 The OpenSSL Project. All rights reserved. This product may include cryptographic software written by Eric Young
(eay@https://www.doczj.com/doc/bc14740931.html,). Gecko and Mozilla components are subject to the Mozilla Public License Version 1.1 at https://www.doczj.com/doc/bc14740931.html,/MPL. Software distributed under the Mozilla Public License (MPL) is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either expressed or implied. See the MPL for the specific language governing rights and limitations. Mozilla Japanese localization components are subject to the Netscape Public License Version 1.1 (at https://www.doczj.com/doc/bc14740931.html,/NPL). Software distributed under the Netscape Public License (NPL) is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either expressed or implied (see the NPL for the rights and limitations that are governing different languages). The Original Code is Mozilla Communicator client code, released March 31, 1998 and the Initial Developer of the Original Code is Netscape Communications Corporation. Portions created by Netscape are Copyright ? 1998 Netscape Communications Corporation. All Rights Reserved. Contributors: Kazu Yamamoto (kazu@mozilla.gr.jp), Ryoichi Furukawa (furu@mozilla.gr.jp), Tsukasa Maruyama
(mal@mozilla.gr.jp), Teiji Matsuba (matsuba@https://www.doczj.com/doc/bc14740931.html,).
UNITED STATES GOVERNMENT RESTRICTED RIGHTS LEGEND
This document and the software described herein are Commercial Computer Documentation and Software, pursuant to FAR 12.212(a)-(b) (OCT’95) or DFARS 227.7202-1(a) and 227.7202-3(a) (JUN’95), and are provided to the US Government under a limited commercial license only. For procurements predating the above clauses, use, duplication, or disclosure by the Government is subject to the restrictions set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software Clause at
DFARS 252.227-7013 (OCT’88) or Commercial Computer Software-Restricted Rights at
FAR 52.227-19(c)(1)-(2) (JUN’87), as applicable. 010505 Parametric Technology Corporation, 140 Kendrick Street, Needham, MA 02494 USA
Contents
Change Record (v)
About This Guide (vii)
Preface (vii)
What Is the Design Review Process Guide? (vii)
Comments (viii)
Background of Design Reviews........................................................................1-1 Overview of Design Reviews.....................................................................................................1-2 Design Reviews of the Past.......................................................................................................1-2 Market Trends of Collaborative Product Development..............................................................1-4 Types of Design Reviews..........................................................................................................1-6 The Value of Design Reviews in the Development Process......................................................1-7 Common Objectives of Successful Design Reviews.................................................................1-8 The Relationship Between Design Reviews and Other Business Processes............................1-9 Overview of the Design Review Process.........................................................2-1 Objectives of the Design Review Process.................................................................................2-2 Fundamental Concepts..............................................................................................................2-2 Teams and Roles Involved in Design Reviews....................................................................2-2 Maturity of Items...................................................................................................................2-2 The Capabilities of an Informal Design Review Process...........................................................2-2 Share Design Items..............................................................................................................2-3 Subscribing to Design Items................................................................................................2-4 Accessing Related Design Items.........................................................................................2-5 Discussing Design Items......................................................................................................2-5 Share the Design Item with external partners, customers or suppliers................................2-7 Route the Design Item in Windchill ProjectLink....................................................................2-9 Review the Design Items in DIVISION Reality or ProductView..........................................2-10 The Steps of the Formal Design Review Process...................................................................2-11 Step 1: Prepare Items for Review......................................................................................2-11 Step 2: Initiate a Review....................................................................................................2-12 Step 3: Notify Reviewers of Assignment............................................................................2-13 Step 4: Conduct the Review...............................................................................................2-13 Step 5: Record Comments and Decisions.........................................................................2-15 Examples of the Design Review Process................................................................................2-16
v
An Example Model Design Team Development Use Case...............................................2-16 The Design Review Process and the PDS Roadmap......................................3-1 The PDS Adoption Roadmap....................................................................................................3-2 What are Processes and Scenarios?........................................................................................3-2 Growing the Design Review Process........................................................................................3-3
vi Product Development System Design Review Business Process Guide
Change Record
Chapter Description
Book-level change Updated guide for PDS 6.0.
v
About This Guide
Preface
Business Process Guides are process-oriented descriptions of how PTC’s Product
Development System (PDS) supports common Product Development processes.
The goal of a Business Process Guide is to:
? Define recommended business process steps and activities that could be
performed by a Product Development organization using PTC’s PDS.
? Provide a common understanding of concepts and terminology relevant to
the business process.
A Business Process Guide is designed for use in conjunction with a Validated
Process document. Validated Process documents describe the paths through PTC
PDS software that are used to test a given business process. The goal of a
Validated Process document is to:
? Describe the scope of process-oriented testing in the PTC PDS Quality
Systems Test Group
? Provide implementation guidance by illustrating detailed use cases.
Standard product documentation which is functionality-oriented rather than
process-oriented, should be referenced for more detailed descriptions of exactly
how specific capabilities work and are used.
Note: This document describes an on-premise deployment of Windchill
and, therefore, may cover functionality that is not available to customers of
PTC’s hosted PLM On Demand Standard service. For specific details, refer to the
user's guides for your PTC PLM On Demand offering.
What Is the Design Review Process Guide?
This is a guide to using PTC’s Product Development System (PDS) to manage
the design review process. In this document, you will learn about:
vii
? Recommended methods and techniques for performing design reviews
? Capabilities within the PDS that support and manage the design review
process
This process guide has a different focus than typical product documentation. It is
process-focused, while product documentation is functionality-focused. Here you
will find general descriptions of the activities you will perform at various steps in
the change process, and descriptions of the appropriate PDS capabilities to help
you accomplish these activities. The emphasis is on the Design Review Process.
This guide should be used in conjunction with PDS 5.0, which should be
referenced for more detailed descriptions of exactly how specific capabilities
work and are used.
The overall methodology and procedures described here are the result of
countless consultant and customer experiences. They collectively provide the
best approach to design review; however, it is understood that every company
manages their Design Review Process differently. Accordingly, the tools in the
PDS have been designed as flexible solutions that are scalable and modular
enough to be adopted, in whole or in part, to your established change
management methodology. Because of this, we encourage you to explore the
ideas presented here, even if you have an established methodology in place.
Some minor modification inspired by an idea described here could make your
change process more efficient, making your investment in reading this guide
worthwhile.
Comments
PTC welcomes your suggestions and comments on its documentation—send
comments to the following address:
documentation@https://www.doczj.com/doc/bc14740931.html,
Please include the name of the application and its release number with your
comments. For online books, provide the book title.
viii Product Development System Design Review Business Process Guide
1 Background of Design Reviews
1-1
Overview of Design Reviews
The Design Review activity is a critical component of an organization’s overall
product development process to develop and deliver successful products to the
marketplace. While the transformation of ideas and concepts into new products
may take many paths, a balanced, constructive approach is needed to validate
these concepts, designs and detailed plans so that these new products are
successful.
“What would cost one dollar to fix at requirements phase, would cost five
dollars to fix during detailed design, ten dollars to fix during design
implementation, fifty dollars to fix during system test, and one hundred
dollars after delivery.” (Boehm, B. "Software Engineering," IEEE Transactions
on Computers, Vol.C-25(12),December, 1976.). While this reference is for the
software industry, the dynamics are similar for other types of product
development.
At one point or another, everyone has recognized the benefits of products that
were well designed and developed. Whether it is an appliance for your home, a
computer you use at work, a car, bike or train you recently rode to your
destination, or that favorite recreation item, that product met or exceeded your
needs. Truly successful products don’t just happen; it is hard work from diverse
team members who can effectively share ideas and build consensus in the overall
product definition, design and manufacturing processes. Effective design reviews
are a critical tool to the overall development effort but, more importantly – to the
results!
Likewise, everyone has used a product that has failed to meet their expectations.
Whether the product was of poor quality, unacceptable reliability or grossly
inadequate for the proposed purpose, the results are a frustrating experience for
the customer and the company that introduced that product to the market. Design
reviews are one tool that can help a development team reduce unnecessary risks
and to deliver a better solution by evaluating the proposed product before
significant company resources have been committed to deliver it to market.
Design Reviews of the Past
In the past, Design Reviews have been a very labor-intensive, ineffective process
to prepare and execute.
In the past, to prepare for a formal design review, the designer would:
? Print out the appropriate review materials (Models, Drawings, Parts Lists,
specifications and associated documents) for the review
? Make copies of the review materials for participants
? Build review packages and distribute review materials before the meeting to
local and remote participants
During the review process, the designers hosting the review would need to:
? Create presentation materials or explain existing sets of materials for review
1-2 Product Development System Design Review Business Process Guide
? Manage multiple handwritten comments on review materials from reviewers
? Track issues lists and resolutions
After the review session, the designers would be responsible for:
? Updating the review materials and manually re-routing to confirm issue
resolution
? Manually maintaining the approval signature page for each design and
tracking signatures
? Submitting final design materials to the configuration control team
While Design Reviews were setup to help improve the overall design, ensure
requirements were adequately met, promote consistency of design, minimize
manufacturability costs and other goals, the efforts to prepare and execute Design
Reviews sometimes caused several problems:
? Too much valuable design time was spent preparing for design reviews,
sometimes freezing designs earlier than desired
? Too much valuable design time was spent managing the complex feedback of the designs and the approval process
? Difficult to provide traceability for issues raised and resolutions (especially
for complex feedback on 3D models and drawings)
? Inadequate review of design materials among cross-functional teams
? Inadequate review of the product as a whole (or system wide level)
Some additional example issues that organizations identified for Design Review
processes are discussed in an article Ex-SE: Design Reviews - Background
Information on Best Practices in Manufacturing web site. This article highlights:
“Design reviews are extremely important because, in limiting technical risk and
assessing design maturity, they are of proven benefit to development projects and
DoD procurement. They are often misunderstood, misused, and underutilized in
the design process. Other design review problems:
? Viewed as mandated "dog and pony shows" for government clients or senior management
? Thought useful only if they comply with military standards.
? Omitted due to lack of time and budget (low-level technical reviews)
? Expected to present only "good news;" "bad news" is postponed due to
anticipated, but often unrealized, solutions
? Focused on success or adhering to a schedule (rather than finding unmet
requirements)
? Expected to cover too much material at too fast a pace with too little
preparation”
Background of Design Reviews 1-3
See more information here: https://www.doczj.com/doc/bc14740931.html,/library/books/ex-
se/0003e4f5.html.
So while companies acknowledge the need to perform design reviews, they have
been difficult to plan and execute effectively. Some organizations recognized that
other types of design reviews could be held to help reach some of the goals of
design reviews while minimizing risk and helping maintain development
schedules.
Market Trends of Collaborative Product Development
At one time or another, you may have heard about needs for product
development teams to respond more quickly as market competition increases and
becomes more global. Many product development teams actively work toward
reducing the times to define and develop products so that they can remain
competitive in the market.
In a recent survey of more than 400 companies by the Product Development
Management Association (PDMA), many companies reported that their average
product development cycle times reduced significantly as described in the table
below.
Product Development Cycle Times
Type of Product
1995
(in Months)
2003
(in Months) Range Average Median Range Average Median
New-to-the
World
3-120 41.7 30 2-129 24.0 18
Major
Revisions
3-48 18.1 12 1-69 14.2 11 Incremental 0.5-24 7.6 6 0.5-41 6.7 4.6
Source: PDMA Comparative Performance Assessment Study Results, 2004
These results dramatically illustrate how significant the reduction of development
cycle times has been within many manufacturing companies.
To respond to these market pressures, many companies are adopting strategies to
facilitate more effective early product definition and analysis. Accord to the same
PDMA study, more than 38% of the time companies use rapid prototyping or
FMEA systems as part of their product development processes. The usage of
these types systems continues to increase since the original survey of 1995.
1-4 Product Development System Design Review Business Process Guide
Background of Design Reviews
1-5
Many companies are incorporating early stage design reviews to help provide high more innovative design within their products. Not only do these early
reviews provide an important tool to mitigate risk; when the organization decides to incorporate system wide early stage design reviews, overall product designs may be greatly improved before too much cost has been committed by the organization into an existing design.
As aircraft manufacturers are driven to provide more sophisticated capabilities to pilots and passengers within planes, the challenge of making these capabilities easily understandable, usable and consistent with safety consideration is critical
to ensure realized benefits of the new capabilities.
Here are some industry examples of how organizations are using high impact design review capabilities to help deliver better products to customers.
Early stage prototyping - From a Desktop Engineering Online, February 2003
article: The U.S. Army used to redesign its tanks, transport vehicles, and
weapons-launching platforms over a 20-year period, during which it paid for
numerous costly prototypes. However, under a government plan launched in
2000, the Army had just eight years to design a lighter, tougher, more
technologically advanced array of vehicles and war machines. With little time
left for multiple prototypes, the Army turned to virtual prototyping with
advanced visualization technology. See the entire article here:
https://www.doczj.com/doc/bc14740931.html,/articles/03/feb/cover/main.htm.
In Best Practices for Manufacturing, a web site funded by the U.S. Navy which is
dedicated for sharing best practices across industries, ITT
Aerospace/Communications Division identifies how they improve their product
development processes by using 3D prototyping early in their product
development phase to help review approaches and find better solutions. See the
entire article here (https://www.doczj.com/doc/bc14740931.html,/bestpractices/internal/itt/itt_23.html).
Driving to better products through cultural change - In Automotive Design
and Production, there is an article on the Culture and the Improvement of the
Design Process which identifies how some companies use early stage
development processes to facilitate more innovative product development and a
review of a recent book by Michael Schrage, How the World’s Best Companies
Simulate to Innovate. Schrage’s premise is: What’s important is that these ideas
take form in such a way that other people can have their ideas about your idea,
and, ideally, share them with you so that your idea is, via feedback, improved. It
is all about interaction, about give-and-take. According to Schrage, "In world
class companies, an interesting prototype emits the social and intellectual
equivalent of a magnetic field, attracting smart people with interesting ideas
about how to make it better." See the article here:
https://www.doczj.com/doc/bc14740931.html,/articles/020001.html.
Many of these market trends are applicable when working with more than one
company in the development process. Whether the development team includes
outsourcing partners, customers or suppliers, the value of tightly linking these
teams together for Design Review processes is critical to success.
For additional information on general Design Review topics, see some general
system engineering practices for Design Reviews discussed here:
https://www.doczj.com/doc/bc14740931.html,/library/books/ex-se/0003e4f5.html.
Types of Design Reviews
Today, with the aid of technology, Design Reviews are used more effectively as
a tool in the development process. There are at least two realms of design
reviews – a program level review and individual reviews of elements of a product
or system. For the purposes of this Business Process Guide, the scope of Design
Reviews are centered around the individual reviews held during the development
of a product.
1-6 Product Development System Design Review Business Process Guide
Additionally, while each company may hold many different kinds of design
reviews, for simplicity in this guide, we shall define two types of Design
Reviews for reference which represent two major points on the spectrum of
design review activities. We will refer to these types of Design Reviews
throughout this guide.
? Informal Design Reviews - Informal Design Reviews are often used to share ideas among members of one team or across multiple disciplines at the early
stage of a design proposal.
– May involve ad hoc participants or designated product experts to collect
breadth of experience.
– Design proposals may be in a very informal stage of development.
– Informal reviews may occur over a period of time where input is
solicited from a group of people.
– Informal design reviews may be extremely valuable to shape early
concepts or trade off competing concepts before significant portions of
the solution are committed.
? Formal Design Reviews – Formal Design Reviews are often used to validate design proposals that are maturing or close to completion. A formal design
review may involve multiple broader audiences and disciplines than informal
reviews.
– Depending upon factors such as the industry, type of customer, schedule
and culture within the organization, the responsibilities of participants in
a design review may include validating requirements are met, validating
approach for design, commenting on manufacturability, serviceability,
product costs, quality, reliability and many other factors.
– Typically, the organization designates that formal approval of the design
is required by certain cross-functional discipline representatives in order
to pass this gate.
– Formal design reviews often occur as part of scheduled program
milestones or associated with Change Board review processes.
The decisions of a formal design review are often documented and maintained by
the company for reference, accountability and traceability purposes.
The Value of Design Reviews in the Development Process How do you quantify the value of Design Reviews in your company? Consider
some of the following questions.
? How much does it cost to change the initial design of a new part or product?
? How much does it cost to introduce a new part in your company?
? How much does it cost to change a part currently in production with an
updated part?
Background of Design Reviews 1-7
? How much does it cost to recall a product introduced in the market? How
much credibility does this recall cost the company?
Effective Design Reviews are central to the business culture of the company and
provides significant value to the entire organization for creating new products or
maintaining existing products in the marketplace. Some common benefits of
effective design reviews include:
? Enhanced innovation and creativity
? Improved consistency across multiple designs and system design
? Reduced costs of product development
? Improved communication among team members and across the organization Common Objectives of Successful Design Reviews
Here are some example Design Review Objectives from identified in an article
on Best Practices in Manufacturing web site. This article lists the following
items as valuable objectives for Design Reviews:
Design Review Objectives
The overall objective of a design review is to ensure that the product will fulfill
its requirements. Many design reviews fail to meet this objective because they
lack specific plans, discipline, and resources to perform a truly objective
evaluation of the new product and processes.
With the overall objective in mind, the main purposes of the design review are to:
? Assess design maturity.
? Clarify the design requirements and evaluate the design for compliance.
? Challenge the design and related processes.
? Bring additional knowledge and experience to bear on the design and
processes.
? Shorten development time, reduce changes, and prevent mistakes and
omissions.
? Determine what issues remain to be solved and what effort will be required.
? Ensure the product is testable, manufacturable, and usable.
? Ensure the product is safe and reliable.
? Communicate requirements, design concepts and descriptions to other
departments.
See related information in this article: https://www.doczj.com/doc/bc14740931.html,/library/books/ex-
se/0003e4f5.html.
1-8 Product Development System Design Review Business Process Guide
The Relationship Between Design Reviews and Other Business Processes
Design Reviews are used as a tool by a company throughout the development
process to support higher-level business processes. Therefore there are references
throughout this guide from the following other PDS Business Process Guides:
? Top Down Planning and Design
? Enterprise Change Management
? Project Manage an Engineering Team
? Global Design Collaboration
Similarly, Design Review processes may themselves utilize some capabilities
described in detail in other PDS Business Process Guides for the PDS:
? Online Product Collaboration
Background of Design Reviews 1-9
2 Overview of the Design Review
Process
2-1
场效应管是利用电场效应来控制电流的一种半导体器件，它的输出电流决定于输入电压的大小，基本上不需要信号源提供电流，所以输入电阻高，且温度稳定性好。 绝缘栅型场效应管 MOS管增强型NMOS管耗尽型NMOS管增强型PMOS管耗尽型PMOS管 1.4 绝缘栅场效应管(IGFET)
1. G 栅极D 漏极 S 源极B 衬极 SiO 2 P 型硅衬底耗尽层 N + N + 栅极和其它电极之间是绝缘的，故称绝缘栅场效应管。 MOS Metal oxide semiconductor 1.4.1 N 沟道增强型绝缘栅场效应管(NMOS)电路符号 D G S
G D S B P N + N + 2. 工作原理 (1) U GS 对导电沟道的控制作用(U DS =0V) 当U GS ≥U GS(th)时，出现N 型导电沟道。 耗尽层 开启电压：U GS(th) U GS N 型沟道 U GS 值越大沟道电阻越小。
G D S B P N + N + (2) U DS 对导电沟道的影响(U GS >U GS(th)) U GS U DD R D U DS 值小，U GD >U GS(th)，沟道倾斜不明显，沟道电阻近似不变，I D 随U DS 线性增加。 I D U GD =U GS -U DS 当U DS 值增加使得U GD =U GS(th)，沟道出现预夹断。U DS =U GS -U GS(th) 随着U DS 增加，U GD
1 234 U GS V 2 4 6I D /mA 3. 特性曲线 输出特性曲线:I D =f (U DS ) U GS =常数 转移特性曲线:I D =f (U GS ) U DS =常数 U GS =5V 6V 4V 3V 2V U DS =10V 恒流区 U GS(th) U DS /V 5 10 151 234 I D /mA 可变电阻区 截止区 U GD =U GS(th) 2 GS D DO GS(th)1U I I U ?? =- ? ??? I DO 是U GS =2U GS(th)时的I D 值 I DO U GD >U GS(th) U GD 半导体照明技术作业答案
某光源发出波长为460nm 的单色光，辐射功率为100W ，用Y 值表示其光通量，计算其色度坐标X 、Y 、Z 、x 、y 。 解：由教材表1-3查得460nm 单色光的三色视觉值分别为0.2908X =，0.0600Y =， 1.6692Z =，则对100W P =，有 4356831000.2908 1.98610lm 6831000.0600 4.09810lm 683100 1.6692 1.14010lm m m m X K PX Y K PY Z K PZ ==××=×==××=×==××=× 以及 )()0.144 0.030x X X Y Z y Y X Y Z =++==++=
1. GaP绿色LED的发光机理是什么，当氮掺杂浓度增加时，光谱有什么变化，为什么？GaP红色LED的发光机理是什么，发光峰值波长是多少？ 答：GaP绿色LED的发光机理是在GaP间接跃迁型半导体中掺入等电子陷阱杂质N，代替P原子的N原子可以俘获电子，又靠该电子的电荷俘获空穴，形成束缚激子，激子复合发光。当氮掺杂浓度增加时，总光通量增加，主波长向长波移动，这是因为此时有大量的氮对形成新的等电子陷阱，氮对束缚激子发光峰增加，且向长波移动。 GaP红色LED的发光机理是在GaP晶体中掺入ZnO对等电子陷阱，其发光峰值波长为700nm的红光。 2. 液相外延生长的原理是什么？一般分为哪两种方法，这两种方法的区别在哪里？ 答：液相外延生长过程的基础是在液体溶剂中溶质的溶解度随温度降低而减少，而且冷却与单晶相接触的初始饱和溶液时能够引起外延沉积，在衬底上生长一个薄的外延层。 液相外延生长一般分为降温法和温度梯度法两种。降温法的瞬态生长中，溶液与衬底组成的体系在均处于同一温度，并一同降温（在衬底与溶液接触时的时间和温度上，以及接触后是继续降温还是保持温度上，不同的技术有不同的处理）。而温度梯度法则是当体系达到稳定状态后，整个体系的温度再不改变，而是在溶液表面和溶液－衬底界面间建立稳定的温度梯度和浓度梯度。 3. 为何AlGaInP材料不能使用通常的气相外延和液相外延技术来制造？ 答：在尝试用液相外延生长AlGaInP时，由于AlP和InP的热力学稳定性的不同，液相外延的组分控制十分困难。而当使用氢化物或氯化物气相外延时，会形成稳定的AlCl化合物，会在气相外延时阻碍含Al磷化物的成功生长。因此AlGaInP 材料不能使用通常的气相外延和液相外延技术来制造。
LED半导体照明的发展与应用 者按：半导体技术在上个世纪下半叶引发的一场微电子革命，催生了微电子工业和高科技ＩＴ产业，改变了整个世界的面貌。今天，化合物半导体技术的迅猛发展和不断突破，正孕育着一场新的革命——照明革命。新一代照明光源半导体ＬＥＤ，以传统光源所没有的优点引发了照明产业技术和应用的革命。半导体ＬＥＤ固态光源替代传统照明光源是大势所趋。１、ＬＥＤ半导体照明的机遇 （１）全球性的能源短缺和环境污染在经济高速发展的中国表现得尤为突出，节能和环保是中国实现社会经济可持续发展所急需解决的问题。作为能源消耗大户的照明领域，必须寻找可以替代传统光源的新一代节能环保的绿色光源。 （２）半导体ＬＥＤ是当今世界上最有可能替代传统光源的新一代光源。 其具有如下优点： ①高效低耗，节能环保； ②低压驱动，响应速度快安全性高； ③固体化封装，耐振动，体积小，便于装配组合； ④可见光区内颜色全系列化，色温、色纯、显色性、光指向性良好，便于照明应用组合； ⑤直流驱动，无频闪，用于照明有利于保护人眼视力； ⑥使用寿命长。 （３）现阶段ＬＥＤ的发光效率偏低和光通量成本偏高是制约其大规模进入照明领域的两大瓶颈。目前ＬＥＤ的应用领域主要集中在信号指示、智能显示、汽车灯具、景观照明和特殊照明领域等。但是，化合物半导体技术的迅猛发展和关键技术的即将突破，使今天成为大力发展半导体照明产业的最佳时机。２００３年我国人均ＧＤＰ首次突破１０００美元大关，经济实力得到了进一步的增强，市场上已经初步具备了接受较高光通量成本（初始成本）光
源的能力。在未来的１０～２０年内，用半导体ＬＥＤ作为光源的固态照明灯，将逐渐取代传统的照明灯。 （４）各国政府予以高度重视，相继推出半导体照明计划，已形成世界性的半导体照明技术合围突破的态势。 ①美国：“下一代照明计划”时间是２０００～２０１０年投资５亿美元。美国半导体照明发展蓝图如表１所示； ②日本：“２１世纪的照明计划”，将耗费６０亿日元推行半导体照明目标是在２００６年用白光ＬＥＤ替代５０％的传统照明； ③欧盟：“彩虹计划”已在２０００年７月启动通过欧共体的资助推广应用白光ＬＥＤ照明； ④中国：２００３年６月１７日，由科技部牵头成立了跨部门、跨地区、跨行业的“国家半导体照明工程协调领导小组”。从协调领导小组成立之日到２００５年年底之前，将是半导体照明工程项目的紧急启动期。从２００６年的“十一五”开始，国家将把半导体照明工程作为一个重大项目进行推动； （５）我国 的半导体ＬＥＤ产业链经过多年的发展已相对完善，具备了一定的发展基础。同时，我国又是照明灯具产业的大国，只要政府和业界协调整合好，发展半导体ＬＥＤ照明产业是大有可为的； ２ＬＥＤ的发展历程（如图１所示） ２．１ＬＥＤ技术突破的历程
《半导体照明技术及其应用》课程教学大纲 （秋季） 一、课程名称：半导体照明技术及其应用Semiconductor Lighting Technology and Applications 二、课程编码： 三、学时与学分：32/2 四、先修课程: 微积分、大学物理、固体物理、半导体物理、微电子器件与IC设计 五、课程教学目标： 半导体照明是指用全固态发光器件LED作为光源的照明，具有高效、节能、环保、寿命长、易维护等显著特点，是近年来全球最具发展前景的高新技术领域之一，是人类照明史上继白炽灯、荧光灯之后的又一场照明光源的革命。本课程注重理论的系统性﹑结构的科学性和内容的实用性，在重点讲解发光二极管的材料、机理及其制造技术后，详细介绍器件的光电参数测试方法，器件的可靠性分析、驱动和控制方法，以及各种半导体照明的应用技术，使学生学完本课程以后，能对半导体照明有深入而全面的理解。 六﹑适用学科专业：电子科学与技术 七、基本教学内容与学时安排： 绪论（1学时） 半导体照明简介、学习本课程的目的及要求 第一章光视觉颜色（2学时） 1光的本质 2光的产生和传播 3人眼的光谱灵敏度 4光度学及其测量 5作为光学系统的人眼 6视觉的特征与功能 7颜色的性质 8国际照明委员会色度学系统 9色度学及其测量 第二章光源（1学时） 1太阳 2月亮和行星 3人工光源的发明与发展 4白炽灯 5卤钨灯 6荧光灯 7低压钠灯
8高压放电灯 9无电极放电灯 10发光二极管 11照明的经济核算 第三章半导体发光材料晶体导论（2学时） 1晶体结构 2能带结构 3半导体晶体材料的电学性质 4半导体发光材料的条件 第四章半导体的激发与发光（1学时） 1PN结及其特性 2注入载流子的复合 3辐射与非辐射复合之间的竞争 4异质结构和量子阱 第五章半导体发光材料体系（2学时） 1砷化镓 2磷化镓 3磷砷化镓 4镓铝砷 5铝镓铟磷 6铟镓氮 第六章半导体照明光源的发展和特征参量（1学时）1发光二极管的发展 2发光二极管材料生长方法 3高亮度发光二极管芯片结构 4照明用LED的特征参数和要求 第七章磷砷化镓、磷化镓、镓铝砷材料生长（3学时）1磷砷化镓氢化物气相外延生长（HVPE） 2氢化物外延体系的热力学分析 3液相外延原理 4磷化镓的液相外延 5镓铝砷的液相外延 第八章铝镓铟磷发光二极管（2学时） 1AlGaInP金属有机物化学气相沉积通论 2外延材料的规模生产问题 3电流扩展 4电流阻挡结构 5光的取出 6芯片制造技术
第一章 常用半导体器件 自 测 题 一、判断下列说法是否正确，用“√”和“×”表示判断结果填入空内。 （1）在N 型半导体中如果掺入足够量的三价元素，可将其改型为P 型半导体。（ ） （2）因为N 型半导体的多子是自由电子，所以它带负电。（ ） （3）PN 结在无光照、无外加电压时，结电流为零。（ ） （4）处于放大状态的晶体管，集电极电流是多子漂移运动形成的。 （ ） （5）结型场效应管外加的栅-源电压应使栅-源间的耗尽层承受反向电压，才能保证其R G S 大的特点。（ ） （6）若耗尽型N 沟道MOS 管的U G S 大于零，则其输入电阻会明显变小。（ ） 解：（1）√ （2）× （3）√ （4）× （5）√ （6）× 二、选择正确答案填入空内。 （1）PN 结加正向电压时，空间电荷区将 。 A. 变窄 B. 基本不变 C. 变宽 （2）设二极管的端电压为U ，则二极管的电流方程是 。 A. I S e U B. T U U I e S C. )1e (S －T U U I （3）稳压管的稳压区是其工作在 。 A. 正向导通 B.反向截止 C.反向击穿 （4）当晶体管工作在放大区时，发射结电压和集电结电压应为 。 A. 前者反偏、后者也反偏 B. 前者正偏、后者反偏 C. 前者正偏、后者也正偏 （5）U G S ＝0V 时，能够工作在恒流区的场效应管有 。 A. 结型管 B. 增强型MOS 管 C. 耗尽型MOS 管 解：（1）A （2）C （3）C （4）B （5）A C
三、写出图T1.3所示各电路的输出电压值，设二极管导通电压U D＝0.7V。 图T1.3 解：U O1≈1.3V，U O2＝0，U O3≈－1.3V，U O4≈2V，U O5≈1.3V， U O6≈－2V。 四、已知稳压管的稳压值U Z＝6V，稳定电流的最小值I Z mi n＝5mA。求图T1.4所示电路中U O1和U O2各为多少伏。 图T1.4 解：U O1＝6V，U O2＝5V。
电子技术复习 CH14半导体器件 1.本征半导体、N型半导体、P半导体的基本概念；PN的单 向导电特性；温度和参杂浓度对多子和少子的影响。 2.二极管的基本参数（死区电压、导通电压）及相关应用， 学会判断二极管在电路中的工作状态（导通、截止）。掌握含二极管电路的分析方法。 3.了解稳压管的工作原理，基本稳压管稳压电路的分析。(两 稳压管串联、并联) 4.半导体三极管工作状态的特点（放大、饱和、截止）。 5.半导体三极管的管脚的判定 CH15基本放大电路 1.放大电路（共射）的分析方法（直流通路法、微变等效电 路法） 2.静态工作点稳定电路(分压式偏置电路)的结构、特点和分 析方法(静态、动态) 3.射极输出器的特点，电路分析。 4.差分放大电路的输入信号（共模、差模、比较），共模抑制 比的概念（理想共模抑制比=？） CH16集成运算放大器 1.运放的理想化条件 2.运放在线性区和非线性区的分析方法
3. 运放线性应用电路的分析（比例运算[同相（电压跟随器）、反相(反相器)]、反相加法运算、减法运算） CH17电子电路中的反馈 1. 反馈的基本概念 2. 负反馈类型的判断方法（会判断正、负反馈；电压、电流反馈；串联、并联反馈） 3. 负反馈对放大器性能的影响（影响类别？闭环放大倍数？ AF A A f += 1） 4. 自激振荡起振的条件、振荡建立条件、稳振条件？ 5. 典型RC 两种类型电路的电路分析。 CH18直流稳压电源 1. 直流稳压电源的组成及各部分的作用 u 1- + 2. 单相半波、全波(桥式整流)电路的构成和工作原理，二极管的选择依据（计算，见例题和作业题），桥式的输出波形受二极管的影响
1. GaP绿色LED的发光机理是什么，当氮掺杂浓度增加时，光谱有什么变化，为什么？GaP红色LED的发光机理是什么，发光峰值波长是多少？答：GaP绿色LED的发光机理是在GaP间接跃迁型半导体中掺入等电子陷阱杂质N，代替P原子的N原子可以俘获电子，又靠该电子的电荷俘获空穴，形成束缚激子，激子复合发光。当氮掺杂浓度增加时，总光通量增加，主波长向长波移动，这是因为此时有大量的氮对形成新的等电子陷阱，氮对束缚激子发光峰增加，且向长波移动。 GaP红色LED的发光机理是在GaP晶体中掺入ZnO对等电子陷阱，其发光峰值波长为700nm的红光。 2. 液相外延生长的原理是什么？一般分为哪两种方法，这两种方法 的区别在哪里？ 答：液相外延生长过程的基础是在液体溶剂中溶质的溶解度随温度 降低而减少，而且冷却与单晶相接触的初始饱和溶液时能够引起外 延沉积，在衬底上生长一个薄的外延层。 液相外延生长一般分为降温法和温度梯度法两种。降温法的瞬态生 长中，溶液与衬底组成的体系在均处于同一温度，并一同降温（在 衬底与溶液接触时的时间和温度上，以及接触后是继续降温还是保 持温度上，不同的技术有不同的处理）。而温度梯度法则是当体系 达到稳定状态后，整个体系的温度再不改变，而是在溶液表面和溶 液－衬底界面间建立稳定的温度梯度和浓度梯度。 3. 为何AlGaInP材料不能使用通常的气相外延和液相外延技术来制造？答：在尝试用液相外延生长AlGaInP时，由于AlP和InP的热力学稳定性的不同，液相外延的组分控制很困难。而当使用氢化物或氯化物气相外延时，会形成稳定的AlCl化合物，会在气相外延时阻碍含Al磷化物的成功生长。故AlGaInP材料不能用通常的气相外延和液相外延技术来制造。 4. 对三基色体系的白光LED，列出基色光源的三个最佳峰值波长。对荧光转换的白光LED和多芯片的白光LED，这三基色用什么方法来实现？答：三基色体系的白光LED，基色光源的三个最佳峰值波长分别为450nm、540nm和610nm。对荧光转换的白光LED，是用部分被吸收的AlInGaN 芯片的蓝光和适当的绿光和橙红光两种荧光粉来实现。对多芯片白光LED，是用峰值波长600nm附近的AlGaInP基LED，以及峰值波长450nm 和540nm的AlInGaN LED组成。 5. 简要说明LED封装技术发展三个阶段的时间范围、典型LED及其驱动电流、器件应用领域。 答：LED封装技术发展的3个阶段分别为： （1）1962~1989年期间，典型的LED为?3和?5的LED，驱动电流一般小于等于20mA，主要用做信号指示和显示。 （2）1990~1999年，发展了大光通量LED食人鱼和Snap，驱动电流在50~150mA，主要用于大型信号指示，如汽车信号灯、景观照明。 （3）2000年至今，研发和生产了功率型LED，电流≥350mA，开始用于照明，并开始了更大光通量输出的组件的研制和生产。 6. 画出透明衬底的AlGaInP LED的结构示意图，简要说明其芯片制造流程。 答：结构示意图如下图所示。 此LED结构用的是MOCVD生长在GaAs上的双异质结(AlxGa1-x)0.5In0.5P，并在结构上方VPE生长一个小于50μm厚的GaP 窗层。在外延生长后，用通常的化学腐蚀技术移除GaAs吸收衬底，使双异质结结构的N型层暴露，再通过升高温度和加压，将晶片黏结到200~250μm厚的N型GaP衬底上。1. 画出典型的具有GaP窗层和吸收衬底的双异质结AlGaInP LED的结构示意图，简述为什么需要使用电流扩展窗层。 答：结构示意图如下图所示。 为了使LED芯片获得高效的发光，电流扩展是主要关键之一，如 上图的结构，器件的上方覆盖了圆形的金属顶，电流从芯片的顶部 接触通过P型层流下到达结区，在结区发光。但是假如P型层的电 阻太高，电流将扩展很少，而仅仅限在金属之下，光仅仅发生在电极 之下，而且被芯片内部吸收。有效的最好性能的AlGaInP LED是在 通常的双异质结顶部再生长一个厚的P型窗层，而不用AlGaInP材 料。这个电流扩展窗层与AlGaInP相比，具有高的薄层电导率，而 且对发射光是透明的，可以达到很好的电流扩展效果。 4.LED作为城市景观照明中的首选光源的优点：①色彩丰富纯度高、节能②响应时间短，瞬时达到全光输出，可深度调光③体积小、方向 性强④直流低压驱动，简化系统设计，降低电路成本⑤寿命长，工作 安全可靠，维护费用大大降低。景观常用LED灯具有护栏灯、树灯 5. LED的电学性能特点：LED是单向导电器件。LED是个具有PN结结构的半导体器件，具有势垒电势，所以就有导通阈值电压。LED的电流—电压特性是非线性的。LED的正向压降与PN结结温的温度系数为负。流过LED的电流和LED的光通量的比值也是非线性的。 6. 电源驱动方案：（1）低电压驱动。是指用低于LED正向导通压降的电压驱动LED，如一节普通干电池、镍镉电池供电的低功耗照明器件，LED 手电、头灯、应急灯、路障灯、节能台灯等，采用电荷泵式升压变换器（2）过渡电压驱动。是指给LED供电的电源电压值在LED正向压降附近变动。如一节锂电池或两节串联的铅酸蓄电池，电池充满时在4V以上，快用完时在3V以下，应用有矿灯等，是反极性电荷泵式变换器（3）高压驱动。是指给LED供电的电压值高于LED的正向压降，如6V.12V.24V蓄电池，应用有太阳能草坪灯、太阳能庭院灯等，变换器电路是串联开关降压电路。（4）市电驱动。是对半导体照明应用最具有价值的供电方式，中小功率LED采用隔离式单端反激变换器，大功率用桥式变换电路。 7.可靠性试验指：产品在规定的条件下、在规定的时间内完成规定的功能的能力。产品在设计、应用过程中，不断经受自身及外界气候环境及机械环境的影响，而仍需要能够正常工作，这就需要以试验设备对其进行验证，按试验目的可分为筛选试验、例行试验、鉴定验收试验；按照试验项目可分为环境试验和寿命试验。 8. （1）平均寿命：指一批电子器件产品寿命的平均值（2）可靠寿命：指一批电子器件产品的可靠度下降到时，所经历的工作时间（3）中位寿命：指产品的可靠度降为50%时的寿命（4）特征寿命：指产品的可靠度降为1/e时的寿命（5）LED的寿命：通常用“半衰期”即器件的光输出下降到起始值50%时的时间作为LED的寿命。 用B50和L70来表示功率LED的寿命。L70（B50）表示功率LED比起初始值来，平均流明值下降到维持70%（50%）的时间。 9. 画出器件失效率随时间变化的曲线，说明曲线的各个阶段及其失 效原因。 答：曲线如图分为三个阶段： 第一个阶段称为早期失效或 老化阶段，失效率较高，随工作时间的延长而迅速下降。造成早期 失效的原因大多属生产型缺陷，由产品本身存在的缺陷所致。 第二个阶段为有效寿命阶段，又称随机失效阶段，失效率很低且 很稳定，近似为常数，器件失效往往带有偶然性。 第三个阶段称耗损失效阶段，失效率明显上升，大部分器件相继出现 失效，耗损失效都由于老化、磨损和疲劳等原因使器件性能恶化所致。 10. 伏安特性指流过PN结的电流随电压变化的特性，应将正、反向均包括在内。（1）反向击穿电压Vb：表示器件反向耐压高低的参数，通常是指一定漏电流下器件两端的反向电压值（2）反向电流Ir：给定反向电压下流过器件的反向电流值（3）正向电压Vf：指定正向电流下器件两端的正向电压值。作用：标志着结的体电阻及欧姆接触串联电阻的高低，可在一定程度上反应电极制作的好坏 12. 热管是依靠自身内部工质液相和气体二相变化来实现传热的导热元件，它是由高纯度的无氧铜管及铜丝网或铜粉烧结物组成，内充液体为工作介质。当受热端将工作液相蒸发成气相，气流经过中空管道流到冷却端，冷却后将工作流体凝结成液相，冷凝液借助于铜丝网或铜粉烧结物的毛细组织吸回受热端，完成吸热-放热循环，可在一定温差下将热量传导出。具有重量轻、结构简单、热传输量大、耐用寿命长、导热能力强等优点。回路热管比单管热管效率更高且不受位置影响。
第一章、半导体器件（附答案） 一、选择题 1．PN 结加正向电压时，空间电荷区将 ________ A. 变窄 B. 基本不变 C. 变宽 2．设二极管的端电压为 u ，则二极管的电流方程是 ________ A. B. C. 3．稳压管的稳压是其工作在 ________ A. 正向导通 B. 反向截止 C. 反向击穿区 4．V U GS 0=时，能够工作在恒流区的场效应管有 ________ A. 结型场效应管 B. 增强型 MOS 管 C. 耗尽型 MOS 管 5．对PN 结增加反向电压时，参与导电的是 ________ A. 多数载流子 B. 少数载流子 C. 既有多数载流子又有少数载流子 6．当温度增加时，本征半导体中的自由电子和空穴的数量 _____ A. 增加 B. 减少 C. 不变 7．用万用表的 R × 100 Ω档和 R × 1K Ω档分别测量一个正常二极管的正向电阻，两次测量 结果 ______ A. 相同 B. 第一次测量植比第二次大 C. 第一次测量植比第二次小 8．面接触型二极管适用于 ____ A. 高频检波电路 B. 工频整流电路 | 9．下列型号的二极管中可用于检波电路的锗二极管是： ____ A. 2CZ11 B. 2CP10 C. 2CW11 10．当温度为20℃时测得某二极管的在路电压为V U D 7.0=。若其他参数不变，当温度上 升到40℃，则D U 的大小将 ____ A. 等于 B. 大于 C. 小于 11．当两个稳压值不同的稳压二极管用不同的方式串联起来，可组成的稳压值有 _____ A. 两种 B. 三种 C. 四种 12．在图中，稳压管1W V 和2W V 的稳压值分别为6V 和7V ，且工作在稳压状态，由此可知输 出电压O U 为 _____ A. 6V B. 7V C. 0V D. 1V
电子技术查新训练文献综述报告 题目半导体照明技术的发展现状及趋势 学号 班级 学生 指导教师 2012 年
半导体照明技术的发展现状及趋势 摘要：随着半导体照明技术的进步，对于半导体照明技术有了更高的要求。本文主要介绍了半导体照明技术的定义概念背景发展以及趋势进行了详细的报告。使得更多的人对半导体照明技术有一个系统的认知。 关键词：半导体技术评价标准照明技术LED Semiconductor lighting technology development present situation and trends Abstract：Along with the progress of the semiconductor lighting technology, for semiconductor lighting technology have higher requirements. This paper mainly introduces the definition of semiconductor lighting technology background and development concept trend for the detailed report. Make more people to the semiconductor lighting technology is a cognitive system Key Words：Semiconductor technology evaluation standard LED lighting technology 1 引言 半导体照明亦称固态照明，是指用固态发光器件作为光源的照明，包括发光二极管（LED）和有机发光二极管（OLED），具有耗电量少、寿命长、色彩丰富、耐震动、可控性强等特点。 90年代以来，半导体照明技术不断突破，应用领域日益扩展。在指示、显示领域的技术基本成熟，并广泛应用；在医疗、农业等特殊领域的技术方兴未艾。近几年，半导体照明产业发展迅速，国外及我国台湾地区在不同领域具有较强优势。随着我国产业结构调整、发展方式转变进程的加快，半导体照明节能产业作为节能减排的重要措施迎来了新的发展机遇期。LED（LightingEmittingDiode）即发光二极管，是一种半导体固体发光器件。它是利用固体半导体芯片作为发光材料，在半导体中通过载流子发生复合放出过剩的能量而引起光子发射，直接发出红、黄、蓝、绿、青、橙、紫、白色的光。LED照明产品就是利用LED作为光源制造出来的照明器具。