Use Cases in object oriented
What a complicated and simple concept lets crumble step by step. First let me give you some definitions:
«a behaviorally related sequence of transactions in a dialogue with the system»
Jacobson et al. Object oriented software engineer 1992 [15]
«a description of set or sequence of actions, including variants, that a system performs that yields an observable result of value to a particular actor»
Rational Unified Process
Basically the general idea of a use case is that you can represent intended sequences between the system and all the world outside them. Easier, there are the steps that the real user have to do in the process of a solution for example:
The concept of a use case can help designers develop better object-oriented solutions for embedded systems applications. Use cases are abstractions of interrelated events or interaction sequences. By analyzing applications in terms of use cases and organizing the software functionality on the same basis, separating functionality into three distinct types of object modules, software can be made more robust, with components that are both more reusable and more amenable to change.
do you want to be a pro? che out this video. Its a little longer but its only for pro´s check it out in parts if you want
references:
Haz clic para acceder a CRPITV4Biddle.pdf
Credits to the outstanding image:
Pixabay
recovered of https://www.pexels.com/photo/painting-and-drawing-tools-set-207665/
Understated Chaos 