What order of priority? [modified]
-
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
Usability (we are nothing if it is not used) Performance (we are just the average joe, if we are not fast) Dependability \_ I put these two as equal Reliability / Customisability Maintainability Scalability However, they are all very important, the gap would be minor. Usability and Performance are a must. I've had that argument before. We can make some negotiations here and there, but if you run 10% in performance because it is easy to write/maintain, rewrite it. This has long been my issue with mutexes. They are easily abused tools. They are necessary, but if used too often you lock-step your threads and you have the performance of a single core, plus the overhead of the additional lock-sleep-wake events. In that case you might as well have written it as a single thread and didn't need all the mutex overhead. Thus I have been accused of hating mutexes. Just me...
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
What is the difference between reliable and dependable?
Gary Kirkham Forever Forgiven and Alive in the Spirit He is no fool who gives what he cannot keep to gain what he cannot lose. - Jim Elliot Me blog, You read
Gary Kirkham wrote:
What is the difference between reliable and dependable?
now that everyone asks... I guess I should have asked.... I associate Reliability on the software, I associate dependabiltiy on the team that supports the software (fixing bugs, adding customer features) but I should have asked too since they really mean the same.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
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
Where's security on that list?
-
What is the difference between reliable and dependable?
Gary Kirkham Forever Forgiven and Alive in the Spirit He is no fool who gives what he cannot keep to gain what he cannot lose. - Jim Elliot Me blog, You read
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.
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
-
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.
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
But isn't, Uptime == software is stable and won't crash
Gary Kirkham Forever Forgiven and Alive in the Spirit He is no fool who gives what he cannot keep to gain what he cannot lose. - Jim Elliot Me blog, You read
-
Where's security on that list?
I was waiting for someone to spot that!... :-O Honest :-D
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
-
But isn't, Uptime == software is stable and won't crash
Gary Kirkham Forever Forgiven and Alive in the Spirit He is no fool who gives what he cannot keep to gain what he cannot lose. - Jim Elliot Me blog, You read
Gary Kirkham wrote:
Uptime == software is stable and won't crash
I can see what you are getting at. A crash could be so severe that it takes the whole process or server with it. But, I was thinking more about scheduled maintenance. How does it impact the users? If the software can be designed so that it is all done out of hours then great. But sometimes (24hr ecommerce sites) might need to schedule downtime during normal opening hours. Sure the definitions are a bit vague, but I'm hoping people would define what they mean by that also.
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
-
Gary Kirkham wrote:
Uptime == software is stable and won't crash
I can see what you are getting at. A crash could be so severe that it takes the whole process or server with it. But, I was thinking more about scheduled maintenance. How does it impact the users? If the software can be designed so that it is all done out of hours then great. But sometimes (24hr ecommerce sites) might need to schedule downtime during normal opening hours. Sure the definitions are a bit vague, but I'm hoping people would define what they mean by that also.
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
OK, thanks for clarifying. So, to somewhat answer your question, I tend to look at software from the point of view of the user and to me the most important things on your list are usability and reliability/dependability. The other things are important, but if you don't get these right, then the other stuff doesn't really matter. 2 cents worth, not expecting change. :)
Gary Kirkham Forever Forgiven and Alive in the Spirit He is no fool who gives what he cannot keep to gain what he cannot lose. - Jim Elliot Me blog, You read
-
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
Colin Angus Mackay wrote:
In alphabetical order
Yes.
-
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
Eye candy. And no, that's not the same as usability :)
"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus "Real men use mspaint for writing code and notepad for designing graphics." - Anna-Jayne Metcalfe
-
But isn't, Uptime == software is stable and won't crash
Gary Kirkham Forever Forgiven and Alive in the Spirit He is no fool who gives what he cannot keep to gain what he cannot lose. - Jim Elliot Me blog, You read
Well... Uptime == operating system is stable and won't crash and since we can rule out Windows ... X|
-
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
Primary Importance =-=-=-=-=-=-=-=-=-= reliability / dependability / Security / Maintainability (The first two are the same thing and the others are all part of the same thing so they are all on a level together and inseperable) Supportability should be in this top tier as well but you didn't mention it, it's critical. Secondary Importance =-=-=-=-=-=-=-=-=-=-= Usability / performance / scalability (these again are all equal in my opinion but secondary) Custimization is in here as well but it's application dependant, in some apps it's not optional, in others it is. In the optional class of apps I would put it last. I haven't read the other responses yet, but anyone who doesn't put reliability and maintainability near the top I wouldn't hire to write a screensaver.
"110%" - it's the new 70%
-
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
- Me ('cause if i hate what i've written, how can i in good conscience inflict it on someone else?)
- Maintainability (if it falls apart when left alone, i don't want it. See also: why i dumped SQL Reporting Services)
- Usability (i don't want it if i can't use it)
- Performance (to the extent that it effects usability)
- Reliability (though i kinda think this fits into usability; hard to be usable if it's unavailable)
- Dependability (this really fits into usability, but i'll rank it lower 'cause frankly if it ain't usable i don't care how dependable it is)
- Scalability (i always kick myself for not ranking this higher... but then, i still never rank it higher)
- Security (let your children run wild and free... Naw, but realistically it was most secure before i wrote it.)
- Customisability (to the extent that it can improve usability)
----
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
-
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
IMO 1. Customisability: if you mean extensibility, the most important , right now software and service becomes much more usable if it can talk to other software and service easily i.e. EXTEND ITSELF functionality makes it much more valuable than an island application 2. Usability: if you mean "Ease of Use" of the end product for the customer/client 3. Maintainability: another important one, you should be able to make changes to your work EASILY after say 6 months Then rest of the stuffs , in what ever order [added] the application or the above three priorities dictates [/added] btw its a very nice question to introspect -- modified at 14:55 Thursday 26th April, 2007
Omit Needless Words - Strunk, William, Jr.
Vista? Touch Screen Explorer with Pen Flicks here
-
- Me ('cause if i hate what i've written, how can i in good conscience inflict it on someone else?)
- Maintainability (if it falls apart when left alone, i don't want it. See also: why i dumped SQL Reporting Services)
- Usability (i don't want it if i can't use it)
- Performance (to the extent that it effects usability)
- Reliability (though i kinda think this fits into usability; hard to be usable if it's unavailable)
- Dependability (this really fits into usability, but i'll rank it lower 'cause frankly if it ain't usable i don't care how dependable it is)
- Scalability (i always kick myself for not ranking this higher... but then, i still never rank it higher)
- Security (let your children run wild and free... Naw, but realistically it was most secure before i wrote it.)
- Customisability (to the extent that it can improve usability)
----
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
-
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
-
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
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
-
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
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"
-
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
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[^]