bfwebster - Slashdot User

Submission + - Copyright ruling on calculated results

Submitted by bfwebster on Monday February 24, 2014 @05:34PM

bfwebster writes: During the past few years, I served as an IT expert witness in BanxCorp v. Costco et al., in which BanxCorp sued Costco and Capital One for citing (with credit) its web-published national averages for CD and money market rates in their advertising. Judge Kenneth M. Karas issued his summary judgment opinion last fall, finding that BanxCorp's published averages are "uncopyrightable facts" due to the simple calculation involved and the lack of ongoing human judgment in what banks were involved. Here is my summary of his findings, along with a link to the actual ruling.

Submission + - New concept -- the Peter Pinnacle -- inspired by Ballmer? 1

Submitted by bfwebster on Sunday August 25, 2013 @12:08PM

bfwebster writes: Michael Swaine — long-time, well-known and very prolific author/editor in the programming and personal computing worlds — has just devised a new twist on the Peter Principal: the Peter Pinnacle, 'meaning to get promoted so high and to be so unqualified for your job that the company tells you that you can name your price just to go away.' I'm sure the timing of the neologism is just a coincidence.

Submission + - More warnings about high-frequency trading (HFT)

Submitted by

bfwebster

on Monday September 10, 2012 @12:14PM

bfwebster writes: "From The Big Picture (a great finance/econ blog) comes a link to this New York Times article on some of the risks and problems of high-frequency trading on financial markets and a couple of "gadflies" who are pushing hard to get some changes and reforms in how Wall Street handles HFT. Key question: when is fast trading too fast?"

Submission + - NYPost goes app-only for iPad users (paidcontent.org)

Submitted by

bfwebster

on Sunday June 19, 2011 @11:57AM

bfwebster writes: "Browsing the web this morning, I discovered that the New York Post is blocking iPad users from reading its website via Safari. Instead, iPad users must download and use the NYPost App instead. That app previously required a paid subscription (which is one reason I didn't use it); however, the version I downloaded this morning isn't making any demands for payment. Yet."

Submission + - Does cheap technology undermine this court ruling? (volokh.com)

Submitted by bfwebster on Monday January 04, 2010 @05:08PM

bfwebster writes: Orin Kerr, a George Washington University law professor who focuses on legal issues regarding information technology (I own a copy of his book "Computer Crime Law") raises an interesting issue about a 2001 Supreme Court decision (Kyllo v. United States) that prohibited police from using a thermal imaging device on a private home without a warrant. (The police were trying to detect excess heat coming from the roof of a garage, as an indication of lamps being used to grow marijuana inside.) The Court made its decision back in 2001 because thermal imaging devices were "not in general use" and therefore represented a technology that required a warrant. However, Kerr points out that anyone can now buy such thermal imaging devices for $50 to $150 from Amazon, and that they're advertised as a means of detecting thermal leakage from your home. In light of that, Kerr asks, is the Supreme Court's ruling still sound?

Submission + - HR 3200 considered as software (brucefwebster.com)

Submitted by

bfwebster

on Monday September 07, 2009 @10:16PM

bfwebster writes: "Independent of one's personal opinions regarding the desirability and forms of government-mandated health care reform, there exists the question of how well HR 3200 (or any other legislation) will actually achieve that end and what the unintended (or even intended) consequences may be. There are striking similarities between crafting software and creating legislation, including risks and pitfalls — except that those risks and pitfalls are greater in legislation. I've written an article (first of a three-part series) examining those parallels and how these apply to HR 3200."

Submission + - Judge, Citing Bilski, Invalidates Software Patent (bfwa.com)

Submitted by

bfwebster

on Thursday July 09, 2009 @07:41PM

bfwebster writes: "US District Court Judge Andrew Gilford (Central District of California) granted a summary judgment motion in DealerTrack v. Huber et al., finding DealerTrack's patent (US 7,181,427) — for an automated credit application processing system — invalid due to the recent In re Bilski court decision that requires a patent to either involve "transformation" or "a specific machine". According to Judge Gilford's ruling, DealerTrack "appears to concede that the claims of the '427 Patent do not meet the 'transformation' prong of the Bilski test." He then applied the "specific machine" test and noted that, post-Bilski the Board of Patent Appeals and Interferences has ruled several times that "claims reciting the use of general purpose processors or computers do not satisfy the (Bilski) test." Judge Gilford analyzes the claims of the '427 patent, notes that they state that the "machine" involved could be a "dumb terminal" and a "personal computer", and then concludes: "None of the claims of the '427 Patent require the use of a 'particular machine,' and the patent is thus invalid under Bilski." DealerTrack apparently plans to appeal the ruling. Interesting times ahead."

Submission + - Book Review: Why New Systems Fail (bfwa.com)

Submitted by

bfwebster

on Tuesday July 07, 2009 @04:50PM

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.

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. ..bruce.."

Submission + - Are you ready for road tolls anywhere? (and-still-i-persist.com)

Submitted by

bfwebster

on Saturday February 14, 2009 @11:24AM

bfwebster writes: "Here in Denver, we have E-470, a toll section of the 470 beltway that uses the usual transponder attached to your windshield. Fair enough, and I make use of it, particularly in driving to the airport. But they've just implemented new technology on E-470 that allows anyone to drive through the automated toll gates. If you don't have a transponder, it takes a photo of your license plate and sends a monthly bill to your house. As a result, the company that runs E-470 plans to close all human-staffed toll booths by mid-summer. And as an article in this morning's Rocky Mountain News notes, "Such a system could be deployed on other roads, including some that motorists now use free. The result: a new source of money for highways and bridges badly in need of repair." You can bet that legislators, mayors, and city councilpersons everywhere will see this as an even-better source of income than red-light cameras. You've been warned.""

Submission + - Did the Zipingpu Dam trigger the Sichuan 'quake? (and-still-i-persist.com)

Submitted by

bfwebster

on Tuesday February 03, 2009 @04:48PM

bfwebster writes: "An article in the Telegraph (UK) raises an interesting question: was the massive (7.9) Sichuan earthquake that wracked China last year and left millions homeless caused by ground stresses following the completion of the Zipingpu dam? As the article reports (emphasis added), 'The 511ft-high Zipingpu dam holds 315 million tonnes of water and lies just 550 yards from the fault line, and three miles from the epicentre, of the Sichuan earthquake. Now scientists in China and the United States believe the weight of water, and the effect of it penetrating into the rock, could have affected the pressure on the fault line underneath, possibly unleashing a chain of ruptures that led to the quake.' Oops."

Submission + - The post-Bilski era gets underway (bfwa.com)

Submitted by

bfwebster

on Friday December 19, 2008 @05:08PM

bfwebster writes: "A set of pharmaceutical process patents for "evaluating and improving the safety of immunization schedules" (Classen v. Biogen et al.; see US Patents 6,420,139; 6,638,379; 5,728,385; 5,723,283) were held to be invalid due to unpatentability. The decision was appealed to the US Court of Appeals for the Federal Circuit, but was upheld with a terse citation to In re Bilksi. Here's the entire text of the appeals decision:
In light of our decision in In re Bilski, 545 F.3d 943 (Fed. Cir. 2008) (en banc), we affirm the district court's grant of summary judgment that these claims are invalid under 35 U.S.C. 101. Dr. Classen's claims are neither "tied to a particular machine or apparatus" nor do they "transform[] a particular article into a different state or thing." Bilski, 545 F.3d at 954. Therefore we affirm.

It will be interesting to see what happens when these same standards are applied to software-related patents."

Submission + - Court ruling: calculating a hash value == search (bfwa.com)

Submitted by

bfwebster

on Tuesday October 28, 2008 @12:32AM

bfwebster writes: "Orin Kerr over at The Volokh Conspiracy (a great legal blog, BTW) reports on a U.S. District Court ruling issued just last week that finds that doing hash calculations on a hard drive is a form of search and thus subject to 4th Amendment limitations. In this particular case, the U.S. District Court suppressed evidence of child pornography on a hard drive because proper warrants were not obtained before imaging the hard drive and calculating MD5 hash values for the individual files on the drive, some of which ended up matching known MD5 hash values for known child pornography image and video files. More details at Kerr's posting."

Submission + - Police secretly planting GPS devices on cars (brucefwebster.com)

Submitted by

bfwebster

on Wednesday August 13, 2008 @07:43AM

bfwebster writes: "The Washington Post has a long investigative article on how more and more police departments are secretly planting GPS tracking devices on the cars of people they are investigating — usually without a warrant. After-the-fact court challenges on this technique have largely upheld such use of a GPS device, though the Washington State Supreme Court has ruled that a warrant is required."

Submission + - First all-drone USAF air wing (brucefwebster.com)

Submitted by

bfwebster

on Monday August 11, 2008 @08:59PM

bfwebster writes: "Strategy Page reports that the United States Air Force has announced its first air wing that will consist entirely of unmanned craft. The 174th Fighter Wing has flown its last manned combat sorties; its F-16s will be entirely replaced by MQ-9 Reapers. Reasons cited include costs (maintenance and fuel) and the drone's ability to stay in the air up to 14 hours, waiting for a target to show itself."

Submission + - Japan "running out of engineers" (brucefwebster.com)

Submitted by

bfwebster

on Saturday May 17, 2008 @08:58AM

bfwebster writes: "A story in the New York Times reports that Japan, a country that rebuilt itself as a technological power after World War II, now faces an increasing shortage of college graduates with degrees in science and engineering. Says the article: "By one ministry of internal affairs estimate, the digital technology industry here is already short almost half a million engineers." The article goes on to point out that the overall trend of waning interest in science and technology has been going on for "almost two decades" and that the shortage is made worse by the traditional reluctance of Japanese companies to hire and use foreign workers. The US has had a similar trend for quite some time: "Undergraduate engineering enrollment declined through most of the 1980s and 1990s, rose from 2000 through 2003, and declined slightly in recent years.""

Slashdot Top Deals