Academic Integrity: tutoring, explanations, and feedback — we don’t complete graded work or submit on a student’s behalf.

Use cases are simple representations of a person\'s understanding of a process t

ID: 3898435 • Letter: U

Question

Use cases are simple representations of a person's understanding of a process to be modeled by the system. In relation to this statement, answer the following questions:

An overly simplified set of documents can cause some problems. Evaluate this statement and explain your stand.


Discuss at least three ways in which you think use cases may hinder the development process.


Use cases are not the best approach as a method of representing processes. Can you state any situations? What aspect of the situation would make use cases not the perfect solution? Please give enough information in your answer to set the stage for your example. Also state any assumptions that you are making.


Use cases are a means of communication to nontechnical stakeholders. In Weeks 1 and 2, we analyzed different ways of eliciting requirements as well as several types of people who may be involved with the development of the new system. Do you think that use cases should reach anyone who was involved in the requirements elicitation process (such as employees you interviewed) or just key stakeholders? Discuss your opinion, justifying your answer.


Part 2
UML is a tool that enables people to easily exchange information, but it is not necessarily the only tool. Discuss at least three reasons you think are significant enough to let a company choose a solution other than UML for their needs. Justify your answers..

Explanation / Answer

Answer)

Overly simplified documents would help to understand the subject better, especially for non-technical person , it can even identify the exceptional scenario's and can be used for many software developments where as it might lose out on the functionality part which would cause the biggest problem.

Ways in which use case can hinder the process are:

1) Might lacks functionality requirements

2) Definitely lacks non-functional requirements

3) Learning curve is created for developers as well as client.

Use case would not be the best aspect when non-functional requirements are taken into consideration.

USe case can be used for any for example stake holder, employee and managers, those who are to be required in the discusssion process.

Hope this answer helps. Happy to help. :)