Methods & Tools Software Development Magazine

Software Development Magazine - Project Management, Programming, Software Testing

 

Methods & Tools - News, Facts & Comments Edition - January 2005

*** Products ***********************************************************

* Product News

You can view the last product press releases from software development tools vendors on our forum

*** Companies **********************************************************

* Christmas Shopping

The last month of 2004 saw many acquisitions in the IT industry.

Oracle finally signs an agreement to acquire Peoplesoft for $10.3 billion. This is the end of a take-over battle started 18 months ago. Oracle declared having a 3 years plan to merger Oracle, Peoplesoft and J.D. Edwards products. Oracle will also eliminate about 5'000 jobs after the takeover, leaving the company with 50'000 employees.

Symantec agreed to merge with Veritas software in a stock deal valued at $13.5 billion, forming a company active in security and data storage software, both for business and retail customers.

Siebel put $115 million in cash to acquire Edocs, an e-billing software vendor. Siebel said that this acquisition would help to answer customer demand for better integration of front-office applications.

The IT mergers and acquisitions' market seems to be a little more active in 2004 than in the 2000-2003 period. Companies are looking for buying opportunities to fuel growth by external acquisitions or to sell themselves for a good price. In the case of Oracle, this is also part of the general consolidation trends that usually leave only one or two major suppliers in mature markets.

------------------------------------------------------------------------

* Delphi meets CMM

Borland announced this month the acquisition of TeraQuest Metrics Inc. This company was co-founded by Dr Bill Curtis, one of the authors of the Capability Maturity Model (CMM). This acquisition should enable Borland to increase the offer of its services division with process optimisation practice. Dr Bill Curtis has become Chief Process Officer of Borland and will work with Borland R&D teams to apply TeraQuest expertise to Borland's product development.

This could seem strange to see a company like Borland, which has built its reputation selling tools for the "lonesome programmer", embracing the process improvement mantra, not exactly the deepest love of code-oriented developers. In these recent years, Borland has diversified its product offering, notably after the acquisition of TogetherSoft. Currently the company gets more than 20% of its revenue from its Design software division and more than 30% from its services division. These two areas have provided the majority of the growth at Borland last year. Considering these facts, and even if services provide less gross margin than software, the acquisition of TeraQuest becomes more logical for Borland.

------------------------------------------------------------------------

* Company News

You can view the last company press releases from software development tools vendors on our forum

*** Numbers ************************************************************

* Training for Testing

The current M&T poll looks at the amount of training received by software development professionals in the area of software testing. Currently it seems that the answer is "none" for most of the respondents. Go to our [Vote] section to disclose your situation and to see intermediate results. The final results will be published in our next issue.

*** Read for You *******************************************************

* The Quality is in the Database

As Fred Brooks described in his famous "no silver bullet" paper, there is no single action in the computing community can take to radically improve software quality. There are however "copper bullets" - lesser steps that improve quality over time. One such copper bullet is the notion of software engineering, the practice of thinking carefully before immersing yourself in the minutia of coding. Judiciously applied, software engineering should improve quality. [...]

Companies now routinely assess vendor software on the basis of cost, functionality, user interface, and vendor stability, but none of these dimensions addresses the software's intrinsic quality. Database quality, on the other hand, could be a litmus test for overall quality. If a product has a flawed database, it is likely to have other quality issues, such as messy programming. In contrast, the quality evident in a sound database is likely to be present in the software's other parts.

Over the past 11 years, my colleagues and I have been evaluating software using database quality as the basis for product grading. We have found that reverse-engineering a database can help a company deeply understand the associated product. Moreover, the time to do the evaluation (sometimes only a few person-weeks) is trivial compared to the millions it can cost to buy and deploy the application. [...]

This experience prompted us to look at additional databases, after which we decided that database reverse engineering was not an odd technology, but something we should routinely perform. We started keeping records of our experiences and have amassed 11 years of data in a grading table (available in its entirety at www.modelsoftcorp.com). I believe our results represent broad practice, given that a different team prepared each database. We evaluated databases only from developers we did not advise as part of our consultant work, and we included databases only for applications that a vendor actually completed. [...]

Many articles tend to give reverse engineering a sinister image, implying that developers typically use it to re-create a product. In all our case studies, we made it clear that this was not our goal. Besides being unethical, reimplementation is usually uneconomical. Instead, we assured vendors that our focus was to assess the software's merit, to get past hidden assumptions and the sales claims and to gain a deeper understanding of the product so that we could better communicate with the vendor and use the software more effectively. In short, when we assess products, we are merely trying to determine what the vendor is selling.

When we reverse engineer a product, we openly ask vendors for their database structure and tell them why we want it. If they refuse, we tell them we will penalize them in the evaluation. We performed many of these reverse-engineering case studies under commission from large companies. Large companies emphatically do not want to devote their resources to re-create a product. Commercial software is important to them, but it is incidental to their primary business. Otherwise, they would be writing their own software, not purchasing it. [...]

Database quality is undeniably a good indicator of application quality. I have found that business leaders welcome the insights gained from database reverse engineering and use them to make more informed decisions about purchasing an application. More important, the benefits have the potential to ripple into the entire computing community. If vendors improve, in-house software development will follow suit. [...]

Source: Michael Balha, "A Copper Bullet for Software Improvement", Computer, February 2004

This seems an interesting starting point to check the quality of applications before buying them. It is true that if the development team did not take some time to design the database, there are few chances that the code was architected.

*** Books **************************************************************

* Integrating Agile Development in the Real World by Peter Schuh

In our last issue, we presented three articles on the agile approaches. This book provides excellent material for a transition from a traditional approach to an agile method. The book gives only a brief description of the agile methods (XP, Scrum, FDD, etc.), but you will find a detailed presentation of the best practices common to agile approaches. For each of them, the author exposes the purposes, the prerequisites, the implementation, the opportunities and obstacles.

The books provides an agile treatment of many of the daily problems of software development projects like database management, data conversion, test data management, project communication, documentation, end-user contacts or developers management. The most interesting point for me in this book is that the author recognises that you cannot always start with a white page and require an "all-agile" process. It provides information on how to integrate gradually agile practices in a traditional software development context.

Click here get more details on this book or buy it on amazon.com

Click here to get more details on this book or buy it on amazon.co.uk click

*** Conferences ********************************************************

* XP DAY TORONTO 2005 www.xpday.info

February 19, 2005 Westin Prince Hotel, Toronto, Canada

XP Day is a one-day event especially for those who want to get started learning about Extreme Programming from the best minds in the community. It has a little something for everyone, whether you're:

  • An executive wondering how XP can improve the contribution your software organization makes to the bottom line,
  • A manager looking for ways to increase your team's effectiveness,
  • A skeptic, hoping to challenge the most experienced and outspoken XP practitioners,
  • A programmer itching to experience a real XP project room,
  • An experienced practitioner, hoping to share ideas with other experienced practitioners.

XP Day includes tutorials, a project room and the Open Space workshop "From the Fringes to the Mainstream"

J. B. Rainsberger and Ron Jeffries invite you to join us in OpenSpace at XP Day Toronto on February 19, 2005 to explore what is happening in the software development market and in agile software development today. Come to network and swap ideas, and join with our invited experts to influence what happens on a local scale.

Register before February 1, 2005 to take advantage of a 16% discount. Go to www.xpday.info to register today.

------------------------------------------------------------------------

3rd Canadian Agile Network Workshop: "User Interaction in Agile Teams"

The Banff Centre Banff, Alberta, Canada, March 13-14, 2005

Building on the success of the first and second Canadian Agile Network Workshops, this workshop will examine Usage-Centered Design and testing in the context of Agile Methods.

Feedback and evaluation from participants will be provided on the CAN-RAC website following the conference.

See you in Banff!

http://www.agilenetwork.ca/ws2005

 
October 2019
September 2019
August 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
November 2009
October 2009
August 2009
May 2009
April 2009
February 2009
January 2009
November 2008
October 2008
August 2008
May 2008
April 2008
February 2008
January 2008
November 2007
October 2007
August 2007
May 2007
April 2007
February 2007
January 2007
November 2006
October 2006
August 2006
May 2006
April 2006
February 2006
January 2006
November 2005
October 2005
August 2005
May 2005
April 2005
February 2005
January 2005
November 2004
October 2004
August 2004
May 2004
April 2004
February 2004
January 2004
November 2003
October 2003
August 2003
May 2003
April 2003
February 2003
January 2003
November 2002
October 2002
May 2002
April 2002
February 2002
January 2002
November 2001
October 2001
May 2001
April 2001
February 2001
January 2001
Winter 2000
Fall 2000

Software Testing
Magazine


The Scrum Expert