Moving FAST Forward



Email    print   
August 15, 2005 —  (Page 1 of 3)
Creating software is hard enough. Tweaking it to create a software product line—multiple versions of the same product for different platforms, different feature sets, different pricing and different customer branding—can quickly get out of control. Imagine if every time Toyota wanted to release one Camry with automatic transmission and another with a five-speed manual stick, or one red and another silver, the company’s engineers had to redesign the car, and draw up a new set of specifications, and that all the components, such as side-view mirror motors and the interior speakers, would have to be re-tested. I’m sure that before you could say “You’ve got it, Toyota,” the company would stop offering options.

Software product line development is no different. It grew out of research done in the 1990s to define a methodology for reusing software assets effectively and efficiently. Visionaries such as David Weiss, then of Bell Laboratories, believed that reuse in software product line development should require that a software artifact only be created when the reuse of the asset can be assured across the product line. (Most other asset reuse plans simply call for placing all software components in a repository in the hopes that someone else in the organization can find a project to reuse the asset in someday.)

The idea back then was to look at this kind of development as creating different members of a family, taking advantage of work done in previous iterations to eliminate rework, rather than creating a whole new project each time requirements change. This family-oriented approach to development, where the abstractions between versions are described, specified and then translated into deliverable software, came to be known as the FAST process.

Fast-forward to today, and the reality is that the process of developing product-line software is anything but fast. Data extrapolated from Software Engineering Institute case studies indicates that as much as 50 percent of development time is eaten up dealing with issues surrounding multiplicity. A software company called BigLever wants to change that by assigning first-class problem status to variations in a software product line.




Pages 1 2 3 


Share this link: http://sdt.bz/28784
 
Most Read Latest News Blog Resources

Add comment


Name*
Email*  
Country     


  • Comment
Loading




close
NEXT ARTICLE
Zeichick’s Take: Fast cars! Fast phones! And a new developer conference!
The North American International Auto Show and the Consumer Electronics Show made headlines, but another show is coming Read More...
 
 
 
 
News on Monday
more>>
SharePoint Tech Report
more>>


   

 
 

Download Current Issue
FEBRUARY 2012 PDF ISSUE

Need Back Issues?
DOWNLOAD HERE

Want to subscribe?


 
blogs tab
Are you at risk for burnout?
Burnout is a severe problem and it can strike at any time. Here's how to tell if you are nearing the edge.
02/09/2012 02:16 PM EST

Agility, mom, and apple pie
If we're to evaluate the state-of-the-art in software development, we should start with the values espoused in the Agile Manifesto.
02/07/2012 11:57 AM EST

RIM woos developers with free tablet
How do you get more apps ported to the BlackBerry PlayBook? By giving every developer a free tablet, of course!
02/04/2012 01:57 PM EST

GitHire: Use Headhunters to Find Your Perfect Programmer
Are you a hiring manager tired of scouring the job boards? Check out this new service that will find 5 people interested in your jobs.
02/03/2012 12:17 PM EST

Facebook claims hacker cred
Facebook's SEC S-1 filing form includes a short essay on the Hacker Way by Mark Zuckerberg himself.
02/02/2012 08:26 AM EST

Ryan Dahl steps down
Ryan Dahl, creator of Node.js, steps back from his position as gatekeeper for the project.
02/01/2012 04:58 PM EST

 
Events calendar tab
2/13/2012 to 2/16/2012
Santa Clara
TechWeb

2/26/2012 to 2/29/2012
San Francisco
BZ Media

2/27/2012 to 3/2/2012
San Francisco
RSA

3/4/2012 to 3/7/2012
Las Vegas
IBM Tivoli

3/5/2012 to 3/9/2012
San Francisco
TechWeb