software development,

Tags:
Development
Software Quality
Drawing upon your knowledge of software development, which process requirements, design, coding, or testing do you think has more impact on the overall success and quality of development?

Answer Wiki

Thanks. We'll let you know when a new response is added.

I can’t narrow it down to one, but I think it would be requirements and testing.

The requirements should go beyond capturing functional application requirements and capture the expectations of the customer as well give feedback up front on what is not possible and what the end product is going to look like. For this, its essential to capture the requirements in the areas of availability, performance, security etc.

Testing : Should make ensure all requirements are met and should include load, stress, volume testing.

That should ensure that the customer has the right expectations and that the product meets the expectations.

*****************************************
All have sequential, serious and equal impact on the product but if you see an incomplete or wrong process requirements document will lead to a poor design which even if leads to a good coding and good testing has a little value overall. So the initial processes have to be very clear and complete so that the recursive effect on the project is least.

Discuss This Question: 1  Reply

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Emvee
    Requirements very important. Testing too. Some systematic approach to development,whether waterfall, or agile, depending on circumstances, but must be realisitic. 'Must be realistic' is where it starts. Most software quality problems have the same cause: too much time pressure to deliver without having been realistic about requirements and resources. Managers pick deadlines out of thin air and they become 'carved in stone'. Then everyone fixates on deadline and quality suffers. Very old story.
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following