The most expensive developments in the computer world

Here we will have a talk about the most expensive developments in the computer world. People spend a lot of money to invent smth special and spend a lot of money to become an owner of smth special and also the most expensive in its category.

The most expensive computer has been created in Japan. The Japanese government estimates the Earth Simulator’s cost in $400,000,000. Each processor node contains 8 vector processors running at 500MHz with 16GB of shared memory, and the total main memory in the machine is 10 terabytes. The operating system running on the supercomputer is NEC’s UNIX-based OS called “SUPER-UX” which is used on NEC’s SX Series of supercomputers. This expensive computer is used on a wide variety of international projects, most of which are related to atmospheric, climate, and oceanographic simulation.

Should there be a separate methodology for testing?

There are a lot of words said about web development and functional programming methodologies. Usually they are oriented to development mostly and do not deal very much with testing. So should testing have a separate methodology?

It is not a secret that quality software is one of the most important requirements for a customer. It often doesn’t matter the timeframe or even the budget of the project, but whether the end users will be pleased with the product developed. So the importance of testing is great and on some projects good testing is even more valuable than good development. Anyway this doesn’t mean that testing should have a separate methodology. As testing is a very agile and flexible process, which closely connected with web application development, there should be the same methodology for testing as for development.

Testing is flexible enough to choose the best process to achieve the result easily and quickly. It can be various, depending on the development methodology, project team specification and customer’s goals.
If you think of a separate testing methodology – just take all the best practices together and work out your own testing methodology!