From your point of view, describe the strengths and weaknesses of users
during the requirements elicitation activity. Describe also the strengths and
weaknesses of developers during the requirements elicitation activity.
Elicitation activity can be described as the process of gathering and putting
together of information that which is paramount in the process of software
development. This whole process is very key for the developer so that he/she
understands the business context. The customer has to define what they
need in detail so that the developer can come up with a working solution.
The advantages to the user are:
1. Helps the user describe in detail what exactly they want
2. The user will be able to describe where the solution will be used
therefore solving an urgent need
Disadvantages to the user include:
1. The user might not fully explain what exactly they need
2. The user might not understand the solution needed to address a
problem therefore the provided solution might not work well when
deployed.
Strengths for the developer are:
1. The developer will be able to come up with a great solution provided
that the client gave a detailed to the problem being addressed.
2. The developer will be in a position to provide a detailed knowledge of
formal languages to provide the possible solutions
Disadvantages to the developer might be:
1. In the event that the user provides insufficient information then the
developer will come up with something that might not work, in this
case the developer will have wasted lots of time.
2. A developer with a poor knowledge of the problem to be solved might
come up with a system that might not be beneficial to the user.
For both parties to come up with a solution that is both beneficial to the user
and solves the problem then both parties must have a good knowledge of
what is needed to be solved. The user has to fully explain to the developer
how exactly they want then the developer has to use his/her knowledge to
build a great solution.
Reference
V. S., Dr. (2012, August 11). Requirement of Elicitation Techniques. Retrieved
July 1, 2018, from
http://www.umsl.edu/~sauterv/analysis/6840papers_f12/Chen/index.html
during the requirements elicitation activity. Describe also the strengths and
weaknesses of developers during the requirements elicitation activity.
Elicitation activity can be described as the process of gathering and putting
together of information that which is paramount in the process of software
development. This whole process is very key for the developer so that he/she
understands the business context. The customer has to define what they
need in detail so that the developer can come up with a working solution.
The advantages to the user are:
1. Helps the user describe in detail what exactly they want
2. The user will be able to describe where the solution will be used
therefore solving an urgent need
Disadvantages to the user include:
1. The user might not fully explain what exactly they need
2. The user might not understand the solution needed to address a
problem therefore the provided solution might not work well when
deployed.
Strengths for the developer are:
1. The developer will be able to come up with a great solution provided
that the client gave a detailed to the problem being addressed.
2. The developer will be in a position to provide a detailed knowledge of
formal languages to provide the possible solutions
Disadvantages to the developer might be:
1. In the event that the user provides insufficient information then the
developer will come up with something that might not work, in this
case the developer will have wasted lots of time.
2. A developer with a poor knowledge of the problem to be solved might
come up with a system that might not be beneficial to the user.
For both parties to come up with a solution that is both beneficial to the user
and solves the problem then both parties must have a good knowledge of
what is needed to be solved. The user has to fully explain to the developer
how exactly they want then the developer has to use his/her knowledge to
build a great solution.
Reference
V. S., Dr. (2012, August 11). Requirement of Elicitation Techniques. Retrieved
July 1, 2018, from
http://www.umsl.edu/~sauterv/analysis/6840papers_f12/Chen/index.html
