An actor is a type of user (for example, cardholder) that interacts with the system. Thus, there are three key things we need to know to describe a use case: Note: A use case describes how a type of user (or known as an actor) uses a system to achieve a particular user goal. The test planner can extract scenarios from the use cases for test cases. Use cases are also very helpful for writing acceptance test cases. Use cases are developed during requirements elicitation and are further refined and corrected as they are reviewed (by stakeholders) during analysis. Use case diagrams are used during requirements elicitation and analysis as a graphical means of representing the functional requirements of the system. A use case typically represents a major piece of (end-to-end) functionality that is complete from beginning to end. Melihat dan memutar presentasi PowerPoint secara online.Ī use case, a concept invented by Ivar Jacobson at 1992, is a sequence of transactions performed by a system that yields an outwardly visible, measurable result of value for a particular actor.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |