Considering the above it is safe to say that the user

This preview shows page 30 - 32 out of 44 pages.

Considering the above, it is safe to say that the user has some strengths. The ³rst strength is the fact that the user has a better understanding of what to be made and what reequipment needs to be considered for the system. The user also knows the limitation of the system such as what an application is for and what is the limitation for using it. However, the user doesn’t know how to develop a system and the solutions to the problems might be encountered throughout the process. The user also doesn’t understand what process needs to be implemented which could lead to so many miscommunications between the user and developer while the requirements are being met 280 words Permalink | Show parent | Reply Re: Week 2 Discussion Question by Jim Casale (Instructor) - Wednesday, 13 February 2019, 6:33 AM Sabawoon, How would a user "knows the limitation of the system such as what an application is for and what is the limitation for using it."? Wouldn't the developer know the limitations of the software? Jim 36 words Permalink | Show parent | Reply Re: Week 2 Discussion Question by Sabawoon Hanan - Wednesday, 13 February 2019, 2:56 PM Hello Professor,
01.04.2019 CS 2401 - AY2019-T3: Week 2 Discussion Question 31/44 Thanks for the feedback. What I meant is that the developer knows the limitation in terms of developing a system but the user will be the one to tell the developer what limits to consider while developing a system. 41 words Permalink | Show parent | Reply Re: Week 2 Discussion Question by Jim Casale (Instructor) - Tuesday, 12 February 2019, 9:25 AM All, This is a reminder that you should be providing feedback to any rating that is not a 10. Your peers need to know what they can do to improve their response. That does not however mean you give 10's when they are not warranted. Please look at this posting if you need more information. Jim 65 words Permalink | Show parent | Reply Re: Week 2 Discussion Question by Mohammad Maysam - Tuesday, 12 February 2019, 7:52 PM Strengths and weaknesses of users during the requirements elicitation activity Requirement gathering or requirement elicitation is the ³rst and the most important step towards creating an application, which leads to a solid written contract and paves the way for the programmers to start on developing of the program. This activity has some strengths and weakness for the user and developer and here I will discuss them from the User’s perspective (Marsic, 2012). The most important strength of elicitation activity for the user is that they get to present their needs in simple statements without having to be worried about the semantics, terminologies or any speci³c knowledge of programming. Also, at this step the user can ask all the question that they might have or even ask for some temples, diagrams or graphs to make sure their points are clearly made. However, the weaknesses of user is that in most cases, the users are not speci³c enough and do not know exactly what they want. Most users

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture