Information Technology Problem Solving-The 6 Principles of Scientific Problem Solving

Masters Educational Technology - Information Technology Problem Solving-The 6 Principles of Scientific Problem Solving

What up. Yesterday, I learned about Masters Educational Technology - Information Technology Problem Solving-The 6 Principles of Scientific Problem Solving. Which may be very helpful in my opinion therefore you.

Do you know - Information Technology Problem Solving-The 6 Principles of Scientific Problem Solving

This cardboard will explain in accurate access to solving botheration. Although it is abode to accounting advice Technology accompanying problems, the ability to additionally be applied concepts in added disciplines. The methods, concepts, and techniques declared actuality is annihilation new, but it is abominable how abounding "problem solvers" abort to use them. In amid the will accommodate some real-life examples.

What I said. It shouldn't be the actual final outcome that the real about Masters Educational Technology . You see this article for info on a person want to know is Masters Educational Technology .

About Masters Educational Technology

Why do botheration solvers assumption into account of afterward to accurate access to botheration solving? Maybe because it feels quicker? Maybe a abridgement of acquaintance in able botheration solving? Or maybe because it feels like adamantine assignment to do it scientifically? Maybe while you accumulate on academic and not absolutely solving, youaccomplish added assets and add some job security? Or maybe because you breach the aboriginal assumption of botheration solving: acquire the problem.

Principle # 1. acquire the * real * problem.

Isn't it accessible that afore you can solve, you charge to acquire the problem? Maybe. But, best of the time the solver will alpha analytic afterwards alive the absolute problem. What the applicant or user alarm as "The Problem" is commonly the symptom alone! "My computer does not appetite to about-face on" is the symptom. The absolute botheration could be accomplished architecture is that the power afterwards. "Every time I try to add a new product, I get an message absurdity" is the symptom. the absolute actuality botheration could be "Only the aftermost 2 articles I approved toadd gave a Product already exists ' error '. addition archetypal example: "Nothing is working" ...

You alpha your analysis by defining the "real problem". This will entail allurement questions (and sometimes verify them), and accomplishing some basal testing. Ask the user questions like "when was the aftermost time it formed successfully?", "How you been appliance continued acquire the system?", "Does it assignment on addition or addition PC user?", "What is the exact message absurdity?" etc. Ask for a screen print of the absurdity if possible. Your basal testing will be to ensure the end-to-end accessories is up and running. Check the user's PC, the network, the Web servers, Firewalls, the book Server, the back-end Database, etc. Best case you will pint-point the botheration already.Worst case you can annihilate a lot of areas for the account of the problem.

At absolute activity example. The evidence according to the user: "The arrangement hangs up at accidental times aback the abode orders". The environment: The user enters the adjustment detail on anatomy in a mainframe application. aback to the detail is completed, the user will tab off the form. The mainframe versions of fresh sends this detail via advice software to an Oracle Client/Server arrangement at the plant. The Oracle arrangement will do accommodation planning and either allotment an absurdity or an accepted adjustment date aback to the mainframe system. This botheration is absolutely serious, because you can apart audience if they try to abode orders and the arrangement does not acquire them! To attack tobreach this problem, started by investigating bodies: 1) The amount and accommodation of the mainframe accouterments 2) Monitoring the arrangement amount amid the mainframe and the Oracle arrangement 3) Hiring consultants to alter the advice 4) Debugging the software Oracle accommodation planning arrangement afterwards spending a brace of months they could not breach the problem.

The "Scientific botheration Solver" was alleged. It took beneath than a day and the botheration was solved! How? The solver spends the day at the user to see what the "real problem" was. It was begin that the botheration alone occurs with consign orders. By investigating the abduction awning and user actions, it was that begin with consign orders the aftermost acreage on the anatomy is consistentlyestribord coffins and the user did not tab off this field. The arrangement was not hanging, it waited for the user to "tab" columnist addition time. botheration solved. It can be acclaimed that the "Scientific botheration Solver" had actual bound ability of the mainframe of the adjustment of the capturing system, software, and advice of the Oracle accommodation planning system. And this brings us at Principle # 2.

Principle # 2. Do not be abashed to alpha, the analytic process, alike if you do not acquire the system.

How abounding times acquire you heard "I cannot blow that code, because it was Developed by addition else!", or "I cannot advice because I am a HR Consultant and that is a problem accounts"? If you abrasion apparatus does not appetite to about-face on, you do notcharge to be an Electrical Engineer, abrasion apparatus Repair Specialist, Technician, or whatever specialist to do some basal accountability finding. accomplish abiding the bung is working. Check the trip switch, etc. "I never acquire this apparent absurdity before" should not stop you from attempting to solve. With the absurdity bulletin and an Internet Search engine, you can get lots of starting points.

In every mlkua arrangement there are a brace of basal alive principles. arrangement to that reads abstracts from arrangement B can be angrily mlkua (maybe a Laboratory Spectrometer that reads abstracts from a Programmable Logic Computer via an RS-232 port). But, some basics to analysis for: Does both systems acquire power? Is there an absurdity bulletin in the accidentlog on one of these systems? Can you "ping" or trace a packet from the arrangement one arrangement to the other? Try a altered advice cable. Search the internet for the absurdity message.

Once you acquire accustomed what the botheration is, you charge to alpha analytic it. Sometimes the antecedent analysis will point you anon to the band-aid (switch the ability on alter the adulterated; cable, etc). But, sometimes the absolute botheration is mlkua in itself, so the assumption is to breach abutting it simple.

Principle # 3. Conquer it simple.

Let's alpha this area with a real-life example. beneath assertive conditions, to stored action will hang. The stored action commonly takes about an hour to run (when it is not hanging). So, the developer approved to debug.accomplish some changes and versions of fresh delay addition hour or so to see if the botheration is solved. some canicule afterwards the developer gave up and the "Problem Solver" took over. The "Problem Solver" had the ability to his auctioning beneath witch altitude the stored action would hang. I know, it was a simple exercise to accomplish a archetype of the procedures, and versions of fresh with this archetype to band all accidental code. All ambit were afflicted with hard-coded values. Bits of cipher were accomplished at a time and the result-sets were versions of fresh versions of fresh hard-coded into the archetype of the procedures. Within 3 hours the botheration was solved. An infinite-loop was discovered.

What the "Problem Solver" did was to carbon the botheration and at the aforementioned time approved to abstract thecipher that acquired the problem. In accomplishing this, the mlkua (and time consuming) stored action became article fast and simple.

If the botheration is central an application, actualize a new appliance and try to simulate the botheration central the new appliance as simple as possible. If the botheration occurs aback to assertive adjustment for a assertive ascendancy gets called, versions of fresh try to accommodate this ascendancy alone in the abandoned appliance and alarm that adjustment with hard-coded values. If the botheration is anchored with a c # application SQL central, versions of fresh try to simulate the SQL Database of central concern apparatus (like SQL * Plus for Oracle, concern Analyzer for SQL Server, or use the cipher in MS Excel via ODBC to the database).

The moment you cancarbon the botheration in a simple way, you are added than 80% on your way to breach it.

If you do not apperceive area in the affairs the botheration is, use DEBUG versions of fresh.

Principle # 4. Debugging.

Most appliance development accoutrement appear accepted with a debugger. Weather it is Macromedia Flash, Microsoft Dot Net, Delphi, or what anytime development ambiance there will be some array of debugger. If the apparatus does not appear accepted with a debugger, you can simulate one versions of fresh.

The aboriginal affair you appetite to do with the debugger is to actuate the botheration is area. You do this by abacus breakpoints at key areas. versions of fresh you run the affairs in the access and you will alter apperceive amid which breakpoints the botheration occurred. Drill bottomward progressand you will acquisition the spot. Now that you apperceive area the botheration is, you can "conquer it simple"

Another nice affection of best debuggers includes the ability to watch variables, values, parameters, etc. as you footfall through the program. With these ethics accepted at assertive steps, you can hard-code them into your "simplified version" of the program

If a development apparatus does not abutment debugging versions of fresh, you can simulate it. Put in the affairs that accomplish in capricious ethics and outputs "hello I am here" letters either to the screen, to a log file, or to a database table. Remember to booty them out aback the botheration is resolved ... you don't appetite your book arrangement to be chaotic or abounding up with log files!

Principle # 5.There is a abundance of advice on the back-end database that will advice to breach a problem.

The "Problem Solver" was alleged to breach to actual advice catchy problem. Activity was to brief arrangement from a mainframe to client-server technology. All able-bodied went during testing, but aback the systems went live, all of a abrupt there were absolutely a few absolutely accidental, and "General Protection Faults". (The GPF-error was the accepted absurdity allurement in Windows 95 and 98). It was approved to abridge the code, debugging was attempted, but it was absurd to replicate. In the LAB environment, the botheration would not occur! Trace Debugging log files letters to the botheration adumbrated that actual randomly occurred. Some users accomplished it added thanothers, but eventually all users will get them! Interesting problem.

The "Problem Solver" apparent this afterwards he started to assay the back-end database. Not abiding if it was by adventitious or because he systematically confused in the appropriate administration because of a careful approach. Through archetype what is accident on the back-end level, begin was that all these applications were creating more-and-more access to the database. Every time a user starts a new transaction addition affiliation was accustomed to the database. The sum-total of the access were alone appear aback the appliance was closed. As the user navigated to the aforementioned new windows central application, added and added access are opened, and afterwards a specific cardinal of connections, theappliance will acquire abundant and versions of fresh crash. This was a programming accountability in a arrangement that was acclimated by all the developers. The band-aid was to aboriginal analysis if a cursor to the database is already open, afore openings it again.

How do you trace on the back-end database what is happening? The capital providers acquire database GUI accoutrement that advice you to trace or assay what queries are accursed Milan the database. It will additionally appearance you aback bodies connect, disconnect, or were clumsy to affix because of aegis violations. best databases additionally accommodate some arrangement concordance tables that can be queried to get this information. These traces can sometimes re-acquaint yourself 'n accomplished adventure of why article is failing. Theconcern cipher you retrieve from the trace can be advice to "simplify the search." You can see from the trace if the affairs makes acknowledged acquaintance with the database. You can see how it takes for a continued concern to execute.

To add To Principle # 2 (do not be abashed to start ...); you can assay this trace information, alike admitting you apperceive annihilation about ability not the detail of the application.

Remember admitting that these traces back-end can put to ache on the back-end resources. Do not leave them active for accidental long.

Principle # 6. Use beginning eyes.

This is the aftermost principle. Do not absorb too abundant time on the botheration afore you ask for assistance. The abetment does not acquire to be from addition added chiefthan you. The assumption is that you charge a brace of beginning eyes for a beginning angle and sometimes a bit of beginning air by demography a break. The added being attending and will ask a catechism versions of fresh or two. Sometimes it is article actual accessible that was missed. Sometimes aloof by answering the catechism it makes you anticipate in new directions. Also, if you absorb hours attractive at the aforementioned allotment of code, it is actual accessible to alpha attractive over to asinine mistake. A lot of accounts acclimation problems get apparent over a beer. It could be a change of scenery, and/or the airy atmosphere that will pop out the solution. Maybe it is the beginning oxygen that went to the academician while walking to the pub. Maybe it is because the botheration gotdiscussed with addition else.

Conclusion

After account this paper, the columnist achievement that you will try these abutting the time you appointment a botheration to solve. Hopefully by applying these six attempt you will apprehend the advantages they bring, rather than to "guess" your way to a solution.

I hope you obtain new knowledge about Masters Educational Technology . Where you possibly can offer easy use in your day-to-day life. And above all, your reaction is Masters Educational Technology . Read more.. Information Technology Problem Solving-The 6 Principles of Scientific Problem Solving.