
	Where results make sense

Topic: Software crisis

Related Topics

History of computers

	Software crisis - Wikipedia, the free encyclopedia
		The 'software crisis' was a term used in the early days of software engineering, before it was a well-established subject.
		The causes of the software crisis were linked to the overall complexity of the software process and the relative immaturity of software engineering as a profession.
		The software crisis was at least partially addressed by the implementation of various processes and methodologies.
	en.wikipedia.org /wiki/Software_crisis (311 words)

	The Software Crisis (Site not responding. Last check: 2007-11-03)
		A crisis similar to the software crisis is not seen in the hardware industry, where well documented, formal processes are tried and true, and ad hoc hardware development is unheard of.
		Software developers pick up the ad hoc approach to software development early in their computer science education, where they are taught a "product orientation" approach to software development.
		Software process engineering, is, unfortunately, not taught until very late in a computer science student’s academic career (usually in graduate school), or in company sponsored classes on the job.
	www.unt.edu /benchmarks/archives/1999/july99/crisis.htm (1449 words)

	The Software Patent Crisis
		Especially disturbing is that the broad claims of many recent software patents appear to establish monopolies on the automation of such common functions as generating footnotes and comparing documents.
		The problem is compounded by the fact that a modern software package may contain thousands of separately patentable processes, each of which adds to the risk of infringing patents that are already in the pipeline.
		It is quite possible that the separate software publishing industry may cease to exist as companies find that they need the patent portfolios and legal resources that the hardware giants can provide.
	deoxy.org /swpc.htm (3291 words)

	Planning the Software Industrial Revolution
		The familiar process-centric paradigm of software engineering, where progress is measured by advancement of the software development process, entered the crisis stage 23 years ago when the term, software crisis, was first coined.
		Software is a place where dreams are planted and nightmares harvested, an abstract, mystical swamp where terrible demons compete with magical panaceas, a world of werewolves and silver bullets.
		Software is a closed universe in which all potential interactions between the parts of that universe can be declared when these parts are created by their compiler.
	virtualschool.edu /cox/pub/PSIR (6207 words)

	CMPE 3213 Advanced Software Engineering
		The first software engineering conference was sponsored by NATO in 1968, with the proclamation that there was a software crisis, namely, that the quality of the software of the day was generally unacceptably low and that deadlines and cost limits were not being met.
		The software designers had not anticipated the use of control inputs in nonstandard ways and as a result, the machine issued a high dose of radiation when low levels were intended.
		Software design is actually a multistep process the focuses on four distinct attributes of a program: data structure, software architecture, interface representations, and procedural (algorithmic) detail.
	www.ee.unb.ca /kengleha/courses/CMPE3213/IntroToSoftwareEng.htm (4492 words)

	The Silver Bullet
		Software experts (such as the folks at Cigital) have a vested interest in seeing that the crisis lasts as long as possible.
		The primary reason for bad software is that it is based on the algorithm, a practice that is as old as Lovelace and Babbage (*).
		Software has become too much a part of our everyday life to be entrusted to the vagaries of an outdated and flawed paradigm.
	pages.sbcglobal.net /louis.savain/AI/Reliability.htm (3642 words)

	Software Tech News 5:2 - Education, Information Technology, and the Software Crisis (Site not responding. Last check: 2007-11-03)
		Ever since the "software dark ages", prior to circa 1975, and even during, many people have called attention to the so-called 'software crisis' and how it is causing all manner of problems in our high technology society.
		We assert that there is definitely a crisis and the unpredictable, 'software dragon' is part of it; but there is a larger issue that must be addressed from the system, organization, or the enterprise point of view.
		For whatever reason, the "software education crisis" is not being rectified, and the 'dragon' still roams the land.
	www.softwaretechnews.com /stn5-2/crisis.html (1971 words)

	Wikinfo \| Software engineering
		Software engineering is the technologies and practices that are used to create computer software while improving productivity and quality.
		Software engineering is much younger than civil engineering and electronic engineering and much older than space engineering and biological engineering.
		Software engineering arose out of the so called software crisis of the 1960s, 1970s, and 1980s, when many software projects had bad endings.
	www.wikinfo.org /wiki.php?title=Software_engineering (3021 words)

	The Silver Bullet (Site not responding. Last check: 2007-11-03)
		I will argue that the main reason that software is so unreliable and so hard to develop has to do with a custom that is as old as the computer: the practice of using the algorithm as the basis of software construction (*).
		Software reliability experts (such as the folks at Cigital) have a vested interest in seeing that the crisis lasts as long as possible.
		Software has become too much a part of our everyday lives to be entrusted to the vagaries of an archaic and hopelessly flawed paradigm.
	www.rebelscience.org /Cosas/Reliability.htm (7212 words)

	Sphere Data Systems Inc: Software Crisis (Site not responding. Last check: 2007-11-03)
		Software development is in a state of crisis, and the industry as a whole is in a state of denial.
		Hence the growing interest in software tools that can analyse code as it is being written, and automate the testing and quality-assurance procedures.
		The best place to put this bug-squashing software is as close as possible to the programmer—because the earlier in the development process that a bug can be identified, the cheaper it is to fix.
	www.sphere-data.com /pages/solutions/software_failure_detail.shtml (805 words)

	Software Engineering LG #95
		But those devices are useless if there are not software that are able to explore those features as much as possible, thus it is appropriate to say that the software development process, called software engineering, is one of the most important areas of computing.
		In the future that can be very dangerous, mainly to the free software community since, in some cases, there is no one in charge of monitoring and moderating the development phase of the project, once that several projects are developed by volunteers programmers.
		Many programmers just want their software producting the expected results, but if a programmer wants to be a successfull developer and have high quality and reliable software, it is essential to know all the theorycal bases that is hide under the practice.
	linuxgazette.net /issue95/rondina.html (943 words)

	History of software engineering - Wikipedia, the free encyclopedia
		Software engineering was spurred by the so-called software crisis of the 1960s, 1970s, and 1980s, which identified many of the problems of software development.
		The software crisis has been slowly fizzling out, because it is unrealistic to remain in crisis mode for more than 20 years.
		Discipline: Some pundits argued that the software crisis was due to the lack of discipline of programmers.
	en.wikipedia.org /wiki/History_of_software_engineering (1530 words)

	Software's Chronic Crisis
		By the time it reached 25, the difficulties of building big software loomed so large that in the autumn of 1968 the NATO Science Committee convened some 50 top programmers, computer scientists and captains of industry to plot a course out of what had come to be known as the software crisis.
		By combining their efforts, academia, industry and government may be able to hoist software development to the level of an industrial-age engineering discipline within the decade.
		Software is buckling as well under tectonic stresses imposed by the inexorably growing demand for "distributed systems": programs that run cooperatively on many networked computers.
	cispom.boisestate.edu /cis320emaxson/softcris.htm (6632 words)

	How Computer Science curriculm added to the problems of the Software Crisis (Site not responding. Last check: 2007-11-03)
		As Buxton states, "The average software development project overshoots is schedule by half; larger projects generally do worse." (Buxton, pg153) Some three quarters of all large systems are "operating failures" that either do not function as intended or are not used at all.(Gibbs, pg86).
		The software crisis was caused by programmers using a hand-to-mouth, every-programmer-builds-everything-from-the-ground-up approach to developing software.
		The idea that the computer science curriculum is producing students under-qualified in engineering is clearly shown by the many examples of the software crisis.
	www.cs.utexas.edu /users/almstrum/cs370/summer/softwarecrisis.html (1213 words)

	Report: 'Complexity Crisis' To Hold Back Software Growth - E-business & Business Technology News by TechWeb
		The worldwide software industry may be continuing its recovery, but the "complexity crisis" that has been plaguing the industry will keep it from reaching the booming double-digit growth rates achieved before the recent recession, according to a new report.
		While software sales began dropping in 2000, and were down to just one-half of one percentage point of growth in 2001, worldwide software revenue increased 5.1 percent, to $178 billion, in 2003, he said.
		Going forward, software growth will be driven by many smaller initiatives, according to the IDC report.
	www.techweb.com /wire/ebiz/52200114 (505 words)

	Software Crisis (Site not responding. Last check: 2007-11-03)
		There is a lot of excellent software development being done by programmers, and there are a lot of unhappy users who can't find software that works the way they think it should.
		It is arguably a complexity crisis rather than a software crisis.
		I believe the term was coined by DougMcIlroy, while presenting his paper on mass produced software components to the NATO Conference in Software Engineering conference in 1968.
	c2.com /cgi/wiki?SoftwareCrisis (277 words)

	BYTE.com
		It is, in fact, the heart of the real software crisis: There is more software to be developed than there are capable developers to do it.
		The conclusion I have reluctantly come to after more than 20 years of software development is this: Excellent developers, like excellent musicians and artists, are born, not made.
		This is not to slight the decent, talented software engineers, the ones who study hard and work hard at developing and maintaining their skills.
	www.byte.com /art/9601/sec15/art1.htm (883 words)

	EHS Software - Environmental, Health & Safety - Crisis Management Software
		ESS is a leading provider of Operational Risk Management software and services that focus on Environmental, Health and Safety (EHS) regulatory reporting and Crisis Management activities that assure compliance while building a foundation for operational excellence.
		The company's Crisis Management, Refrigerant Management and Waste Management solutions were the first of their kind.
		ESS solutions also move users beyond compliance, transforming their environmental and crisis data into the information needed to support regulatory reporting and business-enhancing performance metrics that drive out operational expenses and risk.
	www.ess-home.com (307 words)

	The Software Crisis (Site not responding. Last check: 2007-11-03)
		The most visible symptoms of the software crisis are
		There may not be enough good developers around to create all the new software that users need
		A significant portion of developers’ time must often be dedicated to the maintenance or preservation of geriatric software
	www.ics.uci.edu /~ziv/ooad/intro_to_se/tsld010.htm (58 words)

	software crisis concept from the Object Oriented Software Engineering knowledge base (Site not responding. Last check: 2007-11-03)
		software crisis concept from the Object Oriented Software Engineering knowledge base
		has definition The situation that is said to have existed since a least the late 1970's, characterized by an inability of software developers to deliver good quality software on time and on budget
		is a subtopic of 1.1 - The Nature of Software
	www.site.uottawa.ca:4321 /oose/softwarecrisis.html (73 words)

	Christmas Crisis - Free Software Downloads and Software Reviews - Download.com
		Christmas Crisis 1.0.5 has been updated to Christmas Crisis 1.0.7.
		In a moment, you will be re-directed to the latest version of Christmas Crisis.
		Please click here for Christmas Crisis 1.0.7 if your browser does not automatically re-direct you.
	www.download.com /Christmas-Crisis/3000-2278_4-10557531.html (58 words)

	Tag: software - Crisis Averted!
		Recently while working on a few Swing applications at work, I realized that one of the most frustrating aspects of developing Swing apps (and perhaps GUI software in general) is also one of the most mundane: user preferences.
		Building out the main application is tremendously rewarding, but providing users with preferences can be a huge pain.
		On the upside, now that Basecamp provides native time reports across all projects, there's no longer a need for Basecamp Time Reporter to export and parse each project's report individually...
	socket7.net /tag/software/1 (1191 words)

	Software's Chronic Crisis; Scientific American; September 1994
		TRENDS IN COMPUTING by W. Wayt Gibbs, staff writer.
		Errors in real-time systems such as Clementine are devilishly difficult to spot because, like that suspicious sound in your car engine, they often occur only when conditions are just so [see "The Risks of Software," by Bev Littlewood and Lorenzo Strigini; SCIEN~FIC AMER ICAN, November 1992].
		There have been only a few such partnerships.
	www.cis.gsu.edu /~mmoore/CIS3300/handouts/SciAmSept1994.html (6642 words)

Try your search on: Qwika (all wikis)