Use Case Approach to Software Testing
The product use case specifies the sequence of communications between the system and the external actor. The actor can be another software system, hardware appliance or a person that interacts with the system with the aim to achieve a certain objective. Another name for the actor is the user role, since this is the role that members of one or more user classes can take on with regard to the system. For instance, the actor can be an employee who placed the order for the chemical participates in the use case “Chemical Tracking System”. There is no class of users of the Chemical Tracking System with this name. Both chemists and specialists working in chemical warehouse can request chemicals, so members of any of these classes can play the role of an Employee who placed an order for a chemical.
The concept of “use case” came from the world of object-oriented programming. Nevertheless, use cases are suitable for projects where any development techniques are used, since users do not care how the software is created. The use cases lie at the heart of the widely used Unified Software Development Process.
People who cannot stand security vulnerabilities tend to use penetration test service. It is one of the most reliable ways to get rid of unauthorized users aiming to access your computer features!
Use cases change the traditional approach to information gathering. Users are not asked, as before, what from their point of view, the system should do. Nowadays there is a tendency to discover what tasks the user is going to solve with the help of the system. The purpose of this approach is to describe all such problems. Prior to including each use case in the approved version of the requirements, the stakeholders ascertain that it does not go beyond the project boundary. Theoretically, the final set of use cases should include all the desired functionality of the system. In practice, you are unlikely to achieve 100% result, but use cases will help you more fully accomplish this task than any other method of collecting information that many testing experts have ever used.
Use-case diagrams allow to you can get an excellent visual representation of the user requirements.
The use case modeling is intended primarily to identify the functional requirements of a system and it is a basis for the entire development process. All major activities such as analysis, design, testing are performed on the basis of use cases. During analysis and design phases, use cases let you understand how the outcome expected by the user impacts system architecture and how the system components should behave so that to implement the user-specific functionality.