This paper will clarify a scientific coming to qoute solving. Although it is written to address facts Technology associated problems, the concepts might also be applicable in other disciplines. The methods, concepts, and techniques described here is nothing new, but it is shocking how many "problem solvers" fail to use them. In in the middle of I will comprise some real-life examples.
Why do qoute solvers guess in stead of following a scientific coming to qoute solving? Maybe because it feels quicker? Maybe a lack of palpate in efficient qoute solving? Or maybe because it feels like hard work to do it scientifically? Maybe while you keep on guessing and not actually solving, you generate more revenue and add some job security? Or maybe because you violate the first principle of qoute solving: understand the problem.
Program Cable Remote
Principle #1. Understand the *real* problem.
URC R6 Learning Remote Control Best
Rate This Product :
URC R6 Learning Remote Control Feature
- 4 My Favorite Channel Buttons
- Simple Sound.
- Macro Power.
- Illuminated Device Buttons
- Quick Setup
URC R6 Learning Remote Control Overview
Learning remote control combines 6 remote controls into 1. Operates virtually all brands of Audio, TV, DVD, VCR, Cable and Satellite devices.Quick and easy setup allows customization to satisfy specific user needs. Thousands of pre-programmed device codes assure it will control your components, and it's learning capability means it will never be obsolete. 4 My Favorite Channel Buttons. MacroPower and SimpleSound Volume Control.
Customer Reviews
*** Product Information and Prices Stored: Jan 23, 2012 06:54:17
Isn't it sure that before you can solve, you need to understand the problem? Maybe. But, most of the time the solver will start solving without knowing the real problem. What the client or user narrate as "The Problem" is commonly only the symptom! "My computer does not want to switch on" is the symptom. The real qoute could be that the whole building is without power. "Every time I try to add a new product, I get an error message" is the symptom. Here the real qoute could be "Only the last 2 products I tried to add gave a 'Product already exists' error". Someone else first-rate example: "Nothing is working"...
You start your investigation by defining the "real problem". This will entail request questions (and sometimes verify them), and doing some basic testing. Ask the user questions like "when was the last time it worked successfully?", "How long have you been using the system?", "Does it work on Someone else Pc or Someone else user?", "What is the exact error message?" etc. Ask for a screen-print of the error if possible. Your basic testing will be to ensure the end-to-end equipment is up and running. Check the user's Pc, the network, the Web Server, Firewalls, the File Server, the Database back-end, etc. Best-case you will pint-point the qoute already. Worst-case you can eliminate a lot of areas for the cause of the problem.
A real life example. The indication of illness according to the user: "The ideas hangs up at random times when I place orders". The environment: The user enters the order information on a form in a mainframe application. When all the information is completed, the user will tab off the form. The mainframe then sends this information via transportation software to an Oracle Client/Server ideas at the plant. The Oracle ideas will do capacity planning and whether returns an error or an incredible order date back to the mainframe system. This qoute is quite serious, because you can loose clients if they try to place orders and the ideas does not accept them! To exertion to solve this problem, people started by investigating: 1) The load and capacity of the mainframe hardware 2) Monitoring the network load in the middle of the mainframe and the Oracle ideas 3) Hiring consultants to debug the transportation software 4) Debugging the Oracle capacity planning ideas After spending a consolidate of months they could not solve the problem.
The "Scientific qoute Solver" was called in. It took less than a day and the qoute was solved! How? The solver spends the day at the user to see what the "real problem" was. It was found that the qoute only occurs with export orders. By investigating the capture screen and user actions, it was found that with export orders the last field on the form is always left blank and the user did not tab off this field. The ideas was not hanging, it waited for the user to press "tab" Someone else time. qoute solved. It can be noted that the "Scientific qoute Solver" had very small knowledge of the mainframe, of the order capturing system, of the transportation software, and of the Oracle capacity planning system. And this brings us at Principle#2.
Principle #2. Do not be afraid to start the solving process, even if you do not understand the system.
How many times have you heard "I cannot touch that code, because it was industrialized by man else!", or "I cannot help because I am a Hr counselor and that is a Finance problem"? If you washing motor does not want to switch on, you do not need to be an Electrical Engineer, Washing motor repair Specialist, Technician, or whatever master to do some basic fault finding. Make sure the plug is working. Check the trip-switch, etc. "I have never seen this error before" should not stop you from attempting to solve. With the error message and an Internet search engine, you can get lots of starting points.
In every complicated ideas there are a consolidate of basic working principles. ideas A that reads data from ideas B can be horribly complicated (maybe a Laboratory Spectrometer that reads data from a Programmable Logic Computer via an Rs-232 port). But, some basics to test for: Does both systems have power? Is there an error message in the event log on one of these systems? Can you "ping" or trace a network packet from the one ideas to the other? Try a dissimilar transportation cable. search the internet for the error message.
Once you have established what the qoute is, you need to start solving it. Sometimes the initial investigation will point you directly to the solution (switch the power on; replace the faulty cable, etc). But, sometimes the real qoute is complicated in itself, so the next principle is to solve it simple.
Principle #3. Conquer it simple.
Let's start this section with a real-life example. Under sure conditions, a stored course will hang. The stored course commonly takes about an hour to run (when it is not hanging). So, the developer tried to debug. Make some changes and then wait Someone else hour or so to see if the qoute is solved. After some days the developer gave up and the "Problem Solver" took over. The "Problem Solver" had to his disposal the knowledge under witch conditions the stored course would hang. So, it was a uncomplicated rehearsal to make a copy of the procedure, and then with this copy to strip all unnecessary code. All parameters were changed with hard-coded values. Bits of code were executed at a time and the result-sets were then again hard-coded into the copy of the procedure. Within 3 hours the qoute was solved. An infinite-loop was discovered.
What the "Problem Solver" did, was to replicate the qoute and at the same time tried to detach the code that caused the problem. In doing so, the complicated (and time consuming) stored course became something fast and simple.
If the qoute is inside an application, generate a new application and try to simulate the qoute inside the new application as uncomplicated as possible. If the qoute occurs when a sure recipe for a sure control gets called, then try to only comprise this control in the empty application and call that recipe with hard-coded values. If the qoute is with embedded Sql inside a C# application, then try to simulate the Sql inside of a Database Query tool (like Sql*Plus for Oracle, Query Analyzer for Sql Server, or use the code in Ms Excel via Odbc to the database).
The occasion you can replicate the qoute in a uncomplicated way, you are more than 80% on your way to solve it.
If you do not know where in the program the qoute is, then use Debug.
Principle #4. Debug.
Most application development tools come accepted with a debugger. Weather it is Macromedia Flash, Microsoft Dot Net, Delphi, or what ever development environment there will be some sort of debugger. If the tool does not come accepted with a debugger, then you can simulate one.
The first thing you want to do with the debugger is to rule where the qoute is. You do this by adding breakpoints at key areas. Then you run the program in debug mode and you will know in the middle of which breakpoints the qoute occurred. Drill down and you will find the spot. Now that you know where the qoute is, you can "conquer it simple"
Another nice highlight of most debuggers includes the facility to watch variables, values, parameters, etc. As you step through the program. With these values known at sure steps, you can hard-code them into your "simplified version" of the program
If a development tool does not sustain debugging, then you can simulate it. Put in steps in the program that outputs changeable values and "hello I am here" messages whether to the screen, to a log file, or to a database table. Remember to take them out when the qoute is resolved... You don't want your file ideas to be cluttered or filled up with log files!
Principle #5. There is a wealth of facts on the database back-end that will help to solve a problem.
The "Problem Solver" was called to help solve a very tricky problem. A scheme was migrating ideas from a mainframe to client-server technology. All went well during testing, but when the systems went live, all of a sudden there were quite a few, and quite random "General protection Faults". (The Gpf-error was the normal error trap in Windows 95 and 98). It was tried to simplify the code, debugging was attempted, but it was impossible to replicate. In the Lab environment, the qoute would not occur! Debugging trace messages to log files indicated that the qoute occurred very randomly. Some users experienced it more than others, but eventually all users will get them! piquant problem.
The "Problem Solver" solved this after he started to analyze the database back-end. Not sure if it was by chance or because he systematically moved in the right direction because of a scientific approach. through tracing what is happening on the back-end level, it was found that all these applications were creating more-and-more connections to the database. Every time a user starts a new transaction Someone else connection was established to the database. The sum-total of the connections were only released when the application was closed. As the user navigated to new windows inside the same application, more and more connections are opened, and after a definite number of connections, the application will have enough and then crash. This was a programming fault in a template that was used by all the developers. The solution was to first test if a cursor to the database is already open, before chance it again.
How do you trace on the back-end database what is happening? The main database providers have Gui tools that help you to trace or analyze what queries are fired against the database. It will also show you when people connect, disconnect, or were unable to connect because of protection violations. Most databases also comprise some ideas dictionary tables that can be queried to get this information. These traces can sometimes tell 'n whole story of why something is failing. The query code you retrieve from the trace can be help to "simplify the search". You can see from the trace if the program makes thriving palpate with the database. You can see how long it takes for a query to execute.
To add to Principle#2 (do not be afraid to start...); you can analyze this trace information, even though you might not know whatever about the information of the application.
Remember though that these back-end traces can put a strain on the back-end resources. Do not leave them running for unnecessary long.
Principle #6. Use fresh eyes.
This is the last principle. Do not spend too much time on the qoute before you ask for assistance. The assistance does not have to be from man more senior than you. The principle is that you need a pair of fresh eyes for a fresh perspective and sometimes a bit of fresh air by taking a break. The other man will look and then ask a query or two. Sometimes it is something very sure that was missed. Sometimes just by answering the query it makes you think in a new directions. Also, if you spend hours finding at the same piece of code, it is very easy to start finding over a silly mistake. A lot of finance balancing problems get solved over a beer. It could be a change of scenery, and/or the relaxed climate that will pop out the solution. Maybe it is the fresh oxygen that went to the brain while walking to the pub. Maybe it is because the qoute got discussed with man else.
Conclusion
After reading this paper, the author hope that you will try these the next time you encounter a qoute to solve. Hopefully by applying these six ideas you will comprehend the advantages they bring, rather than to "guess" your way to a solution.
facts Technology qoute Solving - The 6 principles of Scientific qoute SolvingHow to install a car remote start (roughly) PART 3 Tube. Duration : 4.28 Mins.This Video and the following 2 parts are just a rough overview about how to install a remote starter kit in your car. The car I am installing this in is my 3.8L fully loaded Dodge Grand Caravan. YES I DRIVE A MINIVAN and I dont have kids, so what? xD Anyway I want to show how complex this job is and that it sure aint easy. If you have knowledge as technician or electrician you will be fine, if you are COMPLETLY new to this kinda stuff, I recommend to see a dealership or a outfitter to get your remote start installed. Installing these kind of systems wrong into your car, could cause the electronics to fail. I have never done this before and received no help, so understand this is not to show you how YOU HAVE TO do it, I simply want to show you what needs doing, if you decide to install a cheapy kit. Messing with the security controller (transponder module) could prevent you from driving back home, if damaged during install. As an advice, when you program the transponder module to override the factory anti theft and you fail, DO NOT REPROGRAM right away or try to start the car by remote. Instead, insert the key and start the car until the Anti theft module is reset (let it run for 20 seconds). It WILL lock you out, if you attempt to start the car more than 4 times without having the right "disarm chip". Once the original key is inserted and the car ran, the module will be set to zero counts of fail starts and you will be fine. As for the complainers and haters. Sure there ...
Tags: remote, car, starter, pro, start, dodge, 3.8l
No comments:
Post a Comment