A framework to elicit the skills needed for software development
Proceedings of the 2005 ACM SIGMIS CPR conference on Computer personnel research
Editorial: A roadmap of problem frames research
Information and Software Technology
| Hi-index | 0.00 |
In his opening essay, Ed Yourdon forecasts both a happy and an unhappy future. His bright future promises challenging projects, exciting technologies, innovative applications, giant salaries, and lucrative stock options. His gloomy future warns of US federal and state government departments unable to solve their Year 2000 problem, a business revolt against expensive and troublesome software that delivers no apparent economic benefits, and a consequent drying up of money to buy new releases of COTS software or to finance new software development. The good news and the bad news are essentially commercial. But the dark cloud of Yourdon's bad future offers a silver lining: if it comes to pass, there might be demands for certification and licensing of software professionals and for a formal approach to software development. In a word, we might be expected to become serious software engineers. We won't, of course. Yourdon is confident that we have learned a lot about soft-ware processes, methods, and techniques; he says that we have a vast body of knowledge in requirements, risk management, metrics, testing, and quality assurance incorporated into the SEI Capability Maturity Model. So that's all right, then. We don't really need software engineering in the narrow academic sense.