How JustAnswer Works:
  • Ask an Expert
    Experts are full of valuable knowledge and are ready to help with any question. Credentials confirmed by a Fortune 500 verification firm.
  • Get a Professional Answer
    Via email, text message, or notification as you wait on our site. Ask follow up questions if you need to.
  • 100% Satisfaction Guarantee
    Rate the answer you receive.
Ask Jane T (LLC) Your Own Question
Jane T (LLC)
Jane T (LLC), Former straight A Student - Now Mom
Category: Homework
Satisfied Customers: 8435
Experience:  Degrees in Eng., econ; JD (law), MBA, former valedictorian & winner of academic scholarship
Type Your Homework Question Here...
Jane T (LLC) is online now
A new question is answered every 9 seconds

Drawing upon your knowledge of software development,

This answer was rated:

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? Explain your answer.


To say which part of the software development process is most important is almost like asking which of a car's four tires is most important. Clearly, all elements involved in software development are necessary and critical to its success. However, if forced to select one that I consider most important, that one would have to be the requirements phase. As the building block of the entire process identifying the requirements and then setting the scope of the development process through those requirements is key to the success of a project. If the requirements are improperly defined or identified, then it will not matter whether the design, the coding, or the testing phase proceed perfectly because the project will not do what it is expected to do nor what the customer wants it to do.

Jane T (LLC) and other Homework Specialists are ready to help you
Customer: replied 9 years ago.
Would improperly defined or identified requirements not be discovered during the testing phase? For instance, if the program does not perform a certain task as required by the client, then the program failed the test. Poor requirements gathering also exposes the analyst in charge of gathering the requirements, or the "subject matter expert" that provided the improper information to the analyst, but is not an indication that the project is necessarily a failure. Testing the software, before it is used for production, will expose any inadequacies in the development process.

You need to spend $3 to view this post. Add Funds to your account and buy credits.
Customer: replied 9 years ago.