WordNet

solve problems; "He is known to be good at trouble-shooting" (同)troubleshoot
variegate by interweaving weft threads of different colors; "shoot cloth"
produce buds, branches, or germinate; "the potatoes sprouted" (同)spud, germinate, pullulate, bourgeon, burgeon forth, sprout
a new branch
the act of shooting at targets; "they hold a shoot every weekend during the summer"
hit with a missile from a weapon (同)hit, pip
kill by firing a missile (同)pip
cause a sharp and sudden pain in; "The pain shot up her leg"
emit (as light, flame, or fumes) suddenly and forcefully; "The dragon shot fumes and flames out of its mouth"
measure the altitude of by using a sextant; "shoot a star"
score; "shoot a basket"; "shoot a goal"
send forth suddenly, intensely, swiftly; "shoot a glance"
throw dice, as in a crap game
throw or propel in a specific direction or towards a specific objective; "shoot craps"; "shoot a golf ball"
utter fast and forcefully; "She shot back an answer"
to cause inconvenience or discomfort to; "Sorry to trouble you, but..." (同)put_out, inconvenience, disoblige, discommode, incommode, bother
cause bodily suffering to and make sick or indisposed (同)ail, pain
an unwanted pregnancy; "he got several girls in trouble"
an effort that is inconvenient; "I went to a lot of trouble"; "he won without any trouble"; "had difficulty walking"; "finished the test only with great difficulty" (同)difficulty
a source of difficulty; "one trouble after another delayed the job"; "whats the problem?" (同)problem
an event causing distress or pain; "what is the trouble?"; "heart trouble"
the act of firing a projectile; "his shooting was slow but accurate" (同)shot
killing someone by gunfire; "when the shooting stopped there were three dead bodies"
characterized by or indicative of distress or affliction or danger or need; "troubled areas"; "fell into a troubled sleep"; "a troubled expression"; "troubled teenagers"

PrepTutorEJDIC

(…に)〈銃・大砲〉‘を'『撃つ』,発射する,〈弓など〉‘を'射る,〈弾丸・矢など〉‘を'放つ《+『名』+『at』(『toward』)+『名』》・〈人・物〉‘を'『撃つ』,射る・(…に)〈質問・用葉・考えなど〉‘を'矢つぎばやに出す,浴びせかける《+『名』+『at』(『on』)+『名』》 / (…に)〈光・視線・微笑など〉‘を'放つ,向ける《+『名』+『at』(『on』)+『名』》・〈手・足など〉‘を'突き出す,〈芽・枝など〉‘を'出す《『out』+『名,』+『名』+『out』》・〈急流など〉‘を'矢のように下る / 〈かんぬきなど〉‘を'すっとはめる(はずす) ・《おもに受動態で》(違ったものを)…‘に'織り込む・差し込む,すっと入れる《+『名』+『with』+『名』》・〈写真・映画・テレビ〉‘を'取る,撮影する / 〈ボール・アイスホッケーのパック〉‘を'ゴールにシュートする・《英》〈動物〉‘を'銃猟する;〈場所〉‘を'銃猟して歩く・『射撃する』;(…を)ねらった撃つ《+『at』+『名』》・〈銃・大砲などが〉発射される・《副詞[句]を伴って》す早く動く,矢のように走る,勢いよく出る・突き出る;芽(枝)を出す《+『out』》・(ボール・アイスホッケーをパックなどをゴールに)シュートする・《英》銃猟をする・《米話》話し始める・新芽,若枝・射撃試合,競射会;《英》遊猟会 / 射撃,発砲,発射;《米》)ロケット・宇宙船の)打ち上げ
〈U〉『苦難』,心配,悩み / 〈C〉『苦労の種』,心配事,悩みの種 / 〈U〉危険[な状態],困難 / 〈U〉『骨折り』,手数,めんどう,迷惑 / 〈C〉〈U〉(政治的・社会的)紛争,騒動 / 〈U〉(機械などの)故障 / 〈C〉〈U〉病気 / 〈事が〉〈人・自分〉‘を'『悩ます』,心配させる,苦しめる / 《物事を頼むときていねいに》〈人〉‘を'『わずらわす』,じゃまする / 〈水・空気など〉‘を'かき乱す / 《おもに疑問文・否定文で》心配する,気を遣う;骨を折る
射撃,発射 / 銃猟 / 銃猟権
心配そうな,当惑した / 乱れた,荒れた
シイ!,シッ!(鳥や動物を追い払う声) / 〈鳥や動物〉‘を'シーッと追い払う《+『名』+『away』(『off』),+『away』(『off』)+『名』》 / シイ(シーッ)と言う[擬声語]

Wikipedia preview

出典(authority):フリー百科事典『ウィキペディア（Wikipedia）』「2016/09/12 02:57:19」(JST)

wiki en

Troubleshooting is a form of problem solving, often applied to repair failed products or processes. It is a logical, systematic search for the source of a problem in order to solve it, and make the product or process operational again. Troubleshooting is needed to identify the symptoms. Determining the most likely cause is a process of elimination—eliminating potential causes of a problem. Finally, troubleshooting requires confirmation that the solution restores the product or process to its working state.

In general, troubleshooting is the identification of diagnosis of "trouble" in the management flow of a corporation or a system caused by a failure of some kind. The problem is initially described as symptoms of malfunction, and troubleshooting is the process of determining and remedying the causes of these symptoms.

A system can be described in terms of its expected, desired or intended behavior (usually, for artificial systems, its purpose). Events or inputs to the system are expected to generate specific results or outputs. (For example, selecting the "print" option from various computer applications is intended to result in a hardcopy emerging from some specific device). Any unexpected or undesirable behavior is a symptom. Troubleshooting is the process of isolating the specific cause or causes of the symptom. Frequently the symptom is a failure of the product or process to produce any results. (Nothing was printed, for example). Corrective action can then be taken to prevent further failures of a similar kind.

The methods of forensic engineering are especially useful in tracing problems in products or processes, and a wide range of analytical techniques are available to determine the cause or causes of specific failures. Corrective action can then be taken to prevent further failure of a similar kind. Preventative action is possible using failure mode and effects (FMEA) and fault tree analysis (FTA) before full-scale production, and these methods can also be used for failure analysis.

Aspects

Usually troubleshooting is applied to something that has suddenly stopped working, since its previously working state forms the expectations about its continued behavior. So the initial focus is often on recent changes to the system or to the environment in which it exists. (For example, a printer that "was working when it was plugged in over there"). However, there is a well known principle that correlation does not imply causality. (For example, the failure of a device shortly after it has been plugged into a different outlet doesn't necessarily mean that the events were related. The failure could have been a matter of coincidence.) Therefore, troubleshooting demands critical thinking rather than magical thinking.

It is useful to consider the common experiences we have with light bulbs. Light bulbs "burn out" more or less at random; eventually the repeated heating and cooling of its filament, and fluctuations in the power supplied to it cause the filament to crack or vaporize. The same principle applies to most other electronic devices and similar principles apply to mechanical devices. Some failures are part of the normal wear-and-tear of components in a system.

A basic principle in troubleshooting is to start from the simplest and most probable possible problems first. This is illustrated by the old saying "When you see hoof prints, look for horses, not zebras", or to use another maxim, use the KISS principle. This principle results in the common complaint about help desks or manuals, that they sometimes first ask: "Is it plugged in and does that receptacle have power?", but this should not be taken as an affront, rather it should serve as a reminder or conditioning to always check the simple things first before calling for help.

A troubleshooter could check each component in a system one by one, substituting known good components for each potentially suspect one. However, this process of "serial substitution" can be considered degenerate when components are substituted without regard to a hypothesis concerning how their failure could result in the symptoms being diagnosed.

Simple and intermediate systems are characterized by lists or trees of dependencies among their components or subsystems. More complex systems contain cyclical dependencies or interactions (feedback loops). Such systems are less amenable to "bisection" troubleshooting techniques.

It also helps to start from a known good state, the best example being a computer reboot. A cognitive walkthrough is also a good thing to try. Comprehensive documentation produced by proficient technical writers is very helpful, especially if it provides a theory of operation for the subject device or system.

A common cause of problems is bad design, for example bad human factors design, where a device could be inserted backward or upside down due to the lack of an appropriate forcing function (behavior-shaping constraint), or a lack of error-tolerant design. This is especially bad if accompanied by habituation, where the user just doesn't notice the incorrect usage, for instance if two parts have different functions but share a common case so that it is not apparent on a casual inspection which part is being used.

Troubleshooting can also take the form of a systematic checklist, troubleshooting procedure, flowchart or table that is made before a problem occurs. Developing troubleshooting procedures in advance allows sufficient thought about the steps to take in troubleshooting and organizing the troubleshooting into the most efficient troubleshooting process. Troubleshooting tables can be computerized to make them more efficient for users.

Some computerized troubleshooting services (such as Primefax, later renamed Maxserve), immediately show the top 10 solutions with the highest probability of fixing the underlying problem. The technician can either answer additional questions to advance through the troubleshooting procedure, each step narrowing the list of solutions, or immediately implement the solution he feels will fix the problem. These services give a rebate if the technician takes an additional step after the problem is solved: report back the solution that actually fixed the problem. The computer uses these reports to update its estimates of which solutions have the highest probability of fixing that particular set of symptoms.^[1]

Half-splitting

Efficient methodical troubleshooting starts on with a clear understanding of the expected behavior of the system and the symptoms being observed. From there the troubleshooter forms hypotheses on potential causes, and devises (or perhaps references a standardized checklist of) tests to eliminate these prospective causes. This approach is often called "Divide and Conquer".

Two common strategies used by troubleshooters are to check for frequently encountered or easily tested conditions first (for example, checking to ensure that a printer's light is on and that its cable is firmly seated at both ends). This is often referred to as "milking the front panel."^[2]

Then, "bisect" the system (for example in a network printing system, checking to see if the job reached the server to determine whether a problem exists in the subsystems "towards" the user's end or "towards" the device).

This latter technique can be particularly efficient in systems with long chains of serialized dependencies or interactions among its components. It is simply the application of a binary search across the range of dependencies and is often referred to as "half-splitting".^[3]

Reproducing symptoms

One of the core principles of troubleshooting is that reproducible problems can be reliably isolated and resolved. Often considerable effort and emphasis in troubleshooting is placed on reproducibility ... on finding a procedure to reliably induce the symptom to occur.

Intermittent symptoms

Some of the most difficult troubleshooting issues relate to symptoms which occur intermittently. In electronics this often is the result of components that are thermally sensitive (since resistance of a circuit varies with the temperature of the conductors in it). Compressed air can be used to cool specific spots on a circuit board and a heat gun can be used to raise the temperatures; thus troubleshooting of electronics systems frequently entails applying these tools in order to reproduce a problem.

In computer programming race conditions often lead to intermittent symptoms which are extremely difficult to reproduce; various techniques can be used to force the particular function or module to be called more rapidly than it would be in normal operation (analogous to "heating up" a component in a hardware circuit) while other techniques can be used to introduce greater delays in, or force synchronization among, other modules or interacting processes.

Intermittent issues can be thus defined:

An intermittent is a problem for which there is no known procedure to consistently reproduce its symptom.

— Steven Litt, [1]

In particular he asserts that there is a distinction between frequency of occurrence and a "known procedure to consistently reproduce" an issue. For example, knowing that an intermittent problem occurs "within" an hour of a particular stimulus or event ... but that sometimes it happens in five minutes and other times it takes almost an hour ... does not constitute a "known procedure" even if the stimulus does increase the frequency of observable exhibitions of the symptom.

Nevertheless, sometimes troubleshooters must resort to statistical methods ... and can only find procedures to increase the symptom's occurrence to a point at which serial substitution or some other technique is feasible. In such cases, even when the symptom seems to disappear for significantly longer periods, there is a low confidence that the root cause has been found and that the problem is truly solved.

Also, tests may be run to stress certain components to determine if those components have failed. ^[4]

Multiple problems

Isolating single component failures which cause reproducible symptoms is relatively straightforward.

However, many problems only occur as a result of multiple failures or errors. This is particularly true of fault tolerant systems, or those with built-in redundancy. Features which add redundancy, fault detection and failover to a system may also be subject to failure, and enough different component failures in any system will "take it down."

Even in simple systems the troubleshooter must always consider the possibility that there is more than one fault. (Replacing each component, using serial substitution, and then swapping each new component back out for the old one when the symptom is found to persist, can fail to resolve such cases. More importantly the replacement of any component with a defective one can actually increase the number of problems rather than eliminating them).

Note that, while we talk about "replacing components" the resolution of many problems involves adjustments or tuning rather than "replacement." For example, intermittent breaks in conductors --- or "dirty or loose contacts" might simply need to be cleaned and/or tightened. All discussion of "replacement" should be taken to mean "replacement or adjustment or other maintenance."

References

^ "Troubleshooting at your fingertips" by Nils Conrad Persson. "Electronics Servicing and Technology" magazine 1982 June.
^ "Hewlett Packard Bench Briefs" (PDF). Hewlett Packard. Retrieved 14 October 2011.
^ Sullivan, Mike (Nov 15, 2000). "Secrets of a super geek: Use half splitting to solve difficult problems". TechRepublic. Archived from the original on 8 July 2012. Retrieved 22 October 2010.
^ http://www.ocf.berkeley.edu/~joyoung/trouble/page1.shtml

UpToDate Contents

全文を閲覧するには購読必要です。 To read the full text you will need to subscribe.

1. 錠剤を嚥下できないHIV感染成人患者の治療：液剤、チュアブル、および砕くことができる剤形の薬剤 treatment of hiv infected adults who have trouble swallowing pills liquid chewable and crushable formulations
2. 小児および思春期の自殺行動：疫学および危険因子 suicidal behavior in children and adolescents epidemiology and risk factors
3. 小児および思春期のアスリートにおける脊椎分離症および脊椎すべり症：マネージメント spondylolysis and spondylolisthesis in child and adolescent athletes management
4. 胸部CTの原理 principles of computed tomography of the chest
5. 多発性結節性病変の鑑別診断および評価 differential diagnosis and evaluation of multiple pulmonary nodules

English Journal

"How Hard Could it Be?" A Descriptive Analysis of Errors Made on a Validated Lifetime Physical Activity Questionnaire.

Anderton N1, Newhouse ME, Ainsworth BE, Nygaard IE, Egger MJ, Shaw JM.
Journal of physical activity & health.J Phys Act Health.2015 Mar;12(3):388-94. doi: 10.1123/jpah.2013-0247. Epub 2014 May 6.
BACKGROUND: Measuring historical physical activity in epidemiologic research depends on self-report. We aimed to describe data reporting errors women made in completing 2 validated questionnaires: Lifetime Physical Activity Questionnaire (LPAQ) and Occupational Questionnaire (OQ).METHODS: Participan
PMID 24809450

Cell squeezing as a robust, microfluidic intracellular delivery platform.

Sharei A1, Cho N, Mao S, Jackson E, Poceviciute R, Adamo A, Zoldan J, Langer R, Jensen KF.
Journal of visualized experiments : JoVE.J Vis Exp.2013 Nov 7;(81):e50980. doi: 10.3791/50980.
Rapid mechanical deformation of cells has emerged as a promising, vector-free method for intracellular delivery of macromolecules and nanomaterials. This technology has shown potential in addressing previously challenging applications; including, delivery to primary immune cells, cell reprogramming,
PMID 24300077

Supporting self-management after attending a structured education programme: a qualitative longitudinal investigation of type 1 diabetes patients' experiences and views.

Rankin D1, Cooke DD, Elliott J, Heller SR, Lawton J; UK NIHR DAFNE Study Group.
BMC public health.BMC Public Health.2012 Aug 14;12:652. doi: 10.1186/1471-2458-12-652.
BACKGROUND: Structured education programmes for patients with diabetes and other chronic conditions are being widely adopted. However, follow-up studies suggest that course graduates may struggle to sustain the self-care practices taught on their courses over time. This study explored the support ne
PMID 22891794

Japanese Journal

乳幼児の採血・注射時に親が同席することの現状と看護師の認識

日本小児看護学会誌 17(1), 51-57, 2008-03-20
NAID 110007461762

電気制御システムにおけるトラブルシュート支援機能の開発

電気学会研究会資料. MID, 金属産業研究会 2006(7), 19-22, 2006-06-23
NAID 10018156640

コールセンタを利用したトラブルベース学習(社会心理とコミュニケーション及び一般)

電子情報通信学会技術研究報告. HCS, ヒューマンコミュニケーション基礎 105(306), 23-28, 2005-09-19
NAID 110003271850

Related Pictures

TROUBLESHOOT ] AT&T U-verse Troubleshoot & Resolve Mobile Troubleshoot (Windows 8) Troubleshoot any Issue Using Windows Help How to troubleshoot your computer. Troubleshooting Computer Problems With A Troubleshoot cutout in a sketch for cause