• Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
  • Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

Why NAS failed last week.

Collapse
X
  •  
  • Filter
  • Time
  • Show
Clear All
new posts

    #11
    But CUK errors don’t stop people from flying .
    "I can put any old tat in my sig, put quotes around it and attribute to someone of whom I've heard, to make it sound true."
    - Voltaire/Benjamin Franklin/Anne Frank...

    Comment


      #12
      Originally posted by vetran View Post
      oh dear so they have duplicate waypoints , bet that was designed a consultant - muppets.
      There's an ongoing global project to make all way point designations unique. Unfortunately it involves many different juridstictions which means it takes time, and so the current standard defines that there can be duplicates and the ways of dealing with it.

      Originally posted by GJABS View Post

      I wouldn't say the concept of a single flight plan failing for -some- reason requires particularly deep thought. On the face of it they ought to have designed the system to raise an alarm if a flight plan is rejected in an non-resolvable way immediately, and skip over to process the next flight plans. This would require a robust procedure to guarantee that the failed flight plan receives manual intervention. But dealing with manual intervention issues is nothing new to air traffic controllers (for example in their dealing with aircraft declaring emergencies).
      The flight plan wasn't rejected, because it was valid.

      There are flight plans with duplicate waypoints processed successfully every day. This was just happened to have something about it that the processing system couldn't handle. There was a failure somewhere in the logic of processing it which caused an unresolvable error, so the system did what it was designed to do. Fail safe. As a result although people were inconvenienced nobody actually died.

      It's very easy to point the finger after the event and say "oh, they should have spotted that" but that could be said of the vast majority of bugs that get through into productive systems. Given the details supplied so far, we don't really know whether this was an easy one to spot. As it took over the four hour limit to resolve, either the IT workers are really crap or it was difficult to figure out what had gone wrong.

      Apparently the error has been patched.

      The fact is it is (provably) impossible to guarantee any computer system is free of errors. Even catastrophic ones.


      Down with racism. Long live miscegenation!

      Comment


        #13
        On that basis NAT, I think that the 4 hour window is the bit that airlines are peed about given the amount of money they have to cough up.
        "I can put any old tat in my sig, put quotes around it and attribute to someone of whom I've heard, to make it sound true."
        - Voltaire/Benjamin Franklin/Anne Frank...

        Comment


          #14
          Oh well, could've been worse. Ariane 5. Cough.

          Comment


            #15
            I always do TDD with 100% code coverage.

            Simple to understand clean code.

            So still see so many developers write zero tests and huge 500 line (or longer) methods, amateurs. Some developers have never written a single test case in their whole careers.

            Comment

            Working...
            X