text:
Timeline of Amazon.com
From Wikipedia, the free encyclopedia
Jump to navigation Jump to search
Contents
1 Overview
2 Full timeline
3 See also
4 References
Overview[edit]
Time period
Key developments at Amazon
1994–1998

Amazon starts off as an online bookstore selling books, primarily competing with local booksellers and Barnes & Noble. It IPOs in 1997.
1998–2004 Amazon starts to expand its services beyond books. It also starts offering convenience services, such as Free Super Savers Shipping.
2005–2011 Amazon moves into the cloud computing area with Amazon AWS, as well as the crowdsourcing area with Amazon Mechanical Turk. By being an early player, it eventually dominates the cloud computing scene, allowing it to control much of the physical infrastructure of the Internet.[1] Amazon also offers the Amazon Kindle for people to purchase their books as eBooks, and by 2010, more people buy ebooks than physical books off of Amazon.
2011–2015 Amazon starts offering streaming services like Amazon Music and Amazon Video. By 2015, its market capitalization surpasses that of Walmart.
Full timeline[edit]
Year
Month and date
Event type
Details
1994 July 5 Company Amazon founded.[2]
1997 May 15 Company Amazon IPOs at $18.00/share, raising $54 million.[2]
1998 April 27 Acquisitions Amazon acquires the Internet Movie Database, a comprehensive repository for movie information on the Internet.[3]
1998 August 5 Company Direction Amazon announces that it will move beyond books.[4]
1998 December Competition Jack Ma launches Alibaba in China, which would later grow to dominate the Chinese online retail market, and provide an obstacle to Amazon's attempts to expand in China.[5][6]
2002 January Product Amazon launches Free Super Saver Shipping, which allows customers to get free shipping for orders above $99.[2]
2002 March Legal, Competition Amazon settles its October 1999 patent infringement suit against Barnes & Noble (over its 1-Click checkout system, which it received a patent for in September 1999). It originally charged that Barnes&Noble.com had essentially copied Amazon's 1-Click technology.[7]
2003 October Product Amazon launches A9.com, a subsidiary of Amazon.com based in Palo Alto, California that develops search and advertising technology.[8]
2004 August 19 International Amazon acquires Joyo, an online bookstore in China, for $75 million, which then becomes the 7th regional website of Amazon.com. joyo later becomes Amazon China.[9]
2005 February Product Amazon launches Amazon Prime, a membership offering free two-day shipping within the contiguous United States on all eligible purchases for a flat annual fee of $79.[2]
2005 November Product Amazon launches Amazon Mechanical Turk, an application programming interface (API) allowing any Internet user to perform "human-intelligence" tasks such as transcribing podcasts, often at very low wages.[2]
2006 August 25 Product Amazon launches Amazon Elastic Compute Cloud (Amazon EC2), a virtual site farm allowing users to use the Amazon infrastructure to run applications ranging from running simulations to web hosting.[10]
2006 September 19 Product Amazon launches Fulfillment by Amazon, giving small businesses to use Amazon.com's own order fulfillment and customer service infrastructure - and customers of Amazon.com shipping offers when buying from 3rd-party sellers.[11]
2006 Legal Amazon agrees to settle a legal dispute with Toys R Us (over a partnership that gave Toys R Us exclusive rights to supply some toy products on Amazon's website) and pays $51 million.[12]
2006 March Product Amazon launches Amazon Simple Storage Service (Amazon S3), which allows other websites/developers to store computer files on Amazon's servers.[2]
2007 August Product CreateSpace announces launch of Books on Demand service, which makes it easy for authors who want to self-publish their books to distribute them on Amazon.com.[13]
2007 August Product Amazon launches AmazonFresh, a grocery service offering perishable and nonperishable foods.[14]
2007 September 25 Product Amazon launches Amazon Music, an online music store and music locker.[15]
2007 November 19 Product Amazon launches the Amazon Kindle.[2]
2009 July 22 Acquisitions, Competition Amazon acquires Zappos for $850 million.[16]
2009 October 20 Competition Barnes & Noble announces the Nook, an eReader.[17]
2010 January Competition Apple introduces its own virtual bookstore, called iBooks, and then partners with five major book publishers.[18] It later convinces them to raise the price of ebooks (using the agency pricing model that gives publishers full control over ebook prices).
2010 February 1 Competition Microsoft launches Microsoft Azure, a cloud computing platform that will compete with Amazon AWS over cloud services.
2010 July Product Amazon announced that e-book sales for its Kindle reader outnumbered sales of hardcover books for the first time ever.[19]
2011 January Acquisitions, International Amazon acquires Lovefilm, a DVD rental service known as the Netflix of Europe.[20]
2011 February 16 Competition Borders Group, outcompeted by Amazon, applies for Chapter 11 bankruptcy.[21]
2011 February 22 Product Amazon rebrands its Amazon Video service as Amazon Instant Video and adds access to 5,000 movies and TV shows for Amazon Prime members.[22][23]
2011 March 22 Product Amazon launches the Amazon Appstore for Android devices and the service was made available in over 200 countries.[24]
2011 July 1 Legal California starts collecting sales taxes on Amazon.com purchases.[25]
2011 September Product Amazon launches Amazon Locker, a delivery locker system that allows users to get items delivered at specially-designed lockers.[26]
2011 September 28 Product Amazon announces the Kindle Fire, a tablet computer that takes aim at Apple's iPad with a smaller device that sells at $199, compared with the $499 value of Apple's cheapest iPad.[27]
2012 April Legal The Department of Justice files suit against Apple Inc and five major publishing houses (the "Big Five"), alleging that they colluded in 2010 to raise the price of ebooks (using the agency pricing model that gives publishers full control over ebook prices).[28] Amazon had originally set the price of ebooks at $9.99 (using the wholesale pricing model giving Amazon full control over ebook prices).
2012 March 19 Acquisitions Amazon acquires Kiva Systems for $775 million, a robotics company that creates robots that can move items around warehouses.[29]
2012 April Legal Amazon agrees to allow collection of sales taxes in both Nevada and Texas (starting on July 1), and agrees to create 2,500 jobs and invest $200 million in new distribution centers in Texas.[30]
2012 September 6 Product Amazon announces the Kindle Fire HD series of touchscreen tablet computers.[31]
2013 March Acquisitions Amazon acquires social reading and book-review site GoodReads.[32]
2013 June International Amazon launches in India.[33][34]
2014 July 25 Product Amazon launches the Amazon Fire.[35]
2014 August 25 Acquisitions Amazon announced its intent to acquire the video game streaming website Twitch for $970 million.[36]
2014 October Legal Amazon reaches agreement with Simon & Schuster, allowing the publisher to adopt the agency pricing model and set prices on its books sold on Amazon.[37]
2014 November 6 (announcement), actual rollout occurs through 2015 Product Amazon unveils Amazon Echo, a wireless speaker and voice command device that can take commands and queries, and be used to add items to the Amazon.com shopping cart, among other things.[38][39] The Alexa Voice Service that is built into Amazon Echo can also be added to other Amazon devices.[40]
2014 November Legal Amazon resolves dispute with Hachette, allowing Hachette to adopt the agency-pricing model and set prices on Hachette books sold on Amazon.[41]
2015 July Competition, International Alibaba announces that it will invest $1 billion into its Aliyun cloud computing arm, some of which would go into new Aliyun international data centers. This would allow Aliyun to compete with Amazon Web Services outside of China.[42]
2015 August 26 Product Amazon launches Amazon Underground, an Android app through which users can get gaming and other apps for free that they would otherwise have to pay for, and also get in-app purchases for free. App creator participation is voluntary. App creators are paid $0.002 for every minute a user spends in the app.[43][44][45]
2015 September 8 Product Amazon launches its Amazon Restaurants service that delivers food from nearby restaurants, for Amazon Prime customers in Seattle.[46][47] The service would subsequently be rolled out to many other cities.
2015 November 2 Product Amazon opened its first physical retail store, a bookstore in the University Village shopping center in Seattle. The store, known as Amazon Books, has prices matched to those found on the Amazon website and integrate online reviews into the store's shelves.[48]
2015 December 14 Company Amazon begins moving into their new headquarters campus in the Denny Triangle neighborhood of Seattle, beginning with the 38-story Amazon Tower I (nicknamed "Doppler" after the codename for Amazon Echo).[49] The three towers are scheduled to be completed by 2020.
2016 December 7 Delivery Amazon Prime Air (Amazon's drone-based delivery system) makes its first delivery in Cambridge in the United Kingdom. The successful delivery is announced a week later, on December 14, along with video.[50][51]
2017 June 15 Acquisitions Amazon acquires Whole Foods for $13.7 billion, a high end grocery store located throughout the United States, United Kingdom, and Canada.[52]
2017 September 7 Company Amazon began search for Amazon HQ2, a second company headquarters to house up to 50,000 employees.[53][54]
2018 January 18 Company Amazon narrows down the choices of its second headquarters location to 20 cities.[55]
2018 January 22 Company Amazon opens a cashier-less grocery store to the public.[56]
See also[edit]
Timeline of Amazon Web Services
Business and economics portal
Companies portal
History portal
References[edit]
Jump up ^ "Amazon and Google are in an epic battle to dominate the cloud—and Amazon may already have won - Quartz". Qz.com. Retrieved January 17, 2016.
^ Jump up to: a b c d e f g Stone, Brad (2013). The Everything Store: Jeff Bezos and the Age of Amazon. New York: Little Brown and Co. ISBN 9780316219266. OCLC 856249407.
Jump up ^ "Amazon Media Room: Press Releases". Phx.corporate-ir.net. Retrieved January 17, 2016.
Jump up ^ "Amazon.com Is Expanding Beyond Books". The New York Times. August 5, 1998. Retrieved January 10, 2016.
Jump up ^ "Alibaba chief Jack Ma disappoints investors with London no-show". The Daily Telegraph. September 17, 2014. Retrieved January 17, 2016.
Jump up ^ "Why Amazon Should Fear Alibaba". Forbes. Retrieved January 17, 2016.
Jump up ^ "Amazon, Barnes&Noble settle patent suit - CNET". Cnet.com. Retrieved January 15, 2016.
Jump up ^ "Amazon releases A9 search engine". Macworld.com. Retrieved January 17, 2016.
Jump up ^ "Joyo Amazon was renamed to Amazon China" (in Chinese). NetEase. October 27, 2011. Retrieved October 27, 2011.
Jump up ^ Barr, Jeff (August 25, 2006). "Amazon EC2 Beta". Amazon Web Services Blog. Retrieved May 31, 2013.
Jump up ^ "Amazon.com Investor Relations: Press Release". Phx.corporate-ir.net. Retrieved January 17, 2016.
Jump up ^ "Amazon to pay Toys R Us $51M to settle suit - ABC News". Abcnews.go.com. Retrieved January 15, 2016.
Jump up ^ "CreateSpace: Self Publishing and Free Distribution for Books, CD, DVD". Retrieved January 15, 2016.
Jump up ^ Harris, Craig; Cook, John (2007-08-01). "Amazon starts grocery delivery service". Seattle Post-Intelligencer. Retrieved 2008-11-26.
Jump up ^ "Amazon.com Launches Public Beta of Amazon MP3". BusinessWire (Press release). September 25, 2007. Archived from the original on January 2, 2013.
Jump up ^ "Here's Why Amazon Bought Zappos". Mashable.com. Retrieved January 10, 2016.
Jump up ^ Jeffrey A. Trachtenberg and Geoffrey A. Fowler (October 20, 2009). "B&N Reader Out Tuesday". The Wall Street Journal. Archived from the original on October 21, 2009. Retrieved October 20, 2009.
Jump up ^ "Apple introduces iBooks store for iPad". Appleinsider.com. Retrieved January 17, 2016.
Jump up ^ "Amazon Says E-Books Now Top Hardcover Sales". The New York Times. July 19, 2010. Retrieved January 17, 2016.
Jump up ^ Tim Bradshaw In London, Jonathan Birchall In New York (January 20, 2011). "Amazon acquires Lovefilm for £200m". Financial Times. Retrieved January 17, 2016.
Jump up ^ "Borders Closing: Why the Bookstore Chain Failed". Ibtimes.com. Retrieved January 15, 2016.
Jump up ^ Christina Warren2011-02-22 12:45:05 UTC (2011-02-22). "HANDS ON: Amazon's Prime Instant Video". Mashable.com. Retrieved 2013-11-27.
Jump up ^ "Amazon Media Room: Press Releases". corporate-ir.net.
Jump up ^ Amazon.com (2013-05-23). "Developers Can Now Distribute Apps in Nearly 200 Countries Worldwide on Amazon - Amazon Mobile App Distribution Blog". Developer.amazon.com. Retrieved 2013-11-27.
Jump up ^ "California Becomes Seventh State to Adopt "Amazon" Tax on Out-of-State Online Sellers". Taxfoundation.org. Retrieved January 17, 2016.
Jump up ^ "Photos: A look at Amazon's new delivery locker at 7-Eleven - GeekWire". Geekwire.com. Retrieved January 15, 2016.
Jump up ^ "Amazon Unveils $199 Kindle Fire Tablet, Taking on Apple IPad - Bloomberg Business". Bloomberg.com. Retrieved January 17, 2016.
Jump up ^ "The Justice Department Just Made Jeff Bezos Dictator-for-Life - The Atlantic". Theatlantic.com. Retrieved January 15, 2016.
Jump up ^ "Amazon Acquires Kiva Systems in Second-Biggest Takeover - Bloomberg Business". Bloomberg.com. Retrieved January 10, 2016.
Jump up ^ "Documents: Amazon risking little in Texas sales tax deal". Statesman.com. Retrieved January 10, 2016.
Jump up ^ "Kobo Announces Their New E-Readers". Wired.com. Retrieved January 17, 2016.
Jump up ^ "Amazon Acquires Social Reading Site Goodreads, Which Gives The Company A Social Advantage Over Apple". TechCrunch. March 28, 2013. Retrieved March 29, 2013.
Jump up ^ "Amazon now in India - The Hindu". Thehindu.com. Retrieved January 17, 2016.
Jump up ^ "Amazon Invades India - Fortune". Fortune.com. Retrieved January 17, 2016.
Jump up ^ "Amazon's Fire Phone to sell exclusively on AT&T for $199.99 starting July 25th". Theverge.com. Retrieved January 17, 2016.
Jump up ^ "Amazon acquires Twitch: World's largest e-tailer buys largest gameplay-livestreaming site". Venturebeat.com. Retrieved January 17, 2016.
Jump up ^ "Amazon Closes Multi-Year Deal With Simon & Schuster - Business Insider". Businessinsider.com. Retrieved January 15, 2016.
Jump up ^ Stone, Brad; Soper, Spencer (2014-11-06). "Amazon Unveils a Listening, Talking, Music-Playing Speaker for Your Home". Bloomberg Businessweek. Bloomberg L.P. Retrieved 2014-11-07.
Jump up ^ "Amazon Echo is now available for everyone to buy for $179.99, shipments start on July 14". Android Central.
Jump up ^ "Amazon Unbundles Alexa Virtual Assistant From Echo With New Dev Tools". TechCrunch. AOL. 25 June 2015.
Jump up ^ "Amazon and Hachette have finally resolved their bitter dispute". The Verge. November 13, 2014. Retrieved January 15, 2016.
Jump up ^ "Alibaba $1 Billion Dollar Cloud Investment - International Competition Mounting »". Cloudtweaks.com. Retrieved January 17, 2016.
Jump up ^ Dillet, Romain (August 26, 2015). "Amazon Underground Features An Android App Store Focused On "Actually Free" Apps". TechCrunch. Retrieved April 26, 2016.
Jump up ^ Singleton, Micah (August 26, 2015). "Amazon launches Underground to promote free apps and games. The Free App of the Day program has also come to a close". The Verge. Retrieved April 26, 2016.
Jump up ^ Barrett, Brian (August 29, 2015). "Has Amazon Cracked the Problem With In-App Payments?". Wired Magazine. Retrieved April 26, 2016.
Jump up ^ Duryee, Tricia (September 8, 2015). "Amazon confirms Prime Now restaurant delivery launch in Seattle area, hints at broader rollout". GeekWire. Retrieved December 21, 2016.
Jump up ^ Jennings, Lisa (September 8, 2015). "Amazon launches restaurant delivery in Seattle. Service is available to Amazon Prime Now customers only". Nation's Restaurant News. Retrieved December 21, 2016.
Jump up ^ "Amazon is opening its first physical bookstore today". The Verge. November 2, 2015. Retrieved January 17, 2016.
Jump up ^ Greene, Jay (December 14, 2015). "Workers move in to the first of Amazon's downtown towers". The Seattle Times. Retrieved January 17, 2016.
Jump up ^ Reisinger, Don (December 14, 2016). "Watch Amazon's Prime Air Complete Its First Drone Delivery". Fortune Magazine. Retrieved December 21, 2016.
Jump up ^ Fierberg, Emma (December 14, 2016). "Watch Amazon make its first drone delivery". Business Insider. Retrieved December 21, 2016.
Jump up ^ "Amazon to Acquire Whole Foods for $13.7 Billion". Bloomberg.com. 2017-06-16. Retrieved 2017-06-19.
Jump up ^ "Amazon HQ2". Retrieved September 14, 2017.
Jump up ^ "8 cities fit for Amazon's second headquarters". CNN. September 11, 2017. Retrieved September 14, 2017.
Jump up ^ https://www.nytimes.com/2018/01/18/technology/amazon-finalists-headquarters.html
Jump up ^ https://www.usatoday.com/story/tech/news/2018/01/21/amazon-set-open-its-grocery-store-without-checkout-line-public/1048492001/
show
v
t
e
Amazon
People
Current
Jeff Bezos
Doug Gurr
Tony Hsieh
Werner Vogels
Former
Rick Dalzell
Paul Davis
Brian McBride
Nadia Shouraboura
Ram Shriram
Tom Szkutak
Brian Valentine
Christopher North
Facilities
Doppler
Day 1
Spheres
HQ2
Products
and services
Websites
A9.com
AbeBooks
Amazon.com
China
Alexa Internet
Book Depository
BookFinder
Digital Photography Review
Fresh
Goodreads
IMDb
Box Office Mojo
Withoutabox
Local
Marketplace
Payments
Shopbop
Twitch.tv
Curse
Wireless
Woot.com
Zappos
Souq.com
Amazon Web Services
AMI
Amazon Aurora
CloudFront
DynamoDB
EBS
EC2
EFS
ElastiCache
EMR
AWS Lambda
MTurk
Neptune
Product Advertising API
RDS
Redshift
S3
SES
SNS
SimpleDB
SQS
VPC
Silk
Glacier
Storywriter
Digital
Alexa
Appstore
Audible
ComiXology
Amazon Drive
Video
Prime
Key
Prime Music
Prime Now
Prime Pantry
Prime Video
Kindle Store
Music
Fire OS
Amazon Digital Game Store
Devices
Blink Home
Cloud Cam
Dash buttons
Dash wand
Echo
Show
Kindle
Kindle Fire
Fire HD
Fire HDX
Fire TV
Stick
Fire Phone
Ring
Technology
1-Click
Amazon Game Studios
Amazon Robotics
Carbonado
Dynamo
Graphiq
Lab126
Double Helix Games
Obidos
Liquavista
Publishing
Amazon Publishing
Amazon Studios
Breakthrough Novel Award
Best Books of the Year
Kindle Direct Publishing
Retail
Amazon Books
Amazon Go
Treasure Truck
Whole Foods Market
Logistics
Amazon Air
Amazon Prime Air
Former
43 Things
Askville
Amapedia
Amie Street (Songza)
CDNow
Diapers.com
Endless.com
Lexcycle
LivingSocial
LoveFilm
Mobipocket
PlanetAll
Reflexive Entertainment
Sellaband
Shelfari
Other
Amazon Light
ASIN
Controversies (tax)
Fishbowl
Locker
Perfect 10, Inc. v. Amazon.com, Inc.
Statistically improbable phrase
Vine
List of Amazon brands
List of Amazon locations
List of mergers and acquisitions by Amazon
List of Amazon products and services
LibraryThing
show
v
t
e
Technology company timelines
Amazon.com
Amazon Web Services
Dropbox
Facebook
LinkedIn
Lyft
Microsoft
Netflix
Nortel
PayPal
Pinterest
Reddit
Snapchat
Square
Instagram
Intel
Twitter
Uber
WhatsApp
Xiaomi
Yahoo!
Retrieved from "https://en.wikipedia.org/w/index.php?title=Timeline_of_Amazon.com&oldid=856997011"
Categories:
Technology company timelines
Amazon (company)
Hidden categories:
CS1 Chinese-language sources (zh)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
Add links
This page was last edited on 28 August 2018, at 21:54 (UTC).
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

attrs: class href

values: mw-jump-link #mw-head

values: mw-jump-link #p-search

value: input

attrs: type role id class style

values: checkbox button toctogglecheckbox toctogglecheckbox display:none

value: label

attrs: class for

values: toctogglelabel toctogglecheckbox

value: span

attrs: class dir

values: toctitle ltr

value: li

values:
headerSort
0
columnheader button
Sort ascending

values:
/wiki/Internet_Movie_Database
mw-redirect
Internet Movie Database

values:
/wiki/Amazon_Simple_Storage_Service
mw-redirect
Amazon Simple Storage Service

values:
/wiki/Chapter_11_bankruptcy
mw-redirect
Chapter 11 bankruptcy

values:
/wiki/Kiva_Systems
mw-redirect
Kiva Systems

values:
/wiki/Amazon_Fire
mw-redirect
Amazon Fire

values:
/wiki/Retail_store
mw-redirect
Retail store

values: Amazon.com headquarters (page does not exist)

values:
/wiki/Amazon_Tower_I
mw-redirect
Amazon Tower I

values:
noprint metadata navbox
navigation
Portals
font-weight:bold;padding:0.4em 2em

values:
nofollow
external text
//www.worldcat.org/oclc/856249407

values:
/wiki/Wired_Magazine
mw-redirect
Wired Magazine

values:
/wiki/Fortune_Magazine
mw-redirect
Fortune Magazine

values: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

values:
/wiki/Amazon_Elastic_MapReduce
mw-redirect
Amazon Elastic MapReduce

values:
/wiki/Amazon_Simple_Email_Service
mw-redirect
Amazon Simple Email Service

values:
/wiki/Amazon_Prime_Music
mw-redirect
Amazon Prime Music

values:
/wiki/Amazon_Prime_Video
mw-redirect
Amazon Prime Video

values:
/wiki/Amazon_Key#Cloud_Cam
mw-redirect
Amazon Key

values: nowraplinks collapsible autocollapse navbox-inner mw-collapsible mw-made-collapsible mw-collapsed

values: Template talk:Technology company timelines

values: Category:CS1 Chinese-language sources (zh)

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Timeline_of_Amazon.com
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values: A list of all special pages [ctrl-alt-q]

values: Permanent link to this revision of the page

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

values: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Timeline_of_Amazon_com rootpage-Timeline_of_Amazon_com skin-vector action-view


text:
Software bug
From Wikipedia, the free encyclopedia
Jump to: navigation, search
This article needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (September 2017) (Learn how and when to remove this template message)
To report a MediaWiki error on Wikipedia, see Wikipedia:Bug reports.
Software development
Core activities
Processes
Requirements
Design
Engineering
Construction
Testing
Debugging
Deployment
Maintenance
Paradigms and models
Agile
Cleanroom
Incremental
Prototyping
Spiral
Waterfall
Methodologies and frameworks
DevOps
DSDM
FDD
IID
Kanban
Lean SD
MDD
MSF
PSP
RAD
SAFe
Scrum
SEMAT
TSP
UP
V-Model
XP
Supporting disciplines
Configuration management
Documentation
Software quality assurance (SQA)
Project management
User experience
Practices
ATDD
BDD
CCO
CI
CD
DDD
PP
Stand-up
TDD
Tools
Compiler
Debugger
Profiler
GUI designer
Modeling
IDE
Build automation
Release automation
Infrastructure as Code
Testing
Standards and BOKs
CMMI
IEEE standards
ISO 9001
ISO/IEC standards
SWEBOK
PMBOK
BABOK
v
t
e
A software bug is an error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways. The process of fixing bugs is termed "debugging" and often uses formal techniques or tools to pinpoint bugs, and since the 1950s, some computer systems have been designed to also deter, detect or auto-correct various computer bugs during operations.
Most bugs arise from mistakes and errors made in either a program's source code or its design, or in components and operating systems used by such programs. A few are caused by compilers producing incorrect code. A program that contains a large number of bugs, and/or bugs that seriously interfere with its functionality, is said to be buggy (defective). Bugs can trigger errors that may have ripple effects. Bugs may have subtle effects or cause the program to crash or freeze the computer. Other bugs qualify as security bugs and might, for example, enable a malicious user to bypass access controls in order to obtain unauthorized privileges.
Some software bugs have been linked to disasters. Bugs in code that controls the Therac-25 radiation therapy machine were directly responsible for patient deaths in the 1980s. In 1996, the European Space Agency's US$1 billion prototype Ariane 5 rocket had to be destroyed less than a minute after launch due to a bug in the on-board guidance computer program. In June 1994, a Royal Air Force Chinook helicopter crashed into the Mull of Kintyre, killing 29. This was initially dismissed as pilot error, but an investigation by Computer Weekly convinced a House of Lords inquiry that it may have been caused by a software bug in the aircraft's engine-control computer.[1]
In 2002, a study commissioned by the US Department of Commerce's National Institute of Standards and Technology concluded that "software bugs, or errors, are so prevalent and so detrimental that they cost the US economy an estimated $59 billion annually, or about 0.6 percent of the gross domestic product".[2]
Contents
[hide]
1 Etymology
2 History
2.1 "Bugs in the System" report
3 Terminology
4 Prevention
4.1 Typographical errors
4.2 Development methodologies
4.3 Programming language support
4.4 Code analysis
4.5 Instrumentation
5 Testing
6 Debugging
7 Bug management
7.1 Severity
7.2 Priority
7.3 Software releases
8 Types
8.1 Arithmetic
8.2 Logic
8.3 Syntax
8.4 Resource
8.5 Multi-threading
8.6 Interfacing
8.7 Teamworking
9 Implications
10 Well-known bugs
11 In popular culture
12 See also
13 References
14 Further reading
15 External links
Etymology[edit]
The term "bug" to describe defects has been a part of engineering jargon since the 1870s and predates electronic computers and computer software; it may have originally been used in hardware engineering to describe mechanical malfunctions. For instance, Thomas Edison wrote the following words in a letter to an associate in 1878:
It has been just so in all of my inventions. The first step is an intuition, and comes with a burst, then difficulties arise—this thing gives out and [it is] then that "Bugs"—as such little faults and difficulties are called—show themselves and months of intense watching, study and labor are requisite before commercial success or failure is certainly reached.[3]
The Middle English word bugge is the basis for the terms "bugbear" and "bugaboo" as terms used for a monster.[4] Baffle Ball, the first mechanical pinball game, was advertised as being "free of bugs" in 1931.[5] Problems with military gear during World War II were referred to as bugs (or glitches).[6] In a book published in 1942, Louise Dickinson Rich, speaking of a powered ice cutting machine, said, "Ice sawing was suspended until the creator could be brought in to take the bugs out of his darling."[7]
Isaac Asimov used the term "bug" to relate to issues with a robot in his short story "Catch That Rabbit", published in 1944, and included in his well-known collection of short stories I, Robot. From page 1 of "Catch That Rabbit": "U.S. Robots had to get the bugs out of the multiple robot, and there were plenty of bugs, and there are always at least half a dozen bugs left for the field-testing."
A page from the Harvard Mark II electromechanical computer's log, featuring a dead moth that was removed from the device
The term "bug" was used in an account by computer pioneer Grace Hopper, who publicized the cause of a malfunction in an early electromechanical computer.[8] A typical version of the story is:
In 1946, when Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark II and Mark III. Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug. This bug was carefully removed and taped to the log book. Stemming from the first bug, today we call errors or glitches in a program a bug.[9]
Hopper did not find the bug, as she readily acknowledged. The date in the log book was September 9, 1947.[10][11][12] The operators who found it, including William "Bill" Burke, later of the Naval Weapons Laboratory, Dahlgren, Virginia,[13] were familiar with the engineering term and amusedly kept the insect with the notation "First actual case of bug being found." Hopper loved to recount the story.[14] This log book, complete with attached moth, is part of the collection of the Smithsonian National Museum of American History.[11]
The related term "debug" also appears to predate its usage in computing: the Oxford English Dictionary's etymology of the word contains an attestation from 1945, in the context of aircraft engines.[15]
History[edit]
The concept that software might contain errors dates back to Ada Lovelace's 1843 notes on the analytical engine, in which she speaks of the possibility of program "cards" for Charles Babbage's analytical engine being erroneous:
... an analysing process must equally have been performed in order to furnish the Analytical Engine with the necessary operative data; and that herein may also lie a possible source of error. Granted that the actual mechanism is unerring in its processes, the cards may give it wrong orders.
"Bugs in the System" report[edit]
The Open Technology Institute, run by the group, New America,[16] released a report "Bugs in the System" in August 2016 stating that U.S. policymakers should make reforms to help researchers identify and address software bugs. The report "highlights the need for reform in the field of software vulnerability discovery and disclosure."[17] One of the report’s authors said that Congress has not done enough to address cyber software vulnerability, even though Congress has passed a number of bills to combat the larger issue of cyber security.[17]
Government researchers, companies, and cyber security experts are the people who typically discover software flaws. The report calls for reforming computer crime and copyright laws.[17]
"The Computer Fraud and Abuse Act, the Digital Millennium Copyright Act and the Electronic Communications Privacy Act criminalize and create civil penalties for actions that security researchers routinely engage in while conducting legitimate security research, the report said."[17]
Terminology[edit]
There is ongoing debate over the use of the term "bug" to describe software errors. One argument is that the word "bug" is divorced from a sense that a human being caused the problem, and instead implies that the defect arose on its own, leading to a push to abandon the term "bug" in favor of terms such as "defect", with limited success.[18] Since the 1970s Gary Kildall somewhat humorously suggested to use the term "blunder".[19][20]
In software engineering, mistake metamorphism (from Greek meta = "change", morph = "form") refers to the evolution of a defect in the final stage of software deployment. Transformation of a "mistake" committed by an analyst in the early stages of the software development lifecycle, which leads to a "defect" in the final stage of the cycle has been called 'mistake metamorphism'.[21]
Different stages of a "mistake" in the entire cycle may be described as "mistakes", "anomalies", "faults", "failures", "errors", "exceptions", "crashes", "bugs", "defects", "incidents", or "side effects".[21]
Prevention[edit]
The software industry has put much effort into reducing bug counts.[22][23] These include:
Typographical errors[edit]
Bugs usually appear when the programmer makes a logic error. Various innovations in programming style and defensive programming are designed to make these bugs less likely, or easier to spot. Some typos, especially of symbols or logical/mathematical operators, allow the program to operate incorrectly, while others such as a missing symbol or misspelled name may prevent the program from operating. Compiled languages can reveal some typos when the source code is compiled.
Development methodologies[edit]
Several schemes assist managing programmer activity so that fewer bugs are produced. Software engineering (which addresses software design issues as well) applies many techniques to prevent defects. For example, formal program specifications state the exact behavior of programs so that design bugs may be eliminated. Unfortunately, formal specifications are impractical for anything but the shortest programs, because of problems of combinatorial explosion and indeterminacy.
Unit testing involves writing a test for every function (unit) that a program is to perform.
In test-driven development unit tests are written before the code and the code is not considered complete until all tests complete successfully.
Agile software development involves frequent software releases with relatively small changes. Defects are revealed by user feedback.
Open source development allows anyone to examine source code. A school of thought popularized by Eric S. Raymond as Linus's Law says that popular open-source software has more chance of having few or no bugs than other software, because "given enough eyeballs, all bugs are shallow".[24] This assertion has been disputed, however: computer security specialist Elias Levy wrote that "it is easy to hide vulnerabilities in complex, little understood and undocumented source code," because, "even if people are reviewing the code, that doesn't mean they're qualified to do so."[25] An example of this actually happening, accidentally, was the 2008 OpenSSL vulnerability in Debian.
Programming language support[edit]
Programming languages include features to help prevent bugs, such as static type systems, restricted namespaces and modular programming. For example, when a programmer writes (pseudocode) LET REAL_VALUE PI = "THREE AND A BIT", although this may be syntactically correct, the code fails a type check. Compiled languages catch this without having to run the program. Interpreted languages catch such errors at runtime. Some languages deliberate exclude features that easily lead to bugs, at the expense of slower performance: the general principle being that, it is almost always better to write simpler, slower code than inscrutable code that runs slightly faster, especially considering that maintenance cost is substantial. For example, the Java programming language does not support pointer arithmetic; implementations of some languages such as Pascal and scripting languages often have runtime bounds checking of arrays, at least in a debugging build.
Code analysis[edit]
Tools for code analysis help developers by inspecting the program text beyond the compiler's capabilities to spot potential problems. Although in general the problem of finding all programming errors given a specification is not solvable (see halting problem), these tools exploit the fact that human programmers tend to make certain kinds of simple mistakes often when writing software.
Instrumentation[edit]
Tools to monitor the performance of the software as it is running, either specifically to find problems such as bottlenecks or to give assurance as to correct working, may be embedded in the code explicitly (perhaps as simple as a statement saying PRINT "I AM HERE"), or provided as tools. It is often a surprise to find where most of the time is taken by a piece of code, and this removal of assumptions might cause the code to be rewritten.
Testing[edit]
Software testers are people whose primary task is to find bugs, or write code to support testing. On some projects, more resources may be spent on testing than in developing the program.
Measurements during testing can provide an estimate of the number of likely bugs remaining; this becomes more reliable the longer a product is tested and developed.[citation needed]
Debugging[edit]
The typical bug history (GNU Classpath project data). A new bug submitted by the user is unconfirmed. Once it has been reproduced by a developer, it is a confirmed bug. The confirmed bugs are later fixed. Bugs belonging to other categories (unreproducible, will not be fixed, etc.) are usually in the minority
Main article: Debugging
Finding and fixing bugs, or debugging, is a major part of computer programming. Maurice Wilkes, an early computing pioneer, described his realization in the late 1940s that much of the rest of his life would be spent finding mistakes in his own programs.[26]
Usually, the most difficult part of debugging is finding the bug. Once it is found, correcting it is usually relatively easy. Programs known as debuggers help programmers locate bugs by executing code line by line, watching variable values, and other features to observe program behavior. Without a debugger, code may be added so that messages or values may be written to a console or to a window or log file to trace program execution or show values.
However, even with the aid of a debugger, locating bugs is something of an art. It is not uncommon for a bug in one section of a program to cause failures in a completely different section,[citation needed] thus making it especially difficult to track (for example, an error in a graphics rendering routine causing a file I/O routine to fail), in an apparently unrelated part of the system.
Sometimes, a bug is not an isolated flaw, but represents an error of thinking or planning on the part of the programmer. Such logic errors require a section of the program to be overhauled or rewritten. As a part of code review, stepping through the code and imagining or transcribing the execution process may often find errors without ever reproducing the bug as such.
More typically, the first step in locating a bug is to reproduce it reliably. Once the bug is reproducible, the programmer may use a debugger or other tool while reproducing the error to find the point at which the program went astray.
Some bugs are revealed by inputs that may be difficult for the programmer to re-create. One cause of the Therac-25 radiation machine deaths was a bug (specifically, a race condition) that occurred only when the machine operator very rapidly entered a treatment plan; it took days of practice to become able to do this, so the bug did not manifest in testing or when the manufacturer attempted to duplicate it. Other bugs may disappear when the program is run with a debugger; these heisenbugs (humorously named after the Heisenberg uncertainty principle).
Since the 1990s, particularly following the Ariane 5 Flight 501 disaster, interest in automated aids to debugging rose, such as static code analysis by abstract interpretation.[citation needed]
Some classes of bugs have nothing to do with the code. Faulty documentation or hardware may lead to problems in system use, even though the code matches the documentation. In some cases, changes to the code eliminate the problem even though the code then no longer matches the documentation. Embedded systems frequently work around hardware bugs, since to make a new version of a ROM is much cheaper than remanufacturing the hardware, especially if they are commodity items.
Bug management[edit]
Bug management includes the process of documenting, categorizing, assigning, reproducing, correcting and releasing the corrected code. Proposed changes to software – bugs as well as enhancement requests and even entire releases – are commonly tracked and managed using bug tracking systems or issue tracking systems. The items added may be called defects, tickets, issues, or, following the agile development paradigm, stories and epics. Categories may be objective, subjective or a combination, such as version number, area of the software, severity and priority, as well as what type of issue it is, such as a feature request or a bug.
Severity[edit]
Severity is the impact the bug has on system operation. This impact may be data loss, financial, loss of goodwill and wasted effort. Severity levels are not standardized. Impacts differ across industry. A crash in a video game has a totally different impact than a crash in a web browser, or real time monitoring system. For example, bug severity levels might be "crash or hang", "no workaround" (meaning there is no way the customer can accomplish a given task), "has workaround" (meaning the user can still accomplish the task), "visual defect" (for example, a missing image or displaced button or form element), or "documentation error". Some software publishers use more qualified severities such as "critical", "high", "low", "blocker" or "trivial".[27] The severity of a bug may be a separate category to its priority for fixing, and the two may be quantified and managed separately.
Priority[edit]
Priority controls where a bug falls on the list of planned changes. The priority is decided by each software producer. Priorities are sometimes numerical and sometimes named, such as "critical," "high," "low" or "deferred"; note that these may be similar or even identical to severity ratings when looking at different software producers. For example, priority 1 bugs may always be fixed for the next release, while "5" bugs may never be fixed. Industry practice employs an inverted scale, so that highest priority are low numbers (0 and 1), while larger numbers indicate lower priority.
Software releases[edit]
It is common practice to release software with known, low-priority bugs. Most big software projects maintain two lists of "known bugs" – those known to the software team, and those to be told to users.[citation needed] The second list informs users about bugs that are not fixed in a specific release and workarounds may be offered. Releases are of different kinds. Bugs of sufficiently high priority may warrant a special release of part of the code containing only modules with those fixes. These are known as patches. Most releases include a mixture of behavior changes and multiple bug fixes. Releases that emphasize bug fixes are known as maintenance releases. Releases that emphasize feature additions/changes are known as major releases and often have names to distinguish the new features from the old.
Reasons that a software publisher opts not to patch or even fix a particular bug include:
A deadline must be met and resources are insufficient to fix all bugs by the deadline.[28]
The bug is already fixed in an upcoming release, and it is not of high priority.
The changes required to fix the bug are too costly or affect too many other components, requiring a major testing activity.
It may be suspected, or known, that some users are relying on the existing buggy behavior; a proposed fix may introduce a breaking change.
The problem is in an area that will be obsolete with an upcoming release; fixing it is unnecessary.
It's "not a bug". A misunderstanding has arisen between expected and perceived behavior, when such misunderstanding is not due to confusion arising from design flaws, or faulty documentation.
Types[edit]
This section contains embedded lists that may be poorly defined, unverified or indiscriminate. Please help to clean it up to meet Wikipedia's quality standards. Where appropriate, incorporate items into the main body of the article. (August 2015)
This section is in a list format that may be better presented using prose. You can help by converting this section to prose, if appropriate. Editing help is available. (August 2015)
In software development projects, a "mistake" or "fault" may be introduced at any stage. Bugs arise from oversights or misunderstandings made by a software team during specification, design, coding, data entry or documentation. For example, a relatively simple program to alphabetize a list of words, the design might fail to consider what should happen when a word contains a hyphen. Or when converting an abstract design into code, the coder might inadvertently create an off-by-one error and fail to sort the last word in a list. Errors may be as simple as a typing error: a "<" where a ">" was intended.
Another category of bug is called a race condition that may occur when programs have multiple components executing at the same time. If the components interact in a different order than the developer intended, they could interfere with each other and stop the program from completing its tasks. These bugs may be difficult to detect or anticipate, since they may not occur during every execution of a program.
Conceptual errors are a developer's misunderstanding of what the software must do. The resulting may perform according to the developer's understanding, but not what is really needed. Other types:
Arithmetic[edit]
Division by zero.
Arithmetic overflow or underflow.
Loss of arithmetic precision due to rounding or numerically unstable algorithms.
Logic[edit]
Infinite loops and infinite recursion.
Off-by-one error, counting one too many or too few when looping.
Syntax[edit]
Use of the wrong operator, such as performing assignment instead of equality test. For example, in some languages x=5 will set the value of x to 5 while x==5 will check whether x is currently 5 or some other number. Interpreted languages allow such code to fail. Compiled languages can catch such errors before testing begins.
Resource[edit]
Null pointer dereference.
Using an uninitialized variable.
Using an otherwise valid instruction on the wrong data type (see packed decimal/binary coded decimal).
Access violations.
Resource leaks, where a finite system resource (such as memory or file handles) become exhausted by repeated allocation without release.
Buffer overflow, in which a program tries to store data past the end of allocated storage. This may or may not lead to an access violation or storage violation. These are known as security bugs.
Excessive recursion which—though logically valid—causes stack overflow.
Use-after-free error, where a pointer is used after the system has freed the memory it references.
Double free error.
Multi-threading[edit]
Deadlock, where task A can't continue until task B finishes, but at the same time, task B can't continue until task A finishes.
Race condition, where the computer does not perform tasks in the order the programmer intended.
Concurrency errors in critical sections, mutual exclusions and other features of concurrent processing. Time-of-check-to-time-of-use (TOCTOU) is a form of unprotected critical section.
Interfacing[edit]
Incorrect API usage.
Incorrect protocol implementation.
Incorrect hardware handling.
Incorrect assumptions of a particular platform.
Incompatible systems. A new API or communications protocol may seem to work when two systems use different versions, but errors may occur when a function or feature implemented in one version is changed or missing in another. In production systems which must run continually, shutting down the entire system for a major update may not be possible, such as in the telecommunication industry[29] or the internet.[30][31][32] In this case, smaller segments of a large system are upgraded individually, to minimize disruption to a large network. However, some sections could be overlooked and not upgraded, and cause compatibility errors which may be difficult to find and repair.
Teamworking[edit]
Unpropagated updates; e.g. programmer changes "myAdd" but forgets to change "mySubtract", which uses the same algorithm. These errors are mitigated by the Don't Repeat Yourself philosophy.
Comments out of date or incorrect: many programmers assume the comments accurately describe the code.
Differences between documentation and product.
Implications[edit]
The amount and type of damage a software bug may cause naturally affects decision-making, processes and policy regarding software quality. In applications such as manned space travel or automotive safety, since software flaws have the potential to cause human injury or even death, such software will have far more scrutiny and quality control than, for example, an online shopping website. In applications such as banking, where software flaws have the potential to cause serious financial damage to a bank or its customers, quality control is also more important than, say, a photo editing application. NASA's Software Assurance Technology Center managed to reduce the number of errors to fewer than 0.1 per 1000 lines of code (SLOC)[citation needed] but this was not felt to be feasible for projects in the business world.
Well-known bugs[edit]
Main article: List of software bugs
A number of software bugs have become well-known, usually due to their severity: examples include various space and military aircraft crashes. Possibly the most famous bug is the Year 2000 problem, also known as the Y2K bug, in which it was feared that worldwide economic collapse would happen at the start of the year 2000 as a result of computers thinking it was 1900. (In the end, no major problems occurred.)
The 2012 stock trading disruption involved one such incompatibility between the old API and a new API.
In popular culture[edit]
In Robert A. Heinlein's 1966 novel The Moon Is a Harsh Mistress, computer technician Manuel Davis blames a real bug for a (non-existent) failure of supercomputer Mike, presenting a dead fly as evidence.
In the 1968 novel 2001: A Space Odyssey (and its corresponding 1968 film adaptation), a spaceship's onboard computer, HAL 9000, attempts to kill all its crew members. In the follow-up 1982 novel, 2010: Odyssey Two, and the accompanying 1984 film, 2010, it is revealed that this action was caused by the computer having been programmed with two conflicting objectives: to fully disclose all its information, and to keep the true purpose of the flight secret from the crew; this conflict caused HAL to become paranoid and eventually homicidal.
In the 1999 American comedy Office Space, the plot focuses on an attempt by three employees to exploit the company's preoccupation with fixing the Y2K computer bug by infecting the company's computer system with a virus that sends rounded off pennies to a separate bank account. The plan backfires as the virus itself has its own bug which sends large amounts of money to the account prematurely.
In 2000, Joe Trela correctly answered moth for the million dollar question: "What insect shorted out an early supercomputer and inspired the term Computer Bug." in the United States version of the game show Who Wants to be a Millionaire.
The 2004 novel The Bug, by Ellen Ullman, is about a programmer's attempt to find an elusive bug in a database application.[33]
The 2008 Canadian film Control Alt Delete is about a computer programmer at the end of 1999 struggling to fix bugs at his company related to the year 2000 problem.
See also[edit]
Software Testing portal
Anti-pattern
Bug bounty program
Glitch removal
ISO/IEC 9126, which classifies a bug as either a defect or a nonconformity
Orthogonal Defect Classification
Racetrack problem
RISKS Digest
Software defect indicator
Software regression
Software rot
References[edit]
Jump up ^ Prof. Simon Rogerson. "The Chinook Helicopter Disaster". Ccsr.cse.dmu.ac.uk. Retrieved September 24, 2012.
Jump up ^ "Software bugs cost US economy dear". Web.archive.org. June 10, 2009. Archived from the original on June 10, 2009. Retrieved September 24, 2012. CS1 maint: Unfit url (link)
Jump up ^ Edison to Puskas, 13 November 1878, Edison papers, Edison National Laboratory, U.S. National Park Service, West Orange, N.J., cited in Hughes, Thomas Parke (1989). American Genesis: A Century of Invention and Technological Enthusiasm, 1870-1970. Penguin Books. p. 75. ISBN 978-0-14-009741-2.
Jump up ^ Computerworld staff (September 3, 2011). "Moth in the machine: Debugging the origins of 'bug'". Computerworld.
Jump up ^ "Baffle Ball". Internet Pinball Database. (See image of advertisement in reference entry)
Jump up ^ "Modern Aircraft Carriers are Result of 20 Years of Smart Experimentation". Life. June 29, 1942. p. 25. Retrieved November 17, 2011.
Jump up ^ Dickinson Rich, Louise (1942), We Took to the Woods, JB Lippincott Co, p. 93, LCCN 42024308, OCLC 405243.
Jump up ^ FCAT NRT Test, Harcourt, March 18, 2008
Jump up ^ "Danis, Sharron Ann: "Rear Admiral Grace Murray Hopper"". ei.cs.vt.edu. February 16, 1997. Retrieved January 31, 2010.
Jump up ^ "Bug", The Jargon File, ver. 4.4.7. Retrieved June 3, 2010.
^ Jump up to: a b "Log Book With Computer Bug", National Museum of American History, Smithsonian Institution.
Jump up ^ "The First "Computer Bug", Naval Historical Center. But note the Harvard Mark II computer was not complete until the summer of 1947.
Jump up ^ IEEE Annals of the History of Computing, Vol 22 Issue 1, 2000
Jump up ^ James S. Huggins. "First Computer Bug". Jamesshuggins.com. Archived from the original on August 16, 2000. Retrieved September 24, 2012.
Jump up ^ Journal of the Royal Aeronautical Society. 49, 183/2, 1945 "It ranged ... through the stage of type test and flight test and 'debugging' ..."
Jump up ^ Wilson, Andi; Schulman, Ross; Bankston, Kevin; Herr, Trey. "Bugs in the System" (PDF). Open Policy Institute. Retrieved 2016-08-22.
^ Jump up to: a b c d Rozens, Tracy (2016-08-12). "Cyber reforms needed to strengthen software bug discovery and disclosure: New America report – Homeland Preparedness News". Retrieved 2016-08-23.
Jump up ^ "News at SEI 1999 Archive". cmu.edu.
Jump up ^ Shustek, Len (2016-08-02). "In His Own Words: Gary Kildall". Remarkable People. Computer History Museum.
Jump up ^ Kildall, Gary Arlen (2016-08-02) [1993]. Kildall, Scott; Kildall, Kristin, eds. "Computer Connections: People, Places, and Events in the Evolution of the Personal Computer Industry" (Manuscript, part 1). Kildall Family: 14–15. Retrieved 2016-11-17.
^ Jump up to: a b "Testing experience : te : the magazine for professional testers". Testing Experience. Germany: testingexperience: 42. March 2012. ISSN 1866-5705. (subscription required)
Jump up ^ Huizinga, Dorota; Kolawa, Adam (2007). Automated Defect Prevention: Best Practices in Software Management. Wiley-IEEE Computer Society Press. p. 426. ISBN 0-470-04212-5.
Jump up ^ McDonald, Marc; Musson, Robert; Smith, Ross (2007). The Practical Guide to Defect Prevention. Microsoft Press. p. 480. ISBN 0-7356-2253-1. Archived from the original on 2006-12-02.
Jump up ^ "Release Early, Release Often", Eric S. Raymond, The Cathedral and the Bazaar
Jump up ^ "Wide Open Source", Elias Levy, SecurityFocus, April 17, 2000
Jump up ^ Maurice Wilkes Quotes
Jump up ^ "5.3. Anatomy of a Bug". bugzilla.org.
Jump up ^ "The Next Generation 1996 Lexicon A to Z: Slipstream Release". Next Generation. No. 15. Imagine Media. March 1996. p. 41.
Jump up ^ Kimbler, K. (1998). Feature Interactions in Telecommunications and Software Systems V. IOS Press. p. 8. ISBN 978-90-5199-431-5.
Jump up ^ Syed,, Mahbubur Rahman (1 July 2001). Multimedia Networking: Technology, Management and Applications: Technology, Management and Applications. Idea Group Inc (IGI). p. 398. ISBN 978-1-59140-005-9.
Jump up ^ Wu, Chwan-Hwa (John); Irwin, J. David (19 April 2016). Introduction to Computer Networks and Cybersecurity. CRC Press. p. 500. ISBN 978-1-4665-7214-0.
Jump up ^ RFC 1263: "TCP Extensions Considered Harmful" quote: "the time to distribute the new version of the protocol to all hosts can be quite long (forever in fact). ... If there is the slightest incompatibly between old and new versions, chaos can result."
Jump up ^ Ullman, Ellen (2004). The Bug. Picador. ISBN 1-250-00249-4.
Further reading[edit]
Allen, Mitch, May/Jun 2002 "Bug Tracking Basics: A beginner’s guide to reporting and tracking defects" The Software Testing & Quality Engineering Magazine. Vol. 4, Issue 3, pp. 20–24.
External links[edit]
MediaWiki has documentation related to: Bug management
"Common Weakness Enumeration" – an expert webpage focus on bugs, at NIST.gov
BUG type of Jim Gray – another Bug type
Picture of the "first computer bug" at the Wayback Machine (archived January 12, 2015)
"The First Computer Bug!" – an email from 1981 about Adm. Hopper's bug
"Toward Understanding Compiler Bugs in GCC and LLVM". A 2016 study of bugs in compilers
Retrieved from "https://en.wikipedia.org/w/index.php?title=Software_bug&oldid=809243749"
Categories:
Software bugs
Hidden categories:
CS1 maint: Unfit url
Pages containing links to subscription-only content
Pages using RFC magic links
Articles needing additional references from September 2017
All articles needing additional references
Use mdy dates from September 2012
All articles with unsourced statements
Articles with unsourced statements from February 2017
Articles with unsourced statements from November 2012
Articles with unsourced statements from July 2013
Articles needing cleanup from August 2015
All pages needing cleanup
Wikipedia list cleanup from August 2015
Articles with sections that need to be turned into prose from August 2015
Articles with unsourced statements from September 2009
Webarchive template wayback links
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
In other projects
Wikimedia Commons
Languages
العربية
Български
Català
Čeština
Dansk
Deutsch
Ελληνικά
Español
Esperanto
Euskara
فارسی
Français
Frysk
Gaeilge
Galego
한국어
हिन्दी
Hrvatski
Bahasa Indonesia
Italiano
עברית
Lëtzebuergesch
Lumbaart
Magyar
മലയാളം
Bahasa Melayu
Nederlands
日本語
Norsk
Occitan
Polski
Português
Русский
Scots
Shqip
Simple English
Slovenščina
Српски / srpski
Suomi
Svenska
தமிழ்
తెలుగు
ไทย
Türkçe
Українська
吴语
ייִדיש
粵語
中文
Edit links
This page was last edited on 7 November 2017, at 23:17.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

key: html

type: local

value: div

attrs: id class

values: mw-page-base noprint

values: mw-head-base noprint

value: a

attrs: id class lang

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

value: img

attrs: alt src width height srcset data-file-width data-file-height

attrs: href class

value: td

attrs: href title

value: b

values: Help:Introduction to referencing with Wiki Markup/1

value: i

value: small

value: tr

values: plainlinks metadata ambox ambox-content ambox-Refimprove

values:
/wiki/Wikipedia:Bug_reports
mw-redirect
Wikipedia:Bug reports

values:
/wiki/Software_development_methodology
mw-redirect
Software development methodology

values:
/wiki/Model-driven_development
mw-redirect
Model-driven development

values:
/wiki/Continuous_Integration
mw-redirect
Continuous Integration

values:
/wiki/Continuous_Delivery
mw-redirect
Continuous Delivery

values:
/wiki/Pair_Programming
mw-redirect
Pair Programming

values: Template talk:Software development process

values: float:right;clear:right;width:22.0em;margin:0 0 1.0em 1.0em;background:#f9f9f9;border:1px solid #aaa;padding:0.2em;border-spacing:0.4em 0;text-align:center;line-height:1.4em;font-size:88%

values:
/wiki/Freeze_(computing)
mw-redirect
Freeze (computing)

values:
/wiki/Security_bugs
mw-redirect
Security bugs

values:
/wiki/Black_hat_hacking
mw-redirect
Black hat hacking

values:
/wiki/Ariane_5_Flight_501
mw-redirect
Ariane 5 Flight 501

values:
/wiki/CH-47_Chinook
mw-redirect
CH-47 Chinook

values:
/wiki/Department_of_Commerce
mw-redirect
Department of Commerce

values: National Institute of Standards and Technology

attrs: alt src width height class srcset data-file-width data-file-height

values: Naval Surface Warfare Center Dahlgren Division

values: Ada Byron's notes on the analytical engine

values:
/wiki/Analytical_engine
mw-redirect
Analytical engine

values: Edit section: "Bugs in the System" report

values:
/wiki/Program_specification
mw-redirect
Program specification

values: Edit section: Programming language support

values:
/wiki/Type_checking
mw-redirect
Type checking

values:
/wiki/Maintenance_cost
mw-redirect
Maintenance cost

values:
/wiki/Static_code_analysis
mw-redirect
Static code analysis

values:
/wiki/Software_tester
mw-redirect
Software tester

values: This claim needs references to reliable sources. (February 2017)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values: This claim needs references to reliable sources. (November 2012)

values:
/wiki/Commodity_items
mw-redirect
Commodity items

values:
/wiki/Agile_development
mw-redirect
Agile development

values:
/wiki/Version_number
mw-redirect
Version number

values: This claim needs references to reliable sources. (July 2013)

values: Wikipedia:Manual of Style/Embedded lists

values:
plainlinks metadata ambox ambox-style
presentation

values:
/wiki/Wikipedia:Embedded_list
mw-redirect
Wikipedia:Embedded list

values: plainlinks metadata ambox ambox-style ambox-Prose

values:
/wiki/Arithmetic_overflow
mw-redirect
Arithmetic overflow

values:
/wiki/Arithmetic_precision
mw-redirect
Arithmetic precision

values:
/wiki/Packed_decimal
mw-redirect
Packed decimal

values:
/wiki/Binary_coded_decimal
mw-redirect
Binary coded decimal

values:
/wiki/Access_violation
mw-redirect
Access violation

values:
/wiki/Automotive_safety
mw-redirect
Automotive safety

values: This claim needs references to reliable sources. (September 2009)

values:
/wiki/Who_Wants_to_be_a_Millionaire
mw-redirect
Who Wants to be a Millionaire

values:
/wiki/Portal:Software_Testing
mw-redirect
Portal:Software Testing

values: display:table-cell;padding:0.2em 0.2em 0.2em 0.3em;vertical-align:middle

values: margin:0.5em 0 0.5em 1em;border:solid #aaa 1px

values:
nofollow
external text
http://www.ipdb.org/machine.cgi?gid=129

values:
nofollow
external text
//lccn.loc.gov/42024308

values:
nofollow
external text
//www.worldcat.org/oclc/405243

values:
nofollow
external text
http://catb.org/jargon/html/B/bug.html

values:
nofollow
external text
//www.worldcat.org/issn/1866-5705

values: font-size:0.95em; font-size: 90%; color: #555

values:
nofollow
external text
http://www.securityfocus.com/news/19

values:
/wiki/Imagine_Media
mw-redirect
Imagine Media

values:
external mw-magiclink-rfc
nofollow
//tools.ietf.org/html/rfc1263

values:
nofollow
external text
https://nvd.nist.gov/cwe.cfm

values: Category:Pages containing links to subscription-only content

values: Category:Articles needing additional references from September 2017

values: Category:All articles needing additional references

values: Category:Use mdy dates from September 2012

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from February 2017

values: Category:Articles with unsourced statements from November 2012

values: Category:Articles with unsourced statements from July 2013

values: Category:Articles needing cleanup from August 2015

values: Category:Wikipedia list cleanup from August 2015

values: Category:Articles with sections that need to be turned into prose from August 2015

values: Category:Articles with unsourced statements from September 2009

values: Category:Webarchive template wayback links

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/Software_bug
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: Featured content – the best of Wikipedia

values: Find background information on current events

values:
/wiki/Special:Random
Load a random article [ctrl-alt-x]
x

values: portal navigation p-wikibase-otherprojects p-wikibase-otherprojects-label

values:
uls-settings-trigger
Language settings
0
button
true

values: خطأ برمجي – Arabic

values: Програмна грешка – Bulgarian

values: اشکال نرم‌افزاری – Persian

values:
https://fy.wikipedia.org/wiki/Brek
Brek – Western Frisian
fy
fy
interlanguage-link-target

values:
https://gl.wikipedia.org/wiki/Bug
Bug – Galician
gl
gl
interlanguage-link-target

values: 소프트웨어 버그 – Korean

values: सॉफ्टवेयर बग – Hindi

values:
https://id.wikipedia.org/wiki/Kekutu
Kekutu – Indonesian
id
id
interlanguage-link-target

values:
https://it.wikipedia.org/wiki/Bug
Bug – Italian
it
it
interlanguage-link-target

values:
https://lb.wikipedia.org/wiki/Bug
Bug – Luxembourgish
lb
lb
interlanguage-link-target

values:
https://lmo.wikipedia.org/wiki/Bug
Bug – Lombard
lmo
lmo
interlanguage-link-target

values: സോഫ്റ്റ്‌വെയർ ബഗ്ഗ് – Malayalam

values:
https://ms.wikipedia.org/wiki/Pepijat
Pepijat – Malay
ms
ms
interlanguage-link-target

values:
https://pt.wikipedia.org/wiki/Bug
Bug – Portuguese
pt
pt
interlanguage-link-target

values: Программная ошибка – Russian

values:
https://sq.wikipedia.org/wiki/Bug
Bug – Albanian
sq
sq
interlanguage-link-target

values: Баг (информатика) – Serbian

values: மென்பொருள் வழு – Tamil

values: సాఫ్ట్‌వేర్ దోషం – Telugu

values: סאפטוועיר באג – Yiddish

values:
https://zh-yue.wikipedia.org/wiki/Bug
Bug – Cantonese
zh-yue
zh-yue
interlanguage-link-target

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Software_bug rootpage-Software_bug vector-nav-directionality skin-vector action-view


text:
When the Game Stands Tall
From Wikipedia, the free encyclopedia
Jump to: navigation, search
When the Game Stands Tall
Theatrical release poster
Directed by
Thomas Carter
Produced by
David Zelon
Written by
Scott Marshall Smith
Starring
Jim Caviezel
Michael Chiklis
Alexander Ludwig
Laura Dern
Music by
John Paesano
Cinematography
Michael Lohmann
Edited by
Scott Richter
Production
company
Affirm Films
Mandalay Pictures
Distributed by
TriStar Pictures
Release date
August 4, 2014 (2014-08-04) (Hollywood premiere)
August 22, 2014 (2014-08-22)
Running time
115 minutes[1]
Country
United States
Language
English
Budget
$15 million[2]
Box office
$30.1 million[2]
When the Game Stands Tall is a 2014 sports drama film. The film, which stars Jim Caviezel as Coach Bob Ladouceur, Laura Dern as Bev Ladouceur, Michael Chiklis as assistant coach Terry Eidson and Alexander Ludwig as running back Chris Ryan, is about the record-setting 151-game 1992–2003 high school football winning streak by De La Salle High School of Concord, California.[3][4] The film is an adaptation of the 2003 book of the same name by Neil Hayes, published by North Atlantic Books. De La Salle head coach Bob Ladouceur retired in January 2013 after winning his last Open Division state championship in December 2012.[5] Filming began April 22, 2013 and lasted until June 15, 2013.[5] The film was released on August 22, 2014.
Contents
[hide]
1 Plot
2 Cast
3 Production
4 Reception
4.1 Critical
4.2 Box office
4.3 Home media
5 References
6 External links
Plot[edit]
Bob Ladouceur, the coach of the De La Salle Spartans, watches his team win the championship of their undefeated 2003-2004 season. Following tradition, the seniors share their stories about what the team means to them. The juniors, including Ladouceur's son Danny, celebrate with team captain Chris Ryan who has a chance of breaking the California state record for the highest career number of touchdowns. During an argument about whether to accept a coaching offer at the college level, Ladouceur's wife Beverly tells him that he does not spend enough time with his family. A division meeting between coaches arranges to have De La Salle play against Long Beach Polytechnic High School, a team with a similar reputation.
Ladouceur engages the team members in a passage from the Gospel of Luke which states that all good deeds will be rewarded. Rick Salinas, quarterback of the team, shares that he is blessed for doing the right thing because he gets to play on the streak team. Tayshon Lanear thinks otherwise because he doesn't think Salinas is in line to be starting quarterback because he's done the right thing, but because he is six feet and two inches tall and has a cannon for an arm. This provokes a mixed reaction from players who come from disadvantaged households. Reminded of team alumnus Cameron Colvin, Ladouceur pays him a visit in Richmond, California and discovers that his mother is dying. Upon returning home, Ladouceur suffers a heart attack, impacting his ability to coach in the 2004-2005 season. Colvin is approached by his best friend Terrance Kelly, who urges him to enroll at the University of Oregon so that they can play together. Not wanting to involve friends in the downward spiral he has found himself in, Colvin protests but eventually agrees. Days later, Kelly is shot and killed while trying to pick up a cousin and the Spartan team attends his funeral.
De La Salle's 151-game winning streak comes to an end when they lose a game against Bellevue, Washington. After the game, Mickey Ryan hits his son and threatens further abuse if he does not break the touchdown record. Coach Ladouceur takes the team to a veteran's rehabilitation center, to deconstruct their respective ideas of brotherhood. To prepare for the game against Long Beach, the teammates watch videos of previous games and see that all of the Poly players are faster and more physically imposing. The grueling game becomes a victory for De La Salle after Danny knocks down a pass by Poly into the end zone to help the Spartans hold Poly on all 4 downs from inside the 5-yard-line. The Spartans enter the final 2005 game with a renewed sense of confidence and hope that Ryan can make three touchdowns to break the record.
A number of touchdowns during the game, including two by Chris, place De La Salle in a comfortable lead. Mickey cheers that there is enough time left for him to break the record. When setting up their final play, Ryan gathers his teammates and tells them that it would be wrong for him to end his time with the team by chasing a personal victory. He instead gives up the ball and raises his helmet to Ladouceur. As the audience members do the same, the game ends with a tribute to the coach that brought them there.
Cast[edit]
Jim Caviezel as Coach Bob Ladouceur
Michael Chiklis as assistant coach Terry Eidson
Alexander Ludwig as running back Chris Ryan
Laura Dern as Bev Ladouceur
Gavin Casalegno as Michael Ladouceur
Clancy Brown as Mickey Ryan
Ser'Darius Blain as Cam Colvin
Stephan James as Terrance G. "T.K." Kelly
Matthew Daddario as Danny Ladouceur
Joe Massingill as Joe Beaser
Jessie Usher as Tayshon Lanear
Matthew Frias as Arturo Garcia
LaJessie Smith as Jamal
Richard Kohnke as Rick Salinas
Chase Boltin as Manny Gonzales
Adella Gautier as T-Gram
Marlon Favorite as Buster Matthews
Terence Rosemore as Landrin
Deneen Tyler as Veronica
Anna Margaret Collins as Laurie
James DuMont as Gordy Wilock
Ricky Wayne as Marty
Tre Tureaud as T.K's Killer
Mike Bleed as Cam's Cousin
Billy Slaughter as Hip Sports Reporter
Production[edit]
Thomas Carter, who previously worked on Coach Carter, served as director.[3] The screen adaptation was by Scott Marshall Smith.[6] The film was produced by Mandalay Pictures and distributed through TriStar Pictures,[7] a division of Sony Pictures Worldwide Acquisitions (SPWA).[3] David Zelon produced for Mandalay Peter Nelson and Rich Peluso worked on behalf of SPWA and its distribution arm AFFIRM.[3] Allan Graf, who previously worked on Friday Night Lights, "[coordinated] the football scenes".[4] Hayes, a Contra Costa Times journalist at the time the book was released, was part of the creative team.[5] Zelon said the intrigue of this film was that Ladouceur "placed little value on winning, instead focusing his players on giving a 'perfect effort' in life".[4] SPWA president Steve Bersch noted that the themes in the film transcended sports and cinema: "At its core, this is a timeless and universal story about character, hard work and love".[4]
Reception[edit]
Critical[edit]
When the Game Stands Tall has received mostly negative reviews from critics, but mostly positive reviews from viewers. On Rotten Tomatoes, the film has a critics rating of 17%, based on 63 reviews, but an audience score of 72% based on over 21,000 viewers. The site's critical consensus reads, "An uneasy blend of solid game sequences and threadbare inspirational sports drama clichés, When the Game Stands Tall is overshadowed by better players in a crowded field."[8] On Metacritic, the film holds a score of 41 out of 100, based on 24 critics, indicating "mixed or average reviews".[9]
Box office[edit]
In its opening weekend the film grossed $8,381,509 in 2,673 theaters, ranking at #5. By the end of its run, When the Game Stands Tall grossed $30,127,963 domestically.[2]
Home media[edit]
When the Game Stands Tall was released on Blu-ray and DVD on December 9, 2014.[citation needed]
References[edit]
Jump up ^ "When The Game Stands Tall". AMC Theatres. August 10, 2014. Retrieved August 10, 2014.
^ Jump up to: a b c "When the Game Stands Tall (2014) - Box Office Mojo". August 22, 2014. Retrieved October 27, 2014.
^ Jump up to: a b c d Siegel, Tatiana (April 22, 2013). "Jim Caviezel, Laura Dern, Michael Chiklis to Star in 'When the Game Stands Tall'". The Hollywood Reporter. Retrieved April 23, 2013.
^ Jump up to: a b c d Sneider, Jeff (April 22, 2013). "James Caviezel, Michael Chiklis to Coach Football in 'When the Game Stands Tall'". The Wrap. Retrieved April 23, 2013.
^ Jump up to: a b c Hammon, Stephanie (April 17, 2013). "Filming of 'When the Game Stands Tall' on De La Salle football team to begin Monday". Mercury News. Retrieved April 23, 2013.
Jump up ^ Scott, Mike (April 22, 2013). "Football drama 'When the Game Stands Tall' begins production April 22 in New Orleans". The Times-Picayune. NOLA.com. Retrieved April 23, 2013.
Jump up ^ "When the Game Stands Tall". Box Office Mojo. Retrieved August 18, 2013.
Jump up ^ "When The Game Stands Tall". August 22, 2014. Retrieved October 2, 2014.
Jump up ^ "When the Game Stands Tall Reviews - Metacritic". Retrieved October 2, 2014.
External links[edit]
Official website
When the Game Stands Tall on IMDb
When the Game Stands Tall at Rotten Tomatoes
When the Game Stands Tall at AllMovie
When the Game Stands Tall at Metacritic
When the Game Stands Tall at Box Office Mojo
Special Movie Edition of the Book
De La Salle coach weighs in on “When the Game Stands Tall”
Article about the movie and Coach Ladouceur in The Catholic Voice, the newspaper of the Diocese of Oakland
[hide]
v
t
e
Films directed by Thomas Carter
Swing Kids (1993)
Metro (1997)
Save the Last Dance (2001)
Coach Carter (2005)
Gifted Hands: The Ben Carson Story (2009)
When the Game Stands Tall (2014)
Retrieved from "https://en.wikipedia.org/w/index.php?title=When_the_Game_Stands_Tall&oldid=826803007"
Categories:
2014 films
English-language films
2010s drama films
2010s sports films
American drama films
Affirm Films films
American films
American football films
Films about religion
Films set in the San Francisco Bay Area
Films shot in New Orleans
High school football films
Mandalay Pictures films
Sports films based on actual events
TriStar Pictures films
2010s high school films
Hidden categories:
Use mdy dates from August 2016
All articles with unsourced statements
Articles with unsourced statements from May 2015
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Article
Talk
Variants
Views
Read
Edit
View history
More
Search
Navigation
Main page
Contents
Featured content
Current events
Random article
Donate to Wikipedia
Wikipedia store
Interaction
Help
About Wikipedia
Community portal
Recent changes
Contact page
Tools
What links here
Related changes
Upload file
Special pages
Permanent link
Page information
Wikidata item
Cite this page
Print/export
Create a book
Download as PDF
Printable version
Languages
Español
Bahasa Indonesia
Italiano
Русский
Edit links
This page was last edited on 21 February 2018, at 02:26.
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization.
Privacy policy
About Wikipedia
Disclaimers
Contact Wikipedia
Developers
Cookie statement
Mobile view
Enable previews

values: mw-page-base noprint

values: mw-head-base noprint

values: firstHeading firstHeading en

values: siteSub noprint

values: jump-to-nav mw-jump

value: th

attrs: colspan class style

attrs: colspan style

attrs: scope style

values: De La Salle High School (Concord, California)

values:
/wiki/Terrance_Kelly
mw-redirect
Terrance Kelly

values:
/wiki/Anna_Margaret_Collins
mw-redirect
Anna Margaret Collins

values: This claim needs references to reliable sources. (May 2015)

values:
noprint Inline-Template Template-Fact
white-space:nowrap;

values:
/wiki/Mercury_News
mw-redirect
Mercury News

values: -moz-column-width: 30em; -webkit-column-width: 30em; column-width: 30em; list-style-type: decimal;

values:
nofollow
http://www.whenthegamestandstall.com/
external text

values:
nofollow
https://www.imdb.com/title/tt2247476/
external text

values:
nofollow
external text
https://www.allmovie.com/movie/v581597

values:
/wiki/Swing_Kids_(film)
mw-redirect
Swing Kids (film)

values: nowraplinks collapsible autocollapse navbox-inner

values: Category:Films set in the San Francisco Bay Area

values: Category:Sports films based on actual events

values: Category:All articles with unsourced statements

values: Category:Articles with unsourced statements from May 2015

values: Discussion about edits from this IP address [ctrl-alt-n]

values: A list of edits made from this IP address [ctrl-alt-y]

values: You are encouraged to create an account and log in; however, it is not mandatory

values: You're encouraged to log in; however, it's not mandatory. [ctrl-alt-o]

values:
/wiki/When_the_Game_Stands_Tall
View the content page [ctrl-alt-c]
c

values: Discussion about the content page [ctrl-alt-t]

values: p-namespaces navigation vectorTabs p-namespaces-label

values:
p-variants
navigation
vectorMenu emptyPortlet
p-variants-label

values: Past revisions of this page [ctrl-alt-h]

values: p-views navigation vectorTabs p-views-label

values:
p-cactions
navigation
vectorMenu emptyPortlet
p-cactions-label

values:
mw-wiki-logo
/wiki/Main_Page
Visit the main page

values:
/wiki/Main_Page
Visit the main page [ctrl-alt-z]
z

values: portal navigation p-navigation p-navigation-label

values: Guidance on how to use and edit Wikipedia

values: About the project, what you can do, where to find things

values: A list of recent changes in the wiki [ctrl-alt-r]

values: portal navigation p-interaction p-interaction-label

values: List of all English Wikipedia pages containing links to this page [ctrl-alt-j]

values: Recent changes in pages linked from this page [ctrl-alt-k]

values:
/wiki/Wikipedia:File_Upload_Wizard
Upload files [ctrl-alt-u]
u

values: A list of all special pages [ctrl-alt-q]

values: Permanent link to this revision of the page

values: Link to connected data repository item [ctrl-alt-g]

values: Printable version of this page [ctrl-alt-p]

values: Игра на высоте – Russian

values: /static/images/wikimedia-button-1.5x.png 1.5x, /static/images/wikimedia-button-2x.png 2x

values: /static/images/poweredby_mediawiki_132x47.png 1.5x, /static/images/poweredby_mediawiki_176x62.png 2x

values:
suggestions
display: none; font-size: 13px;

values: mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-When_the_Game_Stands_Tall rootpage-When_the_Game_Stands_Tall skin-vector action-view