1. How do use cases relate to the requirements stated in the requirements determination? In order to know what application will best meet your needs, it is necessary to first specify the requirements for the application. One commonly accepted way to document these requirements is the Use Case approach. Use cases are used during requirements analysis to identify, clarify, and organize requirements. A use case is made up of a set of possible sequences of interactions between the application and users in a particular environment and related to a particular goal. Specifically, a use case is a single task, performed by the end user of a system that has some useful outcome and should contain all system activities that are of significance to the users and can be thought of as a collection of possible scenarios related to a particular goal; the use case and goal are sometimes considered to be synonymous. A use case is written in a way that both non-technical and technical audiences can understand and its focuses on what things the users have to do to solve the problem. Inside the use case we define the purpose of the activity, the actors involved (end users, systems, etc.), the actions and responses, and the end result. 2. Describe the elements of the use case’s basic information section?
Each use case is identified by a unique name and number. An importance level tends to be a subjective priority ranking in relation to the entire system. The primary actor is an external user in which the system will respond to. Other major elements include triggers. These are classified as external or temporal.
3. What is the purpose of stating the primary actor for the use case? A primary actor is the Actor(s) using the system to achieve a goal. The Use Case documents the interactions between the system and the actors to achieve the goal of the primary actor.
The use case is a collection of possible scenarios between the system under discussion and external...