Friday, January 1, 2010

Home Antivirus 2010 Removal - Learn How to Remove Home Antivirus 2010 From Your Computer

Home Antivirus 2010 is a fake security program which is spreading through Internet very fast. If you are getting pop-ups and security alert messages which says your computer is infected with Trojan and Spyware, then your computer could be infected with the deadly Home Antivirus 2010.
Home Antivirus 2010 Infection
You may be interested to know how your PC got infected. There are many ways this fake program gets into your computer. This issue mainly happens when you download files from torrent download or using peer to peer network. Most of the files downloaded using these methods are infected with fake alert trojan. Also many Internet users are getting spam mails which contains attachment infected with Trojan which downloads this fake security software.
How To Check Whether Your Computer Is Infected
If your computer is infected with this rogue spyware, you may get many fake security warnings and alert messages which says your computer is infected with Virus and Trojan. It will also tell you to download Home Antivirus 2010 to remove the Virus and Spyware infection from your computer. Please don't be scared with this warnings and try to avoid clicking any links on the pop-up messages.
How To Remove Home Antivirus 2010
In order to remove this spyware from your computer, you need to remove all the trojan infected files. You also need to remove all the registry entries made by the spyware. It is not an easy task and the user need to have good computer knowledge to clean registry. If you make any mistake when removing registry entries, it could put your computer in great danger. Always seek for expert help when editing registry entries.
Home Antivirus 2010 Removal Tool
You can remove Home Anti-virus 2010 from your computer using free spyware removal tool. You need to run a full scan of your computer using the removal tool to find and remove all the trojan and spyware.
Click here to Remove Home Antivirus 2010 from your computer and easily Remove Spyware from your computer.
Keep your computer safe and clean.

Software Maintenance Implications on Cost and Schedule

Abstract The dictionary defines maintenance as, "The work of keeping something in proper order." However, this definition does not necessarily fit for software. Software maintenance is different from hardware maintenance because software doesn't physically wear out, but often gets less useful with age. Software is typically delivered with undiscovered flaws. Therefore, software maintenance is: "The process of modifying existing operational software while leaving its primary functions intact." Maintenance typically exceeds fifty percent of the systems' life cycle cost . While software maintenance can be treated as a level of effort activity, there are consequences on quality, functionality, reliability, cost and schedule that can be mitigated through the use of parametric estimation techniques.
1. INTRODUCTION One of the greatest challenges facing software engineers is the management of change control. It has been estimated that the cost of change control can be between 40% and 70% of the life cycle costs . Software engineers have hoped that new languages and new process would greatly reduce these numbers; however this has not been the case. Fundamentally this is because software is still delivered with a significant number of defects. Capers Jones estimates that there are about 5 bugs per Function Point created during Development . Watts Humphrey found "... even experienced software engineers normally inject 100 or more defects per KSLOC . Capers Jones says, "A series of studies the defect density of software ranges from 49.5 to 94.5 errors per thousand lines of code ." The purpose of this article is to first review the fundamentals of software maintenance and to present alternative approaches to estimating software maintenance. A key element to note is that development and management decisions made during the development process can significantly affect the developmental cost and the resulting maintenance costs.
2. SOFTWARE MAINTENANCE Maintenance activities include all work carried out post-delivery and should be distinguished from block modifications which represent significant design and development effort and supersede a previously released software package. These maintenance activities can be quite diverse, and it helps to identify exactly what post-delivery activities are to be included in an estimate of maintenance effort. Maintenance activities, once defined, may be evaluated in a quite different light than when called simply "maintenance". Software maintenance is different from hardware maintenance because software doesn't physically wear out, but software often gets less useful with age and it may be delivered with undiscovered flaws. In addition to the undiscovered flaws, it is common that some number of known defects pass from the development organization to the maintenance group. Accurate estimation of the effort required to maintain delivered software is aided by the decomposition of the overall effort into the various activities that make up the whole process.
3. APPROACHING THE MAINTENANCE ISSUE Maintenance is a complicated and structured process. In his textbook, Estimating Software Intensive Systems, Richard Stuzke outlines the typical software maintenance process. It is apparent that the process is more than just writing new code.
The following checklist can be used to explore the realism and accuracy of maintenance requirements.
• Which pieces of software will be maintained?
• How long will the system need to be maintained?
• Are you estimating the entire maintenance problem, or just incremental maintenance?
• What level of maintenance is required?
• Is that which is being called maintenance in fact a new development project?
• Who will do the maintenance? Will it be done organically by the original developer? Will there be a separate team? Will there be a separate organization?
• Will maintainers be using the same tools used during development? Are any proprietary tools required for maintenance?
• How much Commercial-Off-The-Shelf (COTS) is there? How tightly coupled are the interfaces?
• Some follow-on development may be disguised as maintenance. This will either inflate maintenance figures, or else cause shortfalls if basic maintenance gets pushed aside. These questions will help you ask whether maintenance is being honestly represented.
• Is the activity really an incremental improvement?
• Are healthy chunks of the original code being rewritten or changed?
• Will additional staff be brought in to perform the upgrade?
• Is the maintenance effort schedule regular and fairly flat, or does it contain staffing humps that look like new development?
4. SANITY CHECKS Although sanity checks should be sought on a year-by-year basis, they should not be attempted for overall development. The reason for this is that maintenance activities can be carried on indefinitely, rendering any life-cycle rules useless. As an example, consider Grady (p. 17):
We spend about 2 to 3 times as much effort maintaining and enhancing software as we spend creating new software.
This and similar observations apply at an organizational level and higher, but not for a specific project. Any development group with a history will be embroiled in the long tail ends of their many delivered projects, still needing indefinite attention. Here are a few quick sanity checks:
• One maintainer can handle about 10,000 lines per year.
• Overall life-cycle effort is typically 40% development and 60% maintenance.
• Maintenance costs on average are one-sixth of yearly development costs.
• Successful systems are usually maintained for 10 to 20 years.
Finally, as in development, the amount of code that is new versus modified makes a difference. The effective size, that is, the equivalent effort if all the work were new code, is still the key input for both development and maintenance cost estimation.
5. FIVE ALTERNATIVE APPROACHES All software estimation techniques must be able to model the theory and the likely real world result. The real world scenario is that over time, the overlay of changes upon changes makes software increasingly difficult to maintain and thus less useful. Maintenance effort estimation techniques range from the simplistic level of effort method, through more thoughtful analysis and development practice modifications, to the use of parametric models in order to use historical data to project future needs.
5.1 Level of Effort As is sometimes the case in the development environment, software maintenance can be modeled as a level of effort activity. Given the repair category activities and the great variance that they show, this approach clearly has deficiencies. In this approach, a level of effort to maintain software is based on size and type.
5.2 Level of Effort Plus Stuzke proposed that software maintenance starts with basic level of effort (minimum people needed to have a core competency and then that that basic core staff must be modified by assessing three additional factors; configuration management, quality assurance, and project management. His process addressed some of the additional factors affecting software maintenance.
5.3 Maintenance Change Factor Software Cost Estimation with COCOMO II (Boehm 2000) proposes a deceivingly simple, but also quite useful methodology for determining annual maintenance. Maintenance is one of the menu selections in the menu bar. In COCOMO II Maintenance encompasses the process of modifying existing operational software while leaving its primary functions intact. This process excludes:
• Major re-design and re-development (more than 50% new code) of a new software product performing substantially the same functions.
• Design and development of a sizeable (more than 20% of the source instructions comprising the existing product) interfacing software package which requires relatively little redesigning of the existing product.
• Data processing system operations, data entry, and modification of values in the database.
The maintenance calculations are heavily based upon the Maintenance Change Factor (MCF) and the Maintenance Adjustment Factor (MAF). The MCF is similar to the Annual change Traffic in COCOMO81, except that maintenance periods other than a year can be used. The resulting maintenance effort estimation formula is the same as the COCOMO II Post Architecture development model.
As stated previously, three cost drivers for maintenance differ from development. Those cost drivers are software reliability, modern programming practices, and schedule. COCOMO II assumes that increased investment in software reliability and use of modern programming practices during software development has a strong positive effect upon the maintenance stage.
Annual Maintenance Effort = (Annual Change Traffic) * (Original Software Development Effort)
The quantity Original Software Development Effort refers to the total effort (person-months or other unit of measure) expended throughout development, even if a multi-year project.
The multiplier Annual Change Traffic is the proportion of the overall software to be modified during the year. This is relatively easy to obtain from engineering estimates. Developers often maintain change lists, or have a sense of proportional change to be required even before development is complete.
5.4 Managing Software Maintenance Costs by Developmental Techniques and Management Decisions During Development
When it comes to maintenance, "a penny spent is a pound saved." Better development practices (even if more expensive) can significantly reduce maintenance effort, and reduce overall life cycle cost. The more effort put into development, the less required in maintenance. As an example, the software development cost and schedule can be significantly impacted (reduced) by letting the number of defects delivered grow. This cost and schedule reduction is more than offset by the increase in maintenance cost. The following discussion is an example of how management decision can significantly affect/reduce software maintenance costs.
Lloyd Huff and George Novak of Lockheed Martin Aeronautics in their paper "Lockheed Martin Aeronautics Performance Based Software Sustainment for the F-35 Lightning II" propose a series of development and management decision designed to impact and reduce software maintenance costs. They propose an eight step process to estimate and control software maintenance . Their proposed steps are:
1. Strive for Commonality
2. Apply Industrial Engineering Practices to Software
3. Engage
4. Adopt a Holistic Approach to Sustainment
5. Develop Highly Maintainable Systems and Software
6. Manage the Off-the-Shelf Software
7. Plan for the Unexpected
8. Analyze and Refine the Software Sustainment Business Case (use Parametric software sustainment cost estimates)
5.5 A Parametric Assessment of Software Maintenance
Parametric models like SEER for Software allow maintenance to be modeled in either of two ways:
Estimating maintenance as a part of the total lifecycle cost. Choosing the appropriate Maintenance category parameters will include an estimate of maintenance effort with the development estimate for the individual software program. Several reports and charts show breakdowns of development vs. maintenance effort. This method is best used to evaluate life cycle costs for each individual software program.
Estimating maintenance as a separate activity. Using the appropriate maintenance parameters for the software to be maintained you can model the maintenance effort as a separate activity. This method will allow you to fine tune your maintenance estimate by adjusting parameters. Maintenance size should be the same as development size, but should be entered as all pre-existing code. This method can also be useful in breaking out total project maintenance costs from project development costs.
A good parametric estimate for maintenance includes a wide range of information. Critical information for completing a software maintenance estimate is the size or amount of software that will be maintained, the quality of that software, the quality and availability of the documentation, and the type or amount of maintenance that will be done. Many organizations don't actually estimate maintenance costs; they simply have a budget for software maintenance. In this case, a parametric model should be used to compute how much maintenance can actually be performed with the given budget.
Estimating and planning for maintenance are critical activities if the software is required to function properly throughout its expected life. Even with a limited budget, a plan can be made to use the resources available in the most efficient, productive manner. Looking at the diagram above, you can see that not only are the multiple inputs that impact the maintenance, but there are several key outputs that provide the information necessary to plan a successful maintenance effort.
6. Conclusion The conclusions of this article are:
• Software maintenance can be modeled using a simplistic method like Level of Effort Staffing, but this technique has significant drawbacks.
• Software maintenance costs can be significantly affected by management decisions during the developmental process.
• Software maintenance can be accurately estimated using parametric processes.
• Software maintenance is best modeled when development and management decisions are coupled with parametric cost estimation techniques.
REFERENCES [1] Software Maintenance Concepts and Practices (second Edition) by Penny Grubb and Armstrong Takang, World Scientific, 2005.
[2] Estimating Software Intensive Systems; Richard Stuzke, 2005, Addison-Wesley.
[3] Lloyd Huff, George Novak; Lockheed Martin Aeronautics; Lockheed Martin Aeronautics Performance Based Software Sustainment for the F-35 Lightning II.
[4] G. Edward Bryan, "CP-6: Quality and Productivity Measures in the 15-Year Life Cycle of an Operating System," Software Quality Journal 2, 129-144, June 1993.
[5] Software Sizing, Estimation, and Risk Management; Daniel D. Galorath, Michael W. Evans, 2006, Auerbach Publications.
Bob Hunt is Vice President for Services of Galorath Incorporated - http://www.galorath.com - providing project management estimating software for complex projects. Mr. Hunt is responsible for the management and technical direction of the services staff and the quality of the services products.

Software Piracy

SOFTWARE PIRACY

We regularly hear reports about the cost to the software industry of software piracy, but are the claims to be taken at face value? Statistics are notoriously biased towards what the author is trying to say.

Types of Software:

There are three basic types of software, although these do have their own subsections, as will be discussed later:



1. Commercial software, purchased with a licence for one or more computers. This generally is coupled with some form of support and regular updates to patch errors etc. Sometimes a new version of the software is offered at a reduced rate as "update". This type of software is generally relatively expensive and is often designed to cover specific industrial purposes. The big exception is the various sets of "office" software, which are designed for use in the commercial environment, but can naturally be equally used for various tasks at home. The most common application in this category is, of course, text editing. Most of the other classic "office" applications, such as calculations and data bases are only of limited use in the domestic environment, although they will be used in some cases, particularly now that the more computer-literate generation is growing.

2. Simplified or "lite" versions of the commercial software. These are intended principally for small businesses and enterprises that do not need the complete capabilities of, say, a 3-D modelling system, but must be able to view such documentation and prepare compatible drawings. Again, the "office" environment was a long time not represented in this sector, but has recently started to be available. These will also come with a single or multiple, but limited licence and now mostly be registered with the manufacturer.

3. Free or "open source" software. This is designed for general distribution and has no particular limitations as to use, except that it may not be changed in any way. Naturally, such software has its limitations, but may serve very adequately for many purposes. Practically all types of software are to be found in this category. One notable application distributes the software to read its documents freely, but charges for the software to produce the documents. This policy is arguably the motor behind its ride to a position as industry standard, since you can always be certain that he receiver can decipher whatever is sent, without long discussions about compatibility and versions.

Clearly, there can be no piracy of products that fall into the third category, except for changing of the code or reuse of the code for other purposes, but this does not appear to be a major issue at the moment, so we will concentrate our attention on the first two categories.

Both of these categories contain software that is copied and distributed either free of charge or for a nominal fee. Naturally, the full versions of the software are preferred, but the simplified versions are also to be found, depending on what is available.

Types of Software Pirate

This puts our software pirates into two categories of their own:



1. Those who knowingly use a copy of software "borrowed" from work or supplied by friends, who probably acquired it by the same means.

2. Those who prepare copies of software from an original and sell it at a low price through internet auctions or on market stands. Their customers may, in many cases, be unaware that the software has been pirated and simply be pleased to acquire a software package at a bargain price. Some will be quite well aware of the actual source, but still prepared to take this means of saving money.

Composition of the Groups:

So who is to be found in these two groups?



1. This group is very widely ranged and consists of school children, people practicing at home with the company software, various private persons with an interest in computers who will try anything that is free and, possibly, very small businesses. Many schools will supply their students with copies of software licensed for the school to enable them to complete homework or learn to use it for technical subjects. A student finishing a technical school with little or no knowledge of the technical software used in their industry will not easily find employment, so a blind eye is turned in many schools to this practice. Schoolwork is often required to be written on computer these days, and again, this is only really possible if some form of text software is available. Those who use company software at home to play with or for their children to complete homework are also a large group. The computer has become a part of our lifestyle in the western hemisphere, and many people are interested in the possibilities opened by the modern generation of powerful number-crunchers. The days of mainframe computers costing hundreds of thousands of dollars is not gone, but the small computer in a network has taken over in many areas, so the professional software that would earlier have required a mainframe connection and a whole basement full of equipment will now run happily on a home computer. There may be a loss of speed, but who cares? The vast majority of these people know full well that what they are doing is not allowed, but consider this as a very minor matter, and would laugh at any suggestion that they should purchase the software officially. The few companies that also do this are saving money that they probably do not have, despite being aware of the risks.

2. The group of people who copy software and distribute it for sale as being genuine are working simply for profit, taking advantage of the simplicity of the process and the high prices of genuine software. The general public is not aware of the penalties for this type of action and is often unsure about recognising the genuine article. Other items in the consumer market are available from many manufacturers as basically identical products, so why should this not be the case with software? Very many are simply duped into buying what they see as a cheap alternative to a brand-marked product.

Costs of Software Piracy:

So what are the real costs to the software companies?

In most cases, school and college students would not be in a position to pay the costs for the expensive commercial software they use in technical subjects, and the schools and colleges are not in a position to supply this to them free of charge. Most schools have licences for software to be used on the premises, but this is not available for the students at home. Theoretically, they will use the computers at school to complete work and practice, but this is generally not possible due to a lack of resources, or classrooms locked because of vandalism. The only way to solve the problem is for the schools to simply distribute the software to their students on the basis of it being only for their use. There is no licence and no direct upgrade possible. Generally, although illegal, this system works quite well. Schools try to copy upgrades and patches for their students, mostly successfully. The snag to the matter is that we educate people in that this is perfectly acceptable practice, despite it being illegal. No-one would think of insisting or even checking that drop-out students erase the software and no longer use it, but this is probably fairly well assured by the fact that they have dropped out in the first place!

Solutions to Software Piracy:

Student Software:

Low-Cost Software:

One of the best-known software companies has recently started to sell a slightly simplified version of their software in a student package, stating that this is not for commercial use. Naturally, this is being distributed to everybody without regard to their true status as student or not! Nevertheless it is a definite move in the right direction. Providing an affordable alternative is the first step towards a solution for this problem. The quality is good and it contains all the usual features that are needed.

Other companies also offer free software for student use, but this is in most cases pitifully inadequate and simply not up to the job and no preparation for later commercial practice. It remains to be seen how far the availability of reasonably priced student software will affect sales of the commercial product. One of the factors presumably behind this move is the general attitude that the present software is perfectly adequate and can be used for a length of time without being replaced. Since many software houses have distanced themselves from the idea of upgrade software for older versions at a reduced price, this attitude will probably cause sales of the full commercial software to be limited to new systems, and not as an improvement on older systems.

The new wave of student software is probably intended to bridge this gap somewhat by providing extra revenue. Whether the fears of the others that the production of a student version at greatly reduced price will cut into their sales of the full, commercial version will prove to be correct, or the alternative view that these are complementary products will prevail will remain to be seen.

Benefits of Student Use:

It is undoubtedly true that someone who has trained on one type of software will tend to remain loyal to it as far as company policies allow and that this is a definite motivation to purchase a type of software, hence the policy of the schools is unlikely to be challenged or mentioned publicly. Nevertheless, there is no reason for forcing our youth into criminal activity! Providing a solution that allows people to use these applications during training legally should be a priority for the software houses that will bring some revenue in the short term, and possibly more in the long term. One of the problems in the computer branch has always been the emphasis on short term results and quick profits, but this attitude will have to change soon to allow for these factors.

"Fun " Use:

Again, the people who use the company software at home for fun cannot really be seen as a risk to the profits of a software company. They would simply spend their time otherwise in the evenings if they did not have this possibility! The matter only then becomes problematic when they begin producing work privately for other companies. This would then definitely be a matter for concern, both for the producers of the software and other companies in the same branch, who have to calculate the costs of software into their prices.

Geographical Factors:

The problem is also geographically different. Most of the software packages originate, at least on paper, from the United States. The prices in Europe tend to be 1.5 to 2 times higher, without considering sales tax of any type, which is generally higher in most European countries. Whilst this may not be of consequence for the run of low-cost software, it is a significant difference when complex design or technical applications are considered. This price differential is often explained by higher support costs or translation costs, but these factors alone cannot be the complete reason. A change in this policy would probably help to reduce the level of use of copies in the commercial field at least. Splitting software packages into easily-upgraded elements would also enable small companies to purchase what they need immediately and then add the extra features in time as and when necessary.

Reasons for Software Piracy:

Software piracy is legally a crime, but it is a crime that is still acceptable in our society. Very little has been done to combat it for a number of reasons. One reason is that it is almost universal amongst users of computers. Many people "need" an application once per year and do not wish to pay the sometimes horrendous cost for the commercial licences. Companies have made no real attempt to combat it until now, since this is a form of free advertising, and the benefits of having it available to students have been mentioned above. It is only now, when the earning curve start to tip downhill that this is seen as a threat to company existence. In reality it is relatively simple to make something extremely difficult to copy. Impossibility is a dream in the computer world these days!

Concluding Remarks:

That criminal activity should be hindered and software piracy is, broadly speaking, theft, is quite correct, but the solution is not just to seek out and punish wrong-doers, but to find a solution for all these groups of people who, for one reason or other, wish to use the software, but cannot, or will not, find the means of paying the present market cost. An imaginative solution to this problem could well be the break-through that a company needs to make itself known in every household, provided the product is correct.
Simon Fowler is a graduate in Mechanical Engineering and now works as sales technician for flue gas analyzers. He is presently employed by madur electronics in Vienna, Austria.

acer laptop