![]() ![]() Use Cases: A use case describes the actual functionality that can be performed with the component, like “Validate file,” or “Format code,” or “Convert a value from one unit to another.” There are two main types of use cases, concrete and abstract use cases.Ĭoncrete Use Case: A concrete use case defines functionality that the actor can use directly. Sometimes though, there could be other actors, possibly the “User.” The “User” is often seen as an actor in web components that the user directly interacts with, like the Calendar Tag component. Normally, for TopCoder components, the main actor is just an “Application”, as the components are normally libraries that use the component we are designing. It should describe, in simple terms, all major functionality that can be accomplished with a component Use Case ItemsĪ use case is made up of the following items:Īctors: Actors describe the item that uses the functionality of the component. Use Case DiagramsĪ use case diagram is a simple diagram that describes what can be done with the component. Throughout this tutorial we will focus on the File Validator component, using that component to show the right and wrong ways to create the use case and sequence diagrams. This article will cover the standard parts of each diagram and how they fit together, at the proper level, to create a diagram that will help developers and users. The goal of this article is to provide a good understanding of what use case and sequence diagrams are, how they are properly created, and how they can influence a design. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |