Contents 1 Terminology 2 Redundancy 3 Criteria 4 Requirements 5 Replication 6 Disadvantages 7 Examples 8 Related terms 9 See also 10 References 11 Further reading


Terminology[edit] An example of graceful degradation by design in an image with transparency. The top two images are each the result of viewing the composite image in a viewer that recognises transparency. The bottom two images are the result in a viewer with no support for transparency. Because the transparency mask (centre bottom) is discarded, only the overlay (centre top) remains; the image on the left has been designed to degrade gracefully, hence is still meaningful without its transparency information. A highly fault-tolerant system might continue at the same level of performance even though one or more components have failed. For example, a building with a backup electrical generator will provide the same voltage to wall outlets even if the grid power fails. A system that is designed to fail safe, or fail-secure, or fail gracefully, whether it functions at a reduced level or fails completely, does so in a way that protects people, property, or data from injury, damage, intrusion, or disclosure. In computers, a program might fail-safe by executing a graceful exit (as opposed to an uncontrolled crash) in order to prevent data corruption after experiencing an error. A similar distinction is made between "failing well" and "failing badly". Fail-deadly is the opposite strategy, which can be used in weapon systems that are designed to kill or injure targets even if part of the system is damaged or destroyed. A system that is designed to experience graceful degradation, or to fail soft (used in computing, similar to "fail safe"[3]) operates at a reduced level of performance after some component failures. For example, a building may operate lighting at reduced levels and elevators at reduced speeds if grid power fails, rather than either trapping people in the dark completely or continuing to operate at full power. In computing an example of graceful degradation is that if insufficient network bandwidth is available to stream an online video, a lower-resolution version might be streamed in place of the high-resolution version. Progressive enhancement is an example in computing, where web pages are available in a basic functional format for older, small-screen, or limited-capability web browsers, but in an enhanced version for browsers capable of handling additional technologies or that have a larger display available. In fault-tolerant computer systems, programs that are considered robust are designed to continue operation despite an error, exception, or invalid input, instead of crashing completely. Software brittleness is the opposite of robustness. Resilient networks continue to transmit data despite the failure of some links or nodes; resilient buildings and infrastructure are likewise expected to prevent complete failure in situations like earthquakes, floods, or collisions. A system with high failure transparency will alert users that a component failure has occurred, even if it continues to operate with full performance, so that failure can be repaired or imminent complete failure anticipated. Likewise, a fail-fast component is designed to report at the first point of failure, rather than allow downstream components to fail and generate reports then. This allows easier diagnosis of the underlying problem, and may prevent improper operation in a broken state.


Redundancy[edit] Main article: Redundancy (engineering) Redundancy is the provision of functional capabilities that would be unnecessary in a fault-free environment.[4] This can consist of backup components that automatically "kick in" should one component fail. For example, large cargo trucks can lose a tire without any major consequences. They have many tires, and no one tire is critical (with the exception of the front tires, which are used to steer, but generally carry less load, each and in total, than the other four to 16, so are less likely to fail). The idea of incorporating redundancy in order to improve the reliability of a system was pioneered by John von Neumann in the 1950s.[5] Two kinds of redundancy are possible:[6] space redundancy and time redundancy. Space redundancy provides additional components, functions, or data items that are unnecessary for fault-free operation. Space redundancy is further classified into hardware, software and information redundancy, depending on the type of redundant resources added to the system. In time redundancy the computation or data transmission is repeated and the result is compared to a stored copy of the previous result. The current terminology for this kind of testing is referred to as 'In Service Fault Tolerance Testing or ISFTT for short.


Criteria[edit] Providing fault-tolerant design for every component is normally not an option. Associated redundancy brings a number of penalties: increase in weight, size, power consumption, cost, as well as time to design, verify, and test. Therefore, a number of choices have to be examined to determine which components should be fault tolerant:[7] How critical is the component? In a car, the radio is not critical, so this component has less need for fault tolerance. How likely is the component to fail? Some components, like the drive shaft in a car, are not likely to fail, so no fault tolerance is needed. How expensive is it to make the component fault tolerant? Requiring a redundant car engine, for example, would likely be too expensive both economically and in terms of weight and space, to be considered. An example of a component that passes all the tests is a car's occupant restraint system. While we do not normally think of the primary occupant restraint system, it is gravity. If the vehicle rolls over or undergoes severe g-forces, then this primary method of occupant restraint may fail. Restraining the occupants during such an accident is absolutely critical to safety, so we pass the first test. Accidents causing occupant ejection were quite common before seat belts, so we pass the second test. The cost of a redundant restraint method like seat belts is quite low, both economically and in terms of weight and space, so we pass the third test. Therefore, adding seat belts to all vehicles is an excellent idea. Other "supplemental restraint systems", such as airbags, are more expensive and so pass that test by a smaller margin. Another excellent and long-term example of this principle being put into practice is the braking system: whilst the actual brake mechanisms are critical, they are not particularly prone to sudden (rather than progressive) failure, and are in any case necessarily duplicated to allow even and balanced application of brake force to all wheels. It would also be prohibitively costly to further double-up the main components and they would add considerable weight. However, the similarly critical systems for actuating the brakes under driver control are inherently less robust, generally using a cable (can rust, stretch, jam, snap) or hydraulic fluid (can leak, boil and develop bubbles, absorb water and thus lose effectiveness). Thus in most modern cars the footbrake hydraulic brake circuit is diagonally divided to give two smaller points of failure, the loss of either only reducing brake power by 50% and not causing as much dangerous brakeforce imbalance as a straight front-back or left-right split, and should the hydraulic circuit fail completely (a relatively very rare occurrence), there is a failsafe in the form of the cable-actuated parking brake that operates the otherwise relatively weak rear brakes, but can still bring the vehicle to a safe halt in conjunction with transmission/engine braking so long as the demands on it are in line with normal traffic flow. The culmulatively unlikely combination of total footbrake failure with the need for harsh braking in an emergency will likely result in a collision, but still one at lower speed than would otherwise have been the case. In comparison with the footpedal activated service brake, the parking brake itself is a less critical item, and unless it is being used as a one-time backup for the footbrake, will not cause immediate danger if it is found to be nonfunctional at the moment of application. Therefore, no redundancy is built into it per se (and it typically uses a cheaper, lighter, but less hardwearing cable actuation system), and it can suffice, if this happens on a hill, to use the footbrake to momentarily hold the vehicle still, before driving off to find a flat piece of road on which to stop. Alternatively, on shallow gradients, the transmission can be shifted into Park, Reverse or First gear, and the transmission lock / engine compression used to hold it stationary, as there is no need for them to include the sophistication to first bring it to a halt. On motorcycles, a similar level of fail-safety is provided by simpler methods; firstly the front and rear brake systems being entirely separate, regardless of their method of activation (that can be cable, rod or hydraulic), allowing one to fail entirely whilst leaving the other unaffected. Secondly, the rear brake is relatively strong compared to its automotive cousin, even being a powerful disc on sports models, even though the usual intent is for the front system to provide the vast majority of braking force; as the overall vehicle weight is more central, the rear tyre is generally larger and grippier, and the rider can lean back to put more weight on it, therefore allowing more brake force to be applied before the wheel locks up. On cheaper, slower utility-class machines, even if the front wheel should use a hydraulic disc for extra brake force and easier packaging, the rear will usually be a primitive, somewhat inefficient, but exceptionally robust rod-actuated drum, thanks to the ease of connecting the footpedal to the wheel in this way and, more importantly, the near impossibility of catastrophic failure even if the rest of the machine, like a lot of low-priced bikes after their first few years of use, is on the point of collapse from neglected maintenance.


Requirements[edit] The basic characteristics of fault tolerance require: No single point of failure – If a system experiences a failure, it must continue to operate without interruption during the repair process. Fault isolation to the failing component – When a failure occurs, the system must be able to isolate the failure to the offending component. This requires the addition of dedicated failure detection mechanisms that exist only for the purpose of fault isolation. Recovery from a fault condition requires classifying the fault or failing component. The National Institute of Standards and Technology (NIST) categorizes faults based on locality, cause, duration, and effect.[where?][clarification needed] Fault containment to prevent propagation of the failure – Some failure mechanisms can cause a system to fail by propagating the failure to the rest of the system. An example of this kind of failure is the "rogue transmitter" that can swamp legitimate communication in a system and cause overall system failure. Firewalls or other mechanisms that isolate a rogue transmitter or failing component to protect the system are required. Availability of reversion modes[clarification needed] In addition, fault-tolerant systems are characterized in terms of both planned service outages and unplanned service outages. These are usually measured at the application level and not just at a hardware level. The figure of merit is called availability and is expressed as a percentage. For example, a five nines system would statistically provide 99.999% availability. Fault-tolerant systems are typically based on the concept of redundancy.


Replication[edit] Spare components address the first fundamental characteristic of fault tolerance in three ways: Replication: Providing multiple identical instances of the same system or subsystem, directing tasks or requests to all of them in parallel, and choosing the correct result on the basis of a quorum; Redundancy: Providing multiple identical instances of the same system and switching to one of the remaining instances in case of a failure (failover); Diversity: Providing multiple different implementations of the same specification, and using them like replicated systems to cope with errors in a specific implementation. All implementations of RAID, redundant array of independent disks, except RAID 0, are examples of a fault-tolerant storage device that uses data redundancy. A lockstep fault-tolerant machine uses replicated elements operating in parallel. At any time, all the replications of each element should be in the same state. The same inputs are provided to each replication, and the same outputs are expected. The outputs of the replications are compared using a voting circuit. A machine with two replications of each element is termed dual modular redundant (DMR). The voting circuit can then only detect a mismatch and recovery relies on other methods. A machine with three replications of each element is termed triple modular redundant (TMR). The voting circuit can determine which replication is in error when a two-to-one vote is observed. In this case, the voting circuit can output the correct result, and discard the erroneous version. After this, the internal state of the erroneous replication is assumed to be different from that of the other two, and the voting circuit can switch to a DMR mode. This model can be applied to any larger number of replications. Lockstep fault-tolerant machines are most easily made fully synchronous, with each gate of each replication making the same state transition on the same edge of the clock, and the clocks to the replications being exactly in phase. However, it is possible to build lockstep systems without this requirement. Bringing the replications into synchrony requires making their internal stored states the same. They can be started from a fixed initial state, such as the reset state. Alternatively, the internal state of one replica can be copied to another replica. One variant of DMR is pair-and-spare. Two replicated elements operate in lockstep as a pair, with a voting circuit that detects any mismatch between their operations and outputs a signal indicating that there is an error. Another pair operates exactly the same way. A final circuit selects the output of the pair that does not proclaim that it is in error. Pair-and-spare requires four replicas rather than the three of TMR, but has been used commercially.


Disadvantages[edit] Fault-tolerant design's advantages are obvious, while many of its disadvantages are not: Interference with fault detection in the same component. To continue the above passenger vehicle example, with either of the fault-tolerant systems it may not be obvious to the driver when a tire has been punctured. This is usually handled with a separate "automated fault-detection system". In the case of the tire, an air pressure monitor detects the loss of pressure and notifies the driver. The alternative is a "manual fault-detection system", such as manually inspecting all tires at each stop. Interference with fault detection in another component. Another variation of this problem is when fault tolerance in one component prevents fault detection in a different component. For example, if component B performs some operation based on the output from component A, then fault tolerance in B can hide a problem with A. If component B is later changed (to a less fault-tolerant design) the system may fail suddenly, making it appear that the new component B is the problem. Only after the system has been carefully scrutinized will it become clear that the root problem is actually with component A. Reduction of priority of fault correction. Even if the operator is aware of the fault, having a fault-tolerant system is likely to reduce the importance of repairing the fault. If the faults are not corrected, this will eventually lead to system failure, when the fault-tolerant component fails completely or when all redundant components have also failed. Test difficulty. For certain critical fault-tolerant systems, such as a nuclear reactor, there is no easy way to verify that the backup components are functional. The most infamous example of this is Chernobyl, where operators tested the emergency backup cooling by disabling primary and secondary cooling. The backup failed, resulting in a core meltdown and massive release of radiation. Cost. Both fault-tolerant components and redundant components tend to increase cost. This can be a purely economic cost or can include other measures, such as weight. Manned spaceships, for example, have so many redundant and fault-tolerant components that their weight is increased dramatically over unmanned systems, which don't require the same level of safety. Inferior components. A fault-tolerant design may allow for the use of inferior components, which would have otherwise made the system inoperable. While this practice has the potential to mitigate the cost increase, use of multiple inferior components may lower the reliability of the system to a level equal to, or even worse than, a comparable non-fault-tolerant system.


Examples[edit] Hardware fault tolerance sometimes requires that broken parts be taken out and replaced with new parts while the system is still operational (in computing known as hot swapping). Such a system implemented with a single backup is known as single point tolerant, and represents the vast majority of fault-tolerant systems. In such systems the mean time between failures should be long enough for the operators to have time to fix the broken devices (mean time to repair) before the backup also fails. It helps if the time between failures is as long as possible, but this is not specifically required in a fault-tolerant system. Fault tolerance is notably successful in computer applications. Tandem Computers built their entire business on such machines, which used single-point tolerance to create their NonStop systems with uptimes measured in years. Fail-safe architectures may encompass also the computer software, for example by process replication (computer science). Data formats may also be designed to degrade gracefully. HTML for example, is designed to be forward compatible, allowing new HTML entities to be ignored by Web browsers that do not understand them without causing the document to be unusable.


Related terms[edit] There is a difference between fault tolerance and systems that rarely have problems. For instance, the Western Electric crossbar systems had failure rates of two hours per forty years, and therefore were highly fault resistant. But when a fault did occur they still stopped operating completely, and therefore were not fault tolerant.


See also[edit] Control reconfiguration Damage tolerance Defence in depth Elegant degradation Error-tolerant design (human-error-tolerant design) Failure semantics Fault-tolerant computer system List of system quality attributes Resilience (ecology) Resilience (network) Safe-life design


References[edit] ^ Adaptive Fault Tolerance and Graceful Degradation, Oscar González et al., 1997, University of Massachusetts - Amherst ^ Johnson, B. W. (1984). "Fault-Tolerant Microprocessor-Based Systems", IEEE Micro, vol. 4, no. 6, pp. 6–21 ^ Stallings, W (2009): Operating Systems. Internals and Design Principles, sixth edition ^ Laprie, J. C. (1985). "Dependable Computing and Fault Tolerance: Concepts and Terminology", Proceedings of 15th International Symposium on Fault-Tolerant Computing (FTSC-15), pp. 2–11 ^ von Neumann, J. (1956). "Probabilistic Logics and Synthesis of Reliable Organisms from Unreliable Components", in Automata Studies, eds. C. Shannon and J. McCarthy, Princeton University Press, pp. 43–98 ^ Avizienis, A. (1976). "Fault-Tolerant Systems", IEEE Transactions on Computers, vol. 25, no. 12, pp. 1304–1312 ^ Dubrova, E. (2013). "Fault-Tolerant Design", Springer, 2013, ISBN 978-1-4614-2112-2


Further reading[edit] Randell, Brian; Lee, P.A.; Treleaven, P. C. (June 1978). "Reliability Issues in Computing System Design". ACM Computing Surveys. 10 (2): 123–165. doi:10.1145/356725.356729. ISSN 0360-0300.  P. J. Denning (December 1976). "Fault tolerant operating systems". ACM Computing Surveys. 8 (4): 359–389. doi:10.1145/356678.356680. ISSN 0360-0300.  Theodore A. Linden (December 1976). "Operating System Structures to Support Security and Reliable Software". ACM Computing Surveys. 8 (4): 409–445. doi:10.1145/356678.356682. ISSN 0360-0300.  v t e Engineering approaches School Empathic design Frugal innovation Kansei engineering Keep It Simple Stupid Minimalism Use-centered design User-centered design Concepts Ornament and Crime Overengineering Planned obsolescence Sustainability Theory of constraints Usability v t e Design Outline Portal Designer Disciplines Communication design Advertising Book design Corporate design Exhibit design Film title design Graphic design Motion Postage stamp design Print design Illustration Information design Instructional design News design Photography Retail design Signage / Traffic sign design Typography / Type design Video design Visual merchandising Environmental design Architecture Architectural lighting design Building design Passive solar Ecological design Environmental impact design Garden design Computer-aided Healthy community design Hotel design Interior architecture Interior design EID Keyline design Landscape architecture Sustainable Landscape design Spatial design Urban design Industrial design Automotive design Automotive suspension design CMF design Corrugated box design Electric guitar design Furniture design Sustainable Hardware interface design Motorcycle design Packaging and labeling Photographic lens design Product design Production design Sensory design Service design Interaction design Experience design EED Game design Level design Video game design Hardware interface design Icon design Immersive design Information design Sonic interaction design User experience design User interface design Web design Other applied arts Public art design Ceramic / glass design Fashion design Costume design Jewelry design Floral design Game art design Property design Scenic design Sound design Stage/set lighting design Textile design Other design & engineering Algorithm design Boiler design Conceptual design Database design Drug design Electrical system design Experimental design Filter design Job design Integrated circuit design Circuit design Physical design Power network design Mechanism design Nuclear weapon design Nucleic acid design Organization design Process design Processor design Protein design Research design Social design Software design Spacecraft design Strategic design Systems design Approaches Activity-centered Adaptive web Affective Brainstorming By committee By contract C-K theory Closure Co-design Concept-oriented Configuration Contextual Continuous Cradle-to-cradle Creative problem-solving Creativity techniques Critical Design fiction Defensive Design–bid–build Design–build architect-led Domain-driven Ecodesign Energy neutral Engineering design process Probabilistic design Error-tolerant Fault-tolerant Framework-oriented For assembly For behaviour change For manufacturability For Six Sigma For testing For X Functional Generative Geodesign High-level Integrated Integrated topside Intelligence-based Iterative KISS principle Low-level Metadesign Mind mapping Modular New Wave Object-oriented Open Parametric Participatory Platform-based Policy-based Process-centered Public interest Rational Regenerative Reliability engineering Research-based Responsibility-driven RWD Safe-life Sustainable Systemic SOD Tableless web Theory of constraints Top-down and bottom-up Transformation Transgenerational TRIZ Universal Design for All Usage-centered Use-centered User-centered Empathic User innovation Value-driven Value sensitive Privacy by Design choice computing controls flow leadership management marker methods pattern research science strategy theory thinking Tools Intellectual property Organizations Awards Tools AAD Architectural model Blueprint Comprehensive layout CAD CAID Virtual home design software CAutoD Design quality indicator Electronic design automation Flowchart Mockup Product design specification Prototype Sketch Storyboard Technical drawing Web design program Website wireframe Intellectual property Community design Design around Design patent Fashion design copyright Geschmacksmuster Industrial design rights European Union Organizations AIGA Chartered Society of Designers Design and Industries Association Design Council International Forum Design The Design Society Design Research Society Awards European Design Award German Design Award Good Design Award (Chicago) Good Design Award (Japan) Graphex IF product design award James Dyson Award Prince Philip Designers Prize Related topics Aesthetics Agile Concept art Creative industries Cultural icon .design Enterprise architecture Futures studies Innovation Management Intelligent design Lean Startup New product development OODA Loop Philosophy of design Process simulation Slow design STEAM fields Unintelligent design Visualization Wicked problem Design brief change classic director education elements and principles engineer firm history knowledge language life load museum paradigm rationale review specification studio technology Commons Wikibooks Wikinews Wikiquote Wikisource Wiktionary Retrieved from "https://en.wikipedia.org/w/index.php?title=Fault_tolerance&oldid=811057702" Categories: Fault toleranceReliability engineeringComputer systemsControl engineeringSystems engineeringSoftware qualityRAIDHidden categories: Articles needing additional references from January 2008All articles needing additional referencesVague or ambiguous geographic scope from June 2017Wikipedia articles needing clarification from June 2017Wikipedia articles needing clarification from June 2014


Navigation menu Personal tools Not logged inTalkContributionsCreate accountLog in Namespaces ArticleTalk Variants Views ReadEditView history More Search Navigation Main pageContentsFeatured contentCurrent eventsRandom articleDonate to WikipediaWikipedia store Interaction HelpAbout WikipediaCommunity portalRecent changesContact page Tools What links hereRelated changesUpload fileSpecial pagesPermanent linkPage informationWikidata itemCite this page Print/export Create a bookDownload as PDFPrintable version Languages العربيةCatalàČeštinaDeutschEspañolفارسیFrançais한국어ItalianoNederlands日本語NorskPolskiPortuguêsRomânăРусскийSuomiTürkçeУкраїнська Edit links This page was last edited on 19 November 2017, at 07:40. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. Privacy policy About Wikipedia Disclaimers Contact Wikipedia Developers Cookie statement Mobile view (window.RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgPageParseReport":{"limitreport":{"cputime":"0.280","walltime":"0.371","ppvisitednodes":{"value":1785,"limit":1000000},"ppgeneratednodes":{"value":0,"limit":1500000},"postexpandincludesize":{"value":114869,"limit":2097152},"templateargumentsize":{"value":14889,"limit":2097152},"expansiondepth":{"value":16,"limit":40},"expensivefunctioncount":{"value":4,"limit":500},"entityaccesscount":{"value":0,"limit":400},"timingprofile":["100.00% 290.557 1 -total"," 20.41% 59.295 1 Template:Refimprove"," 17.70% 51.427 3 Template:Cite_journal"," 16.46% 47.820 1 Template:Design"," 15.27% 44.379 1 Template:Navbox_with_collapsible_groups"," 13.30% 38.651 1 Template:Reflist"," 13.16% 38.229 2 Template:Clarify"," 12.53% 36.409 1 Template:Ambox"," 11.59% 33.690 2 Template:Fix-span"," 9.56% 27.764 1 Template:ISBN"]},"scribunto":{"limitreport-timeusage":{"value":"0.113","limit":"10.000"},"limitreport-memusage":{"value":3963723,"limit":52428800}},"cachereport":{"origin":"mw1332","timestamp":"20180115160114","ttl":1900800,"transientcontent":false}}});});(window.RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgBackendResponseTime":89,"wgHostname":"mw1212"});});


Fault-tolerance - Photos and All Basic Informations

Fault-tolerance More Links

Wikipedia:VerifiabilityHelp:Introduction To Referencing With Wiki Markup/1Help:Maintenance Template RemovalSystemHigh-availabilityLife-critical SystemFailureComputer SystemThroughputResponse Time (technology)Computer HardwareSoftwareFatigue (material)CorrosionSelf-stabilizationEnlargeFail SafeGraceful ExitFailing BadlyFail-deadlyProgressive EnhancementFault-tolerant Computer SystemRobustness (computer Science)Software BrittlenessResilience (network)Resilience (engineering And Construction)Failure TransparencyFail-fastRedundancy (engineering)John Von NeumannGravitySeat BeltAirbagSingle Point Of FailureFault IsolationNational Institute Of Standards And TechnologyWikipedia:Naming Conventions (geographic Names)Wikipedia:Please ClarifyFirewall (computing)Wikipedia:Please ClarifyAvailability5 NinesReplication (computer Science)Parallel ComputingQuorumRedundancy (engineering)FailoverRAIDRAIDData Storage DeviceData RedundancyLockstep (computing)Replication (computing)Dual Modular RedundancyTriple Modular RedundancyLockstep (computing)Synchronization (computer Science)Nuclear ReactorChernobyl DisasterHuman SpaceflightHot SwappingMean Time Between FailureMean Time To RepairTandem ComputersNonStopUptimeReplication (computer Science)HTMLForward CompatibilityWeb BrowserWestern ElectricCrossbar SwitchControl ReconfigurationDamage ToleranceDefence In DepthElegant DegradationError-tolerant DesignFailure SemanticsFault-tolerant Computer SystemList Of System Quality AttributesResilience (ecology)Resilience (network)Safe-life DesignInternational Standard Book NumberSpecial:BookSources/978-1-4614-2112-2Brian RandellACM Computing SurveysDigital Object IdentifierInternational Standard Serial NumberP. J. DenningDigital Object IdentifierInternational Standard Serial NumberDigital Object IdentifierInternational Standard Serial NumberTemplate:Engineering ApproachesTemplate Talk:Engineering ApproachesEmpathic DesignFrugal InnovationKansei EngineeringKISS PrincipleMinimalismUse-centered DesignUser-centered DesignOrnament And CrimeOverengineeringPlanned ObsolescenceSustainabilityTheory Of ConstraintsUsabilityTemplate:DesignTemplate Talk:DesignDesignOutline Of DesignPortal:DesignDesignerCommunication DesignAdvertisingBook DesignCorporate DesignExhibit DesignFilm Title DesignGraphic DesignMotion Graphic DesignPostage Stamp DesignPrint DesignIllustrationInformation DesignInstructional DesignNews DesignPhotographyRetail DesignSignageTraffic Sign DesignTypographyType DesignVideo DesignVisual MerchandisingEnvironmental DesignArchitectureArchitectural Lighting DesignBuilding DesignPassive Solar Building DesignEcological DesignEnvironmental Impact DesignGarden DesignComputer-aided Garden DesignHealthy Community DesignHotel DesignInterior ArchitectureInterior DesignExperiential Interior DesignKeyline DesignLandscape ArchitectureSustainable Landscape ArchitectureLandscape DesignSpatial DesignUrban DesignIndustrial DesignAutomotive DesignAutomotive Suspension DesignCMF DesignCorrugated Box DesignElectric Guitar DesignFurnitureSustainable Furniture DesignHardware Interface DesignMotorcycle DesignPackaging And LabelingPhotographic Lens DesignProduct DesignProduction DesignSensory DesignService DesignInteraction DesignExperience DesignEmployee Experience DesignGame DesignLevel DesignVideo Game DesignHardware Interface DesignIcon DesignImmersive DesignInformation DesignSonic Interaction DesignUser Experience DesignUser Interface DesignWeb DesignApplied ArtsPublic ArtCeramic ArtGlass ArtFashion DesignCostume DesignJewelry DesignFloral DesignGame Art DesignProperty DesignerScenic DesignSound DesignLighting DesignerTextile DesignEngineeringAlgorithm DesignBoiler DesignConceptual DesignDatabase DesignDrug DesignElectrical System DesignDesign Of ExperimentsFilter DesignJob DesignIntegrated Circuit DesignCircuit DesignPhysical Design (electronics)Power Network Design (IC)Mechanism DesignNuclear Weapon DesignNucleic Acid DesignOrganization DesignProcess DesignProcessor DesignProtein DesignResearch DesignSocial DesignSoftware DesignSpacecraft DesignStrategic DesignSystems DesignActivity-centered DesignAdaptive Web DesignAffective DesignBrainstormingDesign By CommitteeDesign By ContractC-K TheoryDesign ClosureParticipatory DesignConcept-oriented DesignConfiguration DesignContextual DesignContinuous DesignCradle-to-cradle DesignCreative Problem-solvingCreativity TechniquesCritical DesignDesign FictionDefensive DesignDesign–bid–buildDesign–buildArchitect-led Design–buildDomain-driven DesignEcodesignEnergy Neutral DesignEngineering Design ProcessProbabilistic DesignError-tolerant DesignFault-tolerant DesignFramework-oriented DesignDesign For AssemblyDesign For Behaviour ChangeDesign For ManufacturabilityDesign For Six SigmaDesign For TestingDesign For XFunctional DesignGenerative DesignGeodesignHigh-level DesignIntegrated DesignIntegrated Topside DesignIntelligence-based DesignIterative DesignKISS PrincipleLow-level DesignMetadesignMind MapModular DesignNew Wave (design)Object-oriented DesignOpen DesignParametric DesignParticipatory DesignPlatform-based DesignPolicy-based DesignProcess-centered DesignPublic Interest DesignRational DesignRegenerative DesignReliability EngineeringResearch-based DesignResponsibility-driven DesignResponsive Web DesignSafe-life DesignSustainable DesignSystemic DesignSystems Oriented DesignTableless Web DesignTheory Of ConstraintsTop-down And Bottom-up DesignTransformation DesignTransgenerational DesignTRIZUniversal DesignDesign For All (in ICT)Usage-centered DesignUse-centered DesignUser-centered DesignEmpathic DesignUser InnovationValue-driven DesignValue Sensitive DesignPrivacy By DesignDesign ChoiceDesign ComputingDesign ControlsDesign Flow (EDA)Design LeadershipDesign ManagementDesign MarkerDesign MethodsDesign PatternDesign ResearchDesign ScienceDesign StrategyDesign TheoryDesign ThinkingDesign ToolAlgorithms-Aided Design (AAD)Architectural ModelBlueprintComprehensive LayoutComputer-aided DesignComputer-aided Industrial DesignVirtual Home Design SoftwareComputer-automated DesignDesign Quality IndicatorElectronic Design AutomationFlowchartMockupProduct Design SpecificationPrototypeSketch (drawing)StoryboardTechnical DrawingWeb Design ProgramWebsite WireframeCommunity DesignDesign AroundDesign PatentFashion Design CopyrightGeschmacksmusterIndustrial Design RightIndustrial Design Rights In The European UnionAIGAChartered Society Of DesignersDesign And Industries AssociationDesign CouncilInternational Forum DesignThe Design SocietyDesign Research SocietyEuropean Design AwardGerman Design AwardGood Design Award (Chicago)Good Design Award (Japan)GraphexIF Product Design AwardJames Dyson AwardPrince Philip Designers PrizeAestheticsAgile Software DevelopmentConcept ArtCreative IndustriesCultural Icon.designEnterprise ArchitectureFutures StudiesInnovation ManagementIntelligent DesignLean StartupNew Product DevelopmentOODA LoopPhilosophy Of DesignProcess SimulationSlow DesignSTEAM FieldsUnintelligent DesignVisualization (computer Graphics)Wicked ProblemDesign BriefDesign ChangeDesign ClassicDesign DirectorDesign EducationDesign Elements And PrinciplesDesign EngineerDesign FirmDesign HistoryDesign KnowledgeDesign LanguageDesign LifeDesign LoadDesign MuseumDesign ParadigmDesign RationaleDesign ReviewDesign SpecificationDesign StudioDesign TechnologyHelp:CategoryCategory:Fault ToleranceCategory:Reliability EngineeringCategory:Computer SystemsCategory:Control EngineeringCategory:Systems EngineeringCategory:Software QualityCategory:RAIDCategory:Articles Needing Additional References From January 2008Category:All Articles Needing Additional ReferencesCategory:Vague Or Ambiguous Geographic Scope From June 2017Category:Wikipedia Articles Needing Clarification From June 2017Category:Wikipedia Articles Needing Clarification From June 2014Discussion About Edits From This IP Address [n]A List Of Edits Made From This IP Address [y]View The Content Page [c]Discussion About The Content Page [t]Edit This Page [e]Visit The Main Page [z]Guides To Browsing WikipediaFeatured Content – The Best Of WikipediaFind Background Information On Current EventsLoad A Random Article [x]Guidance On How To Use And Edit WikipediaFind Out About WikipediaAbout The Project, What You Can Do, Where To Find ThingsA List Of Recent Changes In The Wiki [r]List Of All English Wikipedia Pages Containing Links To This Page [j]Recent Changes In Pages Linked From This Page [k]Upload Files [u]A List Of All Special Pages [q]Wikipedia:AboutWikipedia:General Disclaimer



view link view link view link view link view link