Journal ArticleDOI
Will there ever be software engineering
Reads0
Chats0
TLDR
In his opening essay, Ed Yourdon forecasts both a happy and an unhappy future; 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.Abstract:
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.read more
Citations
More filters
Conceptual modeling in software engineering and knowledge engineering: concepts, techniques and trends
TL;DR: Although the situation in the field is satisfactory, as can be inferred from the review conducted, there is still a lot of work to be done and a series of shortcomings besetting the different techniques will be identified and an alternative perspective will be described, which points to a way of quieting objections.
Proceedings ArticleDOI
A framework to elicit the skills needed for software development
TL;DR: A theoretical framework will allow for the elicitation of skill-set information by considering the person, their behaviors and the organization they work in to inform an interview instrument.
Dissertation
A reflective architecture to support dynamic software evolution
TL;DR: The main result of the research presented here is a framework which is used to model and control the architecture of a software system, and allows the run-time manipulation of the components which make up aSoftware system.
An investigation of the use of requirements prioritisation in web-based information systems development
TL;DR: The literature on Webbased information system development is strewn with a multitude of methodologies that all aspire to the same elusive goal: to deliver a WIS that satisfies all cost, time, functionality and quality constraints.
Applying the Software Engineering Taxonomy
TL;DR: This thesis describes how sustainable development definitions can be transposed to the software architecture environment for the industrial software system domain and finds trust is found to be critical for sustainable development.
References
More filters
Journal ArticleDOI
An investigation of the Therac-25 accidents
TL;DR: A detailed investigation of the factors involved in the software-related overdoses and attempts by users, manufacturers, and government agencies to deal with the accidents is presented.