Slashdot Mirror

An anonymous reader writes "Highly sensitive financial information, including credit card details, bank account numbers, telephone numbers, and even PINs are available to the highest bidder. The information being traded on the Web has been intercepted by a British company and collated into a single database for the first time. The Lucid Intelligence database contains the records of 40 million people worldwide, mostly Americans; four million are Britons. Security experts described the database as the largest of its kind in the world. The database is in the hands of Colin Holder, a retired senior Metropolitan police officer who served on the fraud squad. He has collected the information over the past four years. His sources include law enforcement from around the world, such as British police and the FBI, anti-phishing and hacking campaigners, and members of the public. Mr. Holder said he has invested £160,000 in the venture so far. He plans to offset the cost by charging members of the public for access to his database to check whether their data security has been breached."

dusty writes "Plans to bring online the first new US nuclear plant since 1995 are on track, on time, and on budget according to the Tennessee Valley Authority. TVA had one major accident with a coal ash spill of late, and one minor one. The agency has plans and workers in place to have Unit 2 at Watts Bar, near Knoxville, online by 2012. Currently over 1,800 workers are doing construction at the plant. Watts Bar #1 is the only new nuclear reactor added to the grid in the last 25 years. From the article: 'TVA estimates the Watts Bar Unit 2 reactor every year will avoid the emission of about 60 million metric tons of greenhouse emissions linked with global warming. ... TVA began construction of Watts Bar in 1973, but work was suspended in 1988 when TVA's growth in power sales declined. After mothballing the unit for 19 years, TVA's board decided in 2007 to finish the reactor because it is projected to provide cheaper, no carbon-emitting power compared with the existing coal plants or purchased power it may help replace.'"

ekran writes "A while ago Opera Software needed more servers. Not just a few servers either — they were planning Opera Mini's growth, implementing Opera Link, and My Opera was also growing quickly. Most of the major hardware vendors grabbed their specs and came back with offers and sample servers shipped all the way to Oslo for testing. One of the biggest vendors, however, did not do their homework. They shipped the server, but when the Opera sysadmins started up the web-admin interface, they were met with a JavaScript statement that managed to piss off the whole company including the CTO. The script, apparently, locked out the Opera web-browser."

1sockchuck writes "A Texas startup called Baryonyx plans to build data centers powered entirely by renewable energy. Its first project will be a wind-powered server farm powered by 100 wind turbines in the Texas panhandle. The company has also leased 38,000 acres in the Gulf of Mexico, where it hopes to build hundreds of 300-foot wind turbines that can each generate up to 5 megawatts of power to support additional facilities. Baryonyx plans to sell excess capacity to the local utility, which it will use as a backup when the wind dies down."

As long as you travel on a select few of Harbin Public Transport Company's buses, you won't have to worry about breaking a window to escape a potentially deadly crash anymore. The company has equipped each bus with two yellow emergency bricks for passengers to use to break windows. A safety hammer used to be provided but they were stolen frequently because everyone can use a good hammer. "We don't think anybody will be interested in stealing bricks," a spokesman said. The company plans on putting bricks on all 700 of its buses if the customer feedback is smashing.

eldavojohn writes "After announcing the sale of The Pirate Bay to Global Gaming Factory X, it was unknown what would become of TPB. Details of the future plans have been released. 'According to Rosso, GGF plans to build a massive "storage cloud" on top of TPB that would use individual users as storage system's nodes. Apparently users can opt out for being part of the decentralized storage system, but then they'd have to pay a monthly fee for the service. More resources the user is willing to commit for the service, the cheaper the monthly subscription fee will be ... GGF's plan is to harness the resources users are willing to allocate to the cloud service and sell that computing power and bandwidth to 3rd party companies, essentially creating a service that could be used as a content delivery network (system that most large sites — including ours — use to deliver static content, such as images, software downloads and stylesheets, faster to the end user) or even as a web hosting cloud. As the service would use P2P technology, it could bring massive savings to ISPs, as the delivery of content to an end user would be provided from the closest possible "node," most likely from an user within the same ISP network.'"

The EFF has restated many of their original privacy objections about California's latest revision to the Pay-As-You-Drive auto insurance proposal. Admitting that the amended bill is an improvement, privacy advocates are still uneasy about the surveillance implications of this program. "The proposal centers on a simple idea: infrequent drivers are less of an insurance risk. By pricing policies according to the mileage driven, insurance companies can offer discounts to lower-risk infrequent drivers, and put an appropriate cost penalty on heavy drivers. The state estimates that 30% adoption of PAYD insurance nationwide would reduce miles driven by at least 10% among subscribers, and save 55 million tons of CO2 over the next ten years. The benefits of such a system could be quite dramatic, as California Insurance Commissioner Steve Poizner is sure to emphasize. Such insurance plans first became available in 2004, and are now available as a limited option in 30 US states from insurance companies like Progressive and Liberty Mutual."

anonymous cowpie sends word of a Utah startup that is about to introduce technology for writing DVDs that can be read for 1,000 years after being stored at room temperature. (Ordinary DVDs last anywhere from 3 to 12 years, on average.) The company, Millenniata, is said to be in the final stages of negotiation with Phillips over patent licensing and plans to begin manufacture in September. 1,000-year "M-ARC Discs" are expected to retail for $25-$30 at first, with the price coming down with volume. "Dubbed the Millennial Disk, it looks virtually identical to a regular DVD, but it's special. Layers of hard, 'persistent' materials (the exact composition is a trade secret) are laid down on a plastic carrier, and digital information is literally carved in with an enhanced laser using the company's Millennial Writer, a sort of beefed-up DVD burner. Once cut, the disk can be read by an ordinary DVD reader on your computer."

bfire writes "Police officers in the Australian state of Queensland plan to conduct a 'wardriving' mission around select towns in an effort to educate citizens to secure their wireless networks. When unsecured networks are found, the Police will pay a friendly visit to the household or small business, informing them of the risks they are exposing themselves to. Officers also hope to return to surveyed areas within a month to see if users have fixed their security settings. The idea is modeled on another campaign where officers walk around railway stations checking cars have been locked, and leaving notes warning people of the dangers involved with leaving their vehicles unsecured."

Moon Workstation writes "In an special meeting held at Santa Clara, CA, 62% of Sun's stockholders voted for the acquisition by Oracle. As a result of this Sun's stock will be taken from the stock market as of Friday. The acquisition is still waiting for approval by the US Department of Justice and anti-trust offices in other countries. The planned acquisition is source for rumors and speculation about the future of different Sun products, like OpenSolaris, CPUs and others." (MySQL among them.)

bfwebster writes "Over the last forty years, a small set of classic works on risks and pitfalls in software engineering and IT project management have been published and remained in print. The authors are well known, or should be: Gerry Weinberg, Fred Brooks, Ed Yourdon, Capers Jones, Stephen Flowers, Robert Glass, Tom DeMarco, Tim Lister, Steve McConnell, Steve Maguire, and so on. These books all focus largely on projects where actual software development is going on. A new book by Phil Simon, Why New Systems Fail, is likewise a risks-and-pitfalls book, but Simon covers largely uncharted territory for the genre: selection and implementation of enterprise-level, customizable, off-the-shelf (COTS) software packages, such as accounting systems, human resource systems, and enterprise resource planning (ERP) software. As such, Simon's book is not only useful, it is important." Read on for the rest of Bruce's thoughts on this book. Why New Systems Fail: Theory and Practice Collide author Phil Simon pages 251 publisher AuthorHouse, 2009 rating 8/10 reviewer Bruce F. Webster ISBN 9781-4389-4424-1 summary Risks and pitfalls of enterprise COTS projects Phil Simon has written a long-needed and long-overdue book. Most risks-and-pitfalls book in the IT category focus primarily on projects where actual software engineering is the principal activity. However, many of the large, expensive and often spectacular IT project failures over the past 20 years have little to do with software design and development. Instead, they involve a given organization selecting and implementing — or trying to implement — a commercial off-the-shelf (COTS) software package to replace existing legacy systems, either homegrown or also commercial. The reasons for such a move can be many: standardizing IT and data management across the enterprise, seeking new functionality, retiring systems that are no longer supported or supportable, and so on. By so doing, the firm (usually rightly) thinks to avoid the risks and expense of from-scratch custom software development. However, the firm (usually wrongly) thinks that such a project comprises nothing more than installing the software, training some users, converting some data, and turning a switch. A quick search on the terms "ERP" and "lawsuit" shows just how mistaken that idea can be.

Simon's book is far more informative and instructive than a Google search and should be required reading for all CIOs, IT project managers, and involved business managers prior to starting any such enterprise COTS project. He covers the complete lifecycle of such projects, starting with the typical expectations by upper management ("Fantasy World") and following it through system selection, implementation, and production, along with a final section on how to maximize the chances of success. Along the way, he uses several real-word case studies (with names changed), as well as a few hypothetical ones, to demonstrate just how such efforts go wrong.

What Simon writes is spot on. For roughly 15 years now, my primary professional focus has been on why IT projects fail. I do that both as a consultant (brought in to review troubled projects to get them back on track) and as a consulting or testifying expert (brought in to review troubled or failed projects now in litigation). I have reviewed hundreds of thousands of pages of project documentation and communication; I have likewise traced or reconstructed project histories for many major IT projects, including enterprise COTS projects. It's clear that Simon knows exactly what he's talking about and knows where all the bodies are buried.

The book itself is very readable. Simon's tone is conversational and a bit humorous; he occasionally dives into technicalities that would be lost on upper management, but always comes back to basic principles. The real-world and hypothetical case studies will have those of us who have been on such projects nodding our heads even as we occasionally wince or shudder. His coverage is exhaustive (and at times a bit exhausting), but his goal appears to be to give those managing and overseeing such projects the information they need to navigate the shoals. He goes into detail about COTS pitfalls such as project estimation, vendor selection, use of consultants, group responsibility, integration with legacy systems, data conversion, and report generation.

The first section of the book covers how and why firms decide to initiate a major COTS project. Besides the "Fantasy World" section that compares management expectations to what really happens, the book also covers why firms hold onto legacy systems, why they buy new (replacement) systems, and how they can (or should) make the decision among building a custom system, buying a COTS system, and "renting" enterprise software via a web-based software-as-a-service (SaaS) vendors such as Workday and Salesforce.

The second section covers COTS system selection. The book divides current ERP and COTS vendors into four different tiers based on company size and use (e.g., SAP, Oracle and BaaN are all Tier 1) and warns of the, ah, enthusiasm of vendor salespersons. (Old-but-still-timely joke: What's the difference between a used car salesman and a software salesman? The used car salesman knows how to use his own product and knows when he's lying.) The book then raises up front an issue often left (by customers) until much later: how will business processes change as a result of the COTS system we're acquiring? It then talks about selecting, if necessary, a consulting firm to help with the installation and project management.

The third section covers the actual COTS implementation process, including the overall strategy, roles and responsibilities, providing the necessary environments, data migration, testing, reports, and documentation. This section is a bit exhausting at times, but it is critical for exactly that reason: far too many firms launch into a major COTS acquisition without fully realizing just what it will take to get the system into production.

The fourth section briefly deals with life after implementation. In theory, one of the reasons a firm buys a COTS system is to avoid doing its own maintenance and support; the reality is that the firm often doesn't like paying those large annual maintenance fees and instead goes off on its own path, which is seldom a good idea.

The fifth and final section talks about how to maximize the chance of success in a large COTS implementation. This section builds upon the rest of the book, which has provided suggestions along the way. In particularly, it talks about how to deal with a troubled project mid-course in order to get it back on track.

Throughout the book, Simon puts a significant focus on human factors in project success and failure. He identifies issues such as internal politics, kingdom-building, reluctance to learn new systems, internal project sabotage, end-user resistance, and staff allocation. Simon divides firm personnel assigned to work on the COTS project into four groups — willing and able (WAA); willing but not able (WBNA); not willing but able (NWBA); and neither willing nor able (NWNA) — and talks about how each groups helps or hurts. Similarly, he identified four dangerous type of project managers: the Yes Man, the Micromanager, the Procrastinator, and the Know-It-All. Again, those of us who have been on major IT projects, particularly those involving COTS implementations, will recognize both sets of categorization and the risks they entail.

While Simon is himself a consultant, he is also quite frank about the role consultancies can play in COTS project failures. In particularly, he notes the tendency of consulting firms to underestimate project duration and cost in order to win business, as well as the frequent unwillingness to point out risks and pitfalls to the client, particularly if they represent something the client wants to do.

My few complaints with Why New Systems Fail are mostly production-related. Simon self-published the book; as such, the book's internal layout and graphic design leaves something to be desired. Likewise, his organization and prose could use a bit of editing in spots; he has a propensity for throwing in terms and abbreviations without clarification, and the technical level can vary within a given chapter. Almost all of his footnote references come from Wikipedia; his bibliography is small (just four books) and cites only Brooks from the cadre of authors listed above. None of this makes the book's content any less important or useful, but some of the very people who should be reading this book might well skip or skim it for those reasons. My understanding is that Simon is working on finding a publisher for the book, which will likely solve all those problems.

In the meantime, if you or someone you love is about to embark on an enterprise-level COTS project, get this book; I've added it to my own short-list of recommended readings in software engineering.

You can purchase Why New Systems Fail: Theory and Practice Collide from amazon.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

theodp writes "Okay Tux fans, let's see how badly you want to see Feynman's Messenger Lectures on Physics. Bill Gates has the goods over at Microsoft Research's Project Tuva site. Also, CNET's Ina Fried has an interesting interview with Gates. He goes into why he spent his own money to make a series of classic physics lectures available free on the Web, talks about the possibility of Project Natal bringing gesture recognition to Windows, gives his thoughts on Google's Chrome OS, and discusses plans to patent 'cows that don't fart.' The last is a joke. I think."

Rock, Paper, Shotgun points out a video showing Portal, redone with ASCII graphics. It's still in development, but appears to be quite far along. Its creator, Cymon, says on his website, "I have Windows XP, so all binaries will by default be for Windows. But I will also be including the source code with the distribution and am doing my best to write it cross-platform compatible, so it should compile in Linux and Mac. I've had successful builds done in Linux." He also talks in detail about his design plans and ideas.

Perhaps T. Boone Pickens was onto something. Al writes "An article in Technology Review argues that plans to string new high-voltage lines across the US to bring wind power from the midsection of the country to the coasts, could be an expensive mistake. What's needed instead are improved local and regional electricity transmission, the development of an efficient and adaptable smart grid, and the demonstration of technology such as carbon capture and sequestration, which could prove a cheaper way to reduce carbon dioxide emissions than transmitting power from North Dakota to New York City."

Vigile writes "The SATA 6G standard offers more than simply a faster 6.0 Gb/s data throughput speed, to wit: improved NCQ support, better power management, and a new connector to support 1.8-inch drives. While modern-day, spindle-based hard drives struggle to keep up with SATA 3G speeds, modern SSDs are nearly saturating the existing standard, and a move to SATA 6G was welcome in the hardware community. It looks like that technology will be delayed, though. The only chip supporting the standard today, the Marvell 88SE9123, is having major issues. Motherboard vendors including ASUS and Gigabyte, which had planned on releasing SATA 6G technology using the chip on Intel Lynnfield platform motherboards later this summer, are having to remove the Marvell 88SE9123 and redesign their boards at the last minute due to significant speed and reliability issues."

Guil Rarey writes "Neat hacks deserve our admiration. Epic kludges, though, have their own "Plan 9 from Outer Space" glory. ThereIFixedIt is dedicated to jury rigs, MacGyver wannabes, and kludges that, errr, may have needed a little more thought."

The Narrative Fallacy writes "We've all heard about the dangers of texting while driving, but 15-year-old Alexa Longueira from Staten Island recently learned a painful lesson about the hazards of texting while walking when, preparing to send a text, she stepped into an open manhole, scraping her arms and back as she slid into the sewer, which had some muck at the bottom. The manhole had been left open briefly by the Department of Environmental Protection (DEP) just as workers were grabbing some cones to cordon off the area. 'It was four or five feet, it was very painful. I kind of crawled out and the DEP guys came running and helped me,' Longueria said. 'They were just, like, "I'm sorry! I'm sorry!"' DEP spokeswoman Mercedes Padilla said in a statement that crews were flushing a high-pressure sewer line at the time. 'We regret that this happened and wish the young woman a speedy recovery.' After being released from Staten Island University Hospital, Longueria's parents say they are planning to file a lawsuit and displayed their daughter's injuries to a photographer from the Staten Island Advance. Longueria's mother said doctors were concerned about possible spine damage suffered in the fall and want a follow-up MRI. Her mother added that she was particularly upset about the sewage. 'Oh my God, it was putrid. One of her sneakers is still down there.'"

An anonymous reader writes "Sony is finally responding to the threat posed by the iPhone, and has started aggressively courting developers around the world to work on digitally distributed games for PSP in a bid to grow the amount of software offered on its handheld. And, Develop has revealed, the firm is planning to introduce a streamlined content pipeline for the platform — which includes abolishing concept approval — plus cheaper devkits, shorter quality assurance processes, and very low price points for new games. It hasn't totally abolished the barriers around the platform for homebrew and indie devs, but it's a start."

We need a fantastic weapon for a fantastic war.

angry tapir writes "Nearly six in 10 companies have no current plans to deploy Windows 7 by the end of next year, according to a new survey. Of 1,100 IT administrators who responded to the survey, 59.3 percent said they didn't have a plan to deploy Windows 7. (Full results, PDF.)"