| Papers [1-16] of 100 :: [Page 1 of 7] | | Go to page : 1 2 3 4 5 6 7 —> | Search results on "OPEN SOURCE SOFTWARE": |
|
|
The Use of Open Source Software, 2006.
A research paper on the legal implications for European Union governments concerning the use of open source software in government and public service.
11,532 words (approx. 46.1 pages), 15 sources, APA, AU$ 243.95
»
Click here to show/hide summary
Abstract
This research paper focuses on European Union (EU) government policy relating to market economies of open source software. The paper discusses the official position and current EU policies regarding open source software, examines a legal case study concerning open source software vs. proprietary software and looks at Brazil's policy regarding this subject. Additionally, the paper looks into EU intellectual property law and a new proposed software patent directive and how each will affect open source legality in the EU.
Table of Contents
Current EU Software Policy: Any Directives,
Regulations, White-papers and Official Documents
Detailing the Current Official Position of the European
Union on Software
Free and Open Source Software versus Proprietary
Software Legal Case Study -
How will E.U. Governments be Affected if They Follow
the Brazilian Example, and its Effect on E.U.
Intellectual Property Policy?
How will E.U. Intellectual Property Law and New
Proposed Software Patent Directive Affect Open
Source Legality in the EU?
Legal Cases that Set Precedents for Intellectual
Property Concern in Open Source Software Use
Conclusion and Summary
From the Paper
"The "Television without Frontiers Directive" focuses on the creation of necessary conditions to allowing television broadcasts free movement all across the EU region. Secondly "Communication" of 2004 clarifies the method by the Directive is applied in relation to the interactive techniques of advertising that are yet new." (Information Society and Media, 2005) Other issues are yet under review and are stated to have the capacity to result in amendments of the TVWF Directive or the new directives proposal by 2005 years end. Other EU policy framework is inclusive of regulations that "promote competition between infrastructure providers and service providers while ensuring access for user of networks and citizen's rights; measures on copyright and digital rights management; access to and use of public information, as specified under the Public Sector Information Directive; and eInclusion, ensuring that all Europeans can access the new generation of digital content and services." (Information Society and Media, 2005)"
| |
|
Open Source Software, 2002.
Examines what factors contribute to governments choosing open source software or proprietary software.
3,388 words (approx. 13.6 pages), 23 sources, MLA, AU$ 104.95
»
Click here to show/hide summary
Abstract
Open source software has recently emerged as the front runner for many industries as the primary method of code production, as it is widely predicted to provide more options for its users in a quicker, quality improved and cost effective format than the more traditional proprietary software. Linux, the dominant player in the market, is a considerable threat to the Microsoft operating system, which has successfully established itself in the global market. Beyond its commercial potential, open source software possesses a potential goldmine in the government sector. However, questions regarding security and privacy continue to plague government officials in their pursuits of this option. This paper provides an overview of open source software as well as proprietary software and their primary components. It provides an evaluation of government options in relation to the products available on the market and discusses the social construction of open source software versus the technological determinism of proprietary software. The paper includes colored graphs.
From the Paper
"The Linux operating system is the chief product that many new open source customers consider as their primary choice. Many IT experts find that Linux is more powerful when enthusiasm is brought into the picture (Zetlin 38). Therefore, learning the ins and outs of the system can take some time and may require some work beyond normal business hours. For this reason, training in Linux and other similar open source offerings should be a primary concern for IT professionals in order to improve its potential and to reduce the possibility of security flaws."
| |
|
Open and Closed Source Software, 2005.
An analysis of the pros and cons of open and closed source software.
3,109 words (approx. 12.4 pages), 21 sources, APA, AU$ 97.95
»
Click here to show/hide summary
Abstract
This paper discusses the respective benefits of open and closed source software from a cost-effectiveness perspective for the RMIT University. The paper describes the background of the problem, a brief overview of open and closed source applications, and presents a discussion of their advantages and disadvantages. An analysis of the findings is followed by a summary of the research and recommendations for the university in the conclusion.
Introduction
Background and Overview
Open Source Applications
Closed Source Applications
Analysis
Conclusions and Recommendations
From the Paper
"Open source software can be purchased for little or no cost, and future upgrades are also obtainable free of charge (Wayner, 2000; Lopez, 2004). Rechtman points out that open-source applications such as Gnumeric, an Excel-like spreadsheet, or Ximian, a desktop organizer that combines features of Palm OS and Microsoft Outlook, cost virtually nothing to install. "In fact," he says, "they are freely available for download from the Internet" (p. 67). According to Kim, educators in particular stand to gain from open source alternatives. "More importantly," she adds, "they may also find a new and improved way to teach" (emphasis added) (p. 15). This was also the finding of Cowpland who reports that a partnership between Corel and three academic institutions in the Ottawa area resulted in the development of pilot programs using Corel LINUX OS and WordPerfect 8 for Linux: "While the project is just finishing its first year, administrators have noticed an increase in the desire of their students to continue pursuing computer technology in upper years. They anticipate rolling out the program on a potentially wider scale for next year" (p. 62)."
| |
|
Open Source Software (OSS), 2002.
This paper describes the philosophy behind Open Source Software (OSS).
1,115 words (approx. 4.5 pages), 4 sources, AU$ 41.95
»
Click here to show/hide summary
Abstract
This paper explains what open software is, why it was organized, what its benefits are and how it can be used. Case studies are included.
From the Paper
"Open source is not a technology, rather a different way of thinking about and organizing the software development process. Open source software (OSS) development is more of a collaborative process that has benefited with the expansion of the Internet. Anyone with an Internet connection can now download source code available in the public domain, modify it and post the results back to the community. As opposed to this proprietary software development adheres to the principle of strict protection of intellectual property found in the publishing industry."
| |
|
Free Software and Open Source Software, 2006.
This paper discusses the differences between the terms 'free Software' and 'open source software'.
675 words (approx. 2.7 pages), 3 sources, AU$ 28.95
»
Click here to show/hide summary
Abstract
This paper discusses free software and open source software, noting that free software actually refers to software providing specific kinds of freedom to users, while "open source software" means that the user is made privy to the code so he or she can change the software as well as use it. The writer maintains that much of the argument dates to 1984 and the publication of the "Gnu Manifesto," written by Richard Stallman.
From the Paper
"Software developers differ on the relative value of the terms "free software" or "open source software." The terms are not completely identical. Free software could be any software for which no charge is made, though it actually refers to software providing specific kinds of freedom to users, while "open source software" means that the user is made privy to the code so he or she can change the software as well as use it. By either name, the associated vision of software and users challenges the usual idea of copyright and intellectual property."
| |
|
Open Source, 2003.
Written in the form of an organizational briefing, this paper looks at the benefits and drawbacks of open-source software and its effects on Sigma Corporation.
2,687 words (approx. 10.7 pages), 8 sources, MLA, AU$ 86.95
»
Click here to show/hide summary
Abstract
This briefing evaluates the pros and cons of open-source software and provides a recommendation to management at the Sigma Corporation regarding open-source strategies. While Sigma has developed a sound information technology (IT) infrastructure and employs a highly skilled IT staff, increasing IT costs have caused the company to examine ways to reduce IT expenses without affecting the effectiveness of the IT program. It defines open-source whereby the product is distributed with the source code. There are risks associated with open-source. The process is not quite mature, so users assume some risk in using these products. Open-source comes with no warranties and no maintenance agreements. A more detailed summary of the pros and cons of open-source is found in this briefing. The paper concludes that open-source is a viable and wise option for Sigma and outlines a strategy for moving the company in that direction.
From the Paper
"The Sigma Corporation has been in the office supply business for over fifty years and has built a reputation of prompt service with low prices. The reputation for prompt service has been attributed to the company's computerized inventory system that automatically orders new materials from the manufacturer at specified intervals. The low prices are maintained by keeping company costs to a minimum while getting the job done. The CEO of Sigma, Sigmund Saveabuck, is always looking for ways to save costs in order to maintain a competitive advantage."
| |
|
Open Source and Open Standards in Ecommerce, 2007.
An in-depth look at the use of open source solutions and standards in the world of e-commerce.
4,190 words (approx. 16.8 pages), 11 sources, MLA, AU$ 120.95
»
Click here to show/hide summary
Abstract
This paper reviews, evaluates and discusses the emergence and use of open source solutions and standards. The paper reviews the importance, benefits and pitfalls of open source solutions and critically evaluates the future. The paper is written in a two-column format.
Outline:
Abstract
Introduction
The Wonder Years
The Market For OSS
The Public and Private Sectors
Open-Source-A-Me, The Enterprise Structure
Why Open Source Me? Pros, Cons and The Future
Benefits
The Future
From the Paper
"MySQL is the overall leader in Open Source databases with over 5 million active installations across the globe and is by the one of the most successful Open Source solutions."
"It is one of the few Open Source software solutions that are available under the dual-license model as it is available both for under GPL and commercial license. MaxDB, which has it's origins as a commercial DB software solution was developed as a result of an alliance between MySQL and SAP to form a market leading enterprise solution, which is capable of running high-end mission-critical applications."
| |
|
Software Configuration Management, 2006.
An analysis of the evolution of software configuration management (SCM) over the past decade.
3,450 words (approx. 13.8 pages), 14 sources, APA, AU$ 105.95
»
Click here to show/hide summary
Abstract
This paper examines how software configuration management (SCM) is an important discipline in professional software development and maintenance and how the importance of SCM has increased as programs have become more complex, long-lasting, and time critical. It aims to critically evaluate the evolution of SCM, as well as the obstacles and progress achieved by this particular segment of software engineering. The paper uses a column page layout.
Outline:
Abstract
Introduction
Foundation Years of Software Configuration Management
Progress and Obstacles - SCM in the Past Decade
Process Support
Versioning and Release
Change Control
The Tools - Third Party and Open-Source
Transitions
Conclusion
From the Paper
"The mid 90's paved the way for much better and more powerful SCM tools. Although much of them were still reliant on old methods, these tools had revved up their ability by nearly two folds in terms of automation from a mere cost effective in-house development. [2, 3] In the late 90's, the evolution of SCM in general was characterised mainly by technological issues, better understanding of the technology and experience acquired by the Software Engineering community towards the complexity of a complete SCM solution. On an Industry level SCM was seen largely as a mature, reliable and ideal technology for software development. "
| |
|
Software Testing In The Product Life Cycle, 2007.
A research analysis of the place of software testing in the development and life-cycle of a software product.
4,289 words (approx. 17.2 pages), 12 sources, MLA, AU$ 122.95
»
Click here to show/hide summary
Abstract
This paper aims to provide an overview of software testing throughout the development and life-cycle of a software product. It focuses on the need for testing and how testing fits into the software development life-cycle. The paper presents a research component that analyzes how to formulate a software testing strategy prior to deploying and releasing a software product.
Table of Contents:
Definitions and Terms in the Research
Objective
Introduction
Software Testing Overview
Purpose of Software Testing Categories
Life-cycle Phase Testing Categories
Software Testing Tools
Test Automation Overview
Product Life Cycle Test Automation
Product Life Cycle
Application Test Tools
Classic Testing Mistakes
Developing a Team of Testers is Key in Software Development and Testing
Summary and Conclusion
From the Paper
"The introduction of technology and features being developed in the rapid action which this occurs and to, at the same time, make improvement to the quality of the product and as well to respond to the issues of customers in product development is quite an initiative to undertake. Driving development and quality assurance of software are the technology market which is characterized by an extremely fast past and the revisions are released just as quickly. While quality is considered to be important in the high-tech marketplace new and robust features are considered even more important. (Ben-Yaacov and Gazlay, 2001) Four key measurements of the software product quality have been identified to be the technology, features, freedom from bugs and responsive support. (Ben-Yaacov and Gazlay, 2001)"
| |
|
E-Business Supply Chain Software, 2002.
This paper discusses the use of software to solve problems in companies categorized as "supply chain", multiple, mass-market stores that supply various items usually at a discount.
2,420 words (approx. 9.7 pages), 5 sources, MLA, AU$ 79.95
»
Click here to show/hide summary
Abstract
This paper discusses i2, which is a value chain management software to control transportation and distribution that is used at Best Buy and IBM WebSphere which is an open infrastructure software to improve the e-business infrastructure and improve customer service that is used at Home Depot. The paper details these software companies and the supply chains featured.This paper includes a glossary of terms.
Table of Contents
Introduction
Best Buy and i2's Transportation and Distribution Management Software
Home Depot and IBM WebSphere Open Infrastructure Software
Conclusion
Glossary
From the Paper
"i2 was founded in 1988 by Sanjiv Sidhu and Ken Sharma. It started based out of a small 2-bedroom apartment in Dallas where the first program was written. Since then i2 has grown to earn more than $1 billion in revenues. They have 40 offices worldwide where they employ a total of 4,890 employees. Currently i2 has more than 1,000 customers and 500 deployments in 2001. That same year they reported a pro forma net loss of $149,013,000. This is not uncommon, at this time, for many companies are currently experiencing losses due to the slump in today's economy."
| |
|
Software Testing and Design, 2000.
An examination of the interdependent process of designing new software and testing it for errors and debugging, focusing on procedural software and object-oriented software.
1,800 words (approx. 7.2 pages), 4 sources, AU$ 68.95
»
Click here to show/hide summary
From the Paper
"Before discussing the comparative testing requirements of traditional, procedural software and object-oriented software, it is necessary to ask a basic question: what does it mean to test software? The answer given by one authority is simple and straightforward. According to Glenford Myers, "testing is the process of executing a program with the intent of finding errors" (Williams, 1995, p. 252). Errors are inevitable; has anyone ever written "Hello, world" in a new language for the first time and had it run on the first attempt?
Moreover, the most serious errors are not those that cause the program to fail to compile, or even runtime errors that produce obvious nonsense output. A tricker class of errors -- and particularly difficult for the designers to find -- are those that result from unintended "error" inputs. The designers, who know..."
| |
|
Software Requirements Engineering, 2002.
A look at the software requirements engineering process part of the analysis phase of the software development life cycle.
1,200 words (approx. 4.8 pages), 3 sources, MLA, AU$ 44.95
»
Click here to show/hide summary
Abstract
This paper discusses how today software requirements analysis has become an indispensable part of software development. It examines how the system development life cycle incorporates the complete analysis, design and maintenance of any software project wherein each phase of the project is meticulously planned and based on the previous phase. It considers the requirements engineering process in a little detail.
Outline
Introduction
The Software Requirements Specification
Languages for Requirements Specification (Automated Tools)
PSL/PSA
RSL/REVS
Structured Analysis and Design Technique
Effect of Bad Requirements Analysis
Conclusion
From the Paper
"The software requirements specification is a comprehensive document, which presents all the different aspects involved in the software development. This includes the product overview, data flow, functional requirements, performance requirements, methods to handle exceptions, provisions for modification etc. It is desirable that the software specification or requirements report should be correct, complete, consistent, clear, functional, verifiable, traceable and easily changeable. If the requirements are badly stated or incomplete we might end up developing software that satisfies the requirements but still way behind the user expectations."
| |
|
Project Management Software Tools, 2004.
This paper compares the advantages and limitations of using a project management software tool such as Microsoft Project versus not using this tool, to manage a project's scope, process, data, time, and cost.
3,655 words (approx. 14.6 pages), 11 sources, APA, AU$ 109.95
»
Click here to show/hide summary
Abstract
The paper explains that a project management software package is designed to assist in managing a project, but that project is controlled by the project manager, not a software package because there are both benefits and inherent limitations to using project management software, which the project manager must understand. The author stresses that the manager must first establish the basic blueprint of the project before beginning a project in a software package and must always remember projects have a way of becoming living entities with their own unique obstacles, requiring more than making sure everything goes according to the printed software plan, or the project is doomed to failure. The paper creates a hypothetical project to demonstrate the strategic points of this software.
Table of Contents
Introduction
Software Limitations
Software Advantages
Scope Management
Time Management and Gantt
Cost Management
Quality Management
Human Resources Management
Project Roles and Responsibilities
Communication Management
Conclusion
Appendix: Work Breakdown Structure
From the Paper
"In other words, a project manager has to maintain the political and social aspects of the project and software has its limitations in these respects. Having the ability to effectively communicate with all relevant parties is a key to managing a successful project. Software can not make a project manager speak and listen effectively or to receive verbal confirmation that all is well or in need of change. It is necessary to regularly communicate verbally with individual members, stakeholders and peers in order to evaluate the project from different perspectives. Software and written reports may in many situations be a waste of a team's time when a brief conversation will suffice. Software also cannot replace a face-to-face meeting, telephone call or voice mail in most situations."
| |
|
Risk Assessment Software Applications, 2004.
An analysis of the effectiveness of risk assessment software applications in the workplace.
11,473 words (approx. 45.9 pages), 10 sources, MLA, AU$ 242.95
»
Click here to show/hide summary
Abstract
The risk assessment process is becoming increasingly important, but it has assumed enormously complex dimensions at the same time. Risk assessment has reached a new level of importance in the Information Age. The growth of sophisticated networked information systems and distributed computing has created a potentially dangerous environment for private and public organizations. This paper examines these issues and provides an analysis of popular risk assessment applications. An original comparison table is provided.
Chapter One: Introduction
Statement of Hypothesis, Research Problem, or Statement of the Purpose
Outline of Thesis/Project
Chapter Two: Methodology/Layout or Reason
Chapter Three: Literature Review
Industrial Settings and Software
Business Credit Settings and Software
Primary Software
Secondary Software
Risk Assessment Software for Credit Applications
Accounts Receivable Processing (ARP) Company
Advisa, Inc.
C/LECT Consulting, Inc.
Competix
Credit & Management Systems, Inc.
Dun & Bradstreet
eCredible, Ltd.
eCredit.com
Experian
GETPAID Corporation
I-many, Inc. (formerly ChiCor, Inc.)
Magnum Communications, Ltd.
9ci, Inc.
NMC Technologies, Inc.
Risk Assessment in Financial Institutions
Selected Banking Risk Management Software
Chapter Four: Pros and Cons
Chapter Five: Findings
Establish the Context
Identify Situations that Have Risk Implications
Analyze and Assess Risk
Design Response Strategies
Implement and Integrate
Measure, Monitor and Report
Chapter Six: Conclusion and Recommendations
Works Cited
From the Paper
"Risk assessment has reached a new level of importance in the Information Age. The growth of sophisticated networked information systems and distributed computing has created a potentially dangerous environment for private and public organizations. "Critical data -- such as from trade secrets, proprietary information, troop movements, sensitive medical records and financial transactions -- flows through these systems" (Hammond 1999:69). Consequently, organizations are becoming increasingly concerned with potential exposure and are looking for ways to evaluate their organization's security profile today. Risk assessment software applications systems allow researchers, managers and others to perform "what if" analyses of the value of their information and various threats and vulnerabilities. For instance, risk assessment software systems such as NetSolar by Cisco, use both passive analysis and active probing methods to identify security vulnerabilities, which may increase the efficiency of vulnerability identification and reduce false-positive results. Hamilton reports that these technical assessments can differentiate between infrastructure devices (routers, switches, or firewalls) and host devices (user workstations or servers such as e-mail servers and Web servers). "Technical vulnerability tools can find vulnerabilities in network TCP/IP hosts, UNIX hosts, Windows NT hosts, Web servers, mail servers, FTP servers, firewalls, routers and switches" (Hamilton 1999:69)."
| |
|
Integra's Software, 2005.
This paper analyzes the case study of Integra's software, a dream project, which turned into a nightmare resulting in this flawless software never being marketed.
935 words (approx. 3.7 pages), 3 sources, APA, AU$ 36.95
»
Click here to show/hide summary
Abstract
This paper explains that the two main problems in this case are (1) the market and risk analysis issues surrounding the potential sale of the software were ignored because Integra assumed the project was so valuable that it could not fail in the market place and (2) only the lower-level credit unions and not the regional offices for the credit unions throughout the rest of Canada were consulted. The author points out that the problems stem largely from the idea that the company put the project on the 'fast track' and assumed that their product was so much better than the competition that the credit unions could not help but realize this and switch over to this new product. The paper suggests that, if there is no market for a particular project, there is certainly no point in continuing to try to sell it to others, which simply ends up costing the company more money.
From the Paper
"Organizational issues were mainly related to the idea that the company was so large and powerful that it could not fail with a project and that the competition would never be able to keep up. Organizational resources fell along these same lines, as money and people for the project were both very plentiful. Technological issues came quickly to the project, as there were so many different systems that the software had to work with, and this was something that had not been anticipated. However, the company had so many technological resources at their disposal that the management felt there would not be any large problems with the technology that could not be overcome."
| |
|
Web and Document Design Software, 2007.
This paper is a historical analysis of software engineering for web and document design as it evolved from 1969 to 2006.
1,845 words (approx. 7.4 pages), 8 sources, APA, AU$ 64.95
»
Click here to show/hide summary
Abstract
This paper explains that understanding the historical development of software is the most effective manner in which to demonstrate the relevance of software technology to web and document design. The author points out that, nearly forty years ago, E.W. Dijkstra was the first to introduce the term "structured programming" and the related basic software concepts. The paper relates that Dijkstra explained that, although structured programming focuses primarily on coding activities, it also was accelerating a movement that lead to the formalization of other life-cycle phases, such as structured design and structured analysis. The author states that the critical choice of which software engineering methodology to use in a development project is always closely related to the size of the associated software system and the environment in which it is to function.
Table of Contents
Introduction
Origins
Software Development
Object-Oriented Design
Structural Design
Designing for HTML
Conclusion
From the Paper
"Berard (1995) explains that there are significant differences between these two groups of object-oriented people. For example, a number of those who emphasize rigor and formality consider the programming language people to be chaotic, overly error prone, wasteful, and largely unpredictable. In contrast, some of the programming language people consider the formality and rigor unnecessary. They feel that at best, rigor and formality add nothing to the quality of the final product, and at worst, they increase the cost of development while simultaneously delaying the delivery and lowering the quality of the resulting software product."
|
|
|
