Docsity
Docsity

Prepare-se para as provas
Prepare-se para as provas

Estude fácil! Tem muito documento disponível na Docsity


Ganhe pontos para baixar
Ganhe pontos para baixar

Ganhe pontos ajudando outros esrudantes ou compre um plano Premium


Guias e Dicas
Guias e Dicas


O Linux é um software melhor que o Windows (is Linux Better than Windows software?), Notas de estudo de Engenharia Elétrica

is Linux Better than Windows software?

Tipologia: Notas de estudo

Antes de 2010

Compartilhado em 02/02/2010

vanilson-gomes-3
vanilson-gomes-3 🇧🇷

4 documentos

1 / 2

Toggle sidebar

Esta página não é visível na pré-visualização

Não perca as partes importantes!

bg1
loyal opposition
104 IEE E Softwar E Published by th e IEEE Computer Soc iety 0740-7459/0 9/$25. 00 © 2009 IE EE
Editor: Robert L . Glass n Computing Trends n [email protected]
In the last decade, the open source movement
has been a vital source of innovation affect-
ing soft ware development.
1
However, open
source community practices have provoked a
debate on software quality—namely, is open
sou rce sof twar e’s qual ity b etter than that of its
closed-source counterpart? Studies have attempted
to correlate metrics with software performance or
validate that metrics can actually predict software
systems’ fault proneness.
2
For open source soft-
ware, a strand of research has emerged on quanti-
fying software quality through code reading and
judging of open source codes.
3
Here, I attempt an
evidence-based or experimental software research
approach
4
to answer the question.
What is open source software?
Whereas you can define closed-source software
as a product created using traditional software
development methods, the definition of open
source software isn’t always straightforward.
This is because a software product can take at
least three paths to become open source. For ex-
ample, a collaborating open source community
developed the Linux kernel, an individual cre-
ated PGP (Pretty Good Privacy), and the Mozilla
browser was originally developed as proprietar y
software. One implication of this is that any con-
clusions about Linux might not hold true for all
open source products.
What Do We Know
from existing studies?
I evaluated studies focusing on performance and
quality rather than total cost of ownership. Mind-
craft conducted one such study, with participation
from RedHat and Microsoft engineers.
5
The engi-
neers tuned the tested systems to ensure maximum
performance. They performed tests on one- and
four-processor configu rations of Dell servers in-
stalled with Windows NT Server 4.0 and the Red
Hat Linux 6.0 kernel. The results showed that Win-
dows NT Server had faster t hroughput than Linux
on both configurations.
In 1999, Bloor Research experimentally com-
pared the maturity of Windows NT to that of
GNU/ Linux for one year.
6
The Windows NT sys-
tem suffered 68 failures, of which 26 were memory
related and eight were file system faults. The Linux
system experienced only one software-related fail-
ure. Bloor rated the Linux servers as good as or bet-
ter tha n the Windows servers in five of the s even ar-
eas monitored. The study has an obvious limitation.
Namely, it’s unclear whether 25 of the 26 memory
failures were due to the Windows OS or to the poor
quality of the intervention to repair the first error.
Ioannis Samoladas and his colleagues found
that the code quality of successive versions of open
source software was equa l to or better than that of
closed-source products.
7
Security Innovation pit-
ted a Windows 2000 system against a SuSE Linux
Enterprise Server 8 for one year. The company con-
cluded that Windows Server environments seem to
man ifest low er risk of inst abilit y when subjected to
modifications.
8
Diomidis Spinellis used CScout, a
source code analyzer, to investigate the code qual-
ity of four operating systems: FreeBSD 6.1, Open
Solaris, Linux 2.6.18, and major por tions of the
Windows Research Kernel.
9
He investigated met-
rics for file organization, code structure, code style,
preprocessing, and data organization. He found
that the open source products’ code quality wasn’t
markedly higher than that of the closed-source
products.
A Vulnerability study
You can define vulnerability as the lack of adequate
security. Security is software’s abilit y to prevent
Adenekan (Nick) Dedeke
The evidence is not that clear- cut.
is Linux Better than
Windows software?
Continued on p. 103
Authorized licensed use limited to: UNIVERSIDADE FEDERAL DO PARA. Downloaded on April 21, 2009 at 12:45 from IEEE Xplore. Restrictions apply.
pf2

Pré-visualização parcial do texto

Baixe O Linux é um software melhor que o Windows (is Linux Better than Windows software?) e outras Notas de estudo em PDF para Engenharia Elétrica, somente na Docsity!

loyal opposition

104 I E E E S o f t w a r E P u b l i s h e d b y t h e I E E E C o m p u t e r S o c i e t y 0 7 4 0 - 7 4 5 9 / 0 9 / $ 2 5. 0 0 © 2 0 0 9 I E E E

E d i t o r : R o b e r t L. G l a s s n C o m p u t i n g T r e n d s n r l g l a s s @ a c m. o r g

I

n the last decade, the open source movement has been a vital source of innovation affect- ing software development.^1 However, open source community practices have provoked a debate on software quality—namely, is open source software’s quality better than that of its closed-source counterpart? Studies have attempted to correlate metrics with software performance or validate that metrics can actually predict software systems’ fault proneness.^2 For open source soft- ware, a strand of research has emerged on quanti- fying software quality through code reading and judging of open source codes. 3 Here, I attempt an evidence-based or experimental software research approach^4 to answer the question.

What is open source software?

Whereas you can define closed-source software as a product created using traditional software development methods, the definition of open source software isn’t always straightforward. This is because a software product can take at least three paths to become open source. For ex- ample, a collaborating open source community developed the Linux kernel, an individual cre- ated PGP (Pretty Good Privacy), and the Mozilla browser was originally developed as proprietary software. One implication of this is that any con- clusions about Linux might not hold true for all open source products.

What Do We Know

from existing studies?

I evaluated studies focusing on performance and quality rather than total cost of ownership. Mind- craft conducted one such study, with participation from RedHat and Microsoft engineers.^5 The engi- neers tuned the tested systems to ensure maximum performance. They performed tests on one- and four-processor configurations of Dell servers in-

stalled with Windows NT Server 4.0 and the Red Hat Linux 6.0 kernel. The results showed that Win- dows NT Server had faster throughput than Linux on both configurations. In 1999, Bloor Research experimentally com- pared the maturity of Windows NT to that of GNU/Linux for one year.^6 The Windows NT sys- tem suffered 68 failures, of which 26 were memory related and eight were file system faults. The Linux system experienced only one software-related fail- ure. Bloor rated the Linux servers as good as or bet- ter than the Windows servers in five of the seven ar- eas monitored. The study has an obvious limitation. Namely, it’s unclear whether 25 of the 26 memory failures were due to the Windows OS or to the poor quality of the intervention to repair the first error. Ioannis Samoladas and his colleagues found that the code quality of successive versions of open source software was equal to or better than that of closed-source products.^7 Security Innovation pit- ted a Windows 2000 system against a SuSE Linux Enterprise Server 8 for one year. The company con- cluded that Windows Server environments seem to manifest lower risk of instability when subjected to modifications. 8 Diomidis Spinellis used CScout, a source code analyzer, to investigate the code qual- ity of four operating systems: FreeBSD 6.1, Open Solaris, Linux 2.6.18, and major portions of the Windows Research Kernel.^9 He investigated met- rics for file organization, code structure, code style, preprocessing, and data organization. He found that the open source products’ code quality wasn’t markedly higher than that of the closed-source products.

A Vulnerability study

You can define vulnerability as the lack of adequate security. Security is software’s ability to prevent

Adenekan (Nick) Dedeke

The evidence is not that clear-cut.

is Linux Better than

Windows software?

Continued on p. 103

Authorized licensed use limited to: UNIVERSIDADE FEDERAL DO PARA. Downloaded on April 21, 2009 at 12:45 from IEEE Xplore. Restrictions apply.

May/June 2009 I E E E S o f t w a r E 103

unauthorized access, whether accidental or deliberate, to programs and data. To investigate vulnerability, I analyzed data from the US National Vulnerability Data- base (http://nvd.nist.gov/nvd.cfm), which is hosted by the National Cyber Security division of the US Computer Emergency Readiness Team (US-CERT). The database integrates all publicly available US govern- ment vulnerability databases. It lists each vulnerability type once. For example, if CERT is notified 300 times of a potentially damaging type of computer vulnerability, it lists that vulnerability only once in the database. I aggregated the known vulnerability types for RedHat Linux and Windows sys- tems reported during 1997–2005. The study included 1,048 vulnerability types for Red- Hat Linux and 552 for Windows 2000 and Windows 2003. The types fall into three categories: high, moderate, and low severity. I based each type’s scoring on the Common Vulnerability Scoring System (CVSS),^10 a global standard. Between 2002 and 2005, the total number of vulnerabilities for Li- nux rose dramatically from 67 to 333, while that of Windows rose from 69 to 86. I also found that for high severity, Linux experi- enced a rise from 31 to 126 while Windows experienced a rise from 38 to 53. I found similar results for low and medium severity.

T

herefore, unless someone can show that Windows systems’ vulnerabilities are underreported, my study doesn’t sup- port the assertion that open source soft-

ware, represented by Linux, is less vul- nerable than Windows systems. It also casts doubt on the global assertion that Linux’s quality is better than that of Win- dows. Could these results hold true for other categories of open source and closed- source software?

References

  1. R. Glass, “A Look at the Economics of Open Source,” Comm. ACM , vol. 47, no. 2, 2004, pp. 25–27.
  2. G. Gousios et al., “Software Quality Assess- ment of Open Source Software,” Current Trends in Informatics: 11th Panhellenic Conf. Informatics (PCI 07), vol. A, New Technolo- gies Publications, 2007, pp. 303–315.
  3. D. Spinellis, Code Quality: The Open Source Perspective , Addison-Wesley, 2006.
  4. F. Shull, “Who Needs Evidence Anyway? IEEE Software , Sept.–Oct. 2007, pp. 10–11.
  5. B. Weiner, Open Benchmark: Windows NT Server 4.0 and Linux , Mindcraft, 1999; www. mindcraft.com/whitepapers/openbench1.html.
  6. Linux versus Windows NT: The Verdict , Bloor Research, 1999; www.bloor-research. com/research/white-paper/188/linux-v- windows-nt-the-verdict.html.
  7. I. Samoladas et al., “Open Source Software Development Should Strive for Even Greater Code Maintainability,” Comm. ACM , vol. 47, no. 10, 2004, pp. 83–87.
  8. H. Thompson, Reliability: Analyzing Solution Uptime as Business Needs Change , Security Innovation, 2005.
  9. D. Spinellis, “A Tale of Four Kernels,” Proc. 30th Int’l Conf. Software Eng. (ICSE 08), ACM Press, 2008, pp. 381–390.
  10. P. Mell, K. Scarfone, and S. Romanosky, A Complete Guide to Common Vulnerability Scoring System Version 2.0 , Forum of Incident Response and Security Teams, 2007; www. first.org/cvss/cvssguide.html.

Adenekan (Nick) Dedeke is a visiting lecturer of information systems and operations management in Northeastern University’s College of Business Administration. Contact him at [email protected].

LoyAL oppositioN

Continued from p. 104

IEEE Software (ISSN 0740-7459) is published bimonthly by the IEEE Computer Society. IEEE headquarters: Three Park Ave., 17th Floor, New York, NY 10016-5997. IEEE Computer Society Publications Office: 10662 Los Vaqueros Cir., PO Box 3014, Los Alamitos, CA 90720-1314; +1 714 821 8380; fax +1 714 821 4010. IEEE Computer Society headquarters: 2001 L St., Ste. 700, Washington, DC 20036. Subscription rates: IEEE Computer Society members get the lowest rate of US$51 per year, which includes printed issues plus online access to all issues published since 1988. Go to www.computer.org/subscribe to order and for more information on other subscription prices. Back issues: $ for members, $163 for nonmembers (plus shipping and handling). Postmaster: Send undelivered copies and address changes to IEEE Software , Membership Processing Dept., IEEE Service Center, 445 Hoes Lane, Piscataway, NJ 08854-4141. Periodicals Postage Paid at New York, NY, and at ad- ditional mailing offices. Canadian GST #125634188. Canada Post Publications Mail Agreement Number 40013885. Return undeliverable Canadian addresses to PO Box 122, Niagara Falls, ON L2E 6S8, Canada. Printed in the USA. Reuse Rights and Reprint Permissions: Educational or personal use of this material is permitted without fee, provided such use: 1) is not made for profit; 2) includes this notice and a full citation to the original work on the first page of the copy; and 3) does not imply IEEE endorsement of any third-party products or services. Authors and their companies are permitted to post their IEEE-copyrighted material on their own Web servers without permission, provided that the IEEE copyright notice and a full citation to the original work appear on the first screen of the posted copy. Permission to reprint/republish this material for commercial, advertising, or promotional purposes or for creating new collective works for resale or redistribution must be obtained from IEEE by writing to the IEEE Intellectual Property Rights Office, 445 Hoes Lane, Piscataway, NJ 08854-4141 or [email protected]. Copyright © 2009 IEEE. All rights reserved. Abstracting and Library Use: Abstracting is permitted with credit to the source. Libraries are permitted to photo- copy for private use of patrons, provided the per-copy fee indicated in the code at the bottom of the first page is paid through the Copyright Clearance Center, 222 Rosewood Drive, Danvers, MA 01923.

Voice of eViDeNce

building on experience other fields have with managing knowledge between cross- functional teams.

W

e’ve seen many claims about KM’s benefits in software engineering, such as decreased time and cost for development, increased quality, and better decision-making abilities. Although we can find some success stories illustrating these claims, particularly on aspects related to the systems and engineering schools, more research is necessary to explore the inter- section between each school and the soft- ware engineering field. Researchers should continue to emphasize the need for a broad focus across multiple KM schools to suc- ceed in improving KM’s practical applica- tion in software engineering.

References

  1. T.H. Davenport and L. Prusak, Working Knowledge: How Organizations Manage What They Know , Harvard Business School Press, 1998.
  2. A. Aurum et al., Managing Software Engi- neering Knowledge , Springer, 2003.
  3. V.R. Basili, G. Caldiera, and H.D. Rombach, “The Experience Factory,” Encyclopedia of Software Engineering , vol. 1, J.J. Marciniak, ed., John Wiley & Sons, 1994, pp. 469–476.
  4. I. Rus and M. Lindvall, “Knowledge Man- agement in Software Engineering,” IEEE Software , vol. 19, no. 3, 2002, pp. 26–38.
  5. M. Earl, “Knowledge Management Strate- gies: Toward a Taxonomy,” J. Management Information Systems , vol. 18, no. 1, 2001, pp. 215–233.
  6. F.O. Bjørnson and T. Dingsøyr, “Knowledge Management in Software Engineering: A Systematic Review of Studied Concepts and Research Methods Used,” Information and Software Technology , vol. 50, no. 11, 2008, pp. 1055–1168.
  7. S. Nerur and V. Balijepally, “Theoretical Re- flections on Agile Development Methodolo- gies,” Comm. ACM , vol. 50, no. 3, 2007, pp. 79–83.

torgeir Dingsøyr is a senior scientist at SINTEF Information and Communication Technology and an adjunct associate professor in the Department of Computer and Information Science, Norwegian University of Science and Technology. Contact him at [email protected].

finn olav Bjørnson is a research scientist at SINTEF Fisheries and Aquaculture. Contact him at finn.o.bjornson@ sintef.no. forrest shull is a senior scientist at the Fraunhofer Center for Experimental Software Engineering, Maryland, and director of its Measurement and Knowledge Management Division. Contact him at [email protected].

Authorized licensed use limited to: UNIVERSIDADE FEDERAL DO PARA. Downloaded on April 21, 2009 at 12:45 from IEEE Xplore. Restrictions apply.