Ploymorphism for IT Business Analysts

[jeshaw2]

To what extent do you think that an IT Business Systems or Requirements Analyst, working at the CIM/PIM level of the MDA, needs to understand all the various forms of polymorphism?  I'm putting together a quick overview of the O-O paradigm to prep them for learning the UML.

[peter.zrnko]

I think it will be good if he/she is able to recognize similarities between classes in domain model (CIM) and point to them (either as inheritens connections in diagrams or in comments).

[jeshaw2]

I agree with Peter.  I am planning to cover the Inclusion forms of polymorphism Sub typing, Duck Typing, and possibly even Dependency Injection.  What I'm not sure about are the Attribute forms: Coercion, Overloading, and Generics.  I think I can build a case for including Overloading, but I'm open to the thoughts of others on this.

I'm thinking that if a BA gets involved with Attribute polymorphism, he/she is getting too bogged down with technology at the expense of articulating the needs of the business.

[thomaskilian]

I think that a BA should bridge between business and technics. Thus he/she should be aware of IT implications.

[jeshaw2]

Point well taken Thomas, and I do agree with you.