Sign In
Create Account
Follow Us on Twitter
Subscribe on Youtube
Hey frnds, I just started to do software development and have been wondering what would affect the product quality-- modularity, security, or maturity?
3 replies to this topic
Back to top|
|
|
#2
Posted 03 July 2010 - 12:29 AM
artificial
-
- Members
-
- 624 posts
Programming God
Hi!
Well, there are many things that affect the mentioned points. For example, an almost bug-free program, a good GUI and a proper manual affect the quality. To have a secure program, you have to use pointers properly and watch for errors.
These are just some points, but maybe you now have an idea of how it should be done.
Greets,
artificial
Well, there are many things that affect the mentioned points. For example, an almost bug-free program, a good GUI and a proper manual affect the quality. To have a secure program, you have to use pointers properly and watch for errors.
These are just some points, but maybe you now have an idea of how it should be done.
Greets,
artificial
Sometimes words ain't enough to express something. That's why computer scientists use double words.
#3
Posted 03 July 2010 - 02:54 AM
JCoder
-
- Members
-
- 245 posts
Programming Professional
- Programming language
- Libraries
- Programmer's abilities
- Tools
- Management
- Deadlines
- Salary
Pretty much everything.
- Libraries
- Programmer's abilities
- Tools
- Management
- Deadlines
- Salary
Pretty much everything.
#4
Posted 03 July 2010 - 03:22 AM
WingedPanther
-
- Moderators
-
- 16,831 posts
A spammer's worst nightmare
Programmer's mentality: is the goal to slap out the most immediately demanded feature, or to produce the family of features so that all the obvious variations are covered? Is the goal to get a product off the shelf as fast as possible, or to be thorough in its implementation?
Components/libraries: Many languages provide a basic set of components that, in all honesty, look pretty bad/dated. Having a few more components purchased can make a huge difference.
QA: Is there somebody going behind the programmers to "poke the code with a stick"? Programmers tend to test code the way it was meant to be used. QA people are more likely to try things like NOT entering the right type of data in a field. A good QA department that tries to break the software can make a huge difference.
As the product starts growing/maturing, failure to adhere to proven programming principle will start to make code more brittle. If code is NOT properly encapsulated, it becomes increasingly difficult to debug/fix. When first writing code, it is tempting to take shortcuts to get it out the door (start making a profit), but those shortcuts build up fast.
Security may or may not be an issue for a product. If you have a web-app with no security, you could be in for a nasty surprise when someone breaks in and destroys a customer's data. It's easier to build with security than add it in afterwards.
Ultimately, you also have to define what you mean by quality. Quality includes appearance, security, ease of debugging, feature set, etc, etc, etc.
Components/libraries: Many languages provide a basic set of components that, in all honesty, look pretty bad/dated. Having a few more components purchased can make a huge difference.
QA: Is there somebody going behind the programmers to "poke the code with a stick"? Programmers tend to test code the way it was meant to be used. QA people are more likely to try things like NOT entering the right type of data in a field. A good QA department that tries to break the software can make a huge difference.
As the product starts growing/maturing, failure to adhere to proven programming principle will start to make code more brittle. If code is NOT properly encapsulated, it becomes increasingly difficult to debug/fix. When first writing code, it is tempting to take shortcuts to get it out the door (start making a profit), but those shortcuts build up fast.
Security may or may not be an issue for a product. If you have a web-app with no security, you could be in for a nasty surprise when someone breaks in and destroys a customer's data. It's easier to build with security than add it in afterwards.
Ultimately, you also have to define what you mean by quality. Quality includes appearance, security, ease of debugging, feature set, etc, etc, etc.
