System Requirements
Results 1 to 6 of 6

Thread: System Requirements

  1. #1
    Senior Member
    Join Date
    Jun 2002
    Posts
    148

    System Requirements

    I have been woundering this for quite some time now. How does a software developer develop a list of Minimum system requirements. When I download software they tell me how much RAM I need, The minimum CPU speed, and other simular information.

    How Can I develop a list of minimum system requirements for software I develop?
    In snatches, they learn something of the wisdom
    which is of good, and more of the mere knowledge which is of evil. But must I know what must not come, for I shale become those of knowledgedome. Peace~

  2. #2
    er0k
    Guest
    well you need to know what speed your program runs at, how much it caches, etc.. you may even need to test it on really slow proc's/RAM and see what it can handle. there are tools out there that will allow you to run your program to see how fast it runs, and what can handle it.. id just google around until i found something. good luck.

  3. #3
    Senior Member
    Join Date
    Nov 2002
    Posts
    606
    ele5125,

    er0k is right, follow his steps and it could be a good idea to have some people testing your programs (friends), sometimes you can't or shouldn't be your own "tester" because you don't see "problems" or "little problems" in your own work, so, if you can, give the program to different friends to test it (as er0k said, better if they have different OS and processors) and ask them to, after the time you think it coulbe be enough, tell you what they think about your software. Good luck !!!

    -DaRK-RaiDeR-

  4. #4
    Senior Member
    Join Date
    Jun 2002
    Posts
    148
    Thank you everone, I have a few friends who can test for me. I will look around for such a program that can put my program through the worst case analysis. I remember in eletronics we did alot of worst case senarios when designing circuits. Thanks.
    In snatches, they learn something of the wisdom
    which is of good, and more of the mere knowledge which is of evil. But must I know what must not come, for I shale become those of knowledgedome. Peace~

  5. #5
    The Iceman Cometh
    Join Date
    Aug 2001
    Posts
    1,209
    When you develop a program, you should also do a thorough algorithm analysis to determine how much processing power, memory, virtual memory, etc., you need during both best case and worst case scenarios. For instace, if you are writing some sort of file cataloging system, the program will react differently to small and large inputs. For large programs, especially ones you wish to commercialize, such steps are necessary to ensure that if a user happens to hit the worst case scenario, the program doesn't die on them. Furthermore, if you do plan to make your program public, run through both Alpha and Beta tests, with a diverse group of people (other than just friends) who can give you unbiased feedback from a wide range of hardware/software platforms. Just my 2 cents.

    AJ

  6. #6
    Leftie Linux Lover the_JinX's Avatar
    Join Date
    Nov 2001
    Location
    Beverwijk Netherlands
    Posts
    2,534
    I usualy test my software by giving it to (about 8) friends of mine, to test it on various Win-Versions and processors / graphiccard etc configs..

    But usualy I just make up the minimum system requirements.. like stating it'll run on a PII 300 up while it will (tested) run on a 200...

    ___________________
    Some things are liquid..
    ASCII stupid question, get a stupid ANSI.
    When in Russia, pet a PETSCII.

    Get your ass over to SLAYRadio the best station for C64 Remixes !

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •