Since I do software development in this line, and use the Bug tracking system, we will tangle in a basic question in every project: Bug and how you can distinguish functional requirements? Of course, if the program crashes, and this no doubt is Bug. However, it may only deal with 10% of you every day problems. In order to avoid a complete failure of the project, the real killer Bug-- its existence can not be made Bug-- version will soon be eliminated. In the Bug tracking system left most of Bug, nobody would fall into the gray area. Users report that the Bug it? Is not entirely. Users requiring a new or improve an existing feature functionality? Not exactly. Well, that in the end is what? This is a very screenwriters issue. Furthermore, I believe that most of the Bug tracking systems are in the 'pit' us because they make us have to answer such silly questions, forcing us to stand - either Heifetz, or Islamic McCaw; or Coca-Cola, or Pepsi; either Bug, either functional requirements - this is a painful choice, choose which side are in the ages, because most of the time both. From the user's perspective, Bug and functional requirements are no different. If you want to do something with a software (or Web site), but not implemented because of a function can not be completed; compared to you in the 2015 Nike Free 5.0 course because of an error can not stop, there are differences between the two it? Translator's Note: the US drama 'Hatfields \u0026 amp; McCoys', also known as 'vendetta', focused on the United States infamous two families (Hatfields and McCoys) dispute. Two family dispute originated in the US Civil War, Anse Hatfield and Randall McCoy this is to good buddy child, but do not want later changed, the two forged hatred, and even attracted the Virginia and Kentucky are not peaceful. Thus, these two families together to manufacture the most notorious bloody dispute in the history of Nike Air Jordan 4 Women the United States. Nike Zoom KD V Let's look at an example: in Windows application development time, Visual Studio does not use the correct font. Air Max 2011 Womens Wine Red White Grey This is regarded Air Max 2012 Black Red White as a Bug or functional needs? I personally think this is a Bug. I guess Microsoft think so (at least in theory), because the problem has existed for more than four years at Microsoft Connect system. When you develop a Windows application, unless you New Nike Free 5.0 V4 Shoes Black Red deliberately want to use a special font, you do not want to use the default font of the operating system it? Well, if you create a new form in Visual Studio 2008, and then add a Label control, and see what the situation is right: if suddenly back in 1996, because you see the 'cute' MS Sans Serif fonts. It is the default font for all new form. You can also take offense, all newly developed applications looks ugly - I have been very restrained wording! Here is a comparison: the default font tag line, another line label explicitly set New Nike Tr Fit Running Shoes Black the default GUI font. Throughout I have used the application software, I found that most Windows Nike Air Max programmers do not care about design. This is not good! Even worse, this disregard for the design was carried Visual Studio, since 2002, constantly New Nike Tr Fit Running Shoes Black Blue infected every user. Of course, the issue of design is subjective. Font use of the Windows graphical user interface, and if we can have some reference material, and that nice ah! Something similar to the standard thing. Such as those on the Microsoft specification to define the user experience of Windows Vista: Use Aero theme and system font (Segoe UI) to use common controls and common dialog boxes use standard New Nike Tr Fit Shoes Black Red forms the border with caution transparency effect ...... this specification total 12 ʱ?? However, I want to find precisely the first: the application should use the system font. I sighed with regret for the overall quality of Windows Vista, for which I also wrote a full article. The list above looks very happy, in fact, has been self-evident. In particular, Article 12: Air Max 2012 Blue Silver White Reserve time to enhance the 'overall quality', so I can not help laughing. In the development of Windows Vista, Microsoft presumably this article regulate heart. It is worth noting that these are from Vista to a loving guy. Sorry, I digress. Although Visual Air Jordan Outlet Studio 2008 in the window font act contrary to Microsoft's own design specifications (the first), the 'Bug' but more than four years has Authentic Mens Basketball Shoes All Red Nike KD 7 Factory Outlet not been amended. It is quietly classified as 'functional requirements' and then shelved. After all, no adverse effects - using the wrong font will not allow the program to crash or reduce productivity. On the other hand, imagine, since Microsoft's own design specifications trampled since, the number of large companies application software has been developed ah. Either because developers do not realize the problem fonts and operating system that does not match the application, or they do not have time to write the necessary code to New Nike Free 5.0 V4 Shoes Black Blue be corrected contingency. Yes, this is a small problem. I believe, to fix this problem does not allow Visual Studio to better sell, sell to big Nike Air Max 2011 companies such as multi-thousands of license. This is also the reason it nobody. Question remains: What is a Bug, or functional requirements? I like to use UserVoice (Stack Overflow is using this tool), it is the most my heart is that it deliberately blurs the boundaries between the Bug and functional requirements. In any case, users do not understand the difference between them; even worse is that the programmer may stall, according to users. They do not want to be classified as 'functional requirements', then on ignore the. They will argue, exclaimed been reported as a 'Bug' the problem is clearly not the Bug, naturally do not have to fix. Fills it, do not distinguish between Bug and functional requirements, let them all go to hell! I hope that we can spend less time in the industry on the concept of a war of words, do not put painstakingly user feedback area into 'Bug' or 'functional requirements.' Faced with user feedback, we should spend more time to do some constructive things.That's not Bug, the new requirements