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.
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..
- Post your response to the Discussion Area by the due date assigned. Respond to at least two posts by the end of the week.