[Sigia-l] Meaning of "unified development methodologies"

[eryk "eof" or ł owski]

On 13-05-05 13:39, "Jonathan Baker-Bates" <Jonathan.Baker-Bates at oyster.com>
wrote:

> 
> Are you saying you're using the UML to create ontologies?  Wow. What
> does this look like? Are you drawing diagrams that show things like the
> word 'purchase' extends 'widget buying' which inherits 'revenue
> generation' or something?
> 

Well, uml is a tool of object oriented methodology, which means "consumer"
would be an object, related to the other objects, like "account" (ownership
relation). Consumer can perform certain actions on the account, using
account's methods ("check the saldo"), etc. Starting from top level business
conceptual model You can end with defining a specification document for
programmers team.

> This sounds incredibly cool - but I would think that having to explain
> the UML to other (non technical) every time you show them diagrams might
> be a bit of a downer.
> 

Non technical parts, like the customer, receive only a top level domain
model, sometimes with use case diagrams & textual descriptions. When You
receive a simple diagram with detailed description, You do not have to be a
business analyst to get the point. Besides, why not educate customers? ;-)

Btw, last week I have seen a business procedure used in an international
environment, defined in UML standard, and it wasn't prepared for computer
geeks...

-- 
eryk "eof" orłowski || gg# 2765 || email/msn: eofek[at]nospam.hotmail.com