News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 
Download Current Issue
ISSUE 2/1/2010 PDF

Need Back Issues?
DOWNLOAD HERE

Receive the print Edition?


 
blogs tab
Visual Studio 2010 Release Candidate Available Today
A Visual Studio 2010 release candidate is available on MSDN.
02/09/2010 09:45 AM EST

Is Microsoft eyeing Office subscription pricing?
Microsoft may be preparing to offer a new Office pricing option called "union," which charges the same for cloud as on-premises.
02/01/2010 09:38 AM EST

Facebook rewrites PHP runtime
Facebook is about to open source its own PHP runtime, written from scratch for speed.
01/30/2010 08:53 PM EST

 

Events calendar tab
2/9/2010 to 2/13/2010
San Francisco
IDG World Expo

2/10/2010 to 2/12/2010
San Francisco
BZ Media

2/17/2010 to 2/25/2010
Atlanta
Python Software Foundation

2/19/2010 to 2/20/2010
Los Angeles
SCALE

2/21/2010 to 2/24/2010
Las Vegas
IBM


 
Most Read Latest News Blog Resources

Zeichick's Take: Seven Drivers of Development Innovation




May 10, 2007 — 
Whenever you have the opportunity to listen to a co-founder of SAP talk about innovation, it's worth listening. SAP is unique among the Giant Software Companies in that it's reinvented itself many times: from a big mainframe enterprise resource planning provider, to a purveyor of massive client/server software, to a maker of a Java application server platform (NetWeaver). Today, it's trying to reinvent itself again, into a SOA-driven software-as-a-service company that offers a whole new hosted application platform.

At the Software 2007 conference, which took place earlier this week in Santa Clara, Calif., Hasso Plattner spoke about drivers for innovation. Plattner, a former IBMer, helped found SAP in 1972, served as its CEO, and today is chairman of its supervisory board, as well as its chief software advisor—a great job title.

Here are seven points that I extracted from Plattner's fire-hose presentation, which alone was worth the price of admission to the conference:

1. Focus on user requirements, instead of thinking only about business requirements. In the past, Plattner said, SAP talked mainly to high-level executives at its customer companies, and built software (like R/3) which addressed what those executives said the business needed. By doing that, he said, SAP missed a lot of features and functions that its software should have delivered. For its new SaaS products, SAP's new emphasis is on figuring out what its users need instead.

2. Separate user interfaces from applications—and be willing to have multiple user interfaces to an application. R/3 had a single user interface for all customers, no matter how big or small they were, what industry they were, or what type of tasks the users were performing. The company has learned that it's better to separate the UI from the core application. Have a single application, with a single code, but build GUIs that fit the customer, instead of expecting that one GUI model fits all.

3. Hosted software works, and works well, even for business-critical applications. Google and Salesforce.com have demonstrated that SaaS works, Plattner pointed out. "The complete enterprise can run in the cloud," he said, "and every year it becomes more obvious that the cloud is a viable alternative to on-site computing."

4. In-memory databases matter. Plattner explained that with one query system it's using as a test case, SAP consolidated five years' worth of data from an accounting application—36 million line items—and went from requiring a 116GB relational database to a 1.2GB in-memory database. The average time to complete a query against all that data: 1.2 seconds. "Think about machines with multiple processors, multiple cores and a hundred gigabytes of memory," he said, "and imagine what this can do for putting information at your fingertips."

5. Speed matters. Plattner wants what he called "Google-speed" for application response time. Enterprise software, whether it's running on-site or in the cloud, should be as fast as Google, he said, and this will change the nature of queries: If it only takes a second to get the results from a query, you can make a first query; if there are too many results, you can refine and filter, and keep making iterative queries until you get the results you want. Contrast that, he said, with older systems, which took sufficiently long to return results that it was worth putting a lot of up-front effort into constructing the query to get it right the first time. Users are very comfortable with making iterative queries, he believes—if the response time is fast enough.

6. Don't make it pretty; make it functional. When you're trying to convey information, Plattner insists, "the most minimalistic form is the best. The more you put colors, three-dimensional images and fancy interfaces around the information, the more you convolute it." Again citing Google's search engine as a ideal, he said, "Beautification is the wrong way. Google does it the right way; other companies beautify and the response time drops to 2 seconds, 3 seconds, 4 seconds or worse. Google stays focused on speed."

7. SOA will accelerate software development. A Google-speed hosted environment in the cloud, coupled with the modular reuse enabled by SOA, and widely available software interfaces, will accelerate the pace of software development tremendously. "We could come back to the speed we had in the early 1990s, when we could roll out a new release every three months," Plattner predicted.

Stodgy, old SAP as the new Google: Who'd have thought it?

Alan Zeichick is editorial director of SD Times. Read his blog at ztrek.blogspot.com.


Share this link: http://www.sdtimes.com/link/30539
 

Add comment


Name*
Email*  
Country     


  • Comment
  • Preview
Loading