![]() The following should be textually analysed and a use case diagram created containing several use cases. First we’ll draw a use case diagram from a plain English description, then build on it using textual use cases. Try the following exercises (from IRM’s Modelling Requirements with Use Case & the UML workshop) to test your skills. Textual use cases can be both formal and informal. To keep things simple we’ll stick to use case diagrams and textual use cases. They will generally be accompanied by a textual use case and if they’re complex, may also have a supporting activity diagram to show what’s going on “inside” the use case. When producing project documentation, use case diagrams are rarely used on their own. ![]() “It’s all very well drawing a picture” they say but what about the details – what’s actually going on? Many business analysts and business users get frustrated at the perceived lack of information in a use case diagram. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |