Software - Revision history

Apisite: /* Quotes */

2025-12-04T07:25:26Z

Quotes

← Older revision		Revision as of 07:25, 4 December 2025
Line 6:		Line 6:
	**[[Bill Gates]], {{cite web\|url=http://news.bbc.co.uk/2/hi/business/7142073.stm\|title=Bill Gates: The skills you need to succeed\|publisher=BBC News\|date=14 December 2007}}		**[[Bill Gates]], {{cite web\|url=http://news.bbc.co.uk/2/hi/business/7142073.stm\|title=Bill Gates: The skills you need to succeed\|publisher=BBC News\|date=14 December 2007}}

	* One of the difficulties in thinking about software is its huge variety. A function definition in a spreadsheet cell is software. A smartphone app is software. The flight management system for an Airbus A380 is software. A word processor is software. We shouldn't expect a single discipline of [[software engineering]] to cover all of these, any more than we expect a single discipline of manufacturing to cover everything from the Airbus A380 to the production of chocolate bars, or a single discipline of social organization to cover everything from the United Nations to a kindergarten. Improvement in software engineering must come bottom-up, from intense specialized attention to particular products.		* One of the difficulties in thinking about software is its huge variety. A function definition in a spreadsheet cell is software. A [[smartphone]] app is software. The flight management system for an Airbus A380 is software. A word processor is software. We shouldn't expect a single discipline of [[software engineering]] to cover all of these, any more than we expect a single discipline of manufacturing to cover everything from the Airbus A380 to the production of chocolate bars, or a single discipline of social organization to cover everything from the United Nations to a kindergarten. Improvement in software engineering must come bottom-up, from intense specialized attention to particular products.
	** [[Michael A. Jackson]] in: K. De Grave (ed.) ''Formalism & Intuition in Software Development; A conversation with Michael A. Jackson conducted by Edgar G. Daylight and Bas van Vlijmen.'' 2015		** [[Michael A. Jackson]] in: K. De Grave (ed.) ''Formalism & Intuition in Software Development; A conversation with Michael A. Jackson conducted by Edgar G. Daylight and Bas van Vlijmen.'' 2015

2806:2F0:3241:EB90:4C7D:3CD5:2184:8EAF: As u

2025-05-14T05:15:35Z

As u

← Older revision		Revision as of 05:15, 14 May 2025
Line 40:		Line 40:

	==External links==		==External links==
	{{Wiktionary}}
	{{Wikipedia}}

	[[Category:Computer science]]		[[Category:Computer science]]
	[[Category:Software]]		[[Category:Software]]

Kaltenmeyer: /* Quotes */ ce

2025-04-01T21:46:05Z

Quotes: ce

← Older revision		Revision as of 21:46, 1 April 2025
Line 13:		Line 13:
	\|volume = 14,15 \|pages = 27-37 \|url = http://doi.acm.org/10.1145/379486.379513 \|doi = 10.1145/379486.379513 \|publisher = YYYY }}		\|volume = 14,15 \|pages = 27-37 \|url = http://doi.acm.org/10.1145/379486.379513 \|doi = 10.1145/379486.379513 \|publisher = YYYY }}

	* You can't physically touch software. You can hold a floppy disk or CD-ROM in your hand, but the software itself is a ghost that can be moved from one object to another with little difficulty. In contrast, a road is a solid object that has a definite size and shape. You can touch ~~the~~ the material and walk the route...<br>Software is a codification of a huge set of behaviors: if this occurs, then that should happen, and so on. We can visualize individual behaviors, but we have great difficulty visualizing large numbers of sequential and alternative behaviors...<br>The same things that make it hard to visualize software make it hard to draw blueprints of that software. A road plan can show the exact location, elevation, and dimensions of any part of the structure. The [[map]] corresponds to the structure, but it's not the same as the structure. Software, on the other hand, is just a codification of the behaviors that the programmers and users want to take place. The map is the same as the structure... This means that software can only be described accurately at the level of individual instructions... A map or a blueprint for a piece of software must greatly simplify the representation in order to be comprehensible. But by doing so, it becomes inaccurate and ultimately incorrect. This is an important realization: any architecture, design, or diagram we create for software is essentially inadequate. If we represent every detail, then we're merely duplicating the software in another form, and we're wasting our time and effort.		* You can't physically touch software. You can hold a floppy disk or CD-ROM in your hand, but the software itself is a ghost that can be moved from one object to another with little difficulty. In contrast, a road is a solid object that has a definite size and shape. You can touch the material and walk the route...<br>Software is a codification of a huge set of behaviors: if this occurs, then that should happen, and so on. We can visualize individual behaviors, but we have great difficulty visualizing large numbers of sequential and alternative behaviors...<br>The same things that make it hard to visualize software make it hard to draw blueprints of that software. A road plan can show the exact location, elevation, and dimensions of any part of the structure. The [[map]] corresponds to the structure, but it's not the same as the structure. Software, on the other hand, is just a codification of the behaviors that the programmers and users want to take place. The map is the same as the structure... This means that software can only be described accurately at the level of individual instructions... A map or a blueprint for a piece of software must greatly simplify the representation in order to be comprehensible. But by doing so, it becomes inaccurate and ultimately incorrect. This is an important realization: any architecture, design, or diagram we create for software is essentially inadequate. If we represent every detail, then we're merely duplicating the software in another form, and we're wasting our time and effort.
	** George Stepanek (2005) ''Software Project Secrets: Why Software Projects Fail''. p. 10-11		** George Stepanek (2005) ''Software Project Secrets: Why Software Projects Fail''. p. 10-11

An9elFish: SPAM link removed

2023-11-16T16:48:22Z

SPAM link removed

← Older revision		Revision as of 16:48, 16 November 2023
Line 44:		Line 44:

	[[Category:Computer science]]		[[Category:Computer science]]
	[[Category:Software\| ]]		[[Category:Software]]
	The [http://startlingworld.in/ startling world] is an API services & Solution provider company in India, offering any kinds of API services.

An9elFish: "+ Cards SG" is not part of the book title. It means that study cards are included.

2023-11-16T15:50:14Z

"+ Cards SG" is not part of the book title. It means that study cards are included.

← Older revision		Revision as of 15:50, 16 November 2023
Line 32:		Line 32:

	* Software gets slower faster than hardware gets faster.		* Software gets slower faster than hardware gets faster.
	** [[Niklaus Wirth]] (1995), cited in: Geoff Lancaster (2001), ''Excel HSC ~~Softw~~ Design~~&Devel~~ + ~~Cards SG,~~'' p. 107		** [[Niklaus Wirth]] (1995), cited in: Geoff Lancaster (2001), ''Excel HSC Software Design and Development'', p. 107

	== See also ==		== See also ==

Swam pl: new key for Category:Software: " " using HotCat

2023-08-18T23:24:03Z

new key for Category:Software: " " using HotCat

← Older revision		Revision as of 23:24, 18 August 2023
Line 44:		Line 44:

	[[Category:Computer science]]		[[Category:Computer science]]
	[[Category: Software]]		[[Category:Software\| ]]
	The [http://startlingworld.in/ startling world] is an API services & Solution provider company in India, offering any kinds of API services.		The [http://startlingworld.in/ startling world] is an API services & Solution provider company in India, offering any kinds of API services.

Ottawahitech: /* Quotes */ Sometimes we have to try to do things for awhile before we really have an understanding of where the problem points are.

2021-12-10T21:04:00Z

Quotes: Sometimes we have to try to do things for awhile before we really have an understanding of where the problem points are.

← Older revision		Revision as of 21:04, 10 December 2021
Line 27:		Line 27:
	:<p>But I don't think you need to think that alchemy is "evil." It's just pointless because you can obviously never do as well in a closed environment as you can with open scientific methods.</p>		:<p>But I don't think you need to think that alchemy is "evil." It's just pointless because you can obviously never do as well in a closed environment as you can with open scientific methods.</p>
	:* {{cite web\| url=http://www.informationweek.com/news/software/linux/showArticle.jhtml?articleID=198002077\| title=The Torvalds Transcript: Why I 'Absolutely Love' GPL Version 2\| date=2007-03-19\| author=[[Linus Torvalds]]\| accessdate=2008-12-31}}		:* {{cite web\| url=http://www.informationweek.com/news/software/linux/showArticle.jhtml?articleID=198002077\| title=The Torvalds Transcript: Why I 'Absolutely Love' GPL Version 2\| date=2007-03-19\| author=[[Linus Torvalds]]\| accessdate=2008-12-31}}

			* I do think we could do a better job of anticipating the software needs of new projects, but it is also important to understand that a lot of needs are not readily apparent a priori. Sometimes we have to try to do things for awhile before we really have an understanding of where the problem points are.
			** [[Jimbo Wales]] in '''[https://en.wikinews.org/wiki/Interview_with_Jimbo_Wales Interview with Jimbo Wales]''' (December 10, 2005)

	* Software gets slower faster than hardware gets faster.		* Software gets slower faster than hardware gets faster.

Kalki: Reverted edit by 207.195.86.77 (talk • contributions) to last version by 117.241.151.50

2021-04-12T00:02:54Z

Reverted edit by 207.195.86.77 (talk • contributions) to last version by 117.241.151.50

← Older revision		Revision as of 00:02, 12 April 2021
Line 1:		Line 1:
			Computer '''[[w:Software\|software]]''' is a general term used to describe a collection of computer programs, procedures and documentation that perform some task on a computer system.
⚫	* solid working knowledge of [[productivity]] software and other IT tools has become a basic foundation for success in virtually any career. Beyond that, however, I don't think you can overemphasise the importance of having a good background in [[maths]] and [[science]].

			==Quotes ==

		⚫	* A solid working knowledge of [[productivity]] software and other IT tools has become a basic foundation for success in virtually any career. Beyond that, however, I don't think you can overemphasise the importance of having a good background in [[maths]] and [[science]].
	**[[Bill Gates]], {{cite web\|url=http://news.bbc.co.uk/2/hi/business/7142073.stm\|title=Bill Gates: The skills you need to succeed\|publisher=BBC News\|date=14 December 2007}}		**[[Bill Gates]], {{cite web\|url=http://news.bbc.co.uk/2/hi/business/7142073.stm\|title=Bill Gates: The skills you need to succeed\|publisher=BBC News\|date=14 December 2007}}

Line 33:		Line 37:

	==External links==		==External links==
			{{Wiktionary}}
			{{Wikipedia}}

	[[Category:Computer science]]		[[Category:Computer science]]
	[[Category: Software]]		[[Category: Software]]

207.195.86.77 at 23:56, 11 April 2021

2021-04-11T23:56:22Z

← Older revision		Revision as of 23:56, 11 April 2021
Line 33:		Line 33:

	==External links==		==External links==
	{{Wiktionary}}
	{{Wikipedia}}

	[[Category:Computer science]]		[[Category:Computer science]]
	[[Category: Software]]		[[Category: Software]]

207.195.86.77 at 23:53, 11 April 2021

2021-04-11T23:53:17Z

← Older revision		Revision as of 23:53, 11 April 2021
Line 1:		Line 1:
	* A solid working knowledge of [[productivity]] software and other IT tools has become a basic foundation for success in virtually any career. Beyond that, however, I don't think you can overemphasise the importance of having a good background in [[maths]] and [[science]].		* solid working knowledge of [[productivity]] software and other IT tools has become a basic foundation for success in virtually any career. Beyond that, however, I don't think you can overemphasise the importance of having a good background in [[maths]] and [[science]].
	**[[Bill Gates]], {{cite web\|url=http://news.bbc.co.uk/2/hi/business/7142073.stm\|title=Bill Gates: The skills you need to succeed\|publisher=BBC News\|date=14 December 2007}}		**[[Bill Gates]], {{cite web\|url=http://news.bbc.co.uk/2/hi/business/7142073.stm\|title=Bill Gates: The skills you need to succeed\|publisher=BBC News\|date=14 December 2007}}