![]() Elaboration is typically done using an activity diagram which describes how the interaction between the actor and the system proceeds, eg Poster initiates post System checks poster's privileges System rejects post if privileges are insufficient etc. The next step is to elaborate your use cases, and that's where you can start talking about conditions. The number of use cases does not translate directly into system complexity, and a large number of clearly defined use cases is better than a small number of large, ambiguous ones. You should not be overly concerned with the number of use cases at this stage. To a person using a forum, it does make sense that creating a post is a separate activity from updating one (or responding to one), so that seems like a sensible start to me. You want to keep that description simple and succinct.Įach use case should in some way make sense to the actor. ![]() A set of use cases is intended to provide an overview of the system's functionality, and each use case describes an interaction between the system and one or more actors. You shouldn't get into conditions and ifs and buts in use cases diagrams.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |