![]() ![]() I avoid use cases strongly, whenever possible (although I personally like them). Sequences can now be build using domain objects, connecting 2 views - customers' and developers'. User stories fit perfectly in this modelling set, you can even make them less formal and more high-level, as the rest will fill the information gap. UI Prototypes as well, so they can see how they business maps to screens.īehind the curtains, I like to support activities with a formal and accurate domain class model, invisible to customers of course, but open to developers and making a nice technical backbone of the future system. I suggest the mix of UML activity diagrams and user interface prototypes (non UML) as far the best tool to work on this level of analysis with non technical business people.Īctivities model their business in an intuitive, easy to understand and clear way. And when they are finally approved, you're never sure whether the customers actually understood them correctly. They are too abstract and complicated even for the most of developers. In my opinion, what works best with the customers are not use cases. Put active objects to the left/top and passive ones to the right/bottom. Express the flow from left to right and from top to bottom. Some examples of tools for creation of sequence diagrams:, , you can Google out many more examples both free and payed both online and offline Include only those attributes of the objects that are relevant.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |