Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. What order of priority? [modified]

What order of priority? [modified]

Scheduled Pinned Locked Moved The Lounge
databasecsharpphpsql-servercom
23 Posts 14 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Raj Lal

    I see we do have 2nd and 3rd priority common, does that mean great minds think alike or what ;P

    Omit Needless Words - Strunk, William, Jr.


    Vista? Touch Screen Explorer with Pen Flicks here

    S Offline
    S Offline
    Shog9 0
    wrote on last edited by
    #21

    Well, it's like my dad always says... "Great minds think alike, and fools seldom differ" ;)

    ----

    It appears that everybody is under the impression that I approve of the documentation. You probably also blame Ken Burns for supporting slavery.

    --Raymond Chen on MSDN

    1 Reply Last reply
    0
    • C Colin Angus Mackay

      What order of priority would you normally put these when developing software? And why? In alphabetical order: * Customisability * Dependability * Maintainability * Performance * Reliability * Scalability * Security # Additional item * Usability #ADDITIONAL INFORMATION: Reliable: Uptime. When the software is available for use Dependable: That the software is stable and won't crash or is relatively bug free. i.e. Quality. #END ADDITIONAL INFORMATION If there are others you'd like to add to the list then please do. ALSO: No cheating, write out your list before looking at what others have replied. Finally, if any of these items don't fit your normal software development then feel free to leave them off. For example, if you never write user interface code then "usability" isn't likely to make your list. If you want to produce a list for each common situation then feel free to write up multiple priority lists. -- modified at 11:32 Thursday 26th April, 2007 -- modified at 11:35 Thursday 26th April, 2007


      Upcoming events: * Glasgow: Introduction to AJAX (2nd May), SQL Server 2005 - XML and XML Query Plans, Mock Objects, SQL Server Reporting Services... Never write for other people. Write for yourself, because you have a passion for it. -- Marc Clifton My website

      A Offline
      A Offline
      Aamir Butt
      wrote on last edited by
      #22

      My order would be: * Dependability * Usability * Maintainability * Performance * Security * Customisability * Reliability * Scalability

      "Some people believe football is a matter of life and death. I'm very disappointed with that attitude. I can assure you it is much, much more important than that. -- Bill Shankly"

      1 Reply Last reply
      0
      • C Colin Angus Mackay

        What order of priority would you normally put these when developing software? And why? In alphabetical order: * Customisability * Dependability * Maintainability * Performance * Reliability * Scalability * Security # Additional item * Usability #ADDITIONAL INFORMATION: Reliable: Uptime. When the software is available for use Dependable: That the software is stable and won't crash or is relatively bug free. i.e. Quality. #END ADDITIONAL INFORMATION If there are others you'd like to add to the list then please do. ALSO: No cheating, write out your list before looking at what others have replied. Finally, if any of these items don't fit your normal software development then feel free to leave them off. For example, if you never write user interface code then "usability" isn't likely to make your list. If you want to produce a list for each common situation then feel free to write up multiple priority lists. -- modified at 11:32 Thursday 26th April, 2007 -- modified at 11:35 Thursday 26th April, 2007


        Upcoming events: * Glasgow: Introduction to AJAX (2nd May), SQL Server 2005 - XML and XML Query Plans, Mock Objects, SQL Server Reporting Services... Never write for other people. Write for yourself, because you have a passion for it. -- Marc Clifton My website

        M Offline
        M Offline
        Mark II
        wrote on last edited by
        #23

        My ansewer: 1. Maintainability 2. Maintainability 3. Maintainability Maintainability above all things: If the application is maintainable, the other attributes can be added. If not, then one day the user's requirements will change and the application will become useless. 4. Usability Software exists for users, because users want to achieve something. Better software that users can actually use, even if it isn't perfect, than an application that is functionally correct but completely unusable. 5. Customisability 5. Dependability 5. Performance 5. Reliability 5. Scalability 5. Security Everything else follows from Maintainability and Usability. In essence: people first. Maintainability = usability for developers. My Blog: http://allwrong.wordpress.com[^]

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups