Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Pareto principle
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== Computing === In [[computer science]] the Pareto principle can be applied to [[optimization (computer science)|optimization]] efforts.<ref name=optimization>{{citation|first1=M.|last1=Gen|first2=R.|last2=Cheng|title=Genetic Algorithms and Engineering Optimization|location=New York|publisher=Wiley|year=2002}}</ref> For example, [[Microsoft]] noted that by fixing the top 20% of the most-reported bugs, 80% of the related errors and crashes in a given system would be eliminated.<ref>{{citation|url=http://www.crn.com/news/security/18821726/microsofts-ceo-80-20-rule-applies-to-bugs-not-just-features.htm|title=Microsoft's CEO: 80β20 Rule Applies To Bugs, Not Just Features|first=Paula|last=Rooney|date=October 3, 2002|publisher=ChannelWeb}}</ref> Lowell Arthur expressed that "20% of the code has 80% of the errors. Find them, fix them!"<ref>Pressman, Roger S. (2010). Software Engineering: A Practitioner's Approach (7th ed.). Boston, Mass: McGraw-Hill, 2010. {{ISBN|978-0-07-337597-7}}.</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)