None isn't and none will be any time soon. If you are not required by contract to use it, then - for Gods sake - go write code and document it well and not spend too much time pondering which modeling thingy is most hip now. Maybe hire consultants to verify if you are doing it right. If your client requires BPMN, then well - read on it and learn it well. Business Process Model and Notation (BPMN) is a standard for business process modeling that provides graphical notation for specifying business processes in a Business Process diagram (BPD), based on traditional flowcharting techniques. The elements can be given a name and detailed descriptions can be added to the notes. It is sort of understood by the community and all ambiguity you can always rewrite in plain English. Activity diagrams can be used to model Business Processes as a UML. If you need to share the doc with others, UML seems like a good choice. It will be faster than going through pages of spec written by experts from OMG (Object Management Group, though Oh My God is not a bad explanation either -)). If you are doing this for yourself, you may just as well use your own notation made up ad hoc. Majority of developers heard only of UML and even that is not really well understood, nor employed extensively in practice.Īs usual, the really important questions you want to ask are: I think BPMN may have some use in companies that have very formal approach to writing specifications, the same kind that would use UML for describing every aspect of simple cancel button.
0 kommentar(er)
