Discussion:
OmegaChart ver 4.0 beta tester wanted
(too old to reply)
Larry Chen
2008-12-17 23:31:26 UTC
Permalink
Dear friends,

Omega Charting Services is now looking for beta tester for their
software product "OmegaChart ver 4.0" and give away the beta version at NO
CHARGE.

OmegaChart ver 4.0 is a Source Code to Flow Chart generator. This
package converts a source code (FORTRAN, VB family of languages and MATLAB
m-file ) to their FlowChart equivalence. The generated flowchart is viewable
through Microsoft Excel, Microsoft Internet Explorer or Microsoft Visio.
OmegaChart 4.0 is a useful tool for untangle behind-the-scenes programming
logic in a messy spaghetti code and generate
visual documentation of the execution logic. While most other analysis tools
only provides you "assembly level" info such as calling trees or variables
cross referencing, OmegaChart provide detailed "module level" logic such as
loops, if-elseif-endif constructs and select-case constructs. With
OmegaChart, you can painlessly minimize the use of GOTO's and therefore
"modernize" your code. Whether you are a programmer, a program analyst or a
software maintain personnel, OmegaChart is a "MUST HAVE" tool to ease your
life and boost up productivity. It can relief you hundreds or even thousands
hours of headache.

OmegaMath is a specialized module of OmegaChart which is capable of
performing statement-level analysis of source code. One-dimensional coding
expressions can be converted, via OmegaMath, to their original
two-dimensional mathematical counter part. Expressions with the radical
symbol, superscript and/or fractions provide a more vivid view of the
mathematical contents behind the program code.

To become a beta tester, please download the package from our web site

http://home.comcast.net/~lchen223621/OC40Beta3.zip and test it out.

( free registration, please notify us that you are beta tester in your email
subject line
email: ***@yahoo.com ).

After test it out, please reply us with

1. three things you like about OC4.0
2. three things you dislike about OC4.0
3. subroutines ( or functions ) that crashes OC4.0 ( as many as possible,
at lease 5 )

The testing is on your own risk. Upon finishing the testing period, you
will get a copy of
the release version (value $200 - $300) as reward.

Only limited tester position is available, so ACT NOW !!! Thank you and
have a great day.


Larry Chen



OmegaChart ver 4.0 beta tester wanted
Michael Mattias
2008-12-17 23:45:43 UTC
Permalink
Post by Larry Chen
Omega Charting Services is now looking for beta tester for their
software product "OmegaChart ver 4.0" and give away the beta version at NO
CHARGE.
......
Post by Larry Chen
After test it out, please reply us with
3. subroutines ( or functions ) that crashes OC4.0 ( as many as possible,
at lease 5 )
Call me a purist but if you expect five functions to "crash", this product
is not ready for "beta" yet.
--
Michael C. Mattias
Tal Systems Inc.
Racine WI
***@talsystems.com
Tom Lake
2008-12-18 15:28:22 UTC
Permalink
Post by Michael Mattias
Omega Charting Services is now looking for beta tester for their software
product "OmegaChart ver 4.0" and give away the beta version at NO CHARGE.
......
After test it out, please reply us with
3. subroutines ( or functions ) that crashes OC4.0 ( as many as possible, at
lease 5 )
Call me a purist but if you expect five functions to "crash", this product is not
ready for "beta" yet.
Maybe not a purist but reading skills could use improvement! 8^)

He's not saying five will crash the system, he's saying he wants at least
five examples of subs or functions that crash the system. Or at least I
*think* that's what he wants!

Tom Lake
Michael Mattias
2008-12-18 15:34:50 UTC
Permalink
Post by Tom Lake
Post by Michael Mattias
Post by Larry Chen
Omega Charting Services is now looking for beta tester for their
software product "OmegaChart ver 4.0" and give away the beta version at
NO CHARGE.
......
Post by Larry Chen
After test it out, please reply us with
3. subroutines ( or functions ) that crashes OC4.0 ( as many as
possible, at lease 5 )
Call me a purist but if you expect five functions to "crash", this
product is not ready for "beta" yet.
Maybe not a purist but reading skills could use improvement! 8^)
He's not saying five will crash the system, he's saying he wants at least
five examples of subs or functions that crash the system. Or at least I
*think* that's what he wants!
No redirect, your honor.

Counsel has made my point for me that author is EXPECTING at least five
functions to "crash." It is the prosecution's contention that such
expectations prima facie demonstrate the unreadiness of the product for
"beta" testing.

The prosecution rests. (Again).

MCM
Larry
2008-12-18 16:31:57 UTC
Permalink
Post by Michael Mattias
Post by Michael Mattias
   Omega Charting Services is now looking for beta tester for their
software product "OmegaChartver 4.0" and give away the beta version at
NO CHARGE.
......
After test it out, please reply us with
 3. subroutines ( or functions ) that crashes OC4.0 ( as many as
possible, at lease 5 )
Call me a purist but if you expect five functions to "crash", this
product is not ready for "beta" yet.
Maybe not a purist but reading skills could use improvement!  8^)
He's not saying five will crash the system, he's saying he wants at least
five examples of subs or functions that crash the system.  Or at least I
*think* that's what he wants!
No redirect, your honor.
Counsel has made my point for me that author is EXPECTING at least five
functions to "crash." It is the prosecution's contention that such
expectations prima facie demonstrate the unreadiness of the product for
"beta" testing.
The prosecution rests. (Again).
MCM- Hide quoted text -
- Show quoted text -
Well, Every software has some sort of bugs. What we really looking
for the the 5 buggy subroutines, out of , for example, 10000
subroutines tested.

Larry
Michael Mattias
2008-12-18 18:53:18 UTC
Permalink
Post by Larry
Well, Every software has some sort of bugs. What we really looking
for the the 5 buggy subroutines, out of , for example, 10000
subroutines tested.
10,000 subroutines? Ten Thousand?

You seriously expect a beta tester to try TEN THOUSAND routines?

My point is more, maybe you do expect "some number" of failures during beta
test.... but giving beta testers a suggested quota is silly.
I am just in the process of sending out a beta test. I expect the testers to
find one or two errors. Last time I did this I expected one, but got three.

Beta testers do not expect to do alpha/unit testing; they are expected to
"use the products normally, report and don't be shocked by any problems."
Your alpha testing should have already tested all 10,000 routines at least
once.

Me? If I tried 50 routines and found five failing, I could only assume that
ten percent of all routines fail.... in your case, that would be one
thousand bugs. Call me a wimp, but if I thought there were 1,000 bugs in a
piece of software, I'm pretty sure I'd be looking for a different product.

Of course, the number of errors you can tolerate is inversely proportional
to the number of users you will have to upgrade when errors are found. So if
you have a relatively small number of users, you can probably deal with more
errors in what you release.
--
Michael C. Mattias
Tal Systems Inc.
Racine WI
***@talsystems.com
Larry
2008-12-19 00:21:50 UTC
Permalink
Post by Michael Mattias
Post by Michael Mattias
   Omega Charting Services is now looking for beta tester for their
software product "OmegaChartver 4.0" and give away the beta version at
NO CHARGE.
......
After test it out, please reply us with
 3. subroutines ( or functions ) that crashes OC4.0 ( as many as
possible, at lease 5 )
Call me a purist but if you expect five functions to "crash", this
product is not ready for "beta" yet.
Maybe not a purist but reading skills could use improvement!  8^)
He's not saying five will crash the system, he's saying he wants at least
five examples of subs or functions that crash the system.  Or at least I
*think* that's what he wants!
No redirect, your honor.
Counsel has made my point for me that author is EXPECTING at least five
functions to "crash." It is the prosecution's contention that such
expectations prima facie demonstrate the unreadiness of the product for
"beta" testing.
The prosecution rests. (Again).
MCM- Hide quoted text -
- Show quoted text -
1. I have more than 100 beta testers.
2. In avarage, everyone only need to test 100 subroutines or
functions.
3. usually, a "real world" program easily exceed 50 subroutines or
functions.
4. The beta testers only need to test our product in their "NORMAL
USAGE", say, 1 or 2 program packages.
5. 95% of the routine tested did not fail OmegaChart. I need to CATCH
the rest.
6. Do your math!

Loading...