What was found was that the use case diagrams conveyed the intent of the system in a more simplified manner to stakeholders and that they were "interpreted more completely than class diagrams". Siau and Lee conducted research to determine if there was a valid situation for use case diagrams at all or if they were unnecessary. The drawings attempt to mimic the real world and provide a view for the stakeholder to understand how the system is going to be designed. ![]() ĭue to their simplistic nature, use case diagrams can be a good communication tool for stakeholders. But in my particular case I think it fit better in the 'System overview'. ![]() A use case diagram should be the graphical representation of a requirement, so put it in that section seems fine. It has been said before that "Use case diagrams are the blueprints for your system". With Piktochart, you can create professional-looking infographics, flyers, posters, charts, videos, and more. Regarding use-case, in my opinion the level of detail it reaches can tell whether to put it in the 'System overview' rather than 'Specifications requirements'. While a use case itself might drill into a lot of detail about every possibility, a use-case diagram can help provide a higher-level view of the system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |