Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 6 years ago.
Improve this question
It is really simple question.
However, really wondering.
I think even we don't software testing,
Program will work.
So, What happens if we don't software testing?
When you are so sure about the your software, why not just wait and see what happens? The simple fact you are asking the question means that you suspect you overlook something, and yes, you are. Testing software is not only about working or not, but concerns the quality of the software, including usability, performance, security, compatibility and so on and what can be improved. Are you sure color-blind people can use your software and your application is free from security vulnerabilities?
The software might work, but you won't know1 it works.
However, history has shown that all software has bugs. Your software will be tested. The question is, do you want your customers to find the bugs, or do you want to find them before the customers do?
1 of course, even with testing you won't know with 100% certainty, but you will certainly know with more than 0% certainty. If you are writing a tic-tac-toe game, a low level of certainty is quite acceptable. If you are writing software for medical equipment, nuclear reactors, or airplanes, your level of certainty needs to be much higher.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 8 years ago.
Improve this question
I've already tried EazFuscator and Dotfuscator but are bad! I was able to easily read the source and pay it, and frankly I'm tired of the people that I copy the software.
I ask you which obfuscator use, at least to protect all the software by beginners.
From the great Joel Coehoorn ... you can read more here
How can I protect my .NET assemblies from decompilation?
One thing to keep in mind is that you want to do this in a way that makes business sense. To do that, you need to define your goals. So, exactly what are your goals?
Preventing piracy? That goal is not achievable. Even native code can be decompiled or cracked; the multitude of warez available online (even products like Windows and Photoshop) is proof of that.
If you can't prevent piracy, then how about merely reducing it? This, too, is misguided. It only takes one person cracking your code for it to be available to everyone. You have to be lucky every time. The pirates only have to be lucky once.
On another note, I would recommend SmartAssembly by RedGate. Ive used this before and its great compared to others. Please note that like any obfuscator, you cannot stop someone cracking your software if they are determined to do so.
You can get more information here...
http://www.red-gate.com/products/dotnet-development/smartassembly/
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
The IEEE defines software engineering in the following way:
(1) The application of a systematic, disciplined, quantifiable
approach to the development, operation, and maintenance of
software; that is, the application of engineering to
software.
Source: http://www.idi.ntnu.no/grupper/su/publ/ese/ieee-se-glossary-610.12-1990.pdf
But what does systematic, disciplined and quantifiable mean in this context? Is there any further explanation from the IEEE?
You can rely on a dictionary:
http://dictionary.reference.com/browse/systematic:
having, showing, or involving a system, method, or plan
http://dictionary.reference.com/browse/disciplined:
having or exhibiting discipline; rigorous
http://dictionary.reference.com/browse/quantifiable:
to determine, indicate, or express the quantity of.
So, applying software engineering requires the exact execution of method that is precise with quantified steps and exact procedures regarding development, operation and maintenance of software.
or as it is state at the end:
http://dictionary.reference.com/browse/engineering:
the art or science of making practical application of the knowledge of sciences, as computer science, as in the construction of software. (I changed a little bit this definition) =)
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
So I've read some reports about both of these methods but I can't really grasp the dif between the two.
If anyone could sum it up for me or try to explain it I'd be ever so grateful!
BR, Fredrik
Similar to a car. If you test it, you usually drive it around or at least turn it on. If you inspect it usually you check fluids, maybe pull a spark plug, connect it to a computer and check its settings, fiddle with buttons and switches to make sure there is connectivity. During an inspection you may test the vehicle, but during a test you do not always inspect the vehicle.
Software testing is useful because it allows for a mock up of a production environment to be used in order to see if there are bugs, or errors which either throw exceptions or cause logical errors such as making relationships out of state.
Software inspection is more involved. It can involve testing, but can also involve doing code review to make sure that efficient process is used, and that the readability and maintainability is proper. It helps to make sure that features are properly decoupled, the program is running as fast as possible, and that nothing is going on behind the scenes which is undesirable.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
Out of interest, how far can buying and selling shares be made automatic? How far do you think it can go? And what would you need to do it?
Very far.
There are real computers performing fully automated trades as we type.
I'd take a look at some trading APIs provided by E*TRADE https://us.etrade.com/e/t/activetrading/api or something similar. You can use virtually any language to call the API and execute trades, get quotes, and generate strategic algorithms.
However, a fair warning, unless you are a large corporation with lots of money to burn you need to be careful as a homegrown algorithmic trading system can be very dangerous.
I believe something like 70% of all trades on the market today are placed by computer systems automatically and not by people. It makes it harder for smaller individuals to compete because we simply don't have the financial resources to purchase the power and speed we need to compete.
Thanks,
Jeffrey Pry
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 7 years ago.
Improve this question
In order to improve my open source project, I need testers. I have created my project independently, so up to now I have been the sole coder and tester. I have tested the thing to death, but as we all know it is dangerous as a developer to test your own code. I'm looking for ideas on how I can get some other eyes to exercise it.
To clarify, I have released it on sourceforge and posted it on freshmeat, dzone, reddit, etc.
Are you looking for "testers" or "users"? There's a world of difference.
A tester uses his time and energy to find your bugs. How many people are willing to do that? At a rough guess, I'd say zero.
A user uses your software to solve his problems. He reports bugs to you because he thinks that you might fix them for him. So you've got to find people with a problem, and convince them that your software will fix it.
One thing you'll need is lots of documentation. A 1-minute screencast, in-depth API, and everything in between. You need to persuade someone that, "If I use tox, I will totally rock!"
That's your tester.
Release an early version, announce it on freshmeat, and wait for the world to beat a path to your door?
Go to where the testers are. Find sites where testers go. http://www.stickyminds.com, local QA groups (like mine) http://redearthqa.blogspot.com/ or local recruiters that have QA people looking for experience.