When new system analysts come in, they are likely to cause a number of problems before they can fully adapt to their new environment. These problems are mostly as a result of the errors that they make. There are quite a number of errors that a new system analyst can make. One of these errors is making assumptions. Although everyone makes assumptions, they are however rarely documented. The problem with this error is that bad assumption can be made and they become a threat. Many new system analysts assume that Use Cases are at all time sufficient (Whitten and Bentley 237). Since they can be understood very easily, and they also provide a focus on the functionality of a system, a system analyst can easily assume that it is sufficient enough. Another error made by new system analysts is that they can at times document a constraint as being a requirement. This error mostly occurs when stakeholders start asking questions on the manner in which things are working.
Question Number: 2
What are the potential consequences of this error?
As noted earlier, assumptions can make a new system analyst to cause some problems. Other than just causing problems, new system analysts that are used to assuming things can as well cause misunderstandings while solving a problem. For instance, if the system analyst fails to do some calculations that are considered to be a requirement, those who are under him or her may start thinking that the system analyst is not qualified for his or her position (Alexander, Smith and Norton). Another consequence that may result from assumptions on the part of a system analyst is that assumptions may hinder creativity. A system analyst that is found of making assumptions, places limits to his or her actions and imaginations. Such a system analyst shuts off various possibilities that would have otherwise brought something new. They assume that things have to be done in a particular manner and they forget the reason as to why they have to be done in that manner.
Question Number: 3
What tool can be used to help avoid this problem?
There being consequences associated with making assumptions, it would be important for a new system analyst to try and avoid making assumptions (Whitten and Bentley 237). One way that a system analyst can avoid making assumptions is by surveying his or her own emotions. Before he or she can have a conversation those who are under him, it is important that he or she takes an investigation of the information that he/she has already collected, and determining if the information is informing the way that he or she fills. Another way in which a system analyst would avoid making assumptions is by him or her to start getting curious. Whether in a meeting or simply having a passing conversation, it is important to be disciplined as this is an art of being curious.
- Do you feel comfortable with the concepts of the question? If not, how can I help you understand it better?
No, I do not fill comfortable with the concept of the question. To help get a better understanding, I would suggest that you consider involving and informed professional. Having a one on one discussion with a system analyst in an organization would greatly contribute to my understanding.
- Does the content of the question relate well to the area of the text you are studying this week?
Yes, the content of the question have relate well with the area that I am studying. The questions have enabled me to do more research on my area of study.