If customers had source code, Hecker says, they could recommend fixes to bugs during the design phase instead of waiting until the proprietary software vendor released the product.
But several panelists maintained that open-source practices can't automatically be transplanted into the proprietary milieu. "It's tricky to change a process," cautioned Mary Shaw, a Carnegie Mellon computer science professor, who doesn't rule out adoption of open-source practices by proprietary software vendors. Mark Evans, president of investment performance software maker Confluence, questioned whether open-source processes have the rigor needed to produce timely, commercially viable products. "Developers sacrifice individual autonomy--they perform a ballet--to get a product out early," he said. "Technical prowess isn't the top-rated feature of a programmer; predictability and consistency are."
Observing the discussion, Software Center executive director Bill Guttman suggested a new term--market source--be adopted for a business model that adapts open source's collaborative approach to the development of proprietary commercial software. "It's a neutral way to describe it and leaves some flexibility in its exact definition."
Stay connected and informed by visiting the CA Solutions Center Community!

Become a member today for instant access to free InformationWeek research, expert advice, peer perspectives, and more on the following topics:
- Application Performance Management (APM)
- Security Management
- Mainframe 2.0
- IT Automation
- Service Assurance
Also, visit our Government and Financial Services groups to see how these technologies apply specifically to those industries.
NOTE: Offer valid for U.S., U.S. possessions, & Canada only.